For businesses that have outgrown how they run.
The problem usually isn't effort.
Nobody built it wrong. It just didn't get rebuilt.
I get called in after a team has already tried the obvious fixes. More meetings. A new tool. A reminder in Slack to 'just follow the process.' None of it holds, because the problem was never the people in the room.
I help scaling companies replace escalation-driven execution (the operational friction that builds as you grow) with operating systems that hold under scale.
Learn moreContents
The visible issue is often only the entry point. The real work is understanding what the pattern is hiding.
The problem is almost never effort. It is almost always the system around the work. Diagnosing that system before redesigning it is the only way to fix it durably.
Leaders are great at diagnosing their pain. They're not great at diagnosing what's causing it. The pain is the symptom. The operational breakdown underneath is the cause, and that's the part I go after.
The leaders I work with are at the edge of something. A reorg. A headcount that doubled in a year. A business that just closed a round and outgrew the way it used to run. How they worked before doesn't work anymore, and they know it before they can name why.
A missed handoff, delayed decision, stalled lead, or broken workflow usually points to something deeper: unclear accountability, weak system design, missing context, or a process that no longer matches how the business operates.
I bring diagnostic judgment and hands-on leadership to that moment. The work starts by identifying what is actually slowing execution down, then aligning stakeholders around the real issue before building new structure. It runs on one rule: every recommendation traces back to evidence from inside your business. If I can't trace it, I don't recommend it. That is the difference between fixing the presenting symptom and fixing the structure underneath it.
The work is diagnostic before it is prescriptive.
The goal is to identify what is slowing execution before more process, tools, or structure are added.
Diagnose
Design
Own
A short, bounded engagement to identify which cross-functional operating problems are real, systemic, and costly enough to warrant intervention. The output is not insight alone. It is a clear view of what needs to be fixed, why, and what success looks like. Every finding in the diagnostic traces to evidence from your own business. Nothing is recommended that cannot be shown.
Once a problem is validated, I design the operating model around it and stay accountable until it holds. This includes structure, decision rights, cross-functional workflows, and escalation paths. The engagement ends with a clean handoff to an internal owner, not an open-ended retainer.
Ongoing embedded operational leadership for companies that need a senior operator inside the business on a continuing basis. I own cross-functional system health, run the governance cadence, catch drift early, and keep execution aligned with where the business is going.
Representative engagements with scaling companies and enterprise teams, where the visible problem pointed to a deeper operating constraint.
Visible issue: A longstanding financial services business had outgrown the tools behind it. Manual workflows, disconnected reporting, blind spots, and outdated client communication were slowing the business down.
What was underneath: The business lacked visibility across workflows, customer communication, deadline risk, and revenue attribution.
What changed: A more connected operating model with reduced manual dependency, stronger accountability, and a leadership team that could see across the business for the first time.
Visible issue: A growing business was struggling to move inbound opportunities through the sales process consistently. Leads were being routed differently across teams, follow-up varied by rep, and important opportunities were getting stuck or lost entirely.
What was underneath: The issue was not capacity alone. Sales workflows had evolved unevenly as the business grew, and different teams were operating with different assumptions about ownership, routing, and escalation.
What changed: A single authoritative lead flow model with defined ownership, routing rules, and fallback behaviour that held as volume continued to grow.
Visible issue: A large B2B organization was seeing repeated late-stage escalations across enterprise deals. Different functions were involved, ownership was unclear, and leadership discussions looped without resolution.
What was underneath: The breakdowns lived between teams, not inside them. Critical decisions were made too late, cross-functional handoffs depended on judgment rather than design, and each function believed the problem sat elsewhere.
What changed: A cross-functional diagnostic clarified decision sequencing, accountability, and handoff logic across the revenue motion. Exception paths were reduced and the organization moved from exception-driven to designed execution — without a reorg or headcount increase.
Built inside complex operating environments.
Companies call me about the thing that's visible. A stalled deal, a broken handoff, a rollout that stopped working. It's almost never the actual problem. I get the right people looking at the real one. Sometimes that's the whole engagement, a clear, evidenced answer to what's actually wrong. When it goes further, I build what the business needs next, then hand it off. Either way, the work isn't finished until whoever's holding it can run it without me in the room.
This grew out of two decades inside fast-moving, regulated businesses. Fintech, payments, the places where the rules matter and the stakes are real. Square, Afterpay, American Express. I watched execution get harder every single time a team scaled and the systems underneath it didn't keep up.
And it was always the same pattern, no matter the function or the industry. Workarounds quietly become the norm. Nobody's sure who owns what anymore. Decisions get made and six months later nobody remembers why. Everyone burns more energy managing the mess than moving the work forward.
I came up through legal. That's where I started, not where I stayed. Legal taught me to protect the reasoning behind a decision, not just the outcome. GTM showed me exactly where execution breaks down between teams. Strategic operations taught me how fast everything slows when workflows, accountability, and decision-making drift out of alignment. Those layers are why, when you bring me in, I'm thinking about all of it at once.
I write about this every month in The Issue Underneath the Issue, my newsletter on LinkedIn.
Start with a diagnostic conversation
Start with a diagnostic conversation
Tell me a little about what's going on. I read every message myself.