The capability conversation always sounds productive. A leadership team is in a room, the year's development budget is on the table, and someone senior says the sentence that will shape the next six months of work: we need our people to think more critically. Or more strategically. Or to show better judgment. The words land with the weight of obvious truth, and everyone nods, because nobody has ever lost status by agreeing that critical thinking is important. It goes onto a slide. By the end of the quarter it is a program with a name, a cohort, a facilitator, and a completion target, and not one person in the chain that built it can tell you what the capability actually is.
Ask the leader who named it to describe a single moment where the capability was present and a matched moment where it was absent, and watch what happens. There is a pause. Then a generality: they need to see the bigger picture, they need to connect the dots, they need to challenge assumptions. Every one of those is another abstraction stacked on the first, a synonym pretending to be a specification. Push once more and the answer arrives dressed as impatience: you know what I mean. The uncomfortable thing sitting under that impatience is that they do not know what they mean, and the request they just funded is a feeling wearing the costume of a requirement.
The Word Is A Container, Not A Specification.
Critical thinking is not a capability. It is a category label under which several dozen distinct and often unrelated behaviours have been filed for the sake of convenience. The person who reaches for it is pointing at a discomfort, not describing a skill. Somewhere behind the word is a specific failure they actually felt: a manager who escalated a decision that should have been made at his own desk, an analyst who accepted a number that was visibly wrong, a team that ran a plan off a cliff because nobody stopped to ask whether the plan still held. Each of those is a different capability with a different root and a different fix. The word flattens all of them into a single purchase, and the flattening is the first error, made before anyone has spent a rupee.
Because the request is vague, the solution can be anything, and anything is exactly what gets built. A vendor receives the word critical thinking and does the rational thing: maps it to the nearest module in the catalogue and ships a beautifully produced program that teaches a framework nobody asked for against a problem nobody diagnosed. This is not fraud. It is the predictable output of a system where the buyer could not specify and the seller was never paid to ask. The program runs. The cohort enjoys it. The feedback scores come back warm. And the decision that triggered the whole exercise happens again the following quarter, because it was never the thing being addressed. The organisation reads the warm scores as progress and quietly schedules the sequel.
Press a leadership team to actually list the capabilities they want and you rarely get a list of capabilities. You get a list of virtues. Critical thinking, strategic thinking, agility, ownership, collaboration, innovation. These are not skills that can be built into a person. They are adjectives the organisation would like to be true about itself. A capability has a behavioural signature: you can describe the moment it is exercised, the decision it changes, the failure it prevents. A virtue has only a glow. The tell is simple. If you cannot name the specific decision that would go differently once the capability exists, you have named a mood, and you are about to spend a budget building training for a mood.
The Request Fails Its Own First Test.
Here is the part that should stop the room. Naming precisely what you want is itself an act of critical thinking. Moving from a felt discomfort to a specified need, interrogating your own vague ask until it resolves into something concrete, is the exact capability the leader claims their people are missing. And the request fails it. A leadership team that cannot specify the capability it wants is demonstrating, live and in the room, the absence of the very capability it is trying to buy for everyone below it. The gap is not downstream in the workforce. It is standing at the front of the room, holding the marker, pointing at a slide.
This is why so many capability programs feel faintly haunted. They are built to fix a deficit that was never located, commissioned by the people exhibiting the deficit they are outsourcing. The organisation looks down the hierarchy for the missing judgment and never turns to examine the judgment that produced the brief. So it builds the wrong thing beautifully: a polished, well-facilitated, high-satisfaction answer to a question nobody ever managed to ask clearly. The production values rise to hide the fact that the target was never found. Everyone can see the program. Nobody can see the problem it was supposed to solve, because it was never written down in a form specific enough to solve.
Extraction Before Design.
Doing this properly starts much earlier and much more uncomfortably than any program launch. Before a single learning objective is written, the real need has to be extracted, and extraction is not a discovery survey or a stakeholder interview that dutifully transcribes what leaders say they want. It is the harder work of refusing to accept the label. You take the leader who said critical thinking and you make them walk you to the scene of the crime: the specific decision, the actual meeting, the real moment where something went wrong that this capability would have prevented. You keep asking until the abstraction collapses into an incident. Under the incident is the capability, sharp and nameable at last, and it is almost never the one that was on the slide.
Design-thinking earns its name here, in the part everyone skips. The point of it was never sticky notes and empathy maps. The point is to treat the stated request as a symptom and to reverse-engineer from the decision the organisation actually needs to go better. Sometimes the extracted need really is a thinking capability. Far more often it is something the org did not want to hear: a structural problem wearing the mask of a skills gap, an accountability that was never assigned, a decision right that lives nowhere, a manager who was never given permission to decide and therefore escalates by design. You cannot train your way out of any of those, and the program built on the unexamined label will spend real money and a year of goodwill proving it.
This is where SSUNDAR starts, and it is deliberately before the point most engagements begin. We do not take the capability brief at face value, because the brief is the first artifact of the problem, not a description of it. We work backwards from the decision that is actually costing the organisation to the capability that would have changed it, which is usually a smaller, sharper, and more inconvenient thing than the word on the slide. And where the extraction is hardest, where a leadership team genuinely cannot name what they want because they have never watched it fail in a controlled setting, we put them and their people inside a simulation and let the pressure name the capability for them. A decision made badly under load is not an opinion. It is a specification. It tells you, precisely and without the shelter of abstraction, which capability was missing and exactly when it went missing.
A capability you cannot name is not a capability gap in your people. It is a specification gap in the request, and every program built on the unexamined label is an expensive, well-produced answer to a question nobody ever managed to ask.
Your people are not failing a capability you have clearly defined. You are asking them to close a gap you have never been able to name, with a program built to fix the wrong thing, commissioned in the exact language that proves the gap begins with the brief. Name the decision. The capability is hiding inside it.