26 posts tagged with "leadership"

Your best senior engineer just got promoted to "lead." Nobody wrote down whether that means Tech Lead or Engineering Manager, so now she does both. She's reviewing every PR, running every 1:1, planning every sprint, and still expected to ship her own code. Three months in, her output collapsed and so did team delivery. A 2024 Stack Overflow Developer Survey found that engineers in hybrid "lead" roles report 1.6× higher burnout than those on either a pure IC or pure management path. Merging the roles is the single most common — and most expensive — leadership mistake we see.

Tech Lead and Engineering Manager are different jobs with different success metrics, different time allocations, and different failure modes. Pick one per person, or pick both and hire two people.

A newly hired VP of Engineering has three things the org watches closely: what they cut, who they keep, and how fast they announce a plan. Get the sequence wrong and credibility is gone by week 4 — the org decides you're either a reorganiser or a lame duck before you understand the codebase. Michael Watkins' The First 90 Days is the foundational reference, but it's written for general executives. Engineering orgs have specific traps.

The counter-intuitive move: announce less in the first 30 days than you think you should. Not "listening tour" theatre — an actual measured pause while you read the org's calendar, incident history, and deploy pipeline.

A CFO usually sees engineering on one line of the P&L: salaries. A headcount column, a loaded-cost multiplier, a big number growing faster than revenue. That's it. Deloitte's 2024 Global Technology Leadership Study put the gap at its starkest: only 31% of CFOs said they could tell whether their engineering investment was producing returns proportionate to cost. The other 69% were flying blind on roughly the largest discretionary spend in the company.

This is not a tooling problem. It's a question problem. The numbers exist. Your CFO peers just haven't learned which five questions extract them.

McKinsey's 2023 developer productivity report found that engineers spend only 25-30% of their time writing code. The rest vanishes into meetings, context switching, and waiting. If you're an Engineering Manager relying on gut feeling, you're blind to where 70% of your team's capacity actually goes.

Here are 10 metrics that will sharpen your decisions. No fluff, no "track everything" advice — just the ones that separate informed management from guesswork.

Gallup research consistently shows that manager quality is the single largest factor in employee engagement — yet most engineering managers run 1:1s the same way: "How are things going?" followed by an awkward silence, then a pivot to project status updates. That's not a 1:1 — that's a standup with extra steps. Real 1:1s should be the most valuable 30 minutes in your developer's week, and data makes them dramatically better.

A Harvard Business Review analysis found that over 90% of managers admit their company's performance review process does not produce accurate results. In engineering, the problem is even worse: managers write vague paragraphs based on what they remember from the last two weeks. High performers who are quiet get overlooked. Loud underperformers get rated higher than they should. And everyone walks away feeling like the process was arbitrary. Data fixes this — but only if you use it correctly.

Stripe's "Developer Coefficient" report estimated that companies worldwide lose over $300 billion annually due to developer inefficiency — much of it from understaffed teams fighting technical debt instead of shipping features. You need more engineers. Your team is overloaded, deadlines are slipping, and technical debt is piling up. You know this intuitively. But your CFO doesn't care about your intuition — they care about numbers, ROI, and risk. The reason most headcount requests fail isn't that they're wrong. It's that they're argued in the wrong language.

Gartner estimates that fewer than 30% of engineering leaders have effective visibility into their team's actual performance. Every CTO has a dashboard — most of them are useless. They're either crammed with dozens of charts that nobody reads, or they're a single graph of velocity that tells you nothing actionable. A good CTO dashboard answers three questions: Are we delivering? Are we healthy? Are we improving? Here's how to build one that actually works.

The Stack Overflow Developer Survey consistently shows that developer autonomy and trust are among the strongest predictors of job satisfaction — yet most metrics implementations ignore this entirely. On one side, leaders who want to understand and improve their teams' performance. On the other, developers who hear "we're implementing metrics" and immediately think "Big Brother." Both sides have valid concerns. The question isn't whether to measure — it's how to measure without destroying the culture you're trying to improve.

As Matthew Skelton and Manuel Pais document in Team Topologies, the communication overhead between engineers grows quadratically: at 10 people there are 45 potential communication channels; at 100, there are nearly 5,000. At 10 engineers, you know everyone, you hear every conversation, you review most PRs. Things just work — because you're the glue holding it all together. At 100, that's impossible. The CTO who tries to manage 100 engineers the way they managed 10 will burn out, create bottlenecks, and watch quality collapse. The transition from 10 to 100 is the hardest organizational challenge a startup CTO faces, and data is the only way to navigate it without losing your mind.