When Your Leadership Team Is a Group, Not a Team

You've built something real. The business has a leadership team now — an operations lead, a sales lead, maybe a controller or a VP of something. On paper, that's exactly what a growing company in oilfield services, engineering, or industrial manufacturing is supposed to have at this size. You're not a one-person shop anymore.

But here's the test that actually matters: when a decision that touches more than one function comes up — a pricing call, a hiring call, a call about which job to walk away from — does your team work it out, or does it land back on your desk?

If it's the second one, you don't have a leadership team. You have a group of capable individuals who report to you.

That distinction sounds academic until you see what it costs. It's not a personality problem and it's rarely a competence problem — the people are usually good at their jobs. It's a structural one: nobody has ever had to build the muscle of deciding together, because you've always been the tiebreaker.

Why this happens almost everywhere in this band

Companies between roughly $1M and $50M in revenue in energy, engineering, and industrial services tend to hit this exact wall, and it's not a coincidence. It's a function of how the business got built.

In the early years, you made every call because there was no one else to make it. That wasn't a flaw — it was the right way to run a five-person operation. The problem is that the habit doesn't expire on its own. The company adds headcount, adds functions, adds a layer of managers with real titles — and the decision-making pattern underneath it all doesn't change. You hired for roles. You never built a room.

A few patterns show up consistently in businesses at this stage:

Individual excellence, collective silence. Each leader is strong in their own lane — operations runs tight, sales hits target, the shop floor is well managed. But put them in the same room on a decision that crosses lanes, and the conversation goes quiet, or it turns into everyone defending their own function instead of solving the actual problem in front of them.

Everything resolves upward. Disagreements between functions don't get worked out between the people who own those functions. They get escalated — sometimes explicitly, sometimes just by someone waiting for you to notice and step in. Either way, you're the conflict-resolution mechanism for the whole business, which means the business can only move as fast as you can personally attend to it.

Meetings that inform instead of decide. The team gets together, status gets reported, and then everyone leaves and you make the calls separately, usually one-on-one. The meeting exists, but the team doesn't actually do anything in it that requires them to function as a team.

None of this is a reason to doubt the people you've hired. It's a reason to look at the system they're operating inside — because a group of strong individuals inside a system built for one decision-maker will keep behaving like a group of strong individuals, no matter how good they are.

How to tell which one you actually have

You don't need an assessment to find out. You need to look at the last few decisions that crossed functional lines — a scheduling conflict between operations and sales, a hire that affects two departments' budgets, a customer problem that touches both service delivery and the shop. Ask three questions about each one:

Did the people affected work it out between themselves, or did it come to you to settle? Was there a visible disagreement in the room, or did everyone nod and then do what they'd already planned to do anyway? And when the decision was made, did it stick — or did it quietly get re-litigated afterward in one-on-ones?

A real leadership team produces friction before it produces agreement, and the agreement holds once it's reached. A group of individuals produces neither — it produces deference in the room and separate conversations with you afterward. If most of your cross-functional decisions follow the second pattern, the team hasn't failed. It's never actually been asked to function as one.

What it's actually costing you

The direct cost is speed — decisions that should take a day take two weeks because they're queued behind you. But the compounding cost is bigger: you can't step back from the business, even partially, because nothing happens without you in the room. Every plan to take a real vacation, delegate a function, or eventually exit runs into the same wall — there's no leadership layer underneath you that can actually run things without your direct involvement.

There's also a quieter cost in talent. Capable people who could grow into bigger roles don't get the chance to practice making cross-functional calls, because those calls never reach them. You end up with a ceiling on how far your own leaders can develop, built entirely by the way decisions flow.

What changes the pattern

Building a leadership team that functions as one isn't about more meetings or a better org chart. It's about deliberately moving specific categories of decisions out of your hands and into the team's, with enough structure that they can actually make them well — not just told to "figure it out."

That means being explicit about which decisions are now theirs to resolve together, not yours to referee. It means the team has to practice disagreeing productively in front of each other instead of routing disagreement through you. And it means you have to tolerate some decisions going slightly differently than you would have made them yourself — because a team that only works when it reaches your exact answer isn't actually making decisions, it's just guessing at yours.

This is slower at first. A team that's never had to decide together will be clumsy at it for a while. But the alternative — staying the single point of resolution indefinitely — doesn't get easier as the business grows. It gets more expensive, because the number of decisions waiting on you only increases with scale.

Concretely, this usually means three things happening together, not in sequence. First, naming the actual decision rights — which calls belong to the team collectively, which belong to one function lead, and which still genuinely require you, stated plainly enough that there's no ambiguity to retreat into. Second, changing what the leadership meeting is for — from a status report you listen to, into a forum where the cross-functional decisions on that list actually get made, with you in the room as a participant rather than the default decider. Third, holding the line when the old pattern tries to reassert itself, because it will — the first time a decision goes sideways under the new structure, the pull to take it back yourself will be strong, and giving in to it once resets the whole effort.

None of this requires a reorganization or new titles. It requires a different habit, practiced consistently enough that it becomes the house style rather than an experiment that quietly lapses after a few weeks.

The businesses that get past this wall tend to do it deliberately, not by accident. Someone has to name the pattern, redesign where decisions sit, and hold the team to the new structure long enough for it to become normal. Left alone, the default reverts — because the owner stepping back in to resolve things quickly is always the path of least resistance in the moment, even though it's the most expensive path over a year.

If your leadership team meets regularly, reports well, and still leaves every cross-functional decision on your desk, that's not a sign you hired the wrong people. It's a sign the system around them was built for a business that no longer exists — the one where you were still making every call alone.

A Complimentary Coaching Session is a good place to start working out where that pattern is costing you the most, and what it would take to close it.