You have 3 people on the team. You run Scrum-style coordination sized for 10.
Daily standups: 15 minutes × 3 people × 5 days = 3.75 person-hours per week. Sprint planning: 2 hours × 3 people = 6 person-hours per sprint. Retros: 1 hour × 3 people = 3 person-hours per sprint. Backlog grooming: 1 hour × 3 people = 3 person-hours per sprint.
That's 15+ person-hours per two-week sprint. On a 3-person team with maybe 120 available person-hours, coordination overhead is 12%+ of capacity.
And for what? Three people who could just talk when they need to.
The Origin of Coordination Overhead
These practices emerged for larger teams:
- Daily standups: Synchronize 8 people who might otherwise work in isolation
- Sprint planning: Align many contributors on shared work
- Retros: Surface issues across a team too large for informal feedback
- Grooming: Coordinate complex backlog across specialists
At scale, the overhead is worth it. Coordination problems at scale are real.
But the practices got applied universally. Small teams run the same ceremonies, justified by habit rather than need.
The AI Team Reality
AI-native teams are often small. Two or three people accomplish what larger teams once did.
Small teams don't need large-team coordination:
- **Three people can just talk.** You don't need scheduled standups to know what each other is doing.
- **Priorities are obvious.** You don't need formal sprint planning to decide what to work on next.
- **Feedback is continuous.** You don't need retros to know what's working and what isn't.
The coordination infrastructure is overhead, not value.
The Signs
You might have excessive coordination overhead if:
- Meeting time rivals work time
- Ceremonies feel performative
- The same information gets shared multiple times through different ceremonies
- You'd move faster if you just... talked when needed
- Coordination is about satisfying process, not actual synchronization need
The Right Size
Match coordination to actual need:
**2-3 person team:** - Talk when needed - Async updates for what doesn't need sync - Weekly check-in for bigger picture - No daily standups, no formal ceremonies
**4-6 person team:** - Maybe weekly sync - Light coordination practices - Async by default, sync when needed
**7+ person team:** - Probably need some ceremony - But still question each element: is this earning its cost?
The Transition
If you're running heavy coordination on a small team:
1. List all recurring coordination activities 2. Estimate time cost for each 3. For each, ask: what problem does this solve for our specific team? 4. Cut what doesn't solve a real problem 5. Replace with lighter alternatives where needed
The goal isn't no coordination. It's right-sized coordination.