38 posts tagged with "leadership"

A VP of Engineering told me the number that hurts: "We spent $140,000 on an offsite in Bali in Q1. By Q3, nobody on the team remembered a single decision we made there." A 40-person engineering offsite routinely costs $80-200K in direct spend (travel, venue, food, activities) plus 200-320 engineer-weeks of displaced work, and the Gallup 2023 Workplace Report documents that only 29% of companies can articulate a measurable outcome from their last off-site event.

The default failure isn't venue or agenda — it's that the offsite was scheduled as a cultural ritual with outcomes defined after the fact. Flipping that order changes the ROI by an order of magnitude. The framework below is how the engineering leaders with repeatable-ROI offsites plan them, and it works across the three formats that produce measurable results: hackathons, strategy sprints, and team-bonding events. Each format has different economics.

A public company we'll call Company X hit its 2023 engineering DEI target: 28% women in engineering, up from 21%. Two years later, the number was back to 22%. Hiring kept working; retention didn't. The post-mortem found three patterns the original program missed: under-promotion of women with 2-4 years tenure, above-average code-review rejection rates for under-represented minorities, and assignment bias toward "glue work" that doesn't count for promotion.

Most engineering DEI programs stop measuring at the top of the funnel. Hiring numbers are public, easy to collect, and lend themselves to targets. What happens after someone joins — the promotion rate, the review cycle, the assignment pattern — is where culture actually lives. And it's where programs succeed or fail quietly, often without management noticing until the exit interviews pile up.

Two senior engineers at a 60-person SaaS I mentored stopped speaking for seven weeks. The cause, by their accounts, was "a personality clash." The cause, by the data: engineer A had merged without review into engineer B's service 23 times in 8 weeks; engineer B's review queue had grown from 4 PRs to 31 in the same window. Each had a legitimate grievance neither could cleanly articulate. The moment their EM put the two numbers on a slide, the fight ended — not because anyone won, but because the dispute stopped being about the other person's character.

Most conflict in engineering teams isn't about personalities. It's about process gaps, priority mismatches, and workload inequities that people can't see from inside the conflict. A 2022 Harvard Business Review study on team dysfunction placed "ambiguity about who owns what" as the #1 driver of interpersonal conflict on knowledge-work teams. The resolution isn't better feelings — it's a shared picture of reality. Data is how you build it.

Netflix's "Freedom & Responsibility" deck was downloaded more than 20 million times after Patty McCord published it in 2009. Stripe's engineering principles, GitLab's Handbook, Basecamp's Shape Up — the public culture documents that became landmarks share three properties: they're short, they're opinionated, and they describe how decisions get made, not what the team values in the abstract.

Most engineering-culture docs written at most companies die within a year. They die because they're written for an offsite, printed on a poster, and never referenced again when the real test comes: a conflict between shipping speed and code quality at 5:30 PM on a Thursday. This post gives a template that survives that moment, with three filled examples drawn from real engineering organizations.

A Series-B board presentation went sideways in 2023 when a director — former GitHub VPE — asked the CTO three questions in a row she hadn't prepared for. She knew deployment frequency and team size. She didn't know median lead time, hiring velocity against plan, or the engineering payroll as a share of operating burn. The board didn't defund engineering, but they added a quarterly engineering review with a different CTO on the call. The meeting became a test the team passed but the CTO didn't.

Boards are harder to prepare for than investors because they have more context and less patience. This is a question list — what a working board actually asks, what the CTO should bring without being asked, and the red flags an experienced director spots in 15 minutes. We collected it from conversations with CTOs who have presented successfully, CTOs who haven't, and two board directors who sit on engineering-heavy portfolios.

In 2024, LinkedIn's Workforce Report flagged "HR-Engineering misalignment" as the #2 reason scaling tech teams lose senior engineers, right behind compensation. The usual failure mode: HR designs job ladders on a generic template, Engineering runs calibration as an undocumented side-channel, and two months later the best senior left because their title didn't update with their responsibilities.

This is not an HR problem, and not an Engineering problem. It's a collaboration problem that surfaces every 6-12 months during promotion and compensation cycles. Here's a playbook for making the partnership actually work — who owns what, when, and which data gets shared.

Will Larson's 2021 survey of 14 staff engineers at large tech companies produced a finding most ladders still ignore: only one in three senior engineers wants the Staff title, and of those, fewer than half make it in five years. The promotion is not a natural continuation of Senior. It's a role change — different work, different signals, different failure modes. Engineering ladders that treat it as "Senior+" produce stalled careers and a pile of ICs who quit for an EM job at another company.

This framework is what actually predicts readiness, drawn from a mix of Larson's research, Tanya Reilly's The Staff Engineer's Path, and the patterns we see in delivery data across 100+ B2B engineering organizations.

The standing monthly engineering cost review at the 80-person org we worked with in March 2026 ran 90 minutes. Six dashboards. Four department leads each defending their numbers. The output: a Slack message saying "let's dig in next month." Same message in February. Same in January. The dashboards were excellent. The decisions were zero.

The problem is not data scarcity. Asana's 2024 Anatomy of Work report found knowledge workers spend 58% of the day on "work about work," meetings, status updates, and dashboard reviews, and that the modal review meeting produces no concrete next action. Engineering cost reviews are a textbook case. Too many numbers, no forcing function for a decision.

Open the Finances page for an organization with 38 active projects. The default view is a sortable table: project name, cost last 30 days, cost all-time, owner, status. The CFO's monthly cost review starts here. 38 rows, 8 minutes of scrolling, and a 60% chance the most-expensive project is on row 17 where nobody actually looks. Edward Tufte made the case in The Visual Display of Quantitative Information (1983, 2nd ed. 2001) that humans process color and size before they process numbers. A heatmap of the same 38 projects surfaces the dark-red square in under a second. Stephen Few's Information Dashboard Design (2006, 2nd ed. 2013) reaches the same conclusion in industry research: when monitoring requires "find the outlier," tabular data is the wrong primary view. PanDev Metrics' Projects Heatmap widget runs both modes side by side. This post is about why the mosaic should be the default and the list the cross-check.

A principal engineer at a 200-person fintech spent Q3 writing 180 lines of code. Her team shipped 340,000 lines in the same period. When her CTO looked at coding-time dashboards for a performance review, she almost got flagged as underperforming. What actually happened in Q3: she rewrote the payment reconciliation spec that unblocked two teams, mentored three senior engineers into tech-lead roles, and killed a six-month project that would have shipped something the market didn't want. Her measurable output was tiny. Her impact was the largest of any engineer in the company that quarter.

This is the principal engineer measurement paradox. Every staff-plus framework (Will Larson's, Tanya Reilly's The Staff Engineer's Path, the Google internal engineering ladder) acknowledges it: principal engineers are paid for judgment and force multiplication, not throughput. But most engineering orgs measure them like senior engineers with a bigger title. This article is how to measure principal impact honestly — and how a principal should measure their own impact when the review conversation comes.