By turning the vision into something people can react to, then letting real users and the people who'd run it try to break it. Done well, it takes weeks, not quarters, and it tells you what to fund first.
Here's the process we use, step by step.
A vision statement can't be tested. A bet can. Rewrite the vision as a short list of things that must be true for it to work. For example: "Customers will switch to self-service for simple requests" or "Staff can handle the new process without extra training." Each bet becomes something to prove or disprove.
Leaders hold the ambition. Frontline teams know what actually happens. You need both before you design anything.
When UNSW wanted to speed up how good ideas moved into action, we interviewed 16 executives one to one, ran stakeholder workshops across the university, and spoke with the IT team's own internal customers.
Turn the riskiest bets into something people can see and use. Storyboards for services, clickable prototypes for digital products, a walk-through for a new process. Keep it rough. The goal is a reaction, not approval.
Put it in front of the people it's for. Score each bet on three questions:
Bring the evidence back to a small panel of decision-makers and the people who'll deliver it. At UNSW, a 15-person panel reviewed the findings before the direction was locked in. That step turns a design team's recommendation into an organisation's decision.
The output isn't a report. It's a clear vision people have seen work, and a sequenced program of work. At UNSW, that meant a vision for an innovation accelerator and a program to deliver it.
Use it before a big investment is approved, when leaders disagree about direction, or when a program has stalled and nobody can say why.
For why this matters, read why vision alone won't drive digital transformation.
Related: Innovation coaching and Our approach.