What is Problem Reporting & Corrective Action template & why PMs should get their hands dirty in creating one?

It’s crucial for PMs to understand the technology issue in detail so that they can create detailed PRD for future features.

Let’s go through the most common format in which such templates are created :

Priority:

<Mention the priority of the issue>

Description:

<Write a detailed description of the issue >

Resolution Steps:

<Explain in detail the steps taken to resolve the issue >

Impact:

<Highlight the business metric which got impacted due to this issue. >

Platform Impacted:

<Call out the list of platforms which got impacted due to this issue >

User Impact:

<Mention the impact or the problems faced by the end user due to this issue>

Long-term resolution :

<Figure out a long-term solution to fix this issue permanently >

Root cause:

<Ask 5 whys>

Learnings:

• <Highlight and list down the key learnings from this incident>
• <Highlight the positives during the issue resolution>

Alerting:

• <Why the system never trigged the alerts>
• <Steps to setup proper monitoring and alerting in real time>

Alerting Channel:

<List of channels where the alerts are received — slack, emails etc. >

Dashboard Links:

<List of dashboards where the performance can be monitored >

Incident Start Time:

<Start time of the issue>

Incident End Time:

<End time of the issue>

RCA Owner:

<Details of the RCA owner>

RCA Owning Team:

< Details of the RCA owning team

Issue Detection:

• <How fast the issue was detected>
• <What mode was the issue detected>
• <How the issue was detected >

Issue Owner:

< Details of the issue owner >

Issue Owning Team:

<Team that fixed the issue>

Thanks for reading! If you’ve got ideas to contribute to this conversation please comment. If you like what you read and want to see more, clap me some love! Follow me here, or connect with me on?LinkedIn?or?Twitter.