Most consultants arrive with the framework before the conversation. That's the problem, not the solution. 

You've probably been through this before.

A firm shows up with a deck. Nice logo. Confident associate. They present a methodology — lean, six sigma, operational excellence, whatever the current label is. Six weeks and $60,000 later, you have a binder. The binder goes on a shelf. Your margin keeps sliding.

The problem wasn't the binder. The problem was that the consultant showed up already knowing the answer. They had a framework before they had a conversation. They fit your business to their theory, presented to your leadership team, and left.

Your foreman — the one who's been running the press brake for 22 years and could tell you exactly where throughput dies on second shift — was never asked. Or they were asked, and what they said didn't fit the framework, so it got filtered out.

This isn't a consulting problem. It's a posture problem.

Chris Hoff, a therapist who writes at Liminal Lab, draws a distinction that translates almost perfectly to our world. He contrasts two stances a practitioner can take: the Expert and the Guide.

The Expert claims portable, universal solutions. They arrive with a methodology and design outcomes. The work is something they perform on the client.

The Guide knows their experience is real but not portable. What worked in the last shop might not work in yours. They hold their methods loosely enough to learn from the business in front of them, and they design conditions and invitations rather than prescribing a destination.

Hoff is writing about therapy. But read it again with a fab shop in mind, or a 60-person construction company, or your O&G service outfit, and tell me it doesn't describe every consulting engagement you've ever been part of.

The Expert shows up with the answer. The Guide shows up with the questions.

Here's why that matters for margin.

In a $5M–$100M industrial business, the answer is already in the building. The welder knows why the fixture is costing them 11 minutes a job. The controller knows which customer's payment terms are quietly bleeding working capital. The foreman knows which scheduler is afraid to push back on sales. None of this is hidden. It's just unspoken — because nobody with authority has asked the right question, or because the last person who asked didn't actually want the answer.

The Expert can't surface this. The Expert's framework filters it out. If the welder's answer doesn't match the lean template, the template wins and the welder shuts up. Permanently.

The Guide's job is the opposite. The Guide builds the conditions where the welder finally says the thing they've been thinking for three years — and gets heard long enough that the fixture actually gets fixed.

This is the mindset shift: the consultant's job is not to know. It's to hear.

That doesn't mean showing up empty. A good guide shows up with sharp questions, operational fluency, and enough pattern recognition to know which thread to pull. But the answer isn't theirs to import. The answer is already standing on your shop floor, in steel-toed boots, waiting to be asked.

I learned this the hard way at U-Flow.

When I started U-Flow Inc. — a specialty flat-roof drain manufacturer — I had read the books. I had the frameworks. I knew what ISO 9001 was supposed to look like on paper. And for about the first year, I tried to run the shop that way: import the system, train the team to comply, measure against the template.

It didn't work. Not because the team wasn't capable. Because the system I was importing didn't know anything about the actual work.

The turn came when I stopped trying to install a quality system and started watching where the same mistakes kept happening. A particular weld kept failing inspection. A specific assembly step kept getting skipped on rush orders. A drawing revision was getting missed somewhere between engineering and the floor.

So I asked the people doing the work. Not in a meeting. On the floor. Why does this keep happening? What would actually stop it?

The answers weren't in any textbook. One person needed a different jig. Another needed the drawing revision printed in a different colour so it was obvious at a glance which version was current. The skipped assembly step was happening because the standard work instruction was wrong — the actual best sequence was different from what the document said, and everyone on the floor knew it except the document.

The ISO 9001 system that eventually got certified wasn't the one I imported. It was the one the team helped build. The procedures were written in their language. The controls addressed the failures they had actually seen. The training stuck because they had written it.

That's the difference between the Expert stance and the Guide stance, made concrete.

The Expert version would have been a binder full of generic procedures, a certification audit we barely passed, and a quality system that everyone resented and quietly worked around. I've seen that version in plenty of shops since. It's the default outcome when someone imports a framework instead of drawing one out.

The Guide version was a quality system the team owned. It survived me leaving. It got better after I left, because the people who built it kept refining it. That's the test — not whether the system works while the consultant is in the building, but whether it survives them walking out the door.

If your last consulting engagement didn't survive the consultant leaving, you didn't have a Guide. You had an Expert. And the binder is on the shelf to prove it.

So what does this actually look like when you hire it?

The Margin Audit isn't a diagnostic I perform on your business. It's a structured way for you and your team to see what you're already standing on.

I sit in on the morning huddle. I walk the floor with your foreman — not with a clipboard, with questions. I read the variance report with your controller, not at them. I ask your scheduler what they've been trying to tell sales for the last six months that nobody's heard. I ask your shop lead which customer's jobs they dread seeing on the board, and why.

None of that requires my framework. It requires my attention.

The findings that come out of a Margin Audit aren't mine. They're yours, surfaced. My job is to ask sharply enough, listen long enough, and pattern-match across enough industrial businesses that the things your team already knows but has stopped saying out loud finally get said — and get connected to the margin number on your P&L.

That's why the work sticks after I leave. Because it was never mine to take with me.

If you've been burned by a consultant who already knew the answer, the question worth asking isn't which framework should I try next.

It's: who's actually willing to listen to the people running my floor?

If that question lands, reply to this email or book a call. The Margin Audit takes about three weeks and is priced against the EBITDA gain, not the hours. The first conversation is free and is mostly me asking what you've already tried.

Ready to Find Your Margin?

Philip Uglow is the founder of The Margin Builders. Better Leadership. Better Operations. Better Margins.

References and further reading

The source for this piece:

Hoff, Chris. Ways of Seeing #6: Ethical Reflexivity. Liminal Lab, Substack. chrishoff.substack.com/p/ways-of-seeing-6-ethical-reflexivity

Hoff is a therapist and the founder of California Family Institute. The Expert/Guide distinction I borrow here comes from his sixth essay in the Ways of Seeing series. He's writing about clinical practice, but the frame translates almost without modification to consulting work in industrial businesses.

If you want to go further:

Schein, Edgar H. Humble Inquiry: The Gentle Art of Asking Instead of Telling. Berrett-Koehler, 2013 (3rd edition 2021 with Peter A. Schein). The closest operational cousin to what I'm describing. Schein — a fifty-year fixture at MIT Sloan and one of the most respected voices on organizational culture — defines humble inquiry as "the fine art of drawing someone out, of asking questions to which you do not already know the answer." Short book. Worth a Saturday morning.

Schön, Donald A. The Reflective Practitioner: How Professionals Think in Action. Basic Books, 1983. The foundational critique of what Schön calls "Technical Rationality" — the assumption that professional work is just applying universal theory to defined problems. Schön argues the best practitioners in any field rely less on imported frameworks than on improvisation, situational reading, and reflection in the middle of the work. Older book, denser read, but the arguments hold up.

Liker, Jeffrey K. The Toyota Way: 14 Management Principles from the World's Greatest Manufacturer. McGraw-Hill, 2004. Principle 12 is genchi genbutsu — "go and see for yourself." Toyota's stance is that you cannot understand a problem from a desk, a report, or a deck. You have to be on the floor where the work happens. The same principle, in industrial language your team will recognize.