By Enrique Tasatooling, notion, standup

Why the Notion standup template quietly breaks at 10 people

A Notion database for your weekly standup works for a while. Then the team grows, the template gets in the way, and one Sunday you find yourself rebuilding it.

Almost every small team I have talked to started their weekly standup in Notion. Good reasons: Notion is free, flexible, and already open on everyone's laptop. Bad reason: a weekly rhythm is not a document problem.

The honest version of this post: Notion works. For a while. Then it breaks in three specific ways. It is worth knowing the shape of the break before you hit it.

What typically gets built

The default Notion weekly standup looks like this:

  • A database called "Weeks" with columns for focus, goals, status, owner.
  • A template page with a heading for each teammate.
  • A rollover reminder in someone's Apple Reminders.

It is a good enough first draft. It is also the thing that breaks.

Where it breaks

1. Rollover becomes manual.

On week four, last week's unfinished goals have to be copied into this week's page. At first the team lead does it on Sunday. By week eight it is getting skipped. By week twelve the Friday review says "carry over" next to three items that nobody ever carried over.

A weekly rhythm that forgets last week has a credibility problem. The team notices.

2. Ownership drifts.

Notion lets you have a "Owner" property, which is a relation to People. In practice, team leads put names in free text instead, because the relation dance is annoying when you are writing fast on Monday. By week six the goals on the page look owned. They are not.

3. The template becomes the product.

Every Sunday evening, the team lead opens Notion and thinks "the goal structure should really be nested under a theme." Or "maybe blockers should be a database of their own." Or "I should add a retrospective view per quarter."

This is not wasted work. It is exactly the right instinct. The problem is that now the team lead's Sunday evening is spent building the tool, not running the team.

What this tells you

When a Notion template stops working, the temptation is to invest more — a better template, a dashboard, a database of databases. That investment is real money in time, and it does not fix the underlying thing: the weekly rhythm is a product, not a document.

Purpose-built weekly tools (ours included) are not trying to replace Notion for docs. Keep Notion for wikis, specs, meeting notes, product requirements. The weekly rhythm is a narrow, opinionated product that should do three specific things well:

  • Run Mon/Wed/Fri without your Sunday evening.
  • Roll over unfinished work automatically.
  • Keep ownership as a first-class field, not a free-text habit.

When Notion is the right answer

If your team is 3 to 5 people, in one timezone, and everyone has a habit of weekly updates, a Notion template is more than enough. You do not need a new tool.

If you are growing past ten, writing more than you read on Sunday nights, or noticing that the template is getting in the way of the rhythm, that is the signal. The rhythm is working. The tool is not.