Capacity
The realistic amount of work that can be delivered in a period.
How much you can actually take on.
What It Is
Capacity belongs to Execution, specifically the Engagement part of it. The working definition is simple: the realistic amount of work that can be delivered in a period.
It is an idea you reason with rather than a deliverable you hand over, so two teams can both hold it correctly and still apply it differently. Used with that meaning, it stays a working tool rather than a talking point.
How It's Used
Capacity comes up in project delivery, scheduling and the handover between people doing the work. In real work it sits close to Bottleneck, Workflow and Retainer. The practical test is whether a decision changes because of it.
Why It Matters
Getting Capacity wrong is expensive in a quiet way. When it is unclear, work still happens — it just happens twice. Deciding it deliberately costs one conversation. Leaving it undecided costs several.
It is an idea that changes what you decide, not an item you tick off. How much you can actually take on.
Termshift™
How the meaning shifts depending on who is using it, and where.
Inside the industry, Capacity is used tightly and assumed to be understood: the realistic amount of work that can be delivered in a period.
Away from the jargon, it is how much you can actually take on.
The Bottom Line
The practical takeaway on Capacity: how much you can actually take on. Judge it by that, not by how it sounds.