Blockchain Strategy Map
A blockchain strategy map is Kaplan and Norton's strategy map applied to a blockchain initiative: it forces you to show how a technical capability at the base actually causes the financial result at the top, link by link.
Four bands stack on top of each other, arrows climbing from the technical foundation up to the financial outcome at the peak.
Reach for this when…
- A blockchain project has a budget and a roadmap but nobody can explain how it makes the business more money.
- Different teams, technical, finance, operations, each tell a different story about why the initiative matters.
- You need to defend the initiative's next funding round to people who don't care about the technology.
How to run it
- Start at the top: name the financial result the initiative must eventually cause.
- Below it, name the customer outcome that would justify that result - trust, speed, lower cost to the buyer.
- Below that, name the internal process the technology actually changes - settlement, provenance, reconciliation.
- At the base, name the capability that has to exist first - the network, the nodes, the skills, the governance.
- Draw the arrows between layers and check every link is causal, not just plausible.
- Cut anything on the map that has no arrow leading up to the financial result.
A worked example
Situation. Zhang Wei runs digital strategy at Jinshu Components, a mid-size components manufacturer in Chengdu, China, funding a blockchain pilot for supply-chain financing that finance kept calling 'a science project'.
Applied. He built the map top-down: faster invoice financing (financial), suppliers trusting Jinshu's payment terms enough to offer better prices (customer), automated proof-of-delivery on the ledger (process), and a working consortium of three tier-one suppliers (foundation).
Result. The map showed finance exactly which supplier needed onboarding next to move the financial number, and the 'science project' framing stopped the same week.
The catch
The map shows the causal chain you believe in, it does not prove the links hold - a map full of confident arrows can still be wrong at every layer. It also tempts teams to simplify a messy, multi-stakeholder blockchain governance problem into four tidy boxes.
If you can't draw an arrow from the base capability to the top financial line without a leap of faith, the initiative isn't ready to fund.
Origin: Kaplan & Norton (Strategy Map), applied to blockchain