thehardparts.dev

2 min read Original article ↗

EP-17 Delivery

Run a phased migration

Move from old to new in controlled slices, where each slice has explicit ownership, cutover criteria, rollback, and retirement of the old path.

tech lead

EP-37 Team

Repair trust after a painful incident

Repair trust by making the event intelligible, changing the conditions that produced it, and demonstrating through behavior that the team is safer, more honest, and more accountable than before.

engineering manager

EP-16 Architecture

Refactor a dangerous hotspot

Refactor a hotspot by targeting the specific reasons it is dangerous: high churn, poor testability, unclear ownership, or oversized responsibility - and improving it in narrow, repeatable steps.

maintainer

EP-25 Operations

Run an incident review that actually helps

Turn an incident review into a system-learning exercise that explains what happened, why it made sense at the time, what conditions enabled it, and what changes will reduce recurrence.

incident lead

EP-01 Ai

Upgrade code review for AI-assisted work

Redesign review so that AI-assisted changes are judged by risk, understanding, and behavioral correctness, not by surface polish or author confidence.

tech lead

EP-05 Ai

Evaluate an AI feature against real tasks

Evaluate the feature against real user jobs, realistic failure patterns, and operational constraints so the team learns whether the system actually helps, not just whether it performs well on curated examples.

evaluation owner

Browse all 40 Playbooks →