You Have a Clarity Problem, Not a Capability Problem.

The investment goes in, the programs run, the people attend. Then they come back to work, and nothing shifts.

You cannot build capability against an undefined standard. When expectations are vague, when what good looks like varies by manager, when the gap between a role description and actual performance requirements is never addressed, development becomes noise.

Vague expectations produce inconsistent performance, inconsistent performance gets attributed to capability, capability programs fail to measure behaviour change, against a standard nobody has clearly defined. The cycle repeats.

The L&D budget is the visible cost, the real cost is the frustration of people who are trying to meet expectations they can’t fully see, the over-reliance on a handful of high performers who figured out what good looks like without being told, and a leadership pipeline that never quite materialises because progression criteria are inconsistently applied or absent entirely.

The diagnostic question isn’t what capability we need to build. It’s can we clearly define good in terms of decisions, behaviours, and outcomes? Do managers across the organisation describe performance the same way? Are people guessing what matters? If the answer to any of those is unclear, the capability program will not fix it.

The shift is definitional before it is developmental. Define the standard, make expectations explicit at role level, align what you measure to what drives performance. Then build capability into the flow of work, not as a separate program people attend and return from unchanged.

Where in your organisation are people trying to meet a standard that has never been fully named?