For many of our customers, an important part of adopting DevOps is moving from a centralized NOC or incident handling process to a distributed service ownership model.

As teams move towards a service ownership model, it’s more important than ever to understand and map service dependencies, as these provide a path to faster remediation. When teams are empowered to change and armed with DevOps best practices, it means a better incident response process and improved quality of life for responders.

Teams need a clear understanding of how to configure their services at scale to meet organization requirements. This helps teams see “what good looks like” while also giving organization leaders visibility into the state of their services across the technology ecosystem.

Join Hannah Culver, Associate Product Marketing Manager, Davis Godbout, Principal Product Manager and Karen Meyers, Sr. Strategic Customer Success Manager as they discuss:

• What service ownership looks like at scale and how it can improve incident response
• How PagerDuty’s Service Standards and Dynamic Service Graph can help teams during and after the transition period
• Lessons learned from working with PagerDuty customers such as how to overcome challenges adopting service ownership at scale