The compound growth operating system

Clarify the signal before the sprint

Every sprint begins with a shared view of the field. Before we assign pods, we map the momentum scorecard and rank the signals that actually move revenue. That alignment takes one workshop, not a quarter.

• Frame the north-star outcome in language the board expects.
• Identify the three metrics that prove velocity and the single leading indicator for each.
• Assign owners to every signal so updates never bottleneck on a deck.

Design loops that keep teams shipping

Pods operate in loops. Each loop has a cycle time, a deliverable, and a way to surface signal. We prefer four-week loops with weekly demos so leadership sees progress before the retrospective.

1. Kickoff lab: Align on outcomes, define the experiment backlog, lock owners.
2. Build sprints: Two-week pushes pairing experience and growth pods.
3. Enablement drop: Package outputs into assets the field can deploy immediately.

Cadence beats heroics. Each loop ships something observable, even if it is a narrative update or refined signal definition.

Make enablement drops that stick

Operationalizing growth means enablement ships alongside product. We embed enablement strategists in every pod so the materials are co-authored, not thrown over the wall.

• Live narrative briefings recorded with built-in feedback prompts.
• Interactive decision trees that show what to do when a signal moves.
• Activation office hours with ops owners to remove blockers fast.

Checklist before you mobilise a pod

• Success narrative agreed on by revenue, product, and finance.
• One living workspace for experiments, assets, and scorecard updates.
• Dedicated analyst to maintain dashboards and nudge owners.
• Executive sponsor committed to the weekly momentum review.

Once these are true, you can mobilise pods in under two weeks. Anything longer usually means misalignment upstream.