My client showed up with a half-written resignation and a full systems diagram. Award-winning engineer, patents for breakfast, the whole résumé that makes LinkedIn sigh. And yet: ready to walk. Not because the work was hard; because the directions from leadership behaved like rogue vectors, equal and opposite, canceling momentum at every turn.
“Make it more strategic.” Compared to what?
“Move fast, no surprises.” Please pick one.
A roadmap that existed and did not, like Schrödinger’s Gantt.
He didn’t need applause; he needed a spec. Engineers can handle load but not load without tolerances. When requirements shape-shift mid-sprint, you don’t get velocity, you get heat (literally).
We walked it back like a root-cause analysis so he could bring his version of “excellence” back to his leader… Where’s the signal? Who owns the decision? What are the guardrails? We laughed when he called the weekly “strategy sync” a smoke machine; lots of fog, no solutions. The fix isn’t heroic, but it is disciplined:
-Define the outcome in customer terms and timestamp the decision. No more version-control wars in chat.
-Park “nice to have” in a backlog that actually stays parked.
-Swap two status meetings for one block of maker time. (Throughput increased; everyone pretend to be shocked.)
-Give direct feedback with numbers, not vibes. “Tighten error handling by Thursday; checkout failures doubled” beats “polish.”
He didn’t need a tighter leash; he needed a clearer runway to be the multiplier he always had been.
Here’s what leaders need to know: the environment is the manager. Raise the SKILL standard so “done” means done. Route decisions through the right nodes so blockers don’t become permanent. Prioritize work that works (not theater). Make KNOWLEDGE findable so wins replicate. Do that, and excellence stops being seen as a personality trait and starts being recognized as a system.
So no, my client didn’t quit (at least not this week), instead he shipped. And hopefully will move the culture in the right direction.
Your turn: What single change (killing a meeting, tightening a spec, time-boxing reviews) turned confusion into momentum for a top performer? Or, if you’re the engineer, what finally made you stay (or go)? Drop one concrete move in the comments so someone else can copy-paste courage.
