Paul Graham’s maker schedule versus manager schedule idea has survived because it describes something people feel in their bones. Makers need long, uninterrupted blocks to get into real work. Managers can often move in hour-long chunks without much penalty. The standup is one of the most reliable ways to force the manager’s schedule onto the maker’s morning.
Why the timing matters
A ten-minute interruption at 10:00 is not a ten-minute interruption. It prevents a developer from starting something meaningful at 9:15 because the brain knows it will be pulled out soon. Then it leaves residue afterward while the person tries to climb back into the work. The calendar says fifteen minutes. The day experiences far more.
Why teams keep doing it
Because the standup is optimized for managerial convenience. Everyone gets one pulse point. Everyone is present. The information arrives on schedule. That is useful for coordination, but it comes at the precise moment most makers need protection.
A lot of teams accept this tradeoff because they think the cost is unavoidable. It is not. It is just familiar.
The better answer
If the work is visible by default, you do not need to interrupt every maker just to gather status in one place. People can read updates when they need them. Live conversation can happen when there is actual disagreement or ambiguity worth paying the interruption cost for.
Every standup violates the maker’s schedule because it treats visibility as something that must be extracted synchronously. Build a system where visibility already exists and the violation becomes unnecessary.