I've sat on both sides of the consulting table. As a VP hiring consultants, and now as a consultant myself. The pattern is painfully consistent.
A leadership team identifies a problem — operations are straining under growth, digital transformation is stalling, AI strategy is unclear. They hire a consulting firm. The firm sends smart people who conduct interviews, gather data, and build a comprehensive analysis. Eight weeks later, the team receives a beautifully designed slide deck with strategic recommendations.
Six months after that, the deck is in a shared drive nobody opens. The problems persist. The team is back to square one, except now they're also cynical about consultants.
Where the Model Breaks
This isn't because consultants are bad at analysis. Most are quite good at it. The model breaks at the handoff between "what should change" and "how to actually change it." Strategy without execution is an academic exercise. Execution without strategy creates chaos. Most consulting engagements live entirely in the first category.
The standard consulting approach treats organizations like case studies. Diagnose from the outside, prescribe from a framework, present to leadership, and leave. But organizations aren't case studies. They're living systems with informal power structures, tribal knowledge, competing priorities, and deeply embedded habits that no slide deck can overcome.
What Practitioner-Led Consulting Looks Like
After twenty years of leading transformation from the inside and building teams, shipping systems, surviving core banking conversions, running lean programs. I've developed a fundamentally different view of how consulting should work.
Start with the management system, not the strategy document. If an organization can't make performance visible, create accountability rhythms, and surface problems before they become crises, no amount of strategic clarity matters. The first question isn't "what should we do?" It's "do we have the operational discipline to execute anything at all?"
Build capability, not dependency. Every engagement should aim to make the consultant unnecessary. That means coaching leaders, building internal skills, and creating systems that the team owns. If the organization needs you to come back every quarter to keep things running, you haven't built anything. You've created a subscription.
Work across silos, not within them. The most important problems in scaling organizations don't live in one department. They live in the hand-offs between departments. This is where ops meets technology, where strategy meets execution, where innovation meets governance. A consultant who only understands one domain produces recommendations that break when they hit the next silo.
Prove it with your own work, not just your recommendations. This is the hardest test, and the one most consultants fail. Can you show me something you've actually built? A system you've implemented? A program you've run? A team you've coached through a real transformation? If the answer is "I've advised on that," we're back to slide decks.
The Lean Lens
My approach is rooted in lean thinking. Not the superficial version with Kanban boards and just sticky notes, but the fundamental discipline of eliminating waste, making work visible, and building systems that improve themselves. However, I do spend a lot of money on sticky notes.
When I assess an organization's operations, I'm looking for specific things. Are there daily management systems that make performance visible? Do leaders have structured rhythms for reviewing work and coaching teams? When problems surface, is there a systematic process for root cause analysis, or does the organization just fight fires? Are improvements sustained through standard work, or do they decay as soon as attention shifts elsewhere?
These aren't glamorous questions. They don't make for exciting slide decks. But they're the questions that determine whether any strategic initiative such as digital transformation, AI adoption, growth scaling actually delivers results.
What to Look For in a Consulting Partner
If you're evaluating consultants, here's what I'd suggest looking for regardless of whether you work with me or someone else.
Ask about implementation, not just analysis. "What does the engagement look like after you deliver recommendations?" If the answer is "that's a separate phase" or "we can support implementation for an additional fee," you're buying a slide deck.
Ask about sustainability. "What systems or capabilities will my team have after you leave?" If the answer focuses on deliverables (reports, frameworks, playbooks) rather than team capability, the value walks out the door with the consultant.
Ask about cross-functional experience. Real transformation touches operations, technology, people, and culture simultaneously. A consultant who only has depth in one domain will produce recommendations that sound right in theory and break in practice.
Ask to see something they've built. Not advised on. Built. Led. Implemented. Shipped. This is the fastest way to separate practitioners from theorists.
The best consulting engagement feels like gaining a teammate who's done this before, not like hiring an outsider who studies your problems and writes about them.
The Real Test
Here's the question I ask myself: "Will this organization be measurably better six months after I leave, without me?"
If the answer is yes because we built systems, coached leaders, and created operational discipline that the team owns. Then the engagement was worth it. If the answer depends on whether they follow the slide deck, we've failed before we've started.
That's the difference between consulting that delivers results and consulting that delivers documents. And it's why I believe the industry needs more practitioners and fewer presenters.
Tired of slide decks that gather dust? Let's talk about what a practitioner-led engagement actually looks like.