Build a data-driven on-call workflow for your team with atomic habits Bianca Costache LeadDev London

Build a data-driven on-call workflow by understanding why issues happen, replacing bad habits, and empowering your team to take ownership of on-call challenges.

Key takeaways
  • Build a data-driven on-call workflow by understanding why on-call issues happen
  • Create a designated on-call backlog to prioritize action items
  • Replace bad habits with new ones, such as collecting on-call data
  • Provide cues for taking action, including alerts and incident reports
  • Make it obvious: share incident data and charts to inform decisions
  • Make it attractive: pair on-call tasks with meetings or other responsibilities
  • Make it easy: simplify workflows and reduce complexity
  • Reflect on results and improve the on-call workflow iteratively
  • Empower team members and leaders to take ownership of on-call challenges
  • Foster a culture of collaboration and continuous improvement
  • Break down on-call challenges into smaller, manageable tasks
  • Identify and address knowledge gaps and dependencies
  • Create a shared understanding of technical systems and workflows
  • Celebrate small wins and milestones in on-call workflow improvement
  • Continuously test and validate on-call workflow changes
  • Review and reflect on on-call statistics and metrics regularly
  • Provide opportunities for team members to learn and grow
  • Leverage on-call data to inform product and service development decisions