Playbook: Build a Strategy Function That Outlasts the Brief

Most organizations add AI capability the way they add software: buy it, install it, wait for results. Then they wonder why the output sits in a Slack thread nobody references.

The problem isn't the AI. It's that buying capability without building the strategy function to absorb it is an engine with no steering. It runs. It doesn't turn.

A strategy team produces work. A strategy function produces decisions that survive the handoff. The difference is accountability architecture, not headcount.

This playbook lays out how to build one — in three phases, with hard timelines and a scorecard that tells you whether it's working.

Phase 1: Move Strategy From a Role to a Function (Weeks 1–2)

Most organizations treat strategy as something a few senior people do between meetings. The result: decisions that evaporate when the meeting ends.

Start here: audit your current decision architecture. For your three most recent strategic decisions, answer:

If you can't answer all four for each decision, strategy isn't a function yet. It's a vibe.

The fix is a cross-functional Strategy Accountability Structure. Below is the RACI that makes it operational — not advisory, not optional.

R = Responsible (does the work), A = Accountable (signs off), C = Consulted, I = Informed

This isn't about adding meetings. It's about removing ambiguity about who owns what — which is why 68% of strategy execution failures trace to unclear accountability, not bad ideas.

Phase 1 exit criteria: A completed RACI, signed by every accountable party, distributed to all stakeholders.

Phase 2: Install a Three-Gate Decision Cadence (Weeks 3–4)

Strategy decays when decisions accumulate without a forcing function. You need a cadence that gates decisions — not a calendar that warehouses them.

Implement three gates:

The cadence produces a decision record — not a memo, not a summary deck — that becomes the operating system for execution. When someone later asks "Why did we do this?" the answer exists in one place.

Phase 2 exit criteria: Three decision records completed through all three gates. If none exist, start with the next real decision — do not invent one.

Phase 3: Embed the Decision Velocity Scorecard (Weeks 5–6)

If you can't measure whether your strategy function works, you don't have one. The Decision Velocity Scorecard tests whether decisions are happening faster and sticking.

Fill in your baselines during Week 5. Re-score at Month 3 and Month 6. The goal isn't perfection — it's trajectory. A strategy function that moves from 28-day median decisions to 12 days in six months is working. One that's flat isn't.

Phase 3 exit criteria: Baseline scores populated, Month 3 check-in scheduled, and the scorecard is visible to every stakeholder named in the RACI.

The Underlying Principle

Tools give you capability. A strategy function gives you steering. One without the other is noise. Both together is how you make strategy that outlasts the brief — and the person who wrote it.