Let the Crew Own the Improvement or Lead It Yourself: Decision Tree
Why this matters
You have identified something to fix - a process that is not working, a recurring problem, a better way to run a job. Now: do you hand it to the crew to own, or do you drive it yourself? Owners get this wrong in both directions. Delegate a fix that actually needed your authority and it stalls for weeks because nobody on the crew can make the call. Grab a fix the crew was ready to own and you teach them that improvement is your job, not theirs, and they stop bringing you problems to solve. The right answer depends on the fix, not on your habit. This tree sorts it.
Start here: does fixing this require authority only you hold
Some fixes need a decision the crew genuinely cannot make. Sort for those first.
- If the fix requires spending real money, changing a customer-facing policy, hiring, or overruling another department - you lead it. Handing someone a problem they lack the authority to solve is not delegation, it is a setup for failure and frustration.
- If the fix is within the crew's daily control - how a job is sequenced, what goes on a checklist, how the truck is stocked, how a handoff works - the crew can own it. Keep going.
Branch 1: are the stakes high enough that a wrong fix is dangerous
- If a botched fix could hurt someone or cause serious damage - a safety procedure, a step that prevents a major loss - you stay close. You can involve the crew heavily, but you own the outcome and you approve the change before it goes live. Safety-critical improvement is not a place to practice hands-off delegation.
- If a wrong first attempt is recoverable - a little wasted time, an easy do-over - let the crew own it, including the freedom to get it slightly wrong on the way to getting it right. Recoverable stakes are exactly where people learn to improve.
Branch 2: who is closest to the problem
- If the people living the problem understand it better than you do - and on the details of the daily work, they usually do - they should own the fix. A solution written by the person who feels the pain every day beats one handed down by someone who sees it from a distance.
- If the problem crosses several people or functions and no one person sees the whole thing - you lead, because someone has to hold the parts together. Cross-cutting problems need a coordinator, and that is usually you.
Branch 3: is the crew ready to own it
Be honest here, and read it as a spectrum, not a verdict on your people.
- If the crew has owned improvements before and it went well - hand this one over with confidence and get out of the way.
- If this would be their first real ownership - do not hand them the hardest, highest-stakes fix as the debut. Give them a contained one, support it, let the win build the muscle. Ownership is grown, not switched on.
The comparison
| Signal | Crew owns it | You lead it |
|---|---|---|
| Authority needed | Within their daily control | Money, policy, hiring, cross-department |
| Stakes of a wrong fix | Recoverable | Safety or major loss |
| Who understands it best | The people doing the work | Nobody has the full picture |
| Scope | Contained to one area | Crosses functions |
| Crew's track record | Has owned fixes before | First time, or past attempts stalled |
Most day-to-day improvements land in the left column. That is the point: the crew owning the small stuff is what frees you to lead the few things that genuinely need you.
When you lead, still pull them in
Leading a fix does not mean doing it alone. The people closest to the problem should shape the solution even when you own the call. And when the crew owns a fix, "own" means real ownership: they decide the how, you agree the what and the by-when, and you resist the urge to swoop in and take it back the moment it wobbles. Taking a fix back the first time it stumbles is the fastest way to guarantee nobody volunteers for the next one.
The recap
- If the fix needs authority only you hold, you lead it.
- If a wrong fix is dangerous, you stay close and approve the change.
- If the crew is closest to the problem and the stakes are recoverable, they own it.
- If it crosses functions, you coordinate.
- Grow ownership deliberately - contained wins first, not a high-stakes debut.
The judgment to bank: your job is not to solve every problem, it is to make sure every problem gets solved by whoever is best placed to solve it. Most of the time that is not you, and acting like it is keeps your crew small.
References
- Trade-standard practice for delegation and continuous improvement
- U.S. Small Business Administration (SBA), leadership and team development for small business
- See related: Building a Team That Fixes Its Own Problems
- See related: Running an Effective Team Huddle; After-Action Review: Learning From a Bad Job