My background is in software engineering and R&D leadership. But what kept pulling my attention wasn't the code — it was how people coordinate around complex work. That curiosity led me deep into Scrum, then Kanban (I co-authored the Kanban Guide and co-created Professional Scrum with Kanban), then SAFe (one of fewer than 50 SAFe Fellows globally).
Most advisors plant a flag in one framework and defend it. I went the other direction — because working across all of them revealed something more useful: every framework is solving a real problem, and every framework creates new problems if applied dogmatically. What actually helps organizations is understanding which constraint they're facing and choosing the right tool for it.
A good example is my work around invitation-based SAFe implementation: the emphasis is not rollout theater, but creating pull-based engagement so change sticks and performance improves.
Across global exchanges, consumer goods, enterprise software, and product-led scaleups, the same pattern kept appearing: teams asked to move faster while the system around them slowed them down. The constraint was almost never execution. It was how decisions were made, how work was prioritized, how funding flowed, and how many things were in flight at once.
That's what I work on — not which framework to use, but whether the operating system around your teams is capable of delivering the outcomes you actually need.
Are you serious about improving flow, focus, and impact? Let's talk.