Three years running, the status report on the university's placement coordination capability says the same thing. On target. Level 2, efficient, standardised, exactly where it was supposed to be. Nobody in governance questions it, because nobody has a reason to. The capability is doing precisely what it was asked to do.
The work-integrated-learning program it quietly supports has tripled in size in that same three years.
You've probably filed a capability the same way. Assessed once, cleared, moved on. It's not carelessness. The original work was rigorous: a real strategic choice, a target derived from it, a plateau capability correctly told to stay boring rather than gold-plated for no reason. That call was right when it was made. What nobody built was a reason to make it again.
A target with no expiry date
Here's the part that doesn't show up on a heat map. A capability can be performing exactly to target and still be aimed at the wrong number, because the target was never wrong.
It just went stale.
Three years ago, the university derived its capability targets from one real strategic choice: distinctive work-integrated learning, delivered through structured employer partnerships. Employer partnership management became the capability that carries that strategy, uplifted to a Peak level, above the sector norm. Placement coordination, the operational capability that schedules and supports every student's work term, was assessed at the same sitting and correctly told to stay a plateau: efficient, standardised, no higher, because work-integrated learning still ran at modest scale and the coordination load was exactly what the process was built for. That derivation was sound too.
Since then, the ground has shifted, mostly because the original fix worked. Employer partnerships multiplied, work-integrated learning rolled out well beyond where it started, and placement coordination now schedules and supports several times the volume it did at the original assessment. Nobody contested any of this as it happened. Each expansion read as a win worth celebrating, not a trigger to reopen a capability nobody had complained about.
Meanwhile, the capability roadmap never returned to placement coordination. It wasn't reassessed, because nothing about it had failed. It was still hitting Level 2, still efficient, still standardised, exactly as designed for a scale the university had long since outgrown. The people who'd own a re-derivation had no trigger to go looking, because "on target" reads as settled, not as due for review. A plateau, correctly assigned once, quietly became the capability the strategy's own success now leans on hardest, while everyone with eyes on the account kept confirming a number that used to be the right one to confirm.
That's the failure a heat map can't show you. Ask a capability whether it's hitting its target and you'll get an honest answer every time. Ask whether the target is still the right one, and you're asking a different question, one the assessment was never built to answer on its own.
The question with the expiry date
There's a single question a capability's target level should always be able to answer: which strategic choice requires this level, specifically, right now. Call it the Target-Level Question. It isn't a formality at the start of the assessment. It's the thing that has to survive the strategy changing underneath it, and most organisations only ever ask it once.
That's a different failure from a capability that reaches its target and then quietly slips, staffing and process eroding while nobody checks whether the level is still actually there. This is upstream of that. It isn't about whether the capability held the level. It's about whether the level was ever still the right one to hold.
Worth being plain about what this isn't. It isn't a case for reassessing everything constantly. Plateaus are supposed to be able to sit still. The failure isn't stillness. It's that nothing was ever built to notice when the ground underneath a plateau moves, so stillness and neglect look identical from the outside, and only one of them is a choice.
Put the redraw on the strategy's own calendar
The fix isn't a better assessment. The original one was fine. It's giving the whole capability map, not just the capabilities already flagged as struggling, a standing date to be checked again, tied to the same cycle that produces the strategy refresh in the first place.
Concretely: whenever the strategic choices get revisited, that same session should ask, for every capability on the map, whether the choice that put it there still holds. Not a full reassessment of everything. A five-minute check per capability: has anything about the strategy changed that this target was derived from? If yes, it goes back through the Target-Level Question properly. If no, it stays exactly where it is, confirmed rather than merely unexamined.
This is the same cycle Design4 already runs for the strategy itself. The capability redraw just needs a seat on it, not a calendar of its own.
Name an owner for that check, the same person or group who owns the strategy refresh, and it stops being optional. A target with a named owner and a date gets revisited. A target that's merely correct gets trusted indefinitely, right up until it's the reason nobody saw the gap coming.
The maturity ladder tells you how to climb. It has never once told you the wall you're climbing has moved.
A capability can be exactly on target and still be aimed at the wrong number. Now you know the second thing to check: not whether it's hitting the target, but whether the target is still the one your strategy actually needs.
This is maturing the deciding capability, one layer down from where How Mature Is the Process That Decides? leaves it: the same discipline, applied to a target instead of a plan.