Skip to main content
Version: 2.0

Continuous Improvement

Continuous improvement. It's a buzzword, sure, but it’s also the bedrock of any thriving engineering organization. Not because it demands sweeping, disruptive changes, but precisely the opposite – because it champions the consistent application of small improvements. As engineering managers, we’re often pressured to deliver big, visible wins. I've seen teams celebrate major feature launches, only to be immediately pulled into firefighting mode due to underlying technical debt or process inefficiencies. The real magic happens in the accumulation of those tiny, almost imperceptible gains. And crucial to unlocking this power is understanding how to build buy-in from your stakeholders – not just your team, but upwards and across the organization.

Beyond “Do More Faster”: The Pitfalls of Impatience​

The mantra “Do More Faster,” popularized in the tech startup world (as advocated by TechStars mentors & alums, 2010), can be alluring. It suggests relentless acceleration and understandably appeals to the desire for rapid progress. However, without a foundation of how we improve – focusing solely on speed without quality or thoughtful iteration – it can quickly lead to burnout, technical debt, and, ironically, slower progress.

I’ve seen it firsthand. A team I led was pressured to rapidly ship a new feature, bypassing crucial refactoring. We delivered, but the resulting instability and mounting technical debt plagued us for months, slowing down all subsequent development. This wasn’t a lack of effort; it was a failure to prioritize continuous, sustainable improvement over short-term gains.

The idea that stifling good ideas – even small ones – can be detrimental rings particularly true. When suggestions are ignored, it breeds disengagement and ultimately, attrition. It sends a clear message: your input isn't valued, and the organization isn’t interested in learning.

Why Incrementalism Wins: A Systems Thinking Approach​

Continuous improvement isn’t about radical innovation every week. It’s about building a system where everyone feels empowered to identify and address small inefficiencies. Think of it like compound interest. Each small improvement, on its own, may seem insignificant, but over time, they accumulate into substantial gains.

Here’s how to frame it:

  • Focus on the Process, Not Just the Outcome: Encourage your team to not just solve a problem, but to improve the way they solve problems. Post-mortems (or retrospectives) are ideal for this.
  • Empowerment & Psychological Safety: A key finding from studies on retrospectives (Lassenius, 2012; Normann & Speicher, 2014) is that teams need to feel safe to voice concerns and suggest improvements without fear of retribution. This requires fostering a culture of psychological safety.
  • Small Batches & Frequent Feedback: Breaking down large tasks into smaller, manageable chunks allows for quicker feedback loops and faster iteration. This reduces risk and accelerates learning.

Stakeholder Management: Getting Buy-In for Continuous Improvement​

The biggest hurdle isn’t doing the small improvements; it’s convincing others of their value. Here’s where stakeholder management comes in. It’s common to encounter resistance – “We don’t have time for this,” or “It feels like extra work.” Addressing these concerns proactively is key.

  • Communicate the “Why”: Explain that continuous improvement isn’t a distraction from “real work,” but is the real work. Connect it to key business objectives (e.g., reduced costs, increased customer satisfaction, faster time to market).
  • Transparency & Visibility: Share the results of small improvements with stakeholders. A simple dashboard tracking key metrics (e.g., code coverage, bug fix rate, build time) can be incredibly effective.
  • Manage Expectations: Don't promise overnight miracles. Proactively communicate that continuous improvement is a long-term commitment, and that results will accumulate over time.
  • Address Resistance: Some stakeholders may resist change, even small changes. Listen to their concerns, address their fears, and demonstrate the benefits of improvement.
  • Link to Strategic Goals: Demonstrate how even incremental improvements contribute to larger strategic objectives. This helps justify the time and effort invested.

Demonstrating impact is crucial for securing continued buy-in. Implement ways to measure the effect of your improvements. A/B testing, user feedback surveys, and performance monitoring are all valuable tools. As the research suggests, it's crucial to empirically validate assumptions about what works in retrospectives and improvement practices. What works for one team may not work for another.

Beyond the Tech: Organizational Level Retrospectives​

Don’t confine continuous improvement to the engineering team. Encourage cross-functional retrospectives involving stakeholders from product, design, and marketing. Siloed improvement efforts can create unintended consequences or fail to address systemic issues. By fostering collaboration, you break down silos and ensure that improvements align with overall business objectives.

Continuous improvement isn’t a destination; it's a journey. By embracing incrementalism, empowering your team, and building strong stakeholder relationships, you can create a culture of continuous learning and innovation that drives long-term success. It’s about shifting from reactive problem-solving to proactive prevention, one small improvement at a time.