Strategy that runs, not strategy that sits

Most strategy work ends the same way. Weeks of research, interviews and modelling are pressed into a deck. The deck is presented, the room agrees or argues, and the strategy is fixed in that form. From that moment, it starts to age.

The thinking may have been good. But a deck freezes the strategy at the moment it is presented.1Show source for note 1 A document records what was true on the day it was written. A competitor changes its price. A rule changes. A KPI the plan depended on starts to drift. The deck does not notice. It sits in a shared folder, describing a world that has moved on.

That is one of four problems with how strategy is usually delivered. Most strategy work still takes weeks and costs a great deal. It is out of date soon after the deck is presented. It sits apart from the systems where the business actually runs. And it is hard to see how any one conclusion was reached.2Show source for note 2

A faster deck fixes the first problem and none of the others. This essay is about the other three, and about what a strategy that runs, rather than sits, looks like in practice.

The alternative to a deck is not a better deck. It is a model of the client's strategic world that stays open after the meeting. We call it the Strategy Twin.

A Twin is a strategic ontology per client, built in the first engagement and enriched in every later one.3Show source for note 3 It holds six domains: the market, the competition, the company, its capital, the context it operates in, and the decisions it has made. Markets, segments and customers sit in one. Regulations, permits, stakeholders and risks sit in another. Initiatives, decisions, KPIs and evidence sit in the last.

It is deliberately small. A Twin models hundreds of objects that matter, not millions of records. We compete on decision speed and quality, not on the breadth of a data platform. A strategy does not need every transaction a business has ever recorded. It needs the parts of the world its decisions depend on, held in a form that can be questioned.

That form has a simple grammar. Objects are the nouns: a competitor, a product, a site, a budget. Links say how they relate: a competitor competes with a product, an initiative is funded by a budget, a decision is supported by evidence. Actions are the verbs a decision can trigger, such as allocating a budget or creating a CRM opportunity. Functions are the calculations, and they run in code.4Show source for note 4

A deck tells you what someone concluded. A model lets you ask why, and lets you ask again when something changes.

The rule that makes a Twin useful is easy to state. Every decision links back to its evidence and forward to its KPIs.5Show source for note 5

Backwards, any recommendation can be traced to its sources. Each number and claim links to a source, a date and the agent that produced it. Each key figure carries a confidence grade in words: a verified primary source or client data, a credible secondary source, or a model estimate. An estimate is labelled as an estimate wherever it appears.

Forwards, each decision names the KPIs that will measure it. That is what lets a strategy be checked against what happened, instead of against what was hoped.

In between, a decision moves through clear states: draft, proposed, approved, executing and measured. Or it is marked rejected or superseded. Anyone looking at the Twin can see where a decision stands, what it rests on and how it will be judged. A deck has no states. It is either current or it is not, and usually nobody says which.

A model that is not kept current is only a slower deck. So the Twin is built to change. When a competitor moves, a rule changes or a KPI drifts, the Twin changes, and the decisions that depend on it are flagged for review.6Show source for note 6

Flagged, not rewritten. The Twin does not quietly change a decision because a number moved. It tells the people who own the decision that its basis has shifted, and shows them what shifted. Whether the decision should change is still a human call, made at a gate, with a signature.

This is the part of the S1 Method that most projects leave out. Most projects end at the presentation. Ours ends at Learn, which feeds Sense. KPIs are tracked against the decision that set them. When results drift, the scenarios re-run and the Strategy Council sees a proposed next decision, with its evidence. The loop starts again, and the same three gates apply on every pass.

The last problem with a deck is where it lives. A strategy that sits in a folder has to be re-typed into plans before anyone can act on it, and something is lost in every re-typing.

A strategy that runs reaches the systems where a business operates. Approved decisions become CRM opportunities, budgets, briefs and run-sheets, after your named owner accepts them.7Show source for note 7 That last clause is the important one. Before any write, the change passes a policy check, the owner approves a dry-run of exactly what will change, and the approval is recorded in a hash-linked audit trail. Nothing is written without that approval, and we never describe it as automatic.

Then outcomes flow back into the Twin. The budget that was approved is measured against the KPI it was meant to move. The brief that was issued is measured against the decision that set it. The strategy and its results sit in the same model, so the next decision starts from what actually happened.

A strategy that runs is not a strategy that runs itself. The model reads, drafts and re-runs. People decide. Every decision still passes a named person at the gates, and every plan still ships with the conditions under which it fails.

Nor does it mean a large system on day one. A 72-Hour Bootcamp leaves a starter Twin scoped to one real decision.8Show source for note 8 An Engine Sprint deepens it for one engine, at full depth. A Strategy Twin retainer keeps it current: KPIs daily, competitor and regulatory scans weekly, scenario re-runs monthly, and a Strategy Council each month. The Twin grows with every engagement, decision by decision.

The test is simple. Six months after a strategy is agreed, can you see which of its assumptions still hold, which decisions it produced, and whether those decisions are working? If the answer lives in a deck, you cannot. If it lives in a model that is kept current, you can. That is the difference between strategy that sits and strategy that runs.