Leadership on the Job Site: What It Takes to Run a Crew Well

Key facts: extreme ownership for a trade crew

What does "extreme ownership" actually mean for a tradie running a crew?

It means you, as the person in charge, own the result of every job your business does — good or bad — before you look anywhere else for the reason it went wrong. If a bathroom reno comes in over budget, a fitting's installed wrong, or a customer's fuming because nobody rang to say the crew would be late, the leader's first move isn't "who was on that job." It's "what did I fail to make clear, check, or set up so that job could go right." That's not about publicly martyring yourself in front of the customer; it's a genuinely different way of diagnosing a problem, and it's the only version of the diagnosis that actually points to a fix instead of an excuse.

The businesses that stay chaotic year after year usually aren't short on effort or skill — they're short on this reframe. Missed callbacks, blown quotes, and crew turnover get filed under bad luck or "you can't get good people anymore" instead of what they usually are: a leadership and process gap that keeps recreating the same problem with a different name on it each time.

Why is blaming the apprentice the wrong first move when a job goes wrong?

Because it treats the mistake as one person's personal failing, when it's almost always a gap in the training, instruction, or process you gave them to work from. Say an apprentice fits the wrong valve. If the real story is that there was no reference photo on the job, no clear standard communicated for that fitting type, and nobody checked the work before it was covered up, blaming the apprentice fixes nothing — the next apprentice makes the same mistake on the next job, because the actual gap is still there. Extreme ownership means you ask what training or system failure let the mistake happen, fix that first, and only then have the individual conversation about the person's own accountability.

There's a trust cost to getting this backwards, too. A crew that expects to be blamed the moment something goes wrong learns fast to stop reporting problems early — the cracked pipe gets patched and not mentioned, the wrong part gets used because nobody wanted to own up to ordering the wrong one. Small, cheap-to-fix mistakes turn into expensive ones because reporting them felt riskier than hiding them. A leader who visibly owns the outcome, including with the customer, is the one whose crew actually tells them when something's gone sideways — while it's still a five-minute fix.

How do you get a crew to actually follow a new system, instead of quietly going back to the old way?

They have to believe you believe it — which means explaining the why behind a change, not just handing down the what. A crew can tell the difference between an instruction that came with a real reason and one that came with "because I said so," and they'll quietly stop following the second kind the day you're not standing over them. Say you're rolling out a requirement from Part 9's systems: every finished stage gets photographed before the crew moves on. "Log photos, that's the new rule" gets skipped the first busy Friday. "This is what protects you if a customer disputes a variation later, and it's what gets an insurance claim through without a fight" gives the crew a reason to keep doing it when nobody's checking.

If you genuinely can't explain why a new process helps the crew doing the work, not just the owner reading the reports, that's worth noticing before you roll it out — the system might need rethinking, not just better selling.

What does "cover and move" mean for a trade business, and why does office-vs-field friction cost you money?

It means the office and the crew on the tools are working toward the same result, and any friction between them is a leadership problem to fix, not a normal cost of running a trade business. It shows up as the office booking a job the field can't realistically hit that day, or the field not reporting a delay so the office quotes the next customer wrong, or an invoice going out late and each side quietly blaming the other. Left alone, both sides start covering themselves instead of covering each other — and customers feel the seams, even if they can't name what they're feeling.

A leader's job here is to unify the two sides around one goal — the job done well and billed correctly — rather than referee a permanent turf war between "admin" and "the tools." The most direct fix is visibility: give office and field the same job information at the same time, so nobody's working from a guess about what the other side already knows.

Does taking full responsibility mean you can never point out someone's mistake?

No — it's about which question you ask first, not about pretending nobody but you ever gets anything wrong. After you've genuinely checked your own leadership and fixed whatever system or training gap allowed the mistake, there's often still a real, direct conversation to have with the individual if the standard truly was clear and they simply didn't meet it. The difference is sequencing and tone: fix the leadership gap first, then correct the person's performance honestly and specifically — not as blame-shifting to protect yourself, but as a fair, unemotional standard being held.

Part of getting this right is checking your own ego. A leader who bristles at pushback, or who treats every question about a decision as a challenge to their authority, is also a leader whose crew stops raising problems until they're too big to hide. Genuinely inviting a foreman or a long-serving crew member to tell you when a plan's wrong is one of the cheapest ways to catch a bad call before it costs you a job.

How does "leading up the chain" apply when you're the owner and there's nobody technically above you?

It applies to every relationship your business depends on but doesn't fully control — demanding clients, suppliers, subcontractors — where the same ownership ethic covers communication breakdowns in both directions, not only the ones your own crew causes. If a supplier delivers the wrong materials and a job's delayed, the first question is still whether your order and the site date were actually confirmed clearly, before you ring up to complain. If a client's expectations drift mid-job, you restate what was actually agreed, get the change confirmed on the record, and if their expectation was never realistic in the first place, you make that case in terms of their own interests — not just "that's not what we quoted." It keeps trust intact with everyone the business depends on, not only the people on your payroll.

What actually changes on the job site when you lead this way?

Fewer excuses get made, and more real problems get raised early instead of hidden. Crew who know a mistake gets treated as something to fix, not something to punish, tell you about it while it's still a five-minute conversation instead of a costly redo. A crew that's had the why explained to them keeps following a process when you're not on site to check. And when a dispute does happen — with a customer, a supplier, or between office and field — there's a shared account of what was actually agreed to settle it, instead of two versions of events and whoever's angrier winning.