# What Operators Know That Consultants Don't — Pilot to Production

> Consultants see the org chart. Operators see what actually runs the business. Why operator experience changes how you build technology.

Canonical: https://thegrowthproject.com/podcast/what-operators-know/

*Pilot to Production*, the Growth Project podcast — hosted by Sam and Maya.

- Listen: https://thegrowthproject.com/podcast/what-operators-know/
- Read the article: https://thegrowthproject.com/blog/what-operators-know/
- Audio: https://thegrowthproject.com/audio/podcast/what-operators-know.m4a?v=0e965505

## Transcript

**Sam:** Seventy percent of digital transformation projects fail. Two point three trillion dollars wasted, globally, every single year.

**Maya:** And most of that money went to people who left before the consequences ever showed up.

**Sam:** Welcome to Pilot to Production, from the Growth Project. I'm Sam.

**Maya:** And I'm Maya. Today: what operators know that consultants don't, and why that gap is where your transformation budget goes to die.

**Sam:** Okay, set it up for me. Consultant versus operator. What's the actual difference?

**Maya:** Consultants see the business from the outside. Operators see it from the inside. Consultants optimise for the recommendation. Operators optimise for Monday morning.

**Sam:** That sounds like a slogan. Make it real.

**Maya:** Here's the pattern, dozens of times over. A consultant comes in, spends six weeks, interviews stakeholders, produces a fifty-page deck. Recommends digital transformation, or system modernisation, or whatever the buzzword is. Then they leave. And nothing changes.

**Sam:** Why nothing? They did the work.

**Maya:** Because they never had to live with the consequences. They didn't see the sales rep who still uses the spreadsheet, because the CRM takes forty-seven clicks to do what Excel does in three.

**Sam:** Forty-seven clicks. I've felt that in my soul.

**Maya:** They didn't know about the workaround Jess in operations invented because the approved process doesn't handle returns properly. They didn't understand why the team ignores the dashboard, because by the time it updates, the information is already stale.

**Sam:** So the consultant sees the org chart.

**Maya:** And the operator sees the shadow org chart. The one that actually runs the business.

**Sam:** Alright, you've been the operator. Years of it. What does that actually teach you?

**Maya:** Four things. First, plans don't survive Monday morning. Every plan looks good in the Friday afternoon meeting. Then Monday happens. The edge case nobody considered. The integration that times out. The team member who's on leave.

**Sam:** And you learn that where, exactly?

**Maya:** At eleven pm, fixing something that wasn't supposed to break. Second thing: the workarounds ARE the process. Every business has the documented process and the real process. The real one has sticky notes, tribal knowledge, and "just ask Sarah" steps that never made the workflow diagram.

**Sam:** And consultants want to delete all of that.

**Maya:** Consultants try to eliminate workarounds. Operators know some of them are load-bearing. Remove the wrong one and everything collapses.

**Sam:** Third?

**Maya:** Best practice isn't always best. Best practice just means what worked for someone else, somewhere else, at some other time. Your constraints are different. Your team is different. Your customers are different. I've seen best-practice implementations fail spectacularly because nobody asked whether the practice actually fit the context.

**Sam:** And the fourth?

**Maya:** Speed to value beats perfection. A seventy percent solution shipped today beats a hundred percent solution planned for next year. Because by next year the requirements changed, the team changed, the market changed. Get something working. Iterate.

**Sam:** Let me push on the failure numbers, because they're brutal. Seventy percent across the board?

**Maya:** McKinsey puts technology project failure at seventy percent. Bain's twenty twenty-four study says eighty-eight. And the Standish Group found only thirty-five percent of projects finish successfully.

**Sam:** So two out of three, minimum, just don't make it. The usual explanation is scope creep, budget, complexity.

**Maya:** All real. But I'd add one. The people designing the solution never had to operate one. They've never been woken at two am because the integration failed. Never explained to a customer why their order vanished.

**Sam:** And that changes how you build.

**Maya:** Completely. When I design a system now, I'm not thinking about the happy path. I'm thinking about what happens when the API is down, the data is messy, the user does something unexpected, the person who understands the system leaves, or it's four pm Friday and something breaks.

**Sam:** You call those edge cases.

**Maya:** I call them Tuesday. They're not edge cases. They're just Tuesday.

**Sam:** Okay. First thing tomorrow. Someone's hiring a partner this week. What do they do differently?

**Maya:** Stop hiring for advice. Start hiring for consequences. Four questions. One, ask about failures. Consultants talk about successes. Operators talk about what broke and what they learned. If someone can't tell you about a system that failed and why, they've never been close enough to the work.

**Sam:** Two?

**Maya:** Ask about workarounds. "How do you handle processes that exist outside the official system?" If they say "we document and formalise everything," they don't understand how businesses actually work.

**Sam:** Three.

**Maya:** Ask about maintenance. Who monitors it? Who fixes it at eleven pm? Who owns it when the project team moves on? If they can't answer, they're not thinking past go-live.

**Sam:** And four.

**Maya:** Ask for operator references. Not client logos. People who worked alongside them, who saw what happened after the deck was delivered.

**Sam:** And if it all sounds like a sales pitch?

**Maya:** Keep looking. Advice is cheap. Execution is expensive. The gap between a good recommendation and a working system is enormous, and it's filled with edge cases, workarounds, politics, and eleven pm fixes.

**Sam:** This has been Pilot to Production, from the Growth Project. If you've got a fifty-page deck and nothing's changed on Monday, that's the gap we close, at thegrowthproject.com.

**Maya:** Thanks for listening. See you next time.