Industrial services field leadership: running crews you cannot see

Industrial services has a leadership problem that does not look like a leadership problem. It looks like a safety problem, a turnover problem, and a margin problem at individual branches — and underneath all three is usually the same thing: nobody has solved how to run people who work a long way from anyone senior.

The three constraints

Crews work unsupervised for days. Not lightly supervised. Unsupervised, making judgment calls about sequence, method and when to stop, on work that is physically consequential. Whatever standard exists is the standard the crew carries with them.

Safety has to hold when nobody is watching. Every company has a safety program. The ones that work are the ones where a crew chief stops a job at four on a Friday because the rigging is wrong, knowing it costs the schedule. That is not a policy outcome. It is a cultural one, and culture at distance is set by whether the last person who made that call was backed or quietly blamed.

The work happens on ground you do not control. A customer’s site, their rules, their people, their schedule, and frequently their willingness to lean on your crew to cut a corner. Your field leader has responsibility for the outcome and no authority over half the environment.

Those three are the job. Everything else — scheduling, utilization, billing accuracy — is downstream, and a leader who cannot handle the three will not fix the downstream metrics no matter how good the software is.

What transfers, specifically

Setting a standard that survives your absence

This is the whole of it, and it has a name: commander’s intent. A concise statement of the purpose and the end state, written so that people can act on their own initiative when the plan stops matching reality.

The practical difference between a leader with this habit and one without is visible within a month. The one without increases reporting — daily calls, more paperwork, tighter check-ins — and gets compliance during the check-in and drift between them. The one with it spends the first month deciding what genuinely has to be escalated and what does not, tells the crews exactly that, and then leaves them alone.

Concretely, on an industrial services crew, it sounds like: stop the job if any of these five things are true, call me if any of these three are, and everything else is yours. That list is a real artifact and most field organizations do not have one.

A standard that was already unsupervised

A career in a community where a shortcut is punished immediately and visibly does not produce somebody who treats a procedure as paperwork. It produces somebody with a practiced suspicion of their own judgment when tired — which is the condition in which most field incidents actually occur.

This is the most direct transfer on the list and it is the one that shows up in the numbers first.

Working through people who do not report to you

The core mission of Army Special Forces is working by, with and through partner forces — getting results from people who did not choose you, do not report to you, and have their own chain of command and their own priorities.

That is a precise description of a field leader standing on a customer’s site. It is also the part that most often breaks a hire promoted from inside a plant, who is used to their own rules on their own floor and reads the customer relationship as an obstacle rather than as the terrain.

The after action habit

A structured review after an event, run regardless of outcome, with rank set aside. In a field organization this becomes the near-miss review that actually happens, and the near-miss review that actually happens is the cheapest safety investment available.

The half most companies skip is running it after a good job. A leader from this background runs it anyway, and that is where the drift gets caught before it becomes an incident.

Where this is the wrong hire

When the job is technical authority. If the role is really about being the person who knows the equipment — the one the crews call when something unusual happens — hire the technician with twenty years on that equipment. Leadership temperament does not substitute for knowing why that pump is doing that.

When the constraint is customer relationships you already have. Some field leadership roles are substantially account management with a hard hat. If the value is a decade of relationships with three named customers, that is a different hire.

When there is no real authority in the seat. The most common way these hires go wrong. Somebody accustomed to being trusted to decide, placed in a role that owns the outcome and routes every decision upward, will work the problem quietly and then leave. If the honest answer is that your branch managers cannot commit spend or stop a job without a call, say so in the interview.

When the pace is the attraction. Industrial services is often a long grind of small improvements. Some people leaving a high-tempo career want exactly that. Some discover eighteen months in that they miss the intensity. Ask directly.

The founder-owned case

A particular version of this comes up often enough to name: the founder-owned industrial services business making its first institutional hire.

The specific difficulty is that the founder has been the standard. Their judgment, their relationships, their willingness to drive four hours on a Saturday. Everything works because they are the escalation path for everything, and the business cannot grow past the number of things one person can be the escalation path for.

Hiring a field leader into that is not primarily a skills problem. It is a question of whether the founder can actually hand over the list — and the honest test is whether they can write down what the new person may decide without asking. A founder who cannot write that list is not ready to make the hire, and the search will surface that in month four at their expense rather than in week one for free.

We say this out loud in the onboarding call because it is the single most common reason a first institutional hire in this sector fails, and it has nothing to do with the candidate.

What to ask

Beyond the general twelve:

1. “What are the five things you would tell a crew to stop the job for?” A real candidate answers immediately and specifically. It also tells you whether they think in terms of decision rules or in terms of oversight.
2. “Tell me about a time somebody on a site you did not control asked your people to do something unsafe.” You want what they did in the moment and what they did afterward with the customer relationship.
3. “How would you know a branch four hours away was drifting, before it showed up in the numbers?” Listening for leading indicators and for a plan to hear from people directly, not for a dashboard.

The roles we have filled in this sector sit in exactly this shape — operations, finance and project leadership, including first institutional hires. If that is the seat, tell us the role.