26 posts tagged with "leadership"

McKinsey research on engineering effectiveness found that the highest-performing organizations share one trait: their engineering goals are explicitly connected to business outcomes. Yet most engineering teams write OKRs like "Improve code quality" with a key result of "Increase test coverage to 80%." That's not an OKR. That's a task with a number next to it. Good engineering OKRs connect technical work to business outcomes, and the right metrics make them actually measurable.

Every quarter, CTOs face the same uncomfortable meeting. The CEO asks: "We spent $2.4M on engineering last quarter. What did we get for it?" And the answer is usually a list of shipped features — not a financial return.

Engineering is the largest cost center in most technology companies, yet it's the one with the least financial accountability. Marketing can show customer acquisition cost. Sales can show revenue per rep. Engineering shows... velocity points? McKinsey's analysis of software developer productivity highlights this gap: engineering output is measurable, but most organizations haven't built the systems to do it.

It's time to change that.

It's budget season. The CTO submits an engineering budget request: $8.2M for next year, up 18% from this year. The CFO asks for justification. The CTO points to headcount growth, salary inflation, and a list of planned projects. The CFO pushes back: "Can we do it for $7M?" The CTO says no. They compromise at $7.5M.

Neither number is based on data. The CTO added a buffer to last year's spend. The CFO cut it by a round number. The compromise has no analytical basis. Both sides walk away slightly unhappy. A Deloitte CFO Survey found that technology spending is consistently one of the hardest budget categories for finance teams to evaluate — largely because the inputs are opaque.

This is how most IT budgets are built. It doesn't have to be.

Every CTO has had this conversation. You walk into the CEO's office and say, "We need to spend the next quarter refactoring." The CEO asks, "What's the business value?" You struggle to answer in terms that don't involve the words "architecture," "coupling," or "dependency injection." The DORA State of DevOps Reports consistently find that teams burdened by technical debt deploy ~50% less frequently and have ~2-3x higher change failure rates.

The CEO isn't wrong to ask. They're not anti-engineering. They just need to understand the investment in business terms. And that's where most CTOs fail — not because they're bad communicators, but because they don't have the right data.

Here's how to fix that.

The most common fear engineers have about activity tracking is simple: "My manager will use this data against me."

They're not wrong to worry. Many organizations have implemented "productivity metrics" as a stick — identifying who codes the least, who commits the fewest lines, who logs the shortest hours. The result is predictable: developers game the metrics, resentment builds, top performers leave, and the remaining team optimizes for looking busy rather than being effective.

There's a better way. Data can be a tool for positive reinforcement — and it's far more effective.

You're considering adding a leaderboard to your engineering team. Maybe your platform already has one. The idea sounds straightforward: show who's contributing the most, and everyone will be motivated to contribute more.

In reality, leaderboards are the most polarizing gamification feature in engineering. Self-Determination Theory (Deci & Ryan) warns that extrinsic ranking systems can undermine intrinsic motivation — but research also shows that well-designed recognition systems boost engagement. Done right, they create healthy engagement and visibility. Done wrong, they create anxiety, gaming, and resentment.

Here's how to get them right.