You can't test a strategy deck. You can test a prototype.
That's the gap most digital transformation programs fall into. The vision is clear and the ambition is real. But nobody has seen it work with the people who'll use it, or the people who'll have to run it.
Every transformation vision quietly makes three bets:
A strategy document can argue all three. It can't prove any of them. Most programs find out which bet was wrong after the money is spent.
The fastest way to test a vision is to make it real enough to react to. That might be a storyboard, a clickable prototype, or a walk-through of a service that doesn't exist yet.
On Sydney Metro's Pitt Street station bid, we used journey mapping and virtual reality prototypes. People could walk through the station and react to it before anything was built. Problems that would be expensive to fix once built could be found and fixed in a model.
Executives approve the vision. Frontline teams decide whether it works. They know where the current process breaks, what customers really ask for, and which workarounds keep things running.
Put the prototype in front of them early. Their objections are the cheapest risk register you'll ever get.
Don't prototype the whole vision. Find the one assumption that would sink it if it were wrong, and test that first. It's often not the technology. It's whether people will change a habit.
Transformation needs money, and money needs confidence. A board will back a prototype that real customers have used far more readily than a slide that says customers will love it. The evidence also gives delivery teams something concrete to build toward.
This is what design thinking is for. Not workshops and sticky notes, but turning a vision into something people can try, break and improve before you commit. Here's how that process works, step by step.
Related: Innovation coaching and Our approach.