The Analog Incident Herb Garden: Growing Tiny Paper Rituals That Calm On‑Call Chaos

If your on‑call rotation feels like a frantic game of whack‑a‑mole, you’re not alone. Pager fatigue, 3 a.m. firefighting, and unclear responsibilities can turn even the best teams into burnt-out responders.

But what if you approached incident response the way a gardener approaches a herb garden—slowly, intentionally, and with small, repeatable rituals that compound over time?

In this post, we’ll explore the “Analog Incident Herb Garden” as a metaphor and practical workshop format. You’ll learn how to use it for team building, strategic planning, conflict resolution, and designing calmer on‑call systems built around tiny paper rituals that grow into resilient habits.

Why an Herb Garden? Because Incidents Are Living Systems

An herb garden is:

Small and manageable – not a wild forest, but something you can see, tend, and influence.
Diverse – different plants with different needs, just like roles on an incident team.
Cyclical – seasons of planting, growth, harvest, and rest; much like on‑call cycles, postmortems, and improvements.

Treating incident response like gardening shifts the mindset from

“We’re constantly under attack!”
to
“We’re cultivating a system that can handle stress.”

The Analog Incident Herb Garden is a way to:

Surface emotions and perspectives using a non-technical image.
Turn ideas into tiny paper rituals: small, written, repeatable practices.
Redesign on‑call schedules and workflows into a well‑tended garden, not an overgrown patch of chaos.

Step 1: Start With the Garden Image (5–10 Minutes)

Begin your session (team retrospective, strategy workshop, or incident review) with a simple garden image—printed on paper or displayed on a screen.

Ask people to reflect individually for 2–3 minutes:

“If our on‑call practice were this garden, which plant would you be?”
“What part of the garden feels overgrown?”
“Where do you see bare soil—places we haven’t planted anything yet?”

Then move into pairs or triads for 5–7 minutes to share reflections:

What emotions came up? (Stress, pride, resentment, hope?)
What surprised you about your partner’s view of the garden?
What “plants” (practices) are thriving? Which are failing?

This brief discussion does several things at once:

Builds psychological safety by starting with metaphor, not blame.
Surfaces hidden expectations and frustrations.
Creates a shared language: “this process feels like a weed,” “this ritual is our rosemary—reliable and hardy.”

You now have fertile soil for deeper work: planning, conflict resolution, and decision‑making.

Step 2: Turn Feelings into “Tiny Paper Rituals” (Planting Seeds)

Next, move from metaphor to concrete action using tiny paper rituals: small notes (Post‑its, index cards, or digital equivalents) that describe a single, repeatable practice.

Think of each note as a seed you’re planting in your incident garden.

Examples of tiny paper rituals:

Pre‑shift check‑in: 5 minutes at the start of each on‑call week to review recent incidents and known issues.
Standard first 10 minutes of an incident: confirm impact, assign roles, check runbooks, notify stakeholders.
Micro‑handoffs: a 10‑minute end‑of‑shift summary (Slack message or ticket note) for the next person on call.
Two-minute decompression after major incidents: quick breathing or walk break before writing notes.
End‑of‑rotation reflection: one question you always answer—“What’s one friction I experienced that we could fix?”

Use the garden image again:

Place each ritual (paper seed) where it belongs: soil (foundations), plants (core practices), tools (automation, runbooks).
Ask: “What happens if we water this ritual regularly? What if we neglect it?”

Over time, these tiny rituals:

Reduce cognitive load during incidents.
Turn reactions into habits.
Make improvement incremental and sustainable instead of relying on rare big-bang changes.

Step 3: Design On‑Call Schedules Like a Garden Plan

A good garden plan prevents chaos: plants are arranged for light, space, and maintenance. On‑call is the same. If your schedule is an afterthought, people burn out.

Use the herb garden metaphor to intentionally design your on‑call rota:

Minimize Night Shifts and Protect Time Off

A healthy garden needs darkness and rest. So do humans.

Design schedules that:

