Last month, one of my customers’ business leaders told me, with complete confidence, that value stream mapping was “an engineering thing.” He filed it somewhere below the strategy table, next to deployment pipelines and Jira boards. He’s right about where it started. He’s badly wrong about where it belongs now.

For about thirty years, we ran on a comfortable story: The business decides what it wants, and IT delivers it. Technology was a cost center, a service desk, a supporting act. I spent a good part of my career inside that story. It’s over. 

More than a decade ago, Marc Andreessen warned in the Wall Street Journal that “software is eating the world.”  Today, the meal is almost finished. In a digitalized company, the product is software-augmented, the supply chain is one of the data flows, and the customer relationship is an interface. And in the AI era, it goes one step further: At CES 2025, Nvidia’s Jensen Huang predicted that “the IT department of every company is going to be the HR department of AI agents.” (2) The function we used to treat as plumbing is now expected to hire, train, and manage a digital workforce. 

When the engine room and the boardroom run on the same machinery, the tools that map that machinery stop being technical. They become strategy. Two of them are climbing into the boardroom right now — Value Stream Mapping and Wardley Mapping are good examples, and I expect more tools born in IT to follow; look at what’s already happening in risk management. 

You Already Use “Promoted” Tools — You Just Don‘t Call Them That 

This is the part I watch leaders miss most often. The strategy tools you already trust were promoted from somewhere humbler. SWOT, the boardroom’s comfort blanket, came out of mid-century corporate planning. The flowchart you scribble on a whiteboard is the grandparent of your operating model. VSM and Wardley Mapping are climbing the same stairs.

Take Value Stream Mapping. Strip away the Lean vocabulary and it answers three questions every director already asks in some form: Where does value actually flow? Where does it stall? And where are we dangerously dependent on a single supplier, system, or person? In the companies I work with, the map almost always surfaces something the org chart hides — the same capability built three times in three systems, or eleven days quietly lost at one hand-off nobody owns. Those aren’t engineering questions. They sit behind every margin review and every acquisition. 

What Wardley Actually Said About Strategy 

Wardley Mapping is even more open about its boardroom ambition, and its creator is refreshingly blunt about why it exists. Simon Wardley, a former CEO whose book Wardley Maps has become a standard reference, built the method out of frustration with the very tools executives lean on. Looking back on years of running a company on instinct and good storytelling, he concluded the whole thing “had more in common with alchemy than chess.” 

His sharpest line lands on the boardroom’s favorite artifact. Picture a general on the eve of battle who admits he has no map and no feel for the terrain — “but have no fear, for I have created a SWOT diagram!” Wardley’s reaction: He’d “flee in panic.” 

I don’t read that as “SWOT is useless.” I read it as a warning. Most strategy tools describe your situation without telling you where you’re standing in it. Wardley Mapping exists to fix exactly that: To give leaders situational awareness before they commit. Or, in his own words, strategy is “the art of manipulating an environment to gain a desirable outcome.” You can’t manipulate an environment you can’t see. 

What Changes When These Tools Reach the Boardroom 

The moment a value stream map or a Wardley map enters an executive conversation, the conversation changes shape. “Engineering is slow” becomes “value stalls for eleven days at a hand-off we could remove.” “Should we build or buy?” becomes a visible bet on which capabilities are sliding toward commodity and which are still worth owning. The diagram stops being a deliverable and becomes the agenda: a shared view of where to invest, what to step away from, and what’s actually worth defending. 

And notice what just happened to you while reading this. If you’ve ever drawn a process on a whiteboard or argued about what to outsource, you’ve already built rough versions of both tools. You already think this way; you just haven’t had the right tools in front of you. That gap is easy to close. 

The One Question for Your Next Meeting 

So here’s the single thing worth carrying into your next leadership meeting: Stop asking whether a tool is “technical.” Ask whether it gives you situational awareness. 

The org chart is the worst possible map of where strategy actually lives today.

If you want to see this in practice — VSM used not for DevOps tickets but for digital-sovereignty calls, portfolio consolidation, and working out where AI genuinely belongs in a business — that’s the conversation we’re having at Flowtopia Live 2026, a community built around treating flow as a business discipline rather than an engineering chore. I dug into several of these examples in my recent Techstrong TV interview, if you’d like a preview.

The tools have already made the move from the engine room to the boardroom. So before your next strategy meeting, ask yourself one thing: Which ‘technical’ tool in your organization is already doing strategy work — and why isn’t it at the table yet?