About

The decisions that shaped NORTH.

NORTH is a diagnostic engine for AI leadership readiness. We build instruments that surface what interviews cannot — the pattern in the trade-offs you make under consequence.

01 · What we removed

The earliest versions had scores.

Dimension percentages. Composite indices. Readiness ratings presented as numbers precise enough to feel scientific. The kind of output that satisfies the request for rigour because it is specific.

We removed them. Not because the calculations were wrong — the underlying arithmetic is precise. But because a number in the hands of a leadership team becomes the conversation instead of the evidence for one.

The artefacts are directional. The language is specific. The conclusions name the pattern without reducing it to a figure that invites challenge on the wrong terms.

02 · Architecture

Why the simulation cannot be gamed.

The answer choices are shuffled. Deterministically — the same participant sees the same order on the same scenario, so their experience is stable — but differently across scenarios, so there is no position that reliably signals the most considered choice.

The Reckoning scenarios cannot be prepared for. They are assembled from the signal the participant has been generating. You cannot anticipate a scenario that does not exist until the decisions that create it have been made.

03 · Team output

What the team output is not.

The Coalition Map does not rank the leadership team. It does not identify the weakest link, the most aligned thinker, or the executive who scored highest on any dimension.

It shows where the team collectively reads the organisation — and where the gaps in that collective reading are. The distinct voice is not a performance finding. It is the signal that the coalition has a counterweight to its own blind spot, if it chooses to use it.

The language creates agency, not shame. This was a product decision with commercial implications. An instrument that names weakness in public creates resistance. An instrument that names the pattern — and names it as a resource — creates the conditions for the conversation that the engagement requires.

04 · How we work

One implementation. Many usages.

01
Rigour over flexibility

Button specifications are fixed in constants. Form field specifications are canonical. When a component changes, it changes everywhere — or it has not changed, it has drifted.

02
Specificity over abstraction

Every sentence in the output is tied to actual leader input. Every recommendation names a pattern. Every sprint plan has an owner and a done-means.

03
Agency over shame

The instrument surfaces what is present, not what is missing. The shadow is named as a risk to manage, not a deficit to fix. The reader leaves with clarity, not indictment.

Start

See the instrument for yourself.

The best way to understand what NORTH does is to complete a diagnostic. Twenty minutes. No correct answers. One leadership archetype that names the shadow you already suspected.