"Capacity planning in most businesses means HR headcount modelling. That is not what teams need. They need to know whether the work assigned this week can actually be done — before the week starts."
What Capacity Planning Actually Means in Execution
When most people hear "capacity planning," they think of HR — headcount forecasts, hiring plans, resource allocation at a strategic level. That kind of planning is important, but it operates months ahead of the moment it matters.
Execution-level capacity planning is different. It answers a more immediate question: do the people on this team have enough available time and focus to complete the work they have been assigned — this sprint, this week, this day?
Without visibility into that question, managers are operating blind. They assign work based on role, not reality. They schedule Milestones without knowing whether the team has the bandwidth to hit them. And they discover overload not through data, but through the symptoms: slipping deadlines, declining quality, exhausted team members.
Task-based capacity planning changes that. It grounds workload management in the actual units of work being executed — tasks — rather than in theoretical availability. And it surfaces imbalances while there is still time to act.
Why Task Lists Are Not Capacity Visibility
Many businesses have task management tools. Virtually none have capacity visibility. The two are not the same thing.
A task list tells you what needs to be done. It does not tell you whether one person has 40 tasks assigned while another has 8. It does not flag when the total estimated effort across a team's task list exceeds the hours available in a sprint. It does not indicate that a particular Milestone is at risk because two key contributors are already at full capacity.
The Visibility Gap
What task lists show
- ✗ Who is assigned to what
- ✗ Task status (open / complete)
- ✗ Due dates
What capacity planning requires
- ✓ Total effort per person vs available hours
- ✓ Load distribution across the team
- ✓ Risk signal before deadlines slip
The absence of this visibility is why well-intentioned managers consistently over-assign work. Not because they do not care about their team's wellbeing — but because the information they need to make balanced decisions simply does not exist in the tools they are using.
The Ripple as a Daily Capacity Signal
In the 1:90 Align framework, the daily standup is called the Ripple. It is not a status update. It is a capacity signal.
The Ripple asks each team member three questions:
What did you complete yesterday?
Confirms actual throughput — not just stated progress.
What are you focused on today?
Creates shared visibility into where capacity is being spent.
Is anything blocking you?
The most important question — surfaces capacity constraints before they become delivery failures.
Done consistently, the Ripple gives managers a live picture of where their team's capacity is going, where it is constrained, and where redistribution is needed. It converts a daily meeting from a performance theatre ritual into a genuine management tool.
The Ripple does not require complex tooling. It requires discipline — and a framework that gives it meaning by connecting daily tasks to the Milestones and Waves above them.
How Milestones Reveal Bottlenecks Before They Escalate
In the 1:90 Align framework, Milestones are the weekly checkpoints within each 30-day Wave. They serve as the early warning system for capacity problems.
When a Milestone is at risk of being missed, one of two things is usually true: the task was too large and needed to be broken down, or the person responsible did not have sufficient capacity to complete it within the sprint.
Weekly Milestone reviews — structured into the rhythm of every Wave — give managers the opportunity to catch either problem at the checkpoint stage, not at the deadline. A missed Milestone in week two of a Wave is recoverable. A missed Arc goal at the end of 90 days is not.
The Milestone Rhythm
Milestone 1
First checkpoint. Are tasks on track? Is capacity distributed correctly?
Milestone 2
Midpoint signal. Bottlenecks identified early enough to resolve.
Milestones 3 & 4
Final sprint. Capacity should be well-understood. Delivery predictable.
This weekly cadence transforms capacity planning from a theoretical exercise into a live operational discipline. Every manager running the 1:90 Align system knows, at any point in a Wave, whether their team is on track — and whether the load is sustainable.
Practical Steps to Implement Capacity Planning Using the 1:90 Framework
You do not need to overhaul your tools or your team to begin. The 1:90 Align approach to capacity planning can be implemented within a single 30-day Wave.
Define Your Wave Arcs and Break Them into Milestones
Before the Wave begins, set the 30-day goal (Arc) and break it into four weekly Milestones. Each Milestone should have clear ownership and a defined output — not just "progress on X" but a specific, verifiable deliverable.
Assign Tasks With Effort Estimates
When tasks are created within a Milestone, assign an effort estimate (hours or story points — pick one and be consistent). The total across an individual's tasks in a week should not exceed their realistic available hours. If it does, redistribute or descope before the week starts.
Run the Daily Ripple as a Capacity Check
The Ripple is not a reporting exercise — it is a capacity management tool. When a team member flags a blocker, the manager's job is not to note it and move on. It is to resolve it or redistribute the load. Every unresolved blocker is a capacity leak.
Review Load Distribution at Each Milestone
At the weekly Milestone review, look at task completion rates by person. Consistent under-delivery from one individual is often a capacity signal, not a performance signal. Is the right amount of work assigned? Is there a recurring blocker? Is this person absorbing reactive work that is not captured in their task list?
Run a Wave Retrospective on Capacity Accuracy
At the end of each Wave, measure planned effort against actual delivery. Where was the team consistently over-capacity? Under-capacity? Use that data to improve estimates and load distribution in the next Wave. Over three or four cycles, capacity planning accuracy improves dramatically.
Key Takeaways
-
Capacity planning in execution is not headcount modelling — it is real-time visibility into whether the work assigned can actually be done.
-
Task lists show what needs doing. They do not show whether the team has capacity to do it. That gap is where burnout and missed deadlines originate.
-
The Ripple (daily standup) is a live capacity signal when run correctly — surfacing blockers and load imbalances before they become delivery failures.
-
Milestones provide the weekly checkpoints that allow managers to catch capacity problems at the sprint level — not at the quarterly deadline.
-
Capacity planning accuracy improves with each Wave cycle — it is a discipline built over time, not a one-off exercise.