Capability by Assumption

The question rarely sounds difficult.

Who is capable of doing this work?

An executive asks it while considering a new appointment, a transformation, a market entry, or a problem that has suddenly become urgent. Names arrive quickly. This person has done something similar before. That person has the right qualification. Another has been with the organization long enough to understand how things really work. Someone else is the obvious choice because she is already performing well.

Within minutes, the organization appears to know where its capability resides.

The speed is not surprising. Leaders make judgments about capability constantly. They decide whom to recruit, promote, trust, develop, deploy, or place in succession. They decide whether a team is ready to absorb new technology, whether a function can take on greater authority, and whether the workforce can deliver a strategy that exists, for now, only in a plan. Management would become impossible if every such decision had to begin from complete uncertainty.

Nor are these judgments arbitrary. Qualifications do reveal something. Experience matters. Performance deserves attention. Managers often know far more about their people than any enterprise system could capture. The familiar signals persist because they contain information and because, under familiar conditions, they often lead to acceptable decisions.

But notice what has happened between the question and the answer. The question concerned capability. The answer consisted of things associated with capability.

The distinction is easy to miss because most organizations possess an extraordinary amount of information about their people. They know employment history, tenure, job level, completed learning, performance ratings, career aspirations, compensation, credentials, and sometimes self-reported skills. They can identify high potentials, critical roles, successor coverage, and populations considered ready for deployment. The sophistication of these systems creates a reassuring impression: if so much is known about the workforce, capability must be among the things that are known.

Usually, it is not.

The systems describe people and the administrative judgments surrounding them. They rarely establish what a particular body of work will demand, or demonstrate that the organization can meet that demand under the conditions in which performance will matter. Capability supply is inferred from the data available. Because the inference is familiar, it is experienced as knowledge.

This is capability by assumption.

The assumption does not begin with bad information. It begins when valid information is asked to support a conclusion it cannot support on its own. A qualification may demonstrate that someone met a defined standard. It does not establish that the person can apply the relevant knowledge to a novel problem in a particular organization. Experience shows exposure to work over time. It does not reveal the variety of conditions encountered, the quality of feedback received, or whether repeated exposure produced deeper judgment. Ten years can represent accumulated mastery, but it can also represent the repetition of conditions that are about to disappear.

Performance seems more convincing because it records results rather than background. Yet results emerge from more than capability. They also reflect resources, systems, authority, leadership, market conditions, the difficulty of the assignment, and the unrecorded intervention of other people. A team may perform well because one expert quietly handles every consequential exception. The result is real. The capability implied by the result may be dangerously concentrated.

Performance ratings increase the distance. They compress outcomes, behaviors, expectations, opportunity, and managerial judgment into a label that travels easily through the organization. Once detached from the conditions that produced it, a strong rating can become evidence that someone is ready for different work. The organization believes it is carrying performance forward. It may be carrying forward only a conclusion reached in another context.

Promotion is where this substitution becomes particularly visible. A person succeeds in one role and is selected for a larger one. The decision is reasonable, often deserved, and still rests on an untested claim. The new role does not merely require more of the old capability. It may change the nature of the work from solving problems to creating the conditions in which others can solve them, from applying standards to resolving conflicts among standards, or from making decisions directly to governing decisions made elsewhere. Past performance supports confidence. It cannot demonstrate capability in work the person has not yet performed.

Succession systems formalize the same leap. A candidate is designated ready now or ready later, as though readiness were a stable property held by the individual. But readiness has no meaning apart from the work. Change the strategy, operating model, technology, or risk environment and the role itself changes. The successor has not become less talented. The capability demand has moved while the label remained still.

Learning creates another form of reassurance. Completion is visible, countable, and easy to govern. It shows that an employee reached the end of an activity and, depending on the design, may show understanding or performance in a controlled exercise. It does not show that work has changed. The employee may lack the authority to apply what was learned, encounter systems that reward the old behavior, or return to a team whose managers interpret the standard differently. A completed program is evidence of participation. Treating it as evidence of organizational capability turns an intervention into its presumed outcome.

These assumptions are not confined to workforce processes. They sit inside strategic decisions. A business case assumes the organization can integrate an acquisition. A transformation plan assumes managers can lead through a redesigned operating model. A technology investment assumes employees can exercise the judgment the system leaves to them. A growth strategy assumes capability can be found, built, or transferred at the speed the financial model requires.

The capability assumption is often among the most consequential assumptions in the decision. It is also among the least examined. Revenue assumptions are tested. Capital requirements are modeled. Technology dependencies are reviewed. Capability is dispersed across recruitment plans, role descriptions, learning programs, headcount forecasts, and assurances that the people are ready. No single document contains the claim on which the strategy actually depends.

