## Overview After a user has identified the root cause of the problem, they can fix it and restore critical services. Fixing the problem often requires collaboration with teammates and is always much faster when the User is armed with a detailed and well-maintained runbook. During the resolution phase, the user will need to update stakeholders on progress and when services are restored as well as any tickets/issues that are being used to track the work. ## Our goal Automate (where feasible) or make as simple as possible, the ability to engage teammates during the resolution phase, update stakeholders, and ensure that the User can get a verified solution released to production as quickly as possible. ## How We should automate the simple and repetitive tasks (spinning up a conference bridge, updating a status page, ticket creation and closure, etc) where we can. Our mission is to help the user restore services as quickly as possible so that they can move from a reactive state to a proactive state where they can [improve](https://gitlab.com/groups/gitlab-org/-/epics/1973) their systems. ## User Journeys The following are high-level, visionary journeys we want to enable in GitLab. Each step in these journeys could be a detailed workflow. Additionally, these journeys are ever evolving as we learn more about our users and identify new opportunities. [Resolve Workflow](https://app.mural.co/t/gitlab2474/m/gitlab2474/1570051051389/4ae08d3ad4f38fa5792240851fd54710e04f5d11)