Most organizations that have invested heavily in Agile and DevOps share a puzzling experience. Deployment frequency is up. Teams are busy. Dashboards are green. And yet value still queues. Strategy still takes months to reach the customer. Feedback still arrives too late to change anything important.
Flow coach Marnus Marx has a name for this condition and a useful analogy. “Speed is not flow,” he says. “Responsiveness is not flow. And automation without systemic alignment simply accelerates chaos.” His analogy is butterfly swimming—the most technically unforgiving stroke in the pool. You cannot muscle through bad timing. If arms, legs, and breath fall out of sync, the swimmer stalls, and fighting harder only creates more drag.
Organizations, he argues, work the same way. Agile without flow becomes theatre. DevOps without systemic alignment becomes an expensive tooling investment that speeds up the wrong things.
The uncomfortable conclusion is that most transformation programs have optimized activity rather than outcomes. Teams are faster. The underlying system is not.
Making the Invisible Visible
The discipline that most consistently exposes this gap is Value Stream Mapping. Originally a manufacturing technique, Value Stream Mapping has moved decisively into software and product delivery—but its practitioners are increasingly arguing that its real scope is broader still.
Jack Maher sees Value Stream Mapping as the connective tissue across the proliferating landscape of frameworks that most enterprises now run simultaneously: Agile, DevOps, TOGAF, ITIL, and whatever comes next. The problem these frameworks share isn’t that they’re wrong—it’s that they each illuminate part of the system while leaving other parts in shadow. Value Stream Mapping forces the whole flow into view.
The practical results Jack cites are significant. Future-state redesigns based on Value Stream Mapping have halved deployment lead times in documented cases. MVP strategies informed by value stream analysis have shortened time-to-first-value by 30 to 50%.
Feature flag and canary release approaches, when aligned to a clear map of the delivery flow, have reduced production incidents by 30 to 60 percent. Technical debt—often invisible until it consumes a third or more of engineering capacity—becomes measurable and therefore manageable. Zombie features, the ones nobody uses but everyone maintains, can finally be identified and retired.
Marcin Karkocha extends this argument further, and in a direction that many Value Stream Mapping practitioners haven’t yet followed. Value Stream Mapping’s core principles — making work visible, identifying waste, measuring flow — are not specific to manufacturing or software delivery. They apply wherever value moves through a system. Marcin has used the same technique for IT strategy assessment, pre-sales pipeline optimization, digital sovereignty evaluation, and license portfolio consolidation. “Think of it as the new SWOT,” he says—a universally applicable diagnostic that adapts to whatever business question needs answering.
He adds a practical note on tooling that’s easy to overlook: The right mapping tool depends on the nature of the value stream. A numbers-heavy financial flow often works better in a spreadsheet than on a visual board. A complex, multi-team IT delivery process needs the spatial thinking that a tool like Miro provides. The map itself should be an accelerator, not a bottleneck.
The Practice of Mapping
Understanding Value Stream Mapping conceptually and being able to use it under real conditions are different things. Miguel Dias compresses the gap between them. His approach takes the essentials of a full Value Stream Mapping engagement—exercises that would normally take 10 or more hours— and makes them actionable in a single, focused session: map an actual delivery workflow, measure handovers, identify constraints, and leave with a prioritized action plan.
The key move, he argues, is shifting from gut feel to quantitative insight. Most people have a rough sense of where work slows down in their process. Mapping makes it precise, which changes the conversation from opinion to evidence.
When Flow Isn’t Enough
Here is where the picture gets more complicated, and where Phil Clark enters with what may be the most important—and most frequently missed—part of the argument. Flow improvements, when they happen, tend to happen faster than the leadership systems around them change. Teams adopt better practices. And then funding resets, priorities churn, teams are reorganized, and the metrics revert to measuring output rather than business impact.
“Flow and Realization are both essential,” Phil says. Flow describes how work moves through the system. Realization describes whether the work produced the intended result. Most organizations measure the first and neglect the second—partly because outcomes often have a long tail, and closing the loop requires a discipline that doesn’t fit neatly into quarterly cycles.
His broader point is structural: Leadership choices determine whether better ways of working survive. What leaders fund, protect, measure, and reinforce either sustains the gains or quietly erodes them. AI, he notes, amplifies this dynamic rather than resolving it. An AI-augmented system that is well-led gets better faster. One that isn’t gets worse faster.
It doesn’t have to be this way. The tools exist. The frameworks exist. The measurement techniques exist. What most organizations are missing is the systemic view that connects them—a clear picture of how value actually moves from idea to customer outcome, where it stalls, and what leadership choices either protect or undermine the improvements teams work hard to make. Flow is not speed. Flow is smoothness. And smoothness, it turns out, requires looking at the whole system.
These ideas will be explored in depth at Flowtopia Live on June 24.
Exclusive Offer: As part of the TechStrong community, get a free LIVE pass.
Use Code: TECHSTRONGFLOW
Get your Live Pass to Flowtopia Live 2026 here.
