Yeret Agility

Why is our delivery still slow after going Agile?

Adding Agile ceremonies to a broken delivery system makes it more bureaucratic, not faster. The real constraint is usually upstream: too many parallel initiatives, unclear ownership, funding locked into projects rather than products, or leadership engagement patterns that create dependency chains. Yuval diagnoses which of these is the primary bottleneck and works with your leaders on the minimum effective changes to unlock flow.

We keep hiring more engineers but output doesn't increase. What's going on?

This is one of the clearest signs of a systemic flow problem — usually excessive work in progress, cross-team dependencies eating capacity, or a portfolio that is funding too many things at once. Adding headcount to a constrained system does not increase throughput; it adds coordination overhead and slows everything down further. The fix starts with mapping where work actually gets stuck.

How do we fix OKRs that have become an administrative burden?

OKRs fail in predictable ways: goals set too high in the organization, disconnected from day-to-day work, updated quarterly in a ritual that nobody believes in. The fix is not a better template — it is reconnecting OKRs to the work funding decisions and team priorities actually drive. Yuval has run the Fixing OKRs live series and advisory work with dozens of organizations to rebuild OKR systems that create real traction.

We're using SAFe but PI Planning hasn't improved our delivery speed. Why?

SAFe's mechanics — PI Planning, ARTs, iterations — are scaffolding. If the underlying product model, team topology, or funding structure haven't changed, the scaffolding creates overhead without improving flow. As one of fewer than 50 SAFe Fellows globally, Yuval has seen every failure mode and knows which SAFe practices actually drive speed versus which ones are theater in a given context.

Why are our AI pilots not producing ROI, and how do we move from AI adoption to business impact?

Most AI investments fail not because the technology doesn't work, but because the operating system around it isn't built to absorb the speed. AI pilots succeed in isolation, but scaling them creates 'acceleration whiplash'—where code/content generation is faster than downstream review, validation, and adoption. Moving to impact requires aiming human + AI capacity at business constraints, redesigning workflows, and shifting to a staged, evidence-based funding model.

What does a Clarity Call with Yuval look like?

A 45-minute structured diagnostic conversation. You describe your current delivery system, the symptoms you're seeing, and what you've already tried. Yuval shares a frank read on what's likely driving the problem and what high-leverage moves look like. You'll walk away with useful diagnostic insight regardless of whether you proceed.