Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-sonnet-4-20250514· AnthropicHugging Face LMArena Human Preference 140K

Make a detailed root cause analysis template

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Amazon Novaamazon.nova-pro-v1:0’s answer.
  1. User

    Make a detailed root cause analysis template

  2. Claude Assistant

    Root Cause Analysis Template

    Incident Overview

    Date of Analysis: [Date]
    Analyst(s): [Name(s)]
    Incident ID: [Reference Number]
    Incident Date/Time: [When the incident occurred]
    Duration: [How long the incident lasted]
    Severity Level: [Critical/High/Medium/Low]

    Problem Statement

    Brief Description: [One-sentence summary of what happened]

    Detailed Description: [Comprehensive explanation of the incident, including what was observed, who was affected, and the scope of impact]

    Impact Assessment:

    • Business impact: [Revenue loss, customer impact, operational disruption]
    • Technical impact: [System downtime, data loss, performance degradation]
    • Stakeholders affected: [Internal teams, customers, partners]

    Timeline of Events

    TimeEventSourceAction Taken
    [Time][What happened][How discovered][Response]
    [Time][What happened][How discovered][Response]

    Investigation Process

    Data Collection Methods:

    • Log analysis
    • System monitoring data
    • Interviews with personnel
    • Documentation review
    • Physical inspection

    Evidence Gathered: [List all relevant data, logs, screenshots, witness statements, and documentation collected during the investigation]

    Root Cause Analysis Method

    Technique Used: [5 Whys, Fishbone Diagram, Fault Tree Analysis, etc.]

    5 Whys Analysis

    1. Why did [problem] occur? [Answer]
    2. Why did [answer from #1] happen? [Answer]
    3. Why did [answer from #2] happen? [Answer]
    4. Why did [answer from #3] happen? [Answer]
    5. Why did [answer from #4] happen? [Answer - Root Cause]

    Contributing Factors Analysis

    People Factors:

    • Training gaps
    • Communication issues
    • Workload/stress
    • Knowledge/experience levels

    Process Factors:

    • Inadequate procedures
    • Missing checkpoints
    • Unclear responsibilities
    • Poor documentation

    Technology Factors:

    • System limitations
    • Configuration issues
    • Hardware failures
    • Software bugs

    Environmental Factors:

    • External dependencies
    • Regulatory changes
    • Market conditions
    • Physical environment

    Root Cause Identification

    Primary Root Cause: [The fundamental reason the incident occurred]

    Secondary Root Causes: [Additional underlying causes that contributed to the incident]

    Immediate Causes: [Direct triggers that led to the incident]

    Corrective Actions

    Immediate Actions (Already Taken)

    ActionOwnerDate CompletedEffectiveness
    [Action][Person][Date][Assessment]

    Short-term Actions (0-30 days)

    ActionOwnerTarget DateSuccess CriteriaStatus
    [Action][Person][Date][Measurable outcome][Status]

    Long-term Actions (30+ days)

    ActionOwnerTarget DateSuccess CriteriaStatus
    [Action][Person][Date][Measurable outcome][Status]

    Prevention Measures

    Process Improvements: [Changes to procedures, workflows, or policies to prevent recurrence]

    Training Requirements: [Additional training needed for staff to prevent similar incidents]

    Technology Enhancements: [System upgrades, monitoring improvements, or new tools needed]

    Monitoring and Detection: [New alerts, checks, or monitoring to catch similar issues early]

    Lessons Learned

    What Worked Well: [Positive aspects of the response and existing processes]

    Areas for Improvement: [Gaps identified in current processes or responses]

    Knowledge Gained: [New insights about systems, processes, or risks]

    Follow-up Plan

    Review Schedule:

    • 30-day review: [Date]
    • 60-day review: [Date]
    • 90-day review: [Date]

    Success Metrics: [How you will measure the effectiveness of corrective actions]

    Communication Plan: [How findings and actions will be shared with stakeholders]

    Approval and Sign-off

    Prepared by: [Name, Title, Date]
    Reviewed by: [Name, Title, Date]
    Approved by: [Name, Title, Date]

    Appendices

    Appendix A: Supporting documentation
    Appendix B: Technical logs and data
    Appendix C: Interview notes
    Appendix D: Visual aids (diagrams, charts, photos)


    Notes for Use:

    • Customize sections based on your organization's specific needs
    • Include relevant stakeholders in the analysis process
    • Focus on systemic issues rather than individual blame
    • Ensure actions are specific, measurable, and assigned to owners
    • Schedule regular follow-ups to verify corrective action effectiveness

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.