This invisibility is reinforced by the way work is described. Recurring observations across roles in transport and logistics, healthcare, manufacturing, financial services, technology, government, and professional services reveal the same pattern. Formal descriptions capture visible tasks and broad accountabilities, while underrepresenting the judgment around them: recognizing exceptions, protecting a control, reconciling conflicting evidence, translating across professional boundaries, stopping work, escalating risk, or explaining why a plausible answer should not be trusted.

These are not incidental additions to the role. They are frequently the point at which ordinary activity becomes safe, reliable, lawful, or valuable. They also appear far below the levels at which organizations usually imagine consequential capability resides. Frontline employees may hold enterprise controls in the course of routine work, even when neither the job title nor the formal hierarchy makes that dependence apparent.

If the work itself has not revealed its capability demand, the organization cannot know whether supply exists. It can only search for people whose histories and labels appear relevant. The first assumption, about what the work requires, is then buried beneath a second assumption, about who can provide it.

For long periods, nothing exposes the weakness. Stable work is forgiving of indirect knowledge. Established routines carry part of the cognitive load. Experienced managers route unusual problems to the people they trust. Informal relationships compensate for incomplete role design. Specialists intervene before errors become visible. Favorable conditions allow performance to continue, and continuing performance appears to confirm the original capability judgment.

What looks like evidence may therefore be the absence of a sufficiently demanding test.

Change supplies that test. A new strategy introduces unfamiliar decisions. A regulatory shift alters the standard. A restructuring breaks the relationships through which expertise used to travel. Rapid growth increases the volume of exceptions beyond what a few trusted people can absorb. The organization then discovers that capability was not distributed as widely as performance suggested, or that what people could do in the former system does not transfer automatically to the new one.

The usual description is that the transformation exposed a capability gap. Often it exposed something more basic: the organization had never established that the capability existed. It had mistaken continuity for proof.

Artificial intelligence is making this mistake harder to sustain. Organizations often begin with evidence of access, adoption, learning completion, or employee confidence. Those signals answer questions about use. They do not show whether people can recognize a weak output, supply missing context, challenge an authoritative recommendation, manage an exception, or explain a consequential decision to someone affected by it.

The work may have shifted from producing an answer to interrogating one. An experienced professional brings knowledge that remains indispensable, but experience in the original task does not by itself demonstrate capability in the redesigned task. Some people adapt their judgment readily. Others defer to the system, reject it indiscriminately, or follow procedure until a case falls outside it. The divergence can surprise leaders because the employees appeared equally capable when the old work still defined performance.

AI did not suddenly create the difference. It removed the conditions that had concealed it.

This is why capability by assumption is an organizational risk rather than a flaw in individual judgment. Each inference may be reasonable. A recruiter uses experience because direct evidence is limited. A manager uses performance because it is observable. A succession committee uses reputation and ratings because comparable evidence across candidates does not exist. A transformation leader uses completion and adoption because those are the measures the program produces.

The danger lies in accumulation. One inference supports another until uncertainty acquires the appearance of assurance. Qualifications support recruitment. Recruitment supports the workforce plan. The workforce plan supports readiness. Readiness supports the investment case. When performance later disappoints, the failure is assigned to execution, resistance, leadership, or learning. The chain of capability assumptions that preceded the decision remains largely intact.

Organizations have built sophisticated systems for administering people because people are visible organizational objects. They occupy positions, receive ratings, complete programs, and move through hierarchies. Capability is less compliant. It exists only in relation to work, a required standard, and the conditions of performance. It crosses the boundaries by which management information is normally organized.

Direct evidence of capability would therefore do more than improve a workforce decision. It could unsettle the way the decision has been framed. It might show that a presumed shortage is actually a problem of access to expertise. It might reveal that high performers are succeeding because the current system protects them from work the strategy will soon require. It might show that a training response cannot resolve unclear authority, or that the most consequential capability in a transformation sits in frontline judgment rather than executive sponsorship.

That is precisely why assumptions endure. They allow established processes to proceed without reopening the question of what the work requires. The qualification can be checked, the rating retrieved, the course assigned, and the successor named. Evidence tied to the actual work may challenge the role, the system, the investment, or the strategy itself.

Management cannot eliminate assumption, nor should it try. Decisions concern the future, and the future cannot be proven in advance. The issue is whether an assumption remains visible as an assumption, especially when substantial value, risk, or strategic dependence rests upon it. Too often, familiar signals erase that distinction before the decision reaches the room.

Organizations have spent decades improving the machinery through which they recruit, promote, rate, develop, and deploy people. The machinery has become more integrated, more data-rich, and more precise. Yet precision about the inputs does not resolve uncertainty about the claim.

Every important management decision assumes capability. Very few organizations examine whether that assumption is justified.

Executive reflection questions

1. Which current strategic commitments depend on capability your organization has inferred but never directly observed?

2. Where are qualifications, performance, tenure, confidence, or learning completion being treated as proof of readiness for different work?

3. What would become uncomfortable if your most important capability assumptions were tested against the work itself?