Skip to content
MHBMMichael Hanna-Butros MeyeringComplex systems · human outcomes
Menu

EP053 · Main episode

Who Owns the Automation After It Changes?

A dispatcher corrects one report. What will the next shift inherit? Use three fictional repair tickets to tell a one-off fix from a change to the saved rule.

Published
Nov 9, 2026
Runtime
15m 46s
Record
Source-backed notes
Listen here15m 46s
Watch the episodeEP053

Desk memo

The operating brief

  1. 01

    Find out what the next dispatcher inherits when a corrected report and the saved instructions differ.

  2. 02

    Separate the person who can edit the rule from the person who accepts the crew list.

  3. 03

    Try the 45-minute shift handoff on paper, using three fictional tickets.

Use the record

Your next practical step

Continue with the source-backed material already connected to this release.

  1. 01Read or print the shift handoff worksheetDownload the companion resource for this release.
  2. 02Read the production script transcriptReview the complete published record and its source citations.
  3. 03Governance vs. changeClarify the decision boundary before turning a policy or control into daily work.

Complete episode file

Notes, chapters, and evidence

The full editorial record lives here. Open only the section you need, without leaving the Desk.

Episode notes2 sections · 3 release notes

Original release summary

  • Find out what the next dispatcher inherits when a corrected report and the saved instructions differ.
  • Separate the person who can edit the rule from the person who accepts the crew list.
  • Try the 45-minute shift handoff on paper, using three fictional tickets.

Overview

Episode 53 of AI Change Desk with Michael Hanna-Butros Meyering.

On Friday, a dispatcher gets a reopened repair back onto the crew list. On Monday she's off. Will the next dispatcher get the corrected list, or just the same mistake at a different address?

A follow-up can fix one report without changing tomorrow's instructions. Michael looks at how shared GitHub Copilot automations survive a handoff, why a Google Cloud skill name doesn't tell you which revision ran, and what Conductor Cloud users need to preserve before its shutdown.

Try It This Week

Give a colleague the saved rule and three fictional tickets: one open, one reopened, one closed. Before they build the list, have the dispatcher write down which repairs should appear. Compare answers. Record who can change the rule, who accepts the result and when they'll check a fresh list.

The dispatch story is fictional. The exercise needs no production access and does not test or certify a vendor's software.

Chapters5 markers
Sources5 records
Disclosure and questionEditorial record

Disclosure

I use AI to help research, produce, and narrate this show. I check the claims, flag the risks, and decide what goes on air. My work in privacy shapes the questions I ask, but I don't discuss nonpublic work here. I speak for myself, not the State of Oregon or any other organization. This is practical guidance, not legal advice.

Read the site-wide AI use and editorial disclosure

Listener question

Could the next dispatcher make the right list using only the rule you leave behind?

Companion resources2 downloads

The shift handoff

Use three fictional repairs to test the rule that survives a shift change.

  • Keep the expected crew list private until the new dispatcher has made a list.
  • Give the new dispatcher only the saved rule, its revision and the tickets.

Before the next dispatch

Name who decides what belongs on the list and who can change the rule.

  • Book the next check.
  • Agree on a fallback if the list looks wrong.