The Five Moves

The full framework. Twenty-five cases across the private, public and civil-society sectors.

Move 1BUILD

Creating durable institutions, infrastructure and capability rather than advising, advocating or piloting.

Diagnostic question: Does your organization own a piece of infrastructure that others depend on, or does it depend entirely on infrastructure owned by others?

Published September.

Move 2COMPOUND

Designing systems where each output becomes the input to the next stage, so effort accumulates instead of resetting.

Diagnostic question: Does each completed cycle of your core activity make the next cycle cheaper, faster or more certain, through a mechanism you can name?

Published October.

Move 3INTEROPERATE

Building so that value moves across firms, sectors and borders through shared rails and common standards.

Diagnostic question: When your organization connects to adjacent systems, does it help set the terms of connection, or accept terms set by others?

Published November.

Move 4LOCALIZE

Re-deriving capability where you are, rather than renting it from where it was invented.

Diagnostic question: Has your operating model been rebuilt around local constraints, or is it an imported model with local adjustments?

LOCALIZE

Move 5PERSIST

Operating on multi-decade horizons, with mechanisms designed to protect long-term commitments from short-term pressure.

Diagnostic question: Could your organization continue on its current trajectory if its founder, its principal funder, or the current government were removed tomorrow?

Published December.

Scoring rubric

Entry sequences

New organization, thin resources

  1. 1. LOCALIZEWith no balance sheet to defend, the only cheap advantage available is a model designed against a constraint incumbents have adapted around rather than solved.
  2. 2. COMPOUNDThin resources make cycle speed the decisive variable; the cases show small organizations overtaking larger ones by running the loop more often, not by running it better.
  3. 3. BUILDBuild only once the localized model has proven demand, and build the narrow layer that model depends on — the sequence Twiga and M-KOPA both followed.

Existing trust network or member base

  1. 1. COMPOUNDThe membership already generates a record; the first task is to capture it institutionally rather than let it dissipate, as KTDA did with grower-level data.
  2. 2. BUILDTrust converts into position only when it is attached to an asset members must route through, which is what turned tea growers into factory owners.
  3. 3. PERSISTMember-based organizations fail at succession more than at strategy; institutionalize governance before the founding cohort turns over.

Regulator or state actor

  1. 1. INTEROPERATERule-setting authority is worth most when it is exercised on connection terms, as in Nigeria's switching standards and the AfCFTA settlement layer.
  2. 2. BUILDA shared public layer with a usage mandate — the Irembo pattern — converts regulatory authority into permanent infrastructure.
  3. 3. PERSISTState initiatives die with administrations; Botswana's fiscal rule shows that statutory basis, not enthusiasm, is what carries a reform across cycles.

Resource or sector incumbent

  1. 1. BUILDIncumbents have the one thing building requires and startups lack: the ability to absorb a cost that only pays back once the layer is load-bearing.
  2. 2. INTEROPERATEThe built layer is only worth its cost if others connect to it; Interswitch's neutrality shows what terms make that possible.
  3. 3. COMPOUNDIncumbents leak their operational record to vendors and partners more than any other group; closing that leak is usually the highest-return move available.

Coalition or alliance builder

  1. 1. INTEROPERATEA coalition's only asset is the terms of connection between members; define them narrowly and operationally, as the Aadhaar interface did.
  2. 2. PERSISTCoalitions dissolve when the convening funder rotates; a fixed cadence and independent governance, as with the Ibrahim Index, is what makes them durable.
  3. 3. COMPOUNDEach member interaction should deposit something the coalition owns — a standard, a dataset, a method — or the coalition remains a meeting.

The 90-day entry protocol

  1. Days 1 to 15 — Locate the constraint

    Trace ten real failed transactions or stalled decisions end to end. Record the first point of breakage in each. Do not commission research; do the tracing with the people who own the work.

  2. Days 16 to 45 — Name one mechanism

    Select the single lowest-scoring move from your profile and define one mechanism that would move it from espoused to mechanized. It must have an owner, a budget line and a cycle time measured in weeks.

  3. Days 46 to 75 — Run the loop three times

    Execute the mechanism at least three times. Three cycles is the minimum needed to distinguish a working mechanism from a successful first attempt driven by leadership attention.

  4. Days 76 to 90 — Fix ownership of the deposit

    Establish where the residue of each cycle accumulates and who holds title to it. Move the record, the method or the relationship in-house before the mechanism scales.