Director of Delivery · APMO · Transformation Leader
I help organizations build capability, remove friction, and create environments where teams operate with true ownership — not dependence.
How I Think
Organizations struggle when priorities compete, systems become fragmented, and teams lose visibility into outcomes. My approach focuses on creating scalable operating models that improve predictability, reduce friction, and enable teams to execute with ownership and confidence.
I prioritize systems that simplify complexity, governance that creates alignment, and coaching that builds long-term capability rather than dependency.
Clarity creates speed.
Featured Conversations
Applying Agile Beyond Engineering Teams
Conversation on operational clarity, delivery maturity, and how Agile principles can improve execution across technology and business organizations.
Selected Transformation Work
Scaling Delivery Predictability Across a Multi-Product SaaS Organization
Challenge
Over a 12-month period, a rapidly growing global SaaS organization expanded across multiple product lines and delivery teams. As growth accelerated, teams developed very different ways of managing intake, prioritization, and delivery planning. Some teams were highly structured. Others relied heavily on Slack messages, side conversations, and escalation requests to move work forward.
In practice, this meant leadership was often making roadmap commitments without a reliable picture of what teams were actually able to deliver.
The friction started showing up everywhere. Dependencies surfaced late. Priorities changed faster than teams could absorb them. Delivery discussions became increasingly reactive, especially as the organization continued scaling.
At that point, the issue wasn't effort. Teams were working hard. The problem was visibility and consistency across the portfolio.
Approach
I led the scaling and operational restructuring of an Agile Program Management Office (APMO) supporting six product lines within a global SaaS environment.
The temptation in situations like this is to over-engineer the solution. More governance. More process. More approvals. We went the other direction.
Instead of forcing identical workflows across teams, we focused on establishing a smaller set of shared operational expectations around intake, prioritization, dependency management, and delivery visibility.
One of the biggest changes was introducing a more structured intake model. Work could no longer quietly enter delivery teams through side conversations or leadership escalations without visibility into capacity or competing priorities. That sounds simple, but it changed a lot of downstream behavior.
I also partnered closely with delivery leadership and Scrum Masters to create more consistent KPI visibility across product lines and improve how delivery risks and dependencies were surfaced. Some teams adapted quickly. Others needed more coaching than expected.
Outcome
Within 12 months, the organization established a more scalable and predictable delivery operating model across multiple product lines.
Beyond the metrics, leadership had a much clearer picture of delivery capacity, roadmap risk, and execution health across the portfolio. Planning conversations became more grounded, and roadmap commitments became easier to make with confidence.
The APMO scaling — from 3 to 7 practitioners in 9 months — was probably the clearest signal that the operating model was creating value across the organization.
Details have been generalized to respect confidentiality and organizational privacy.
About
Most delivery problems aren't execution problems. They're clarity problems — unclear priorities, fragmented visibility, and operating models that haven't kept pace with organizational growth.
My work focuses on the conditions that make consistent delivery possible: shared operational expectations, governance that creates alignment without overhead, and coaching that builds capability rather than dependence. I don't believe in process for its own sake. Every system I build is designed to make teams faster, clearer, and more autonomous — not more reliant on a framework or a consultant.
I've spent 12+ years working inside complex, scaling SaaS organizations. That context matters. I understand the difference between what looks good in a process diagram and what actually works when priorities are shifting, teams are under pressure, and leadership needs answers they can trust.
The measure of success for any engagement is simple: does the organization perform better after I leave than when I arrived?
Leadership Principles
Services
Most teams don't underperform because of skill gaps. They underperform because ownership is unclear, decision-making is centralized, and no one has built the conditions for consistent execution. I work with leaders to redesign how teams are structured, how accountability is distributed, and how performance is sustained — without creating dependence on a single leader or process.
The initiative is usually sound. The gap is between what gets decided in the room and what actually changes on the ground. I help organizations close that gap — aligning stakeholders early, managing resistance before it becomes friction, and keeping teams focused and moving through uncertainty. Transformation that doesn't reach the team level isn't transformation.
If delivery commitments are slipping, priorities are colliding, or leadership is losing visibility mid-program, the problem is rarely effort. It's usually structure. I come in, establish governance that fits your environment without adding overhead, and create the visibility and execution consistency that makes reliable delivery possible.
Most Agile coaching produces teams that are fluent in the framework but still dependent on the coach. That's not the goal. I build the practices, habits, and decision-making clarity that outlast the engagement — so teams continue to improve after I leave. That's the measure of whether it worked.
How I work
I approach delivery and transformation by focusing on three things: making priorities clear, establishing scalable systems, and coaching teams to operate independently.
My goal is never to create reliance on process or leadership — it's to build environments where teams consistently deliver outcomes without friction. The measure of success is a team that doesn't need me.
Let's connect
If you're working on improving predictability, building high-performing teams, or navigating transformation — I'd love to talk.