Why does self-orientation matter more than the others?

Because it's the divisor. You can be credible, reliable, and easy to talk to, and still get a low trust score if every interaction ends up being about your priorities, your career, your image. People can smell self-orientation in the first five minutes of meeting you. Once they've smelt it, the other three components are doing less work than you think.

How do I build credibility quickly as a new ops manager?

Stop trying to. Credibility is a side-effect, not a project. Walk the floor, ask questions, write down answers, come back the next day with a specific thing fixed. Credibility builds itself when people see you doing the thing you said you'd do, in the time you said you'd do it, on the floor where the work happens.

What's the most common reliability failure for ops managers?

Over-promising in week one. New managers come in, get asked twelve things in the first fortnight, and say yes to all of them to look responsive. By week four they've broken nine promises and the team has filed them under 'all talk'. Promise less than you can deliver. Deliver before you said. Do that twice and you're the most reliable person on the site.

How do I lower my self-orientation without becoming a doormat?

You don't lower it by being agreeable. You lower it by genuinely caring about the answer to a question more than how the question makes you look. The test: when someone tells you bad news, is your first thought 'what's broken' or 'how does this reflect on me'. Catch the second thought twice a day and you'll be in the top quartile of ops leaders in six months.

← Notes · 24 May 2026

The trust equation for ops leaders: why most fail the self-orientation test

Q: What is the trust equation?

It's a model from Maister, Green and Galford that says trust = (credibility + reliability + intimacy) ÷ self-orientation. Credibility is what you know. Reliability is what you do. Intimacy is how safe people feel talking to you. Self-orientation is how much of the conversation is about you versus them. The denominator is the one most leaders break.

Credibility plus reliability plus intimacy, divided by self-orientation. The maths is simple. The reason most ops managers blow up the denominator isn't.

There’s a model I rely on more than any other piece of management theory. It’s not from a Lean book. It’s from a slim volume called The Trusted Advisor by David Maister and two co-authors, and it boils trust down to four components arranged as an equation.

Trust = (Credibility + Reliability + Intimacy) ÷ Self-orientation.

Credibility is what you know. Reliability is what you do. Intimacy is how safe people feel talking to you. Self-orientation is how much every interaction ends up being about you, your career, your image, your story.

Three of those go on top of the line. One goes on the bottom. Most ops managers spend their careers polishing the top three and never look at the denominator. That’s why most ops managers (by the team’s reckoning, if not their own) don’t get trusted.

What the maths is actually doing

The reason the equation works is that self-orientation is a divisor, not a subtractor. If your credibility is 8, reliability is 8, intimacy is 6, and your self-orientation is 1, your trust score is 22. If your self-orientation is 4, your trust score drops to 5.5. Same credibility, same reliability, same intimacy. Quarter of the trust.

It’s why the smart, hard-working, technically capable ops manager who can’t stop making things about themselves never gets the loyalty of the team. The numerator is fine. The denominator is destroying the result.

It’s also why a relatively quiet, less-experienced manager (one who doesn’t know all the answers but is genuinely focused on the work and the people) gets trusted faster than the loud, credentialed one. They’ve got lower numbers on top, but a very low number on the bottom. The maths comes out their way.

Credibility: what most people get wrong

Credibility is not the same as expertise.

Expertise is what’s on your CV. Credibility is what people on the floor are willing to assume about you before you’ve said anything. Some of it carries over from your past: you used to run a bigger site, you’ve delivered a similar fix before, your old team rates you. Most of it doesn’t.

On day one of a new job, your credibility is roughly zero, regardless of what your CV says. You build it back up the same way everyone does: by walking the floor, asking questions, writing the answers down, and coming back the next day with a specific thing you said you’d do, actually done.

I’ve watched ops managers arrive at sites with twenty years of experience and lose credibility in week one because they tried to lead with the CV instead of the curiosity. The team doesn’t care that you used to run a bigger plant. They care whether you’ll bother to learn the names of the people on Line 3 by Friday.

The fastest credibility-builder I know is to walk a line, ask the operator the question they think nobody listens to, and come back the next day having actioned the answer. That’s not credibility theatre. That’s just listening to the people who do the job day in, day out. Nine times out of ten they know the fix.

Reliability: the over-promising trap

Reliability is the simplest of the four components and the one most ops managers blow first.

The pattern: new manager arrives. People test them with twelve small asks in the first fortnight. The manager says yes to all twelve because saying no looks rude and saying “let me get back to you” feels slow. Three weeks later, nine of the twelve haven’t been done. The team’s verdict is in.

The fix is boring. Promise less than you can deliver. Deliver before you said you would. Then do it again. And again.

If you don’t know whether you can do something, say so. “Let me check what’s already in the queue and come back to you by end of Thursday.” Then come back by Thursday lunchtime. The single act of beating your own deadline by half a day, twice in a row, will build more reliability than any number of grand commitments.

This is also where the Pick Your Battles rule earns its keep. You can’t be reliable about ten things at once. You can be reliable about one or two. Pick the ones that matter and protect them.

Intimacy: the one ops managers most often skip

Intimacy in this model isn’t personal in the romantic sense. It’s whether people feel safe telling you the truth about the operation when nobody else is in the room.

It’s the operator who comes to you and says “I think there’s something wrong with the line two compressor, I’ve heard it twice this week” instead of waiting for it to fail. It’s the team leader who phones you on a Sunday night to flag the Monday morning issue instead of letting you discover it at 7am. It’s the supervisor who tells you she made a mistake on the rota, before HR finds it.

You can’t manufacture intimacy. You can only earn it by reacting well to the small disclosures so the bigger ones come.

The test is brutal and simple. When someone brings you bad news, what does your face do in the first quarter-second before you’ve composed it? If your team has seen frustration, blame, or “why am I only hearing about this now” in that quarter-second more than once or twice, intimacy is gone. The next time something goes wrong, you’ll be the last person they tell.

I lost intimacy with a team once in exactly this way. A team leader brought me a near-miss that he’d part-caused. He told me, in his own time, with no obligation. I reacted badly. I went into “fix it” mode in front of him, when what he needed was thirty seconds of “thanks for telling me, let me sit with this.” He never brought me anything voluntarily again. I deserved that.

Self-orientation: the divisor that breaks the equation

Here’s the one nobody wants to look at.

Self-orientation is the percentage of any given interaction that, viewed from the other person’s seat, is about you. Your priorities. Your image. Your career. How you’re being perceived. Whether the news being delivered to you reflects well or badly on the decisions you’ve made.

Most ops managers think their self-orientation is lower than it is. Self-orientation is one of the hardest things to see in the mirror because by definition it’s the lens you’re looking through.

The signal you can actually watch for is in the second sentence of any conversation with bad news in it. When the team leader tells you the line is down and you’ve lost two hours, what’s the second thing out of your mouth?

If the second sentence is “what’s broken, what do you need, how can I help unblock you”, your self-orientation is low.

If the second sentence is “how do we explain this to the customer / the MD / the board”, your self-orientation is medium and you’re working on it.

If the second sentence is some flavour of “this is going to look bad”, your self-orientation is high enough to be wrecking the equation.

People can smell self-orientation faster than they can name it. It’s the thing that makes a technically excellent manager feel slightly off to work with, in a way the team can’t quite put words to. The words are: every interaction ends up being about him.

The reason consultants struggle with the equation

I’ll say one thing about the consulting industry I came from the other side of.

The model that most ops consultants run on is structurally high-self-orientation. They arrive, they tell you what’s wrong, they produce a deck, they leave. The deck has their logo on it. The recommendations are scored. There’s a follow-on engagement priced at the end.

That’s not because consultants are bad people. It’s because the model demands it. The deliverable is the deck. The deck is what gets paid for. The deck is, by definition, an artefact about the consultant’s analysis.

The ops manager who buys that deck and has to deliver the change is operating from the other side of the equation entirely. Their deliverable isn’t a document. It’s the line running. The trust the team has in them is what makes the line run. The two roles are not running the same maths.

Which is why operators-turned-founders see what consultants miss. We’ve been on the floor with the team that has to actually do the thing the deck recommends. We’ve watched the change die when the consultant left. We know what the team will do on Monday morning when nobody’s watching, because we’ve been the team on Monday morning when nobody was watching.

That’s the equation, applied to the consulting question. Self-orientation, at the level of a whole business model.

Where to start

Pick one of the four and work on it for a quarter. Just one.

If you’re new in a role, work on credibility. Walk more, talk less, ship one visible thing in the first six weeks.

If you’ve been in the role a while but the team feels distant, work on intimacy. React better to small bad news. Notice your face in the first quarter-second.

If you’re senior and successful and something feels off, work on self-orientation. Watch your second sentences.

Reliability is the easiest of the four to fix, but it’s the one most people don’t think they need to. Promise less. Deliver early. Do it twice.

The maths will do the rest.

The 90-day cadence behind the operating model is laid out in the Playbook. £97 for the first 100 buyers, £197 evergreen after. The Playbook focuses on the work; the trust equation is what makes the team you’re doing the work with stay with you long enough to land it.

Tags: leadership trust lean