My Ficus Has an Incident Commander Now

The ficus dropped four leaves on Tuesday, and by Wednesday it had a Sev-2, a war room, and an on-call rotation that was just me.

The Bit

FernOps is a plant-care agent that treats a drooping ficus like a production outage. A soil-moisture probe and a webcam feed it data. When a leaf turns brown, it declares an incident, assigns itself Incident Commander, and assigns you the role of "Responsible Party."

It does not water the plant, because it has no arms and the plant is not on the roadmap. What it does is page you at 3am, keep a timeline of every missed watering, and publish a status page that your roommates can see. Status: "Degraded. Leaf loss ongoing."

The punchline is the postmortem. It is blameless, in the way a hospital bill is painless. Root cause: "Human did not water for 19 days." Action items: three, all assigned to you, none with a due date you can negotiate.

Why It Works

• Everybody has killed a plant and felt oddly guilty about it. Putting that guilt through tooling built for a payments outage makes the guilt funny instead of private.
• It pokes at tech culture's habit of wrapping small, human failures in process: severity levels, retros, "learnings."
• The audience has either sat through a real postmortem or owns a fern in decline. Usually both.

Content Treatment

• Primary format: Mock product demo, 30 to 40 seconds, vertical.
• Opening shot: Phone buzzing on a nightstand. Lock screen is a wall of gray, wordless alert shapes. A hand reaches for it, and behind the phone a ficus sits in the dark, visibly judging.
• On-screen hook: "I got paged because my plant is dying."
• Escalation: Sev-3, then Sev-2, then Sev-1 when a second leaf falls during the call. The agent starts a bridge and invites the cactus.
• Button: The postmortem lands. Under "What went well" it says: "The plant lasted longer than expected." You close the laptop and quietly water it, and the agent logs it as "Mitigation, 19 days late."

Sample Script Beats

1. 3:02am. Phone lights up. Voiceover: "Sev-2 declared. Ficus. Living room."
2. Cut to the plant, now under a desk lamp like it's being interrogated. A tiny hard hat sits on the pot.
3. The agent reads the timeline aloud, flat and calm: "Day 4, soil dry. Day 9, soil dry. Day 14, you said 'I'll do it tomorrow.'"
4. A fourth leaf drops. Agent: "Escalating to Sev-1. Paging the roommate."
5. Postmortem reveal. Root cause, one line, your name. You pour a glass of water into the pot. Agent: "Incident resolved. Retro Thursday."

Automation Angle

Inputs: a cheap soil-moisture sensor, a webcam pointed at the pot, a shared calendar of your claimed watering days, and your own texts saying "I'll water it tonight." Tools: a monitoring loop, a pager integration, a status page, and a document generator for the postmortem. Outputs: alerts, a timeline, and action items.

The fake product language does the heavy lifting. Dashboard copy reads "Mean Time To Hydration: 19 days." The tagline is "Photosynthesis, but make it observable." The fake CEO quote: "We believe every plant deserves five nines of leaf uptime."

Repurposing

• Short video: film it as one continuous take of a person in a bathrobe taking the call, with the plant as the only other participant.
• Carousel or thread: post the postmortem as slides, one section per slide, ending on the action items.
• Fake product screenshot: a status page for one plant, with a 90-day uptime bar that is mostly red, and a subscriber count of 1.

Guardrails

• Satirical concept; not advice.
• Keep any real-world sensitive domains framed as parody.
• Do not include private personal data, real names, or instructions that would harm someone.