The work you handed off came back half done, so you figured the person wasn’t ready or you delegated too soon. Wrong read. The work didn’t bounce because they failed. It bounced because you handed over the easy part and kept the part that mattered. Delegation isn’t one move. It’s three transfers at the handoff, then a hold afterward, and most engineers do the first transfer and skip everything else.

 Chris walks through a project where he handed the project management work to an internal PM but quietly kept the client relationship, the day-to-day context, the gotchas, the trade-offs. When he had to step away, the team was left deciding blind on the part he never transferred. They did the best they could with the information they had. The problem was the rest of it was sitting with him. This episode is the mechanics behind that failure and how to avoid it: the outcome, the authority, the context, and why taking the work back the moment it comes back at 80 percent is where the whole thing collapses.

What You Will Take Away

• Why “I need to trust my team more” is the wrong diagnosis. The mechanism isn’t how controlling you are, it’s what you actually transferred at the handoff.
• The difference between transferring a task and transferring an outcome. Task assignment keeps the definition of done in your head, so every judgment call routes back to you.
• The three-decision test for authority. If you can’t name three calls the person can make without checking with you, you transferred labor, not authority, and you’re still the bottleneck.
• Why authority without context sets someone up to fail with full permission. Judgment runs on the why, the constraints, and the trade-offs you already rejected, and if you keep those, they decide blind.
• The third path on check-ins, between swooping in when you’re nervous and going dark until something breaks. Pre-scheduled and structured, so your nerves don’t drive it and their silence doesn’t hide a problem until it’s expensive.
• Why holding the line at 80 percent is part of the mechanism, not a personality trait. The moment you take the work back, authority snaps to you and the person learns not to fully commit.

Who This Is For

• Engineers who delegated something and watched it bounce straight back, then assumed the person wasn’t ready
• New leads who feel busier after handing work off than they did before
• Anyone who’s said “I’ll just handle this one” and meant it as a fix rather than a relapse
• Engineers who heard episode four on the indispensability trap and want the actual mechanics for getting out
• Technical leads who keep getting pulled back into work they thought they’d already delegated

Follow Re:Engineered wherever you get your podcasts.

Send us Fan Mail

Re:Engineered is a podcast for engineers and technical professionals navigating the shift from technical excellence to leadership responsibility.

Hosted by Chris Stasiuk, a professional engineer with over 25 years in engineering consulting and leadership roles, the show treats leadership, communication, and decision-making as systems to understand — not personality traits to fake. No buzzwords. No corporate theater. Just clear thinking about how technical people actually lead.

Explore episodes, transcripts, and related resources at https://chrisstasiuk.com/podcast/.