Leaders learn they have exceeded capacity from turnover, slipped deadlines, and lost clients, long after the unplanned work that caused it was quietly absorbed.
A grid built for the work they actually had
The leadership team of a healthcare technology company gathered around a shared whiteboard. Down the left side ran five rows, one for each condition work can arrive in: planned, unplanned, emergent, modified, and cancelled. Across the top ran a set of questions. How does each kind of work arrive, and from where? How much capacity does it consume? Is there a tool anyone can see it in? How is capacity being calculated? How long does the work take? What tells you capacity has been exceeded? How does the team actually handle it?
We opened with the premise the grid was built to test. An intake process designed only for planned work will fall apart when conditions change, and delivery teams meet unplanned, emergent, changed, or deferred work with no idea what to do with it.
Planned was the easy row
Planned work filled quickly. It lived in roadmaps, quarterly business reviews, and the delivery board, written down somewhere a leader could find it. One of the quieter leaders pushed back even there: planned was not planned the same way across teams, because different groups ran different tools and different cadences. We asked the room to hold that thought and keep building the picture.
Unplanned work arrived through chat channels, phone calls, and client portals. Bug reports. Client escalations. One leader said that the minute a client raised something, his team dropped what it was doing, and that the work was never counted against capacity. It was simply absorbed.
Then we asked for percentages, and for honesty: not what the split should be, what it actually was. The estimates did not agree. One leader put planned work at sixty percent of his group's capacity. Another said thirty. A third split the difference at fifty. The leader closest to clients said thirty, then corrected himself to maybe twenty-five. When we averaged every estimate in the room, planned work landed at forty-three percent.
The room went quiet enough to hear people doing arithmetic. One leader said it out loud: more than half of the work they did every week was work their intake process had never been designed for.
- about 43%Planned
- about 38%Unplanned
- about 10%Emergent
- about 7%Changed or modified
- about 2%Cancelled or deferred
Capacity discovered after the fact
The next columns explained why the number had surprised them. Planned work was mostly visible in a tool. Unplanned work showed up there only sometimes, and only after the conversation that created it. Emergent work almost never did. As one leader put it, emergent work lived in someone's head until it became a fire, then in a chat thread until someone wrote a ticket, and by the time it reached the board it was no longer emergent. It was late. Changed work had its own lag: a decision made in a short executive call reached the team by forwarded email days later, after capacity had already been committed to the thing it replaced.
When we asked how capacity was calculated, people looked away. Gut sense, one said. Story points sometimes, recall mostly, said another. The most direct answer was that nobody calculated capacity for unplanned work at all. They discovered they had run out of it, after the fact. We wrote one line on a sticky note and put it at the top of the column: intuition is not a measurement system. Nobody argued.
The question about warning signs produced the most uncomfortable list of the day: staff turnover, slipped deadlines, sprint rollover, client churn. One leader named the problem with the last one. By the time a client leaves, the capacity was exceeded months earlier, yet the organization was using churn as its early warning. It was managing capacity by reacting to its injuries.

One front door, five paths behind it
We zoomed out on the full board and asked the only question left. Could their intake process hold all five conditions without forcing them to pretend to be planned work? The answers came quickly. It could not, not the way it was built. Then redesign it for the work they actually had, not the work they wished they had. The quietest leader in the room made the point that ended the debate: they had been running a planned-work intake process when less than half of their work was planned, so of course they kept missing.
Over the following weeks we worked with the leadership team to rebuild intake around that reality. Everything still came through one front door, but each condition got its own path behind it.
| Before | After | |
|---|---|---|
| Planned | Roadmaps and the board | Structured intake and ranking |
| Unplanned | Absorbed, never counted | Enters fast, stays visible |
| Emergent | In a head, then a fire | Clear path when truly urgent |
| Changed | Forwarded email, days late | Returns for reassessment |
| Cancelled | Stops being discussed | Formal path releases capacity |
Showing the work instead of absorbing it
A few weeks after the new process went live, we joined the leadership team for a check-in. The leader who had first admitted to estimating by gut sense said the unplanned path was what he valued most. His group used to absorb that work invisibly. Now he could see how much of it they were carrying, and he could show other leaders why a planned commitment had slipped.
Another leader said the emergent path had surprised him. When something was genuinely urgent, the route was clear. When something only felt urgent, the process caught it before it could knock a team off its plan. A third had not expected to use the cancelled path at all, then used it that same week to formally retire several backlog items that had felt urgent at the start of the year and no longer mattered.
The forty-three percent was an estimate, not a measurement. Its job was to make the room willing to change, and it did. The workshop also exposed something it did not solve: nobody could agree how long emergent work took, with estimates ranging from a day to three weeks. We noted it as a separate problem to take on later. What had changed was where the cost showed up. Unplanned work was now seen when it arrived, not discovered months later in turnover or a lost client.
If the intake process only knows how to receive planned work, every other kind of work will be paid for in capacity you never agreed to spend.
Share With Your Team
Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.


