Safeguarding

Safeguarding is a rigorous process to decrease the time your team wastes on failure demand and the customer and business losses from failures. Simply: safeguarding lets teams prevent mistakes. They don’t spend as much time finding, managing, and fixing issues, because they never create them in the first place.

Safeguarding your software against bugs will:

  • Improve productivity
    • Less dev time on Tier 2 support / helpdesk
    • Less time managing defects
    • Less time writing customer support documentation
    • Less time debugging
    • Less time responding to QA bug reports
    • Less time putting together test builds
    • Less time deploying
    • Less time testing for bugs
  • Reduce operational costs
    • Fewer customer support calls
    • Lower operational support needs for upgrades
    • Fewer security incidents to respond to
    • Fewer on-call emergencies and decreased operational staffing

Timeline

Each change happens in 3 phases.

Expand
Introduce new behaviors
  • Concrete behavior change.
  • One change at a time.
  • Learn in real world, not lab.
  • Proficiency focus: improve behavior consistency and quality.
Master
Make behaviors habitual
  • Integrate all new behaviors.
  • Apply to novel situations.
  • Fluency focus: make behavior automatic and easy.
Leverage
Integrate into everything
  • Reduce other processes.
  • Reduce defect spend.
  • Pay down defect backlog.

Safeguarding’s Two Big Changes


Module 1: Prevent Problems

Remove the hazards that cause mistakes. Use data to invest incrementally. Ensure each investment reduces cost today. Maximize the value of your investments over time.

Module 2: Show ROI

Learn how to demonstrate the failures that never happened and show the value of your Safeguards.