The Company Looking Back
S03E08 | 2026-09-19

Original dramatic voices inspired by historical perspectives; not historical quotations. The companies and workplace cases are fictional composites.

ARENA EPISODE

At fictional Larkfield Service, staff arrange and maintain equipment for customers. This year the company tried several AI-assisted ways to summarize work, answer routine questions, and preserve operating knowledge. None can authorize a customer promise or change a safety rule. The closing leadership meeting is supposed to choose which pilots continue.
Mara, the service lead, brings a customer booking that the new briefing tool marked ready. It cites an old equipment exception. The exception was withdrawn after a service change, but the original note still exists in a shared archive. Mara caught it before anyone promised the customer a visit. No customer harm or saved cost is claimed. The team has to decide whether it can actually remember a correction, and what it must give up to maintain the work it chooses to keep.

PURPOSE

End the season with a consequential choice about organizational learning: what deserves to persist, who can correct it, and which ambitions the company has capacity to support.

THE STORY

The Eighth Card

Eight colored cards stand on an easel. Beside them Mara sets a plain paper booking with READY stamped across its top. The operations director has reserved this room for the year's AI review.

**DIRECTOR:** We have eight pilots to celebrate. I hoped to end with a wall of what worked.
**MARA:** May I put this on the wall?
**DIRECTOR:** It's a booking.
**MARA:** It was a booking until I checked the equipment note. We cannot make that visit under the old exception.
**DRUCKER:** Did a customer receive the promise?
**MARA:** No. I stopped it before the call. The briefing said ready.
**WALT:** That stamp is doing the work of a very confident actor.
**MARA:** It has better billing than the person who checked it.
**FOLLETT:** Who changed the exception?
**MARA:** Service did, last month. The current rule is in the dispatch record. The older note remains in the archive. The briefing pulled the older one.
**DIRECTOR:** Then the tool needs the current rule.
**OCTAVIA:** And the next withdrawn rule? If the answer is always Mara, the company is remembering by borrowing her attention.
**MARA:** I could do without being the emergency memory.
**DIRECTOR:** No one is asking that.
**MARA:** The screen did.

What Counts As A Win

**DIRECTOR:** I do want to fix this. I also do not want one caught error to erase a year of useful work.
**DRUCKER:** Good. Which work was useful to a customer?
**DIRECTOR:** The briefing prepares the dispatcher. We have summaries that save retyping. The staff can find prior cases.
**MARA:** Some summaries do save me time. I use those.
**FOLLETT:** Which of the eight cards represents the time spent checking whether an old instruction is still safe to use?
**DIRECTOR:** None. These are the pilots.
**WALT:** The ninth card has been working backstage.
**DIRECTOR:** I know how that sounds. But if every benefit waits for perfect maintenance, we'll never try anything.
**WALT:** I agree. A prototype should be allowed to be unfinished. A service promise shouldn't pretend it isn't.
**OCTAVIA:** Nor should a caught mistake be treated as proof of control. Mara noticed this one. What happens when the person reading the briefing is new?
**MARA:** A new dispatcher would call the customer. That's what READY tells them to do.
**DRUCKER:** So we have a saved draft, a caught error, and an untested next user. Those are three different facts.
**DIRECTOR:** I can take that distinction to the review. I still need a decision today.

The Return Of An Old Sentence

**HOST:** The company has heard a current proposition: organizational memory should connect a work item to its source, owner, correction, and next use. The September 14 FCG Signal Desk treated that as a bounded test, drawing on recent external design accounts and internal conversations. It did not establish that any vendor's memory system works here.
**WALT:** The word memory tempts us to build a magnificent attic.
**MARA:** We already have one. That's where the old note came from.
**FOLLETT:** Who was permitted to withdraw it?
**MARA:** Service withdrew the exception. I don't know who can mark the archive note obsolete.
**DIRECTOR:** The systems team can edit it.
**MARA:** They don't decide equipment rules.
**OCTAVIA:** There is the danger in the current fashion. More retrieval can make an old mistake faster.
**WALT:** I was going to propose a better search. I withdraw that as the first move.
**DRUCKER:** A useful concession. Where did the briefing look, and what did it show about the age of the note?
**MARA:** The archive. It showed the old title. No withdrawal, no current rule, no person to call.
**FOLLETT:** Then the correction must be an operating act, not a request for the systems team to guess. Service owns the rule. Dispatch owns whether to release a booking. Systems can make the change visible and test retrieval.
**DIRECTOR:** That is three owners for one sentence.
**FOLLETT:** Three jobs. One decision about the rule.
**MARA:** Thank you. I don't want a committee to decide whether a van has the right equipment.

The Wall Changes

The director turns the first card around. Its back is blank.

**DIRECTOR:** I was going to ask each pilot owner for a success story. What goes on the back?
**DRUCKER:** A customer or worker task, what changed in that task, what evidence you have, what you only hope, and the person who may stop it.
**WALT:** Also what it might become if it works. I won't surrender the future to a form.
**OCTAVIA:** Give the future a cost. Who maintains the correction when the pilot grows?
**WALT:** Fair. A dream with no steward becomes a very charming abandonment.
**DIRECTOR:** If we fill in all eight, is that enough?
**DRUCKER:** Enough for what?
**DIRECTOR:** To call the year successful.
**DRUCKER:** The question is whether the set of work can support the promises you're making. Eight attractive pilots may be too many to sustain. Three might be too few to learn what the business needs next.
**MARA:** We cannot check eight live briefings every morning. We can check one disputed route and keep the ordinary dispatch path.
**DIRECTOR:** You are asking me to retire pilots before the celebration.
**OCTAVIA:** We are asking you to decide what can be cared for. Abandoned work is not the same as a deliberate stop.
**FOLLETT:** And Mara cannot quietly inherit the care of whichever cards survive.
**DIRECTOR:** I hear that. I have been counting starts because they are easy to display.
**WALT:** The cards are still worth displaying. Turn them over.
**MARA:** You may want to use pencil.

A Smaller Promise

**HOST:** The director proposes keeping the briefing everywhere, with a warning to double-check old notes.
**MARA:** That warning tells a new dispatcher to do the work the briefing claims to have done.
**DRUCKER:** What part can you defend now?
**MARA:** Summaries of the current job, if the dispatcher sees the source and still releases the booking. No automatic READY from archived exceptions.
**WALT:** That's less magical.
**MARA:** It is more useful on a Tuesday.
**WALT:** I concede Tuesday.
**OCTAVIA:** Can a withdrawn exception reappear in the summary?
**MARA:** Until we test the retrieval path, yes.
**DIRECTOR:** Then we pause that path. Can we test it without another customer involved?
**MARA:** Use the caught booking and another completed case. Copies, no live release. Have a dispatcher who did not make the correction try them.
**FOLLETT:** During paid time. Service marks the rule and the superseded note; systems verifies the briefing surfaces the correction; dispatch decides whether the proposed view is usable. Mara advises, but isn't the permanent repair desk.
**DRUCKER:** What will reverse your decision?
**DIRECTOR:** If the old exception appears as current again, the briefing remains off for that route. If the source and withdrawal appear clearly and a new dispatcher can make the right call without Mara rescuing them, we can consider a bounded return.
**OCTAVIA:** Consider, not declare victory.
**DIRECTOR:** Consider. We will compare the full effort, including corrections, with ordinary dispatch before expanding.
**WALT:** May I keep one future card? A way for an unfamiliar dispatcher to see why a rule changed, not merely the latest answer.
**MARA:** Yes, if I can correct the explanation when the work changes.
**FOLLETT:** And if the person responsible for the rule can authorize that correction.
**WALT:** My coalition has acquired a maintenance budget.
**DIRECTOR:** It has acquired my budget. That may be the actual finale.

Looking Back

The director writes PAUSED on the briefing card. On the reverse: current job summaries, human release, source visible, archived exception retrieval off. Mara removes the READY stamp from the disputed booking.

**DIRECTOR:** On Monday I'll gather the pilot owners and the people who actually use the surviving work. Each card gets a customer task, evidence, source and correction owner, maintenance time, stop authority, and a next decision date. The pilots we cannot support stay paused or close.
**DRUCKER:** When is the next decision?
**DIRECTOR:** Friday for this briefing route. The wider set gets a review next week, after owners bring a real use case. I won't call the eight-card wall a result.
**OCTAVIA:** What will you say about this booking?
**DIRECTOR:** That Mara prevented a wrong promise. It proves a person caught this instance. It does not prove our memory is reliable.
**MARA:** I can live with that. Please say my name in the room where the fix gets resourced.
**FOLLETT:** There is your participation test.
**WALT:** And leave the eighth card standing. It reminds us there was a possibility worth testing.
**DRUCKER:** On its back, write what would make it useful.
**HOST:** The wall still holds eight beginnings. It no longer pretends they are eight endings.

FIELD NOTE FROM THE ARENA

Larkfield nearly counted a caught error as proof that its AI briefing was governed. The correction lived in one place while an older instruction remained retrievable in another. Mara prevented a wrong customer promise; she did not prove the system had learned.
On Monday the director funds a replay on completed cases, with service owning the rule, systems testing the source and withdrawal, and an unfamiliar dispatcher testing use. Human release stays in place. On Friday the director keeps, narrows, or pauses the briefing route based on whether the correction survives retrieval without Mara's private rescue. The broader pilot review asks whether the company can maintain the set of promises it has begun.
The primary FCG Work OS insight is that memory earns its name when a correction changes the next decision through a clear owner and source. Portfolio sufficiency adds a harder question: can the organization support enough useful work, with the capacity it actually has? **Carry this question:** Which of your apparent wins still works when the person who caught its last error is away?