Measuring for Continuous Improvement

Part 4 of our continued focus is technology in People, Processes, and Technology.

Other Posts in this Series

Part 1: Harnessing Technology for Strategic Transformation

Part 2: Identifying Areas for Technology Intervention

Post 3: Adjusting Technology for Success

Welcome back to our series on transforming technology organizations through the People, Process, and Technology (PPT) framework. If you’re just joining us, check out our previous posts, where we explored aligning business objectives with technology solutions and identifying areas for technology intervention. Let’s dive into the next exciting phase: making those much-needed adjustments.

This is a bit of a reminder of the process we are following within Technology.

Measuring for Continuous Improvement

Welcome back to our series on transforming technology organizations through the People, Process, and Technology (PPT) framework. We’ve come a long way! After aligning business objectives with technology solutions, identifying areas for intervention, and making key adjustments, it’s time to see if our efforts are paying off. Yes, it’s time to measure our progress—because what’s the point of doing all that work if we can’t brag about the results?

In this post, we’ll delve into the art and science of measurement. We’ll discuss how to set up open communication channels for continuous feedback, evolve your tech stack based on performance data, and use quantitative and qualitative metrics to comprehensively view your technology’s impact. We’ll also explore the importance of benchmarking to assess the effectiveness of your interventions.

So grab your magnifying glass and your favorite data-crunching snack, and let’s get down to the measurement business!

Step 4: Measure (aka "Don't Be Afraid of the Data")

Measurement is crucial for assessing the impact of technology changes and ensuring that interventions align with business objectives. This step involves setting up metrics, maintaining open communication channels, evolving the tech stack, benchmarking performance, and using quantitative and qualitative data to guide further adjustments.

Open Communication Channels (Water Cooler 2.0)

• Objective: Foster continuous feedback and collaboration among the tech team and other stakeholders.
• Action: Schedule regular retrospectives and meetings to discuss the effectiveness of implemented tools and processes.
• Example: Hold bi-weekly retrospectives where the tech team discusses what’s working well and what’s not, enabling continuous improvement and quick problem resolution.
• Pro Tip:?Keep these meetings fun and engaging – maybe throw in a "best fail of the week" award.

Tools:

• Retrospectives.io or Retrium:?These tools are specifically designed to facilitate structured retrospectives.

Further Reading:

• The Art of Agile Development?by James Shore:?This book provides in-depth guidance on agile retrospectives and other feedback mechanisms.
• Agile Retrospectives: Making Good Teams Great?by Esther Derby and Diana Larsen:?A classic guide to retrospectives,?offering practical tips and techniques.

Evolving Tech Stack (Superhero Upgrade)

• Objective: Ensure the technology stack remains flexible and capable of evolving with the organization’s needs.
• Action: Regularly review and update the tech stack to incorporate new tools and technologies to enhance performance and efficiency.
• Example: Periodically assess whether current tools meet the organization’s needs and explore new technologies that could offer better performance or cost savings. Implement updates or changes as necessary.
• Warning:?Don't fall into the trap of "shiny object syndrome." New doesn't always mean better.

Tools:

• Dev.to: Great site for going into the details about specific technologies

Further Reading:

• The Lean Startup?by Eric Ries:?This book emphasizes the importance of continuous experimentation and adaptation in technology development.
• Crossing the Chasm?by Geoffrey A.?Moore:?This classic work explores the challenges of bringing new technologies to market and achieving mainstream adoption.
• The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win” by Gene Kim, Kevin Behr, and George Spafford
• Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations” by Nicole Forsgren, Jez Humble, and Gene Kim

Quantitative and Qualitative Metrics (The Heart and Soul)

• Objective: Use a combination of data types to comprehensively view technology performance and impact.
• Action: Define and track quantitative metrics (e.g., system uptime and bug counts) and qualitative metrics (e.g., user satisfaction and team morale).
• Example: Quantitative metrics might include system uptime (targeting 99.9% availability) and mean-time-to-repair (MTTR) for incidents. Qualitative metrics could be gathered through regular surveys of the tech team and end-users to assess satisfaction and morale.
• Pro Tip:?Combine the two for a superpower combo! Numbers show what's happening, but feelings tell you?why.

Tools:

• Datadog:?Monitor system performance,?infrastructure health,?and application logs.
• SurveyMonkey or Typeform:?Create and distribute surveys to gather user feedback and insights.

Further Reading:

• Lean Analytics?by Alistair Croll and Benjamin Yoskovitz:?This book provides a framework for using data to drive business decisions.
• Measuring and Managing Performance in Organizations?by Robert D.?Austin:?This book explores the complexities of performance measurement and offers practical advice.

Benchmarking (Tech Olympics)

• Objective: Compare performance before and after technology interventions to assess impact and effectiveness.
• Action: Set benchmarks for key performance indicators (KPIs) before implementing changes and measure performance against these benchmarks afterward.
• Example: Before implementing a new CI/CD pipeline, measure the average time from code commit to deployment. After implementation, compare the new times to see if the changes have led to significant improvements.
• Pro Tip:?Benchmarking isn't just about winning; it's about learning where you can improve.

Tools:

• Industry Reports:?Look for reports from reputable sources like Forrester,?Gartner,?or IDC that provide benchmarks for your industry and technology area.
• Competitor Analysis:?Conduct research on your competitors' performance and technology choices.
• Internal Data Analysis:?Compare your current performance against historical data to track your own progress.

Further Reading:

• The Balanced Scorecard?by Robert S.?Kaplan and David P.?Norton:?This classic book introduces a framework for measuring organizational performance across multiple dimensions.
• Benchmarking for Best Practices?by Christopher E.?Bogan and Michael J.?English:?This book provides a comprehensive guide to benchmarking methodologies and best practices.

Measurement is Your Crystal Ball

In technology transformation,?measurement isn't just about counting beans or tracking lines of code.?It's about gaining the insights you need to steer your tech ship towards success.?You'll unlock a treasure trove of information by opening communication channels, evolving your tech stack, embracing both the numbers and the feels, and benchmarking your progress.?This data isn't just for bragging rights (although those are fun, too); it's the roadmap to continuous improvement.

Remember,?measurement isn't a one-time event; it's an ongoing journey.?It's about constantly asking questions, challenging assumptions,?and seeking ways to level up your tech game.?So keep your magnifying glasses handy and your data-crunching snacks stocked – because the pursuit of better is never truly finished.

Post 5 Sneak Peek: The Neverending Story of Continuous Improvement

Next time,?we'll dive into the final frontier of tech transformation:?embracing continuous improvement.?We'll explore how to create a culture of learning and experimentation?where innovation is the norm and stagnation is the enemy.?We'll talk about staying ahead of the curve,?embracing the chaos of change,?and making bold and informed decisions.Get ready to transform your tech team into a learning machine – because the best is yet to come!

Stay tuned for Post 5: Embracing Continuous Improvement

Let me know if you'd like any further refinements to the conclusion or introduction!