Tier one — capability strategy

Before anyone builds.
Decide what capability is for.

Most capability functions are asked to deliver before they are asked to decide. The result is a portfolio of well-run programs that nobody can connect to a business outcome, and a function that defends its budget with attendance data.

Tier one is the work that happens upstream of design: what the organisation actually needs people to be able to decide, where the function should sit, what it should stop doing, and how it will be judged.

Advisory · retained or project · global delivery

What it covers

Four engagements at the strategy layer.

Retained advisory

Fractional CHRO / CLO

Senior capability judgement on tap without a full-time hire. Sits in the leadership forum, owns the capability agenda, hands it over when the internal appointment is right.

Retained →
Function design

Capability function strategy

What the function is for, how it is structured, what it stops doing, and the measurement it will be held to. Usually follows a new CHRO or a restructure.

3–6 months →
Positioning

Go-to-market & blue-ocean strategy

For capability businesses and L&D providers: where the offer actually differentiates, what to retire, and how to price against outcomes rather than days.

Project →
Judgement

Judgment architecture consulting

For organisations where AI deployment is outpacing the judgment layer it lands on. Root cause classified as skills, structure, measurement or context before any design begins.

Audit first →
The discipline

Diagnosis before prescription, always.

Every engagement at this tier starts the same way: a diagnosis that classifies the root cause as skills, structure, measurement or context. Three of those four are not training problems, and if the diagnosis lands there I will say so and the engagement ends.

That is not restraint for its own sake. A capability function that runs a program against a structural problem spends its credibility and solves nothing — and it is usually the second attempt, not the first, that costs the function its mandate.

Where the diagnosis does land on capability, the output of tier one is the brief for tier two: the architecture that makes the capability structural rather than episodic.

Start with the diagnosis.

The free diagnostic names where judgment is breaking — which decisions, at which altitude, under which conditions. That determines which tier is the right instrument.

See the AI capability gap →

Free · no obligation