Use follow‑the‑sun coverage where possible—spread on‑call across time zones so fewer people are woken up at night.
Avoid perpetual “hero” patterns where the same individuals constantly absorb night shifts.
Clearly mark protected off‑call time that cannot be overridden lightly.

Ask as a group:

“Where is our garden forcing one plant to grow in the shade all year?”
“Who never gets a winter?”

Use Larger Teams with Monthly or Bi‑Weekly Rotations

Instead of tiny, overloaded on‑call groups, consider:

Larger on‑call pools (20+ people) to share the load.
Monthly or bi‑weekly rotations so that individuals have longer stretches off rotation.

This creates:

Flexibility for vacations and life events.
Reduced “always on edge” stress.
Greater resilience when people change roles or leave.

In the garden metaphor, this is like companion planting—a diverse bed of plants supporting each other instead of a fragile monoculture.

Step 4: Clarify Incident Roles Before the Storm

Confusion during an incident is like watering every plant at once with a firehose: lots of effort, little effectiveness.

Use the garden session to define and document roles clearly:

Common roles might include:

Incident Commander – owns coordination and decision‑making.
Operations / Tech Lead – focuses on diagnosis and remediation.
Communications Lead – keeps stakeholders, customers, and leadership informed.
Scribe – maintains a timeline, notes decisions, and tracks follow‑ups.

Turn each role into a tiny paper ritual:

A one‑page checklist for each role: “In the first 10 minutes, do X, Y, Z.”
A visible place in your tooling where roles are assigned quickly.

When roles are clarified in advance:

People know what to do under stress.
Leadership pressure is channeled through proper communication paths.
New team members can plug into incidents faster and with less fear.

The garden metaphor: you’re not asking every plant to do everything. The trellis supports the vine; the ground cover protects the soil. Each has a role.

Step 5: Automate Like Irrigation, Not Like a Robot Gardener

Automation should feel like a well‑designed irrigation system, not a replacement for human judgment.

Use automation and workflows to:

Speed up detection and triage: alerts that are actionable, aggregated, and de‑duplicated.
Standardize response: runbooks that can be triggered automatically based on known patterns.
Guide humans through workflows: structured incident channels, templates, and checklists.

Examples of “irrigation-style” automation:

Auto‑creating an incident room/channel with the right labels and links when a P1 alert fires.
Automated prompts to assign roles, capture impact, and update status pages.
Scheduled reminders for follow‑up actions and post‑incident reviews.

The payoff:

Faster resolution with less cognitive overhead.
Lower burnout because responders aren’t improvising basic steps at 2 a.m.
A more predictable and humane on‑call experience, like a garden that mostly waters itself.

Using the Herb Garden for Conflict and Decision‑Making

On‑call is emotionally loaded. Who gets paged, who gets blamed, and who gets protected can become political quickly.

The Analog Incident Herb Garden gives you a neutral frame to:

Discuss conflict: “This bed is overcrowded” feels safer than “You take too many incidents.”
Make trade‑offs visible: more coverage here means less investment there.
Facilitate strategy: decide where to plant new “experiments” (e.g., new runbooks, new escalation paths) and where to prune.

When tensions rise, return to metaphor:

“Which part of the garden are we arguing about?”
“Are we fighting over the same patch of sunlight?”

This language helps teams move from personal blame to system design.

Conclusion: Grow Calm, Don’t Chase It

You can’t white‑knuckle your way to a healthy on‑call culture. Calm is grown, not demanded.

Using the Analog Incident Herb Garden:

You start with a simple image to surface feelings and ideas.
You transform insights into tiny paper rituals—small seeds of practice.
You design schedules, roles, and automation like a garden plan, not ad‑hoc patchwork.
You use the metaphor to handle conflict, strategy, and decision‑making without personal attacks.

Over time, these seeds grow into:

Clearer on‑call expectations.
Calmer incident responses.
A team that feels less like a crisis hotline and more like a group of thoughtful gardeners tending a shared space.

If your on‑call life feels like weeds and thorns, don’t look for a single miracle fix. Start with one tiny paper ritual this week. Plant it, tend it, and see what grows.