Picture Priya, a leader on a growing team, trying to keep the week from slipping.
Caleb has been steady for months. He closes the customer follow-ups, keeps the handoff notes clean, and catches the small details that make the next person’s work easier. Then a more complicated issue lands in the queue. The customer wants an exception, the answer is not obvious, and Priya is under pressure.
So she moves the work to the expert.
It is the right move that day. The issue needs judgment. But after the same pattern repeats a few more times, Caleb learns something the org chart never says out loud. Solid execution matters, but the contribution that seems to earn real trust is expertise.
That is how organizations quietly teach people to chase the same ladder. A person starts as a beginner, becomes reliable, becomes an expert, and eventually becomes a leader. That story is partly true, but it is too narrow.
Healthy organizations are not built by moving everyone toward the same destination. They are built by maintaining the right mix of capabilities.
Some people create value by executing work with discipline. Some create value by becoming more reliable over time. Some create value by solving hard problems. Some improve the system itself. Some multiply capability in others.
Those are not the same contribution, and they should not be treated like they are.
The Capability Mix Model is a way to understand the different kinds of value people create inside an organization and the risks that appear when one kind of capability is missing, overused, or misunderstood.
The Big Principle
Priya’s mistake is not trusting the expert. Experts are valuable. Every team needs people who can diagnose problems, make judgment calls, and solve complex work quickly.
The mistake is letting expertise become the only contribution that looks like advancement.
When too much knowledge and too many decisions sit with too few people, Experts become bottlenecks. The team becomes dependent on heroic problem-solvers instead of building broader capability.
A second mistake sits on the other side of the same problem: assuming everyone should eventually become a Multiplier. Multipliers are valuable too. They develop people, transfer standards, and help the organization grow beyond individual talent. But a healthy organization does not need everyone doing the same kind of leadership work.
It still needs people who execute, people who learn, people who solve, people who improve systems, and people who develop others.
The goal is not a taller ladder. The goal is balance.
There is a reason this matters beyond morale. Organizational capability is not just the sum of individual talent. It depends on how well specialized knowledge gets integrated across people, roles, routines, and decisions.
When the mix is off, the business begins to lean too hard in one direction. It may become too dependent on a few people, too heavy with process, too thin on execution, or too weak in developing future talent.
You can hear the difference in the promise each role makes:
- Technicians produce work.
- Apprentices build reliable capability.
- Experts produce solutions.
- Masters improve systems.
- Multipliers produce greater capability in others.
1. The Technician
The Technician is task-capable. They know the steps, tools, and basic requirements of the work. Their value is tied directly to individual effort and disciplined execution.
This contribution can look ordinary, which is why leaders can undername it. But ordinary execution is the foundation of operational trust. If the basic work is inconsistent, everything above it becomes harder to manage.
The Technician’s output is usually one-to-one: one hour of work generally produces one hour of value. The development focus is accuracy, discipline, repeatability, and baseline competence.
The key question is: Can this person do the work correctly?
When this role is weak, quality varies, expectations have to be repeated, and managers spend too much time correcting avoidable misses.
2. The Apprentice
The Apprentice is developing reliable capability. They are learning not only how to do the work, but why the work is done a certain way. Their value is tied to growth, teachability, pattern recognition, and increasing consistency.
Apprentices still create mostly one-to-one output, but the quality of that output improves over time. They need fewer corrections. They notice patterns faster. They begin to understand the standard instead of merely following instructions.
This is one reason the mix matters. The configuration of people inside a team shapes how teams think, behave, relate, and perform. Capability is not only an individual trait. It is also a design question.
For a leader, the development focus is feedback, humility, pattern recognition, standards, and dependable execution. The key question is: Can this person do the work reliably and keep improving?
When this role is weak, the talent pipeline gets thin. The organization may have workers, but not enough people becoming more capable with time.
3. The Expert
The Expert is problem-capable. Experts understand the work deeply enough to diagnose issues, make decisions, and solve problems that others cannot easily solve.
This is the person Priya reaches for when the customer exception gets complicated. Their value is tied to judgment, speed, quality, complexity, and decision-making. One hour of Expert work can produce two or three hours of value because it reduces rework, accelerates decisions, prevents mistakes, and helps others move faster.
Experts are easy to admire because their value is visible. They save the day. They know the answer. They can carry a complex issue when others are stuck.
But if the organization depends on Experts for every hard decision, the strength becomes a bottleneck. People wait. Problems queue up. The Expert becomes a hero contributor, and the system becomes fragile.
The development focus is problem-solving, ownership, decision-making, prioritization, and cross-functional understanding. This is also where clear decision rights matter. Without them, accountability becomes muddy, which is why decision authority and accountability need to develop together.
The key question is: Can this person solve the problem, not just complete the task?
4. The Master
The Master is system-capable. Masters do not simply perform the work at a high level; they improve how the work is done.
Their value is tied to making performance more repeatable, efficient, measurable, and scalable. They strengthen standards, reduce waste, improve quality, increase throughput, and build processes that make good work easier to repeat.
This is a different kind of contribution from expertise. Experts often solve the problem in front of them. Masters ask why the same problem keeps appearing. They improve the system so fewer people have to solve the same issue over and over again.
This is the useful side of process. Some systems help people master the work while others merely control compliance. Masters build the first kind.
For a leader, the development focus is systems thinking, process improvement, standards, measurement, coaching, and operational judgment. The key question is: Can this person make the system better?
When this role is missing, the team repeats the same inefficiencies. It may have talented people, but talent keeps getting spent on problems the system should have prevented.
5. The Multiplier
The Multiplier is capability-capable. Multipliers develop people, transfer knowledge, strengthen standards, and create conditions where others can perform with greater confidence and competence.
Their value is tied to expanding capability beyond themselves. A Multiplier reduces dependency on a few key people. They document what matters, delegate without abandoning, coach without creating dependence, and make others stronger without needing to remain the center of the work.
This is not the same as being helpful. A helpful person may answer the question. A Multiplier helps someone become more capable of answering the next one.
The development focus is mentorship, delegation, documentation, communication, leadership development, and culture-building. The key question is: Can this person help others become more capable without making them dependent?
When this role is missing, capability gets trapped. The organization may have strong individuals, but the strength does not spread.
The Shadow Leadership Track
Leadership develops alongside every stage of capability. It does not begin only when someone becomes a manager.
Technicians can lead through discipline and ownership. Apprentices can lead through humility and coachability. Experts can lead through judgment and peer influence. Masters can lead through systems and standards. Multipliers can lead through development and delegation.
Leadership can be distributed across team members rather than concentrated only in a formal leader. In practical terms, leadership shows up whenever someone strengthens the team’s ability to think, act, decide, or improve.
That matters because organizations often confuse leadership with title. Leadership value can appear long before someone owns a department or manages a team. The question is not only, “Who is in charge?” The better question is, “How is this person creating strength around them?”
This is also why a healthy operating rhythm matters. Without clear rhythms for priorities, decisions, feedback, and follow-through, capability stays harder to see and harder to develop.
When The Mix Is Off
The most useful question is not, “Who is underperforming?” It is, “What kind of capability is the work asking for, and which kind is missing, overloaded, or trapped in one person?”
That question keeps the framework from becoming a personality sorter. The point is not to label people. The point is to read the work.
A Grid For Reading The Mix
Use the grid as a hypothesis tool. Start with the pattern you can observe, look for the capability the work may be asking for, then test that read before deciding whether the answer is training, clearer standards, better systems, or stronger delegation.
This keeps the framework practical. You are not asking, “What type is this person?” You are asking, “What capability does this work need more of right now?”
That small change protects the people and the work. Caleb may not need to become the expert. He may need clearer standards, more practice, a better system, or a leader willing to let judgment develop instead of quietly rerouting every hard moment away from him.
Do not start with promotion plans or generic training. Start with the work the organization needs to perform well, then ask which capabilities are required to support that work.
The right mix depends on the industry, team size, growth stage, complexity, and operating model. A small team may need people to carry more than one capability. A larger team may need clearer distinction between roles. A scaling company may need to move knowledge out of individual Experts and into systems, standards, and people development.
The point is not to label people permanently. The point is to understand how value is being created and where the system is becoming unbalanced.
The Leadership Responsibility
Leaders are responsible for more than identifying talent. They are responsible for building the conditions where the right mix of talent can produce durable performance.
That means respecting skilled execution, developing reliable capability, protecting deep expertise from becoming a bottleneck, improving systems, and multiplying capability through others.
Healthy organizations do not ask everyone to become the same kind of contributor. They learn what kind of contribution is needed, where it is missing, and how to strengthen the whole mix.
That is capability leadership: not turning everyone into an expert, but keeping every valuable form of contribution visible, developed, and connected to the work.
The goal is not to make everyone the same. The goal is to make the whole system stronger.
Sources
- Grant, R. M. (1996). Prospering in dynamically-competitive environments: Organizational capability as knowledge integration. Organization Science, 7(4), 375-387. doi:10.1287/orsc.7.4.375
- Adler, P. S., & Borys, B. (1996). Two types of bureaucracy: Enabling and coercive. Administrative Science Quarterly, 41(1), 61-89. doi:10.2307/2393986
- Bell, S. T., Brown, S. G., Colaneri, A., & Outland, N. (2018). Team composition and the ABCs of teamwork. American Psychologist, 73(4), 349-362. doi:10.1037/amp0000305
- Carson, J. B., Tesluk, P. E., & Marrone, J. A. (2007). Shared leadership in teams: An investigation of antecedent conditions and performance. Academy of Management Journal, 50(5), 1217-1234. doi:10.5465/amj.2007.20159921