The kickoff has real momentum. A senior leader has sponsored a capability program, a budget is approved, a vendor is shortlisted, and eleven people are around a table agreeing that this matters. The energy is genuine. The slides say transformation. Then someone, usually the most junior person present and usually apologetically, asks the question that empties the room. If this works, what will be different? What does success actually look like?
What follows is not an answer. It is a pause, then a series of sentences that sound like answers and are not. Our people will be more strategic. We will build a stronger pipeline. The culture will shift. Every one of them is unfalsifiable, which is another way of saying nobody can tell you when you have arrived, or whether you ever will.
Two questions that dismantle most briefs.
A capability brief tends to arrive with the confidence of something already decided. The work is not to execute it faster. The work is to interrogate it before a rupee is spent, and two questions do most of the damage.
The first: is this a real organizational need, or is it one senior leader's personal conviction wearing corporate clothing? A surprising number of large programs trace back not to a validated gap but to a single executive who read a book, attended a conference, or carried a bias in from a previous employer, and had enough authority that nobody asked for evidence. The need was never diagnosed. It was declared, and the declaration was loud enough to become a line item.
The second: can anyone in the room describe what success looks like in terms specific enough to be wrong? Not a feeling. Not a direction. A described state, with a before and an after that a skeptical observer could tell apart. If the honest answer is a blue-ocean hand-wave about being more agile or more innovative, then there is no target, and a program without a target cannot succeed. It can only end.
An objective nobody can define is not ambitious. It is unfalsifiable, and unfalsifiable goals are the most expensive kind, because they consume budget indefinitely and never trigger the moment where someone is allowed to say it worked.
What the vacuum actually costs.
When the finish line is undefined, several things happen, all of them costly and none of them obvious at the time. The vendor, needing something to build, quietly substitutes their standard offering for the diagnosis nobody did. The program gets scoped against that substitute. Six months later it is delivered, competently, and it lands in an organization that still cannot say whether it needed the thing it just received.
Then comes the review, and this is where the absence of a definition does its quietest work. Because success was never specified, failure cannot be proven either. So the program is declared a qualified success on the strength of completion rates and satisfaction scores, the two metrics that measure whether the event occurred rather than whether it mattered. Everyone moves on. The gap the program was vaguely meant to close is still there, now with a case study attached claiming it was addressed.
Multiply that across a portfolio and you get an L&D function that is perpetually busy, reasonably well reviewed, and structurally unable to demonstrate that any of it changed the business. Not because the work was bad. Because the work never had a target it could hit or miss.
The failure is upstream, and it is nameable.
The instinct, when a program underdelivers, is to look at delivery. The facilitator, the content, the follow-through, the participants who did not apply it. Look earlier. The decision that doomed the program was made in the kickoff, in the moment the room accepted a brief that no one could define success against and chose to proceed anyway because proceeding felt more productive than pausing.
That pause is the whole discipline. The willingness to stop a well-funded, well-sponsored initiative and say we are not scoping anything until we can describe, concretely, the changed state we are buying and prove it is a need rather than a preference. It is an uncomfortable thing to do to a senior sponsor's idea. It is also the single highest-leverage act available in the entire program, and it happens before the program exists.
What rebuilding looks like.
A serious diagnosis extracts the real need before anyone designs a solution to it. It separates the capability the business can demonstrate it lacks from the capability a leader simply admires. It forces the success state into language specific enough to be tested, and it kills the briefs that cannot survive that test, which is a mercy, because those briefs were going to consume budget and produce a case study and change nothing.
This is the work SSUNDAR insists on doing before it will build. Not because diagnosis is a billable phase, but because a program aimed at an undefined target is a beautifully executed way to spend money on the wrong thing. The design is the easy part. Knowing what you are actually solving, and having the discipline to refuse the brief until you do, is where the outcome is decided.
If nobody in the room can say what winning looks like, the program has already been graded, and the grade will arrive dressed as a success.