In most enterprises, the engineering team isn’t the bottleneck. The real constraint sits higher up: A persistent, structural gap between strategy and execution that no amount of sprint velocity can close. Leaders set direction, teams ship features, and somewhere in between, value gets lost. If you can’t trace a story on your backlog to an outcome leadership actually cares about, you’re not managing value—you’re managing hope. 

Four practitioners are challenging that reality with a connected set of ideas. Together, they make the case that effective digital delivery isn’t about better tooling or faster teams. It’s about rebuilding the operating system underneath the work. 

The Framework Trap 

When delivery feels broken, organizations reach for frameworks. OKRs are the current favorite. Nida Khan, Product Manager at Paymentology, has watched this play out enough times to know it rarely ends well—and she’s direct about why.

“OKRs don’t invent strategy,” she argues. “They’re a communication and alignment tool. They only work as well as the thinking, priorities, and leadership standards behind them.” 

Khan identifies three failure modes she sees repeatedly. First, teams in mature products feel pressured by OKRs to dress up maintenance work as growth bets, creating tension without creating value. Second, organizations claim to pursue outcomes but still reward delivery—so key results quietly become feature checklists, everything turns green, and the business stays flat. Third, companies try to install product sense through templates and workshops, when what’s actually missing is judgment, not process. 

The fix, she argues, isn’t a better framework. It’s returning to fundamentals: Clear strategy, causal metrics, honest incentives, and a higher bar for product capability. Diagnose the system before blaming the format. 

The Missing Anchor 

Even when leadership standards are strong, something often goes wrong between strategy and the team. Rich Allen, author of User Needs Mapping, has spent years studying this gap and has identified a structural problem that most organizations overlook: User needs are rarely made explicit. 

“Many organizations jump from strategy to initiatives without a clear translation layer rooted in real user needs,” Allen explains. “When user needs remain implicit, outcomes become fuzzy, and alignment becomes effortful.” 

His technique, User Needs Mapping, is a collaborative visual approach that surfaces dependencies, clarifies ownership, and helps teams understand where coordination overhead is coming from. The insight is that alignment isn’t primarily a communication problem—it’s a structural one. Tight coupling, unclear ownership, and implicit assumptions 

create friction even in capable teams. Make user needs visible, and you create the conditions for clearer priorities, safer autonomy, and better local decision-making. 

The question Allen leaves organizations with is deceptively simple: what would change if user needs truly shaped how you organize, fund, prioritize, and measure work? 

Flow First 

With strategy clarified and user needs anchored, the focus shifts to how work actually moves. Marco Ferra, engineering leader at Sky, takes a deliberately unfashionable angle: He goes back fifty years to the Toyota Production System to make the point that world-class operational efficiency isn’t new—it’s just consistently underapplied in software. 

Ferra introduces the TIMWOOD framework—Transportation, Inventory, Motion, Waiting, Overproduction, Overprocessing, Defects—as a lens for making the seven wastes of software delivery visible. Alongside this, the concepts of Muri (overburdening), Mura (fluctuation), and Muda (waste) give teams a vocabulary for what they’re seeing. 

His central principle: Stop pushing work into teams and start designing for pull. Kanban signals, continuous flow, and regular Gemba walks—going to where value is actually created and asking why problems exist—are the mechanisms. The Kaizen mindset underpins it all: everything done today can be improved. Applied to the SDLC, these aren’t manufacturing metaphors. They’re precise diagnostics for a system that most organizations have never properly examined. 

Seeing the Whole 

Individual team-level improvements only take you so far. Joshua Barnes makes the case that without end-to-end visibility, even well-run teams operate inside a broken system. Strategy sits in one place, portfolio decisions in another, delivery somewhere else—and leaders reconcile the gaps with status reports and gut instinct. 

Barnes advocates building a portfolio backlog structured around Value and Innovation Increments, not project lists or undifferentiated demand. The goal is a fully visible chain: Strategic Outcomes cascade into Initiatives, which decompose into Increments, which flow into Features and Stories. When that chain is intact, every piece of work in progress can be traced to an outcome leadership actually cares about. 

Kanban boards applied at every level of this hierarchy make bottlenecks visible. And for organizations that feel the gap between where they are and where they need to be, Barnes introduces Quick Starts—low-friction entry points that allow improvement to begin without waiting for a transformation. 

The diagnostic question he offers is worth sitting with: When you look at how value moves through your enterprise, are you seeing the end-to-end flow, or are you seeing a stitched-together view of silos and calling it strategy? 

Nida Khan, Rich Allen, Marco Ferra, and Joshua Barnes are all speaking at Flowtopia Live on June 24. If you want to engage with these ideas directly—and pressure-test them against your own organization—this is the place to do it. Rich Allen will also be giving away copies of his book, User Needs Mapping, as a flash prize for lucky attendees—make sure you’re in the event chat for that. 

Join us on June 24th. 

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.