The Fixing Penalty
Why Your Best Technical Instinct Is Your Worst Leadership Move
A developer on my team pinged me on a Friday afternoon. The deployment pipeline had been failing intermittently for three days. He’d already tried the obvious fixescleared caches, rerun the builds, checked for flaky tests. Nothing stuck.
He walked me through every step. His voice was tight. He kept circling back to the same details.
My instinct was immediate: isolate the nondeterministic test, pin the dependency versions, move on. I could see the fix. I almost said it.
Instead, I asked: “How’s this week been for you?”
Twenty minutes later, I knew the pipeline wasn’t the real problem. He’d been handed a second project with no reduction in his existing workload, the on-call rotation had wrecked his sleep, and the flaky pipeline was just the thing that finally cracked his composure. He didn’t need me to fix a CI job. He needed someone to hear that the situation was unsustainable.
If I’d jumped straight to the technical fix, I would have solved the wrong problem and paid for it later.
Two Modes, One Conversation
Every problem someone brings you is running in one of two modes:
Vent mode. They need to process frustration. They’re not asking you to fix it they’re asking you to hear it.
Fix mode. They’re genuinely stuck. They need your expertise, your authority, or your resources to unblock them.
The penalty comes from defaulting to fix mode because that’s what technical leaders are trained to do.
When someone is venting and you respond with a solution, you’re not being helpful. You’re signaling that their frustration is just a puzzle, not an experience. Trust erodes fast when people feel like you’re optimizing them instead of listening to them.
The Guilt Mask
Here’s what makes this hard: people almost never tell you which mode they’re in.
Corporate culture treats emotional needs as weakness. Saying “I need to vent” feels unprofessional, so people disguise it. They frame an emotional need as a tactical question because that’s the only socially acceptable way to get five minutes of a manager’s time.
The developer with the flaky pipeline wasn’t lying about the problem it was real. But the urgency behind it wasn’t about CI. It was about feeling underwater with no one noticing.
If you take every conversation at face value, you’ll misdiagnose this every time. You have to read tone, body language, and context. If someone is agitated well beyond what the stated problem warrants, the stated problem probably isn’t the point.
The Dual Cost of the Fixing Instinct
Yielding to the fixing instinct carries two distinct penalties: one emotional, one operational.
The Trust Penalty (Misreading the Mode)
As established, applying a technical fix to an emotional vent invalidates the employee’s experience. You win a short-term technical victory but damage the psychological safety required for a functional team.
The Agency Penalty (The Ego Trap)
Even if you correctly identify they are in “Fix mode,” handing them the answer damages scalability. Technical leaders often know the optimal path. Letting an engineer struggle, or allowing them to implement a viable solution that differs from your preferred method, requires suppressing your own ego.
When you bypass their cognitive process and dictate the fix, two things happen:
You rob them of agency. The productive struggle is how people develop independent judgment. Every time you short-circuit that process, you trade a short-term efficiency gain for a long-term capability loss.
You build a dependency graph. If every problem routes through you for resolution, you haven’t built a team; you’ve built a bottleneck. You will spend an increasing percentage of your bandwidth maintaining other people’s productivity instead of leading.
The Pause
This isn’t complicated. It’s just hard to do consistently when you can see the answer clearly in your head.
Before you respond to a problem, pause. Ask yourself: is this person stuck, or are they drowning? If you’re not sure, ask a question that isn’t about the problem.
“How’s this week going?”
“What’s your energy level on this right now?”
If they unload about their workload, sleep, or frustration, they needed to vent. Listen. You are doing your job.
If they brush off the personal question and redirect sharply back to the architecture, they need a fix. Now your tactical brain is the right tool provided you guide them to the answer rather than dictating it.
The penalty for guessing wrong isn’t symmetrical. Listening when someone wants a fix costs you a few minutes. Fixing when someone needs to be heard costs you their trust.
The best debugging skill in leadership has nothing to do with code. It’s reading the room before you read the stack trace.