Jonathan Haaswritingnowusesabout
emailgithubx
Jonathan Haaswritingnowusesabout

Keep Your Hands Dirty: Why Executives Who Stop Doing The Work Destroy Companies

April 11, 2024·2 min read

The Executive Trap I've seen it happen a dozen times: A brilliant engineer becomes CTO and suddenly decides their job is 'managing the engineering...

#engineering#leadership#culture#strategy

A brilliant engineer becomes CTO and decides their job is now "managing the engineering organization." A phenomenal salesperson takes the CRO role and shifts to "sales strategy." Both lose the thing that made them worth promoting.

The standard advice says executives should "rise above" the day-to-day. Focus on strategy. Build the team. Delegate execution. There's truth in that -- you can't scale yourself by staying an individual contributor. But the advice has a failure mode nobody discusses honestly: executives who fully disconnect from the work lose the judgment that made them effective.

The Decay Curve

Judgment is perishable. A CTO who hasn't reviewed production code in six months makes architecture decisions based on a mental model of the system that no longer matches reality. A CRO who hasn't run a deal in a quarter makes pipeline calls based on a market that has shifted. The decisions look confident. The inputs are stale.

The team knows. Engineers stop asking the CTO for technical input because the answers aren't grounded anymore. Sales reps stop surfacing deal nuance because the CRO's advice doesn't reflect current buyer behavior. The executive's authority becomes positional rather than earned -- and positional authority degrades team performance because it can't be challenged on substance.

The Time Budget Problem

There's no clean answer for how a CTO at a 200-person company codes for hours daily while running an engineering org. Anyone claiming that's easy is selling a framework, not running a company. The honest answer is that you can't stay hands-on everywhere, and pretending otherwise leads to micromanagement disguised as technical involvement.

The alternative is selective depth. Pick one thread -- the architecture decision that defines the next two years, the deal that reveals where the market is heading -- and stay genuinely involved. Not reviewing a summary. Not reading a dashboard. Actually doing enough of the work to maintain calibrated judgment about what "good" looks like in that domain.

The Warning Signs

If your calendar is entirely meetings and no doing, you've drifted. If you're making decisions based purely on dashboards and slide decks, you've drifted. If your team stops asking for your practical input on hard problems, you've drifted. The gap between "strategic leader" and "disconnected executive" is measured in months, not years.

Stay close enough to the work that your judgment remains grounded. Delegation without contact is just guessing with authority.

share

Continue reading

The Security Tool Comparison Problem

Every security tool comparison site is funded by the vendors being evaluated. This creates a specific, structural problem for security teams making...

The Perfection Paralysis: Why Moving Too Carefully Kills Startups

The most valuable code I've ever written was messy, quick, and written in response to an immediate customer need.

Engineering and Product Collaboration: Breaking Down Silos

'This isn't what we asked for.' Five words that strike dread into every engineering team. Five words that signal a fundamental breakdown in the...

emailgithubx