The Loop · How it works

One operating loop for growth work.

How the loop works

Loopium runs growth as a loop of four parts. Decide: Growth64 narrows many possible moves to a slate the organisation can carry. Install & Sense: the Orchestration Accelerator rebuilds the critical workflows in 12 weeks while the Pulse Index reads progress each quarter. Run: the Loopium Orchestration System drives a weekly review that ends in decisions. Learn: the Loopium Institute turns field lessons into practice. A mission uses the parts it needs.

A growth mission as an operating score Twelve weeks across five lanes. Decide: a growth slate with monthly reviews. Install: workflows rebuilt on live work and handed over. Sense: a Pulse Index read at the start and end of the quarter with weekly signals. Run: weekly decisions in the Loopium Orchestration System (Loopium OS). Learn: practice captured continuously. A playhead marks the current week. W01 W02 W03 W04 W05 W06 W07 W08 W09 W10 W11 W12 DECIDEGrowth646-monthly slate INSTALLOrchestration Accelerator12 weeks SENSEPulse Indexquarterly read RUNLoopium OSweekly decisions LEARNLoopium Institutecontinuous SLATE · 5 PLAYS · 6-MONTH HORIZON DIAGNOSE DESIGN BUILD ON LIVE WORK TRAIN HANDOVER PULSE READ NOW · W07
Work in the installationDecision checkpointRead or reviewPlay stoppedIllustrative mission · 12 weeks

Definition

What is growth operations?

The discipline of running growth priorities as operating work: a small number of chosen moves, each with an owner, a measure, a decision date and a cadence of review.

It sits between strategy, which chooses the moves, and day-to-day operations, which carry them out. Most organisations are well equipped at both ends. The gap is the operating week in between, where priorities meet a calendar that is already full.

Loopium is built for that gap. We run it as a mission studio: one bounded outcome at a time, with your people, on a fixed cadence.

The four parts

What each part does, and how often.

The loop turns at different speeds. The slate moves every six months; decisions happen every week. Each speed has its own instrument.

The four parts of the Loopium loop
PartInstrumentCadenceQuestion it answersWhat you keep
DecideGrowth64Six-monthly slate, monthly progress reviews (replacing 12- to 36-month strategy cycles)Which few moves are worth carrying, and what will they cost?A costed, owned growth slate
Install & SenseOrchestration Accelerator with Pulse Index12 weeks; Pulse read quarterlyWhich workflows must change to carry the slate, and what is holding growth back now?Two or three rebuilt workflows; a named binding constraint
RunLoopium Orchestration System (Loopium OS)WeeklyWhat do we continue, change, escalate or stop this week?A weekly decision review and a decision log
LearnLoopium InstituteContinuousWhat did we learn, and who can now run this without help?Certified practitioners; written operating practice

Where to start

Not every client buys every part.

The loop describes how the parts connect. Most organisations start with the part their current problem calls for, and add others only if the mission needs them.

If you have too many priorities

Start with Growth64

Reduce the field to a slate you can carry, with costs, owners and signal windows.

Growth64

If the slate is clear but execution is slow

Start with the Orchestration Accelerator

Rebuild the two or three workflows that carry the most load, on live work.

Orchestration Accelerator

If you are unsure where the constraint is

Start with a Pulse read

Read five dimensions and name the one constraint worth solving next.

Pulse Index

If the work is running but will not hold

Start with the Loopium Orchestration System

Install the weekly decision review and the evidence behind it.

Loopium Orchestration System

Method

What stays fixed, and what adapts?

The loop is stable. The frameworks and instruments inside it are adjusted to your sector, your maturity and the mission. A distributor and a manufacturer run the same loop with different levers, measures and meeting designs.

Fixed in every mission

  • The four parts and their order
  • A weekly review that ends in decisions
  • An evidence standard for every claim of progress
  • Ownership transferred to the client team

Adapted to you

  • Growth levers and plays in scope
  • Measures and comparison sets
  • Meeting design and attendance
  • Which workflows use AI, and how

Glossary

The terms we use.

We use each term the same way on every page, in every proposal and in every report.

Growth operations
The discipline of running growth priorities as operating work: a small number of chosen moves, each with an owner, a measure, a decision date and a cadence of review.
Mission studio
A firm that works through bounded missions rather than open-ended projects. Each mission has a named outcome, an accountable client owner, a working team, a decision cadence and an end date, and leaves the cadence with the client.
Mission
A bounded piece of growth work with a named outcome, an accountable owner, a working team, a decision cadence and a date.
Growth64
Loopium's decision system for choosing growth moves. It maps 64 growth plays across 8 levers and 8 stages and narrows them to a slate the organisation can carry, costed, resourced and linked to the three financial statements. The slate is reset every six months.
Loopium Orchestration System (Loopium OS)
Loopium's live operating system for running missions. It brings mission progress, supporting evidence and decisions into one weekly leadership view.
Pulse Index
Loopium's quarterly operating read across demand, retention, channel health, employee engagement and operating drag. It uses 40 measures and names one binding constraint per cycle.
AI-native workflow
A repeatable piece of work rebuilt so that AI carries out preparation, analysis or first drafts within defined access rules, while named people review at set control points and remain accountable for the decision.
Orchestration cadence
The fixed rhythm of reviews in which a team reads evidence and makes recorded decisions about its growth moves: weekly for plays, monthly for the slate, quarterly for the Pulse read, six-monthly for the slate itself.
Binding constraint
The single limit that most restricts growth in the current period. Improving anything else produces little until it is addressed.
Signal window
The period in which a growth move is expected to produce its first measurable evidence. If the evidence does not arrive in the window, the move is reviewed and may be stopped.

FAQ

Questions about the loop

What is growth operations?

Growth operations is the discipline of running growth priorities as operating work: a small number of chosen moves, each with an owner, a measure, a decision date and a cadence of review. It sits between strategy, which chooses the moves, and day-to-day operations, which carry them out.

Do we need to buy all four parts of the loop?

No. Most organisations start with one mission and the part of the loop it needs. A team with a clear growth slate may start with the Orchestration Accelerator. A team with too many priorities usually starts with Growth64. The loop explains how the parts connect; it is not a bundle.

What stays the same between clients, and what changes?

The loop is stable: decide, install and sense, run, learn. The frameworks and instruments inside each step are adjusted to the sector, the maturity of the team and the mission. A distributor and a manufacturer will use different measures, levers and meeting designs.

How long before a team runs the loop without Loopium?

The Orchestration Accelerator is designed to transfer ownership within 12 weeks for the workflows in scope. Some clients keep Loopium on the weekly cadence for a period afterwards; that is a choice, not a dependency.

Where does AI sit in the loop?

Inside specific workflows, with defined access, review points and an evidence trail. AI prepares analysis, drafts and options. Accountable people decide.

15-minute scoping call

Bring one outcome.
We will help you decide whether it is a mission.

A 15-minute scoping call is enough to establish whether the work has a clear outcome, a workable team, and a cadence worth installing. If Loopium is not the right fit, we'll say so directly.