Incident Rations
Incident Snacks
Emergency ration for 3 a.m. dashboards.
Plain English: Incidents cost more than repair time. They interrupt focus, trigger coordination overhead, and require postmortem learning.
What this snack represents
Emergency ration for 3 a.m. dashboards. Shelf-stable urgency with notes of pager fatigue and cold coffee.
Plain English: Incidents cost more than repair time. They interrupt focus, trigger coordination overhead, and require postmortem learning.
Formula: 1h triage × responders + 2h fix + 1h comms + 1h postmortem
What this teaches: Incident Cost, Interruption Cost, Postmortems.
Why teams underestimate it
The shelf label works because the cost is usually hidden across clarification, review, context switching, QA, and follow-up decisions. BarkBowl makes those ingredients visible before the work is treated as free.
Time formula
1h triage × responders + 2h fix + 1h comms + 1h postmortem
Worked example
One serving of Incident Snacks is currently modeled at 12 hours, or 12 person-hours. Multiply servings when the work repeats, spreads across more people, or needs another review cycle.
Warning label
Do not normalize hero mode.
Evidence needed
Before committing this snack, collect an owner, a reason, a time formula, a rollback or no-op alternative, and a short explanation of what the receipt does and does not prove.
How to reduce the cost
Runbook Rations
No-op alternative
If evidence, authority, or capacity is missing, the mature move may be to record a no-op decision and revisit when the missing ingredient exists.
What this teaches
- Incident Cost
- Interruption Cost
- Postmortems
Related lesson
incident-cost
Related field report
incident-cost
Related glossary terms
Incident Cost, Interruption Cost, Postmortems
Related blueprint
Decision record starter · Open Blueprint Gallery
Copy decision-record starter
Decision: Consider Incident SnacksTime formula: 1h triage × responders + 2h fix + 1h comms + 1h postmortemEvidence: [link or owner] No-op alternative: [what happens if we do not act] Boundary: This is a draft for human review, not an approval. Reviewed at UTC: [timestamp]
Boundary note
This snack produces draft learning and time-burn evidence only; it does not approve fixes, validate credentials, train models, or certify safety.
Dogfooding notes
Exercises product snapshotting, time totals, TTL refresh, telemetry, learning translation, and checkout record creation.