The quiet cost of context switching in a five-person team
Sample essay on why small teams lose more time to fragmentation than to any single bad decision, and what to do about it.
Placeholder content included with the FoundryLume theme.
At five people, everyone does four jobs. That is not a problem to be solved — it is the shape of the stage. The problem is that the four jobs interleave badly, and nobody notices the cost because it never shows up as a missed deadline. It shows up as a quarter that felt busy and moved nothing.
Fragmentation, not workload
The founders we talk to are rarely working too few hours. They are working hours cut into eleven-minute pieces.
A useful diagnostic: at the end of the week, write down the longest uninterrupted stretch you spent on your most important bet. If it is under ninety minutes, the calendar is the problem, not the plan.
Three changes that cost nothing
Batch the interrupts. Two fixed windows a day for everything asynchronous. Not a policy — just a default that the team can break when it matters.
One shared “now” line. A single sentence at the top of your workspace naming the current priority. When someone asks “should I do X or Y”, the line answers it without a meeting.
Kill the status meeting, keep the decision meeting. Status is a document. Decisions need a room. Conflating the two turns thirty minutes of judgement into an hour of narration.
The counterintuitive part
Small teams tend to respond to fragmentation by adding process. Usually the opposite works better: remove one recurring meeting and see if anything actually breaks.
In most cases nothing does, and you have bought back four hours a month per person — which at five people is most of a working week.
When to stop optimising
There is a point where focus work becomes procrastination with a nicer name. If you have spent more than a day this quarter designing your workflow, the workflow is not the bottleneck.