About Randow Maps

Randow Maps make strategy visible.

Not to agree with, but to see, test and improve how it works.

Randow Maps show how actions can lead to outcomes

An actor, a team, customer or someone else, takes an action (green box) that generates (solid arrow) a thing like a capability, product, outcome, or feedback (gold box), that may be used by another actor.

In this map, a team procures and prepares ice cream. Using that ice cream, a customer feeds their kids, generating a benefit. In doing that, the customer generates a payment, which the team can use to procure and prepare more ice cream.

Most strategy models hide what's really going on

Much strategy work hides the relationships between actions and outcomes. People create beautiful graphics, and talk about goals, objectives and targets, but don’t make the logic between them explicit, so you can't see the gaps.

See some examples of strategy models clarified using Randow Maps.

A Randow Map is a hypothesis

A Randow Map can be clear and still be wrong. Every element is a claim that needs to be tested.

A Randow Map shows what must be true for a strategy to work.

The weakest link: use

Strategies usually fail at the point of use.

A product, capability, or insight only matters if someone actually uses it.

Randow Maps make that visible. If something is not used, the outcome will not happen.

Use Randow Maps to choose your next step

You can use Randow Maps to show:

• your core business model
• how it works today
• alternative ways it could work
• your next step
• what evidence would prove it

Influences

Randow Maps are gratefully influenced by:

• PRUB Logic (Dr Phil Driver) Projects → Results → Uses → Benefits.
• Lean, Agile and Product thinking – build-measure-learn loops.
• The Scientific Method – A Randow Map is a hypothesis to test.