Rollback Decision Framework

J

Jordan Reyes

@jordan-reyes

·

Make structured rollback decisions during production incidents

50 copies0 forks
Help decide whether to rollback {{release_name}} given current issues.

Release details: {{release_details}}
Issues observed: {{issues}}
Users affected: {{affected_users}}
Time since release: {{time_elapsed}}

**Assessment Framework:**

1. **Impact Analysis**
   - Severity of issues (critical/high/medium/low)
   - Scope of impact (% of users)
   - Business impact (revenue, reputation)
   - Is impact growing or stable?

2. **Forward Fix Assessment**
   - Can we fix forward?
   - Time to fix estimate
   - Confidence in fix
   - Risk of making it worse

3. **Rollback Feasibility**
   - Is rollback possible?
   - Data migration concerns
   - User state considerations
   - Rollback risks

4. **Decision Matrix:**
   - Rollback if: [criteria]
   - Fix forward if: [criteria]
   - Wait and monitor if: [criteria]

**Recommendation:**
- Recommended action
- Reasoning
- Steps to execute
- Communication plan

**Post-Decision:**
- What to monitor
- Success criteria
- Escalation triggers
- Post-mortem scheduling

Details

Category

Analysis

Use Cases

Incident responseRelease decisionsRisk assessment

Works Best With

gpt-4claude-3
Created Updated Shared

Create your own prompt vault and start sharing

Rollback Decision Framework | Promptsy