Every 12 to 18 months, a CPO or COO asks the same question:
"Do we have the capability we need to deliver the strategy?"
And every time, someone proposes a six-month capability review that ends in a 90-slide deck that nobody reads.
There is a faster way. The capability review we run with clients fits into 30 days, produces decisions not documents, and is defensible enough to take to the board.
Why the slow version fails
Long capability reviews fail for the same reasons long anything fails in big organisations.
- They lose momentum. By week 14, the sponsor has moved on and the priorities have shifted.
- They over-index on breadth over depth. Analysts survey everyone, get surface-level data, and produce summaries that do not move any specific decision.
- They separate the analysis from the decision. You end up with a report, and then a second workstream to decide what to do about it.
The 30-day review fixes all three.
The 30-day structure
We split the work into four phases, each with a concrete output.
Week 1: Strategic lens (decide what we are measuring against)
You cannot assess capability in the abstract. It is always capability against a plan.
Sit down with 5 to 8 senior leaders and answer three questions:
- What are the 3 to 5 strategic bets we are making in the next 24 months?
- For each bet, what are the 2 to 3 capabilities that, if we are weak, become the binding constraint?
- How will we know, in 12 months, whether we got capable enough?
The output is a Capability Priority Map: a single page listing the 10 to 15 capabilities that matter most for the next 24 months, each tied to a business bet.
This page is the anchor for everything that follows.
Week 2: Evidence gather (move fast, triangulate)
Resist the urge to launch a company-wide survey. Instead, triangulate from three sources:
- Manager calibration on the 10 to 15 priority capabilities, for teams that carry the strategic bets. Short-form: one page per team, 20 minutes per manager.
- Self-assessment from a targeted sample of ICs (around 20% of the relevant population).
- Behavioural artefacts: performance data, quality metrics, customer feedback, retention of senior ICs in the key capability areas.
Three sources keeps you honest. If all three agree, you have a finding. If they disagree, you have a conversation to have.
Week 3: Synthesis + gap diagnosis
Build the capability heatmap: priority capability on one axis, team or function on the other, coloured by current depth. Overlay the strategic bets they serve.
Then ask two questions of every cell:
- Is this gap real, or is it a perception problem? (sometimes the capability is there but invisible)
- If the gap is real, what is the fastest path to close it? (buy, build, partner, redesign the role)
You will end up with 3 to 5 critical gaps: the ones that, if unaddressed, a strategic bet fails.
Week 4: Decision briefing
Now you produce the artefact that actually matters. It is not a report. It is a one-page Capability Investment Brief for each critical gap:
- What the gap is
- Which strategic bet it threatens
- Three credible options to close it, with cost, timeline, and risk
- A recommendation
You take that brief to the executive team. They make decisions. The review is done.
What good looks like at the end of 30 days
- A shared Capability Priority Map anchored to the 24-month strategy
- A capability heatmap showing depth by team against the priorities
- 3 to 5 Capability Investment Briefs ready for decision
- A first investment plan with clear owners for the next 90 days
Not a 90-slide deck.
The three traps to avoid
Trap 1: Surveying everyone. You do not need to hear from 2,000 people. You need to hear the right 200, from three different angles.
Trap 2: Treating the review as a one-off. The Capability Priority Map is a living artefact. Revisit it every 6 months, not every 3 years.
Trap 3: Separating the review from the decision. If the people running the review are not in the room when the investment decisions are made, you will end up with a beautiful document and zero behaviour change.
When to run one
Run a 30-day capability review whenever one of these things happens:
- A new 2 to 3 year strategy has just been signed off
- A new CEO, COO, or CPO is in post and asking "what have we got?"
- A major capability bet is landing (AI, product shift, market expansion) and nobody has actually assessed whether you can deliver it
- You have been quietly losing senior capability and it is now showing up in results
If two or more of these are true right now, you have permission to run this next month.
A lighter starting point
It is free, and the score becomes the simplest version of the Capability Priority Map, a way to start the right argument.
Welcome to better.