Demonstrate Measurable Results from your RCAs

Do the same problems keep showing up over and over? Do you keep scheduling root cause analyses and improvement stories for the same problem?

Commonly, teams will find underlying factors that are too big to solve and never successfully execute the work needed to solve it.

The first step is to ensure that every week results work that can be demonstrated. Implementing a 10% better model addresses the big mountain problems incrementally. These practices heal unhealthy roots in your codebase and culture.

We provide a framework in our Safeguarding: Fixing Problems 10% at a Time. This practical approach allows developers to identify and improve by 10% one source of bugs each week. If this sounds insignificant, consider the compound impact of all your teams doing this for a quarter. You now spend half as much time on bugs and general maintenance.

During three sequential Sprint cycles of integrating Safeguarding into your workflow, you get:

  • 6 concrete practices integrated in your Sprint process
  • Instructional packet detailing each practice
  • Introductory coaching session with Arlo
  • Debugging coaching session with Arlo
  • On-going Slack support

Augment your Safeguarding for high performance, and you get:

  • 5 additional concrete practices for smoother planning flow
  • Safeguarding meeting demo with your team by Arlo
  • One-on-one Scrummaster coaching by Arlo
  • Two observations by Arlo of Scummaster’s meeting facilitation
  • On-going Slack support throughout and after delivery

Client Case Studies

Improving Quality

We needed to improve quality. Not just once, but all the time. And we needed to do it across over 100 teams, each of which had a different context and different quality problems. The problem that impacted the greatest number of teams impacted only 6 — and more than 70% of the problems affected only one team.

No central plan could help. We needed a systematic solution, a strategy, but not a central plan. We needed a practice, a habit — something that combined funding with problem fixing while reinforcing local ownership.

That’s when we used Safeguarding. That was more than a year ago; now teams are owning their quality and actively making things better.

Reducing Risk

Another company had consistent risk aversion. Commonly, people identified the option with the highest expected value…and then did something else. In that environment, the personal costs of even tiny failures were too high. So everyone consistently chose the lowest-risk option, even when that was a guaranteed bad outcome. Psychological safety was universally missing, and yet each relationship was different, with different risks.

Safeguarding was also an effective strategy for creating Psychological Safety.

Let’s have a chat!