85 posts tagged with "engineering-management"

A mid-size team I advised last year had a standing rule: every ticket above 3 story points needed a design doc. Eight engineers, roughly four docs per week, each doc eating a half-day to write and another half-day in review cycles. That's 32 engineering hours per week — four full working days a week, spent on documents that most people scanned once and never reopened. The CTO thought they were a high-discipline shop. The data said they were documentation-heavy and velocity-poor.

The opposite extreme is worse. A 2019 report from Stack Overflow's Developer Survey listed "poor documentation of internal systems" as the #2 productivity blocker after technical debt itself. Skipping design docs entirely means every sixth-month refactor is an archaeology dig.

This is the framework I use to decide which changes deserve a doc, which deserve a 3-sentence RFC comment, and which deserve nothing at all.

The average engineering retro runs 60 minutes, produces five sticky notes, and ships zero action items into the next sprint. The Scrum Alliance's 2023 practitioner survey put "retros feel performative" as the #1 complaint from senior engineers. That's not a meeting problem. It's a measurement problem. Teams debate feelings because nobody pulled the data before the call.

This article gives you a 30-minute retrospective that opens with numbers, ends with named owners, and works on any team between 5 and 25 engineers.

Two developers on one task. Double the labor cost, half the bugs, and nobody agrees on whether it pays back. The most-cited study on this question — Cockburn & Williams, The Costs and Benefits of Pair Programming (2000) — reported a 15% time overhead for paired work and a 15% drop in defects. That looks neutral on paper. It isn't. The math of defects-caught-early flips the ROI by roughly 2× once you include rework avoided and shipped-bug incidents prevented.

This article crosses Cockburn and Williams' academic data with our own IDE heartbeat dataset across 100+ B2B companies — including teams that pair daily and teams that never do — to answer the question practically. Not "is pair programming good?" but "when does it pay back and when is it theatre?".

Right now, your team has pull requests stuck in review. Probably three or more. One's been sitting for five days. A 2018 study from Google's engineering productivity group (Sadowski et al., Modern Code Review: A Case Study at Google) found that the median review at Google completes in less than 4 hours. In most teams we see, that number is 4 days — a 24× gap explained almost entirely by process, not talent.

This is a checklist of 11 rules that cut review time in half without reducing quality. Each is backed by external research, refined against real engineering-team data, and structured into three phases: author discipline, reviewer discipline, team discipline.

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.

Most DORA adoption efforts fail not because of tooling or data — but because they become 6-month projects that die in committee. The Accelerate research (Forsgren, Humble, Kim, 2018) showed that organizations with visible delivery metrics improve faster. The key word is visible: a dashboard nobody looks at is worse than no dashboard, because it creates the illusion of measurement. Here's a day-by-day plan to go from zero to live DORA dashboards in two weeks — fast enough that the momentum doesn't dissipate.

Gloria Mark's research at UC Irvine found that it takes an average of 23 minutes and 15 seconds to refocus after a single interruption. Now consider a typical developer morning: 9:07 Slack pings, 9:15 standup reminder, 9:45 a "quick question" from a PM. By 10:30, they've been "working" for 90 minutes but written exactly 11 lines of code. Three interruptions consumed roughly 70 minutes of cognitive recovery time.

This isn't a productivity problem. It's a focus time problem. And the data shows it's costing your team far more than you think.

Nobody quits on a Monday. The resignation email you receive on a random Thursday was written — emotionally — six weeks ago. The disengagement started three months ago. And the data saw it coming the entire time.

The 2023 Stack Overflow Developer Survey found that over 70% of developers reported some level of burnout symptoms. Replacing a mid-level software engineer costs an estimated 50-200% of their annual salary when you factor in recruiting, onboarding, and lost institutional knowledge. The SPACE framework (Forsgren et al., 2021) explicitly includes "Satisfaction and well-being" as a core productivity dimension — recognizing that burned-out developers aren't just unhappy, they're materially less productive. But the signals are visible in activity data long before the resignation letter.

Here are five patterns that show up in IDE activity data weeks — sometimes months — before a developer burns out or leaves.

Your senior developer is assigned to three projects. You assume they're giving each project a third of their time. Gerald Weinberg calculated the real math in Quality Software Management (1992): with three concurrent projects, each project gets about 20% of a developer's time — and the remaining 40% evaporates into context switching overhead.

This isn't speculation. It's a well-documented cognitive phenomenon, confirmed by our platform data across B2B engineering teams and consistent with Gloria Mark's research at UC Irvine showing 23 minutes of recovery time per interruption. Context switching is one of the most expensive invisible costs in software engineering.

According to McKinsey's research on developer productivity, software engineers spend only 25-30% of their time actually writing code. So where developers work should matter far less than how their time is structured. Yet the remote vs. office debate has been running for six years, with CEOs citing "collaboration" and developers citing "focus" — both arguing from conviction, not evidence.

We have thousands of hours of tracked IDE activity across 100+ B2B companies. The data tells a more nuanced story than either side wants to hear.