A national campaign sold before it was built
Labatt The vision
Labatt had a national designated-driver campaign on the calendar. They'd booked the media, signed the partnerships, and announced the creative, including a feature that let people put their faces on superhero costumes, which would have been a serious build even with months of runway. They had fourteen days. The plan on the table was to ship native iOS and Android apps, which wouldn't clear app store review in time. Everyone on the team knew it. Nobody wanted to be the one to say it.
Making it real
I came in, looked at what was actually possible in the days we had, and said the quiet part out loud: drop the apps, build a high-performance web app instead. We did. I built a custom head-detection feature so the face-on-superhero piece worked in the browser, years before the AI tools that would have made it easy. Launched on time. Zero downtime through the LCBO event deployment and the national rollout.
Why this one matters
Most disasters in technical projects aren't surprises. They're things people know but can't make themselves say. Part of the Vision Builder job is to be the person who can say them, and then offer a real plan immediately, so the saying isn't criticism. It's a course correction.
A platform the team had given up on
Postmedia The vision
After a major acquisition, Postmedia ended up with a legacy platform running at 100% capacity, with chronic outages. The team had been close to the system for so long they'd stopped seeing it. Their honest belief was that they'd hit a hard physical limit. The vision had collapsed into a single belief: the only path forward was a multi-year, multi-million-dollar rebuild.
Making it real
I sat with the system for a few weeks before doing anything. Just looking. Reading code. Talking to people. There was a caching configuration the team had written off as too risky to change. I thought it was worth trying. We piloted it in a low-stakes corner first, where if it broke we could roll it back in minutes. Utilization dropped 40% almost overnight. Postmedia got eighteen months of breathing room to plan the real migration on its own terms.
Why this one matters
Sometimes the team closest to a problem is the team least able to see it. That's not a failure; it's just how proximity works. The Vision Builder's job here wasn't audacity, it was a fresh set of eyes and the willingness to ask 'have we tried this?' without it landing as a criticism.
A vision that had failed for a year
Anheuser-Busch The vision
Anheuser-Busch wanted a global employee portal on Salesforce Lightning. They'd been trying to build it for a year. It was non-functional. The team was demoralized, the executives frustrated, and corporate IT and the project team were talking past each other across multiple time zones. The vision wasn't the problem, it was a clear, reasonable thing to want. Nobody had been in the room with both the authority to decide and the willingness to talk to everyone.
Making it real
The platform was new to me too. I learned it on the way in. The actual problem wasn't technical, though; it was political. I took the role of the person who could make calls and talk to everyone, on every continent, in their own time zone. Brokered alignment between IT and the executives. Got a remote global team pointed in the same direction. Then we built. The portal launched in months and became a flagship piece of internal infrastructure.
Why this one matters
Failed for a year rarely means the vision is impossible. Usually it means nobody had the standing to make a call. That's not a code problem; it's a presence problem. Presence is part of what the Vision Builder brings.
A global event with no margin for error
Autodesk University The vision
Autodesk University needed to host more than 100,000 people simultaneously across 200+ countries. Personalization (who you are, what you're attending, what's relevant to you) at the same time as caching (which is what makes a site fast around the world). Those two things usually fight each other. The vision was both, at the same time, perfectly.
Making it real
We decoupled them. Personalization happened in one layer, caching in another, and they didn't trip over each other. The architecture wasn't standard at the time, but it wasn't exotic, just deliberate. Zero performance degradation, anywhere on the planet, for the duration of the event.
Why this one matters
Big global numbers usually come down to one or two specific architectural decisions made early. The Vision Builder's job is to find those one or two decisions before the event, not after.
A vision a decade ahead of the industry
Southam Newspapers The vision
In the early 2000s, Southam Newspapers (later Postmedia) needed to run dozens of newspaper sites without rebuilding each one from scratch. The industry standard at the time was monolithic, one big CMS doing everything, locked to a specific front-end. I had a different vision: content lives in one place, and can be presented anywhere. The industry didn't even have a name for it yet.
Making it real
I architected the headless platform and grew the team from one person, me, to more than fifty as it scaled. It became the backbone of what would grow into Canada's largest digital media network, serving millions of daily visitors.
Why this one matters
Sometimes the vision is yours, not the client's. The Vision Builder doesn't always wait for someone else to imagine the thing. When it's the right call, you build it, defend it, and let the rest of the industry catch up over the next decade.
A vision the wrong stack couldn't deliver
A startup pivot The vision
A startup I worked with was trying to find product-market fit in the Shopify ecosystem. Their vision required iteration speed, daily releases, fast feedback loops, the ability to try things and see. They'd inherited an enterprise architecture that assumed a slower world. They were doing everything right by the old playbook and moving through molasses anyway.
Making it real
We didn't rewrite. We re-tooled, stripped out the parts of the stack that assumed enterprise pace, kept what was durable, replaced what was heavy with lighter equivalents. They went from monthly releases to daily ones, found product-market fit within months, and grew from there.
Why this one matters
The right tools depend on the market you're in, not the market you came from. A team can be doing everything correctly by their old playbook and still be moving too slowly for the new one. Recognizing the mismatch is half the work. Building the right replacement is the other half.