Sometimes a team looks “stacked” on paper and still struggles in real life. Projects start strong, then stall. Meetings multiply. Decisions get kicked upstairs. People work harder, but the work doesn’t get clearer. Often, that’s not because people don’t care. It’s because the organization is mixing up three different things: Ability, Capability, and Capacity—the Domains of Competence.
Domains Of Competence: The Plain-English Idea
Think of the Domains of Competence like three different questions:
Ability: Can you do the work well right now?
Capability: Can you handle messy, uncertain problems and make good calls over time?
Capacity: How much of this work can you take on, and how far can it spread, without falling apart?
When leaders mix these up, they hire the wrong person, promote too fast, or try to scale before the system can carry the load.
Ability
Ability is your “do it today” skill. It’s the practical know-how to perform tasks effectively in a role right now. You can see it in reliable execution and consistent quality.
If a job is clear and repeatable, Ability is often the main thing that matters. Training, coaching, and practice are usually the right answers when Ability is the gap.
Capability
Capability is about judgment when things aren’t clear. It’s the power to handle complexity through sense-making and decision-making across time—especially when the path isn’t obvious.
A person can be excellent at today’s work and still struggle when the job changes from “do the task” to “figure out what the task should be.” That’s a Capability challenge, not an effort problem.
Capacity
Capacity is how far and how widely Ability and Capability can be applied without losing quality and alignment. It’s not just “more people” or “more hours.” It’s whether the organization’s setup—roles, decision rights, communication, and routines—can carry the work at a bigger scale.
If things fall apart every time you grow, that’s often a Capacity issue: the system can’t reliably carry the load yet.
A Quick Way To Tell Which One You Need
If the problem is “we can’t do the work well today,” start with Ability.
If the problem is “the situation keeps changing and we’re not making good calls,” start with Capability.
If the problem is “we’re growing and everything is getting messy,” start with Capacity.
A Real-World Situation
Imagine a customer support organization that just launched a new product. Complaints are rising, and the team is overwhelmed. The leader’s first instinct is to hire ten more agents.
Before hiring, use the Domains of Competence to diagnose the real constraint.
First, check Ability. Are agents trained on the new product? Do they know the steps to troubleshoot common issues? If not, hiring more people just spreads confusion faster. The fix is clear training, practice, and tighter feedback loops.
Next, check Capability. Are the issues new and unclear, with no simple script? If agents keep escalating because nobody can make sense of the patterns, the team needs stronger judgment at the right level—someone who can spot trends, name trade-offs, and decide what to fix first. That’s Capability: making good calls under uncertainty over weeks and months, not just following today’s process.
Then, check Capacity. Let’s say training is fine and the team has good judgment, but the organization keeps breaking anyway. Escalations bounce between support, product, and engineering. Nobody owns decisions end-to-end. Updates don’t travel. Customers get different answers depending on who they talk to. That’s a Capacity problem: the system isn’t built to carry quality and alignment across teams at this scale. The fix is to redesign how work moves—clear owners, clear handoffs, clear decision rights—so judgment and standards travel reliably.
In this example, hiring ten agents only helps if Capacity can carry them and Capability can guide the work. Otherwise, headcount becomes expensive noise.
How To Use It This Week
Pick one initiative that matters and ask three questions:
What must be executed well today (Ability)?
What calls require judgment under uncertainty over time (Capability)?
What must be true in our setup so the work scales without chaos (Capacity)?
When those three answers line up, staffing gets easier, promotions get safer, and scaling gets less painful.
Final Thoughts
- Name the domain before you prescribe the fix: Ability is present-tense skill, Capability is judgment under complexity across horizons, and Capacity is the reach and scale at which both can be applied while preserving coherence.
- Treat Domains of Competence as a system: raising one domain while neglecting the others simply relocates the bottleneck.
- Use DOES as an operating practice: Design elevates Capability, Organize extends Capacity, Execute expresses Ability, and Sustain renews all three.
- Anchor role decisions in time span: as time horizons expand, Capability becomes the primary limiter of strategic altitude, and Capacity becomes the limiter of coherent scale.
FAQ’s
How are the Domains of Competence different from “skills” or “competencies”?
The Domains of Competence separate present execution (Ability), judgment under complexity across time (Capability), and scalable reach without loss of coherence (Capacity). Skills typically describe the first domain but often blur the other two.
Why do promotions fail when performance is strong?
Because strong present performance may indicate Ability, while the new role may require higher Capability—longer-horizon judgment, framing, and trade-offs under uncertainty.
Is Capacity just headcount or bandwidth?
No. Capacity includes design elements—structures, decision rights, governance routines, communication channels, and cultural norms—that allow intent and standards to travel through the system without degrading.
How does the DOES Leadership Model connect to the Domains of Competence?
DOES operationalizes them: Design raises Capability, Organize extends Capacity, Execute expresses Ability, and Sustain renews all three so performance and coherence can hold over time.
If you want the full diagnostic method, including sample role questions and a simple way to map initiatives to Ability, Capability, and Capacity, read the complete article and apply it to your next leadership or talent review.
