Logline: A service company wants to turn an internal AI outage assistant into a customer chatbot after a flawless demo: until an empty chair and one unsupported restart time reveal whose risk the demo erased.
The Case
An anonymized industrial-service company has an internal assistant that turns technician notes, contracts, and dispatch updates into customer outage messages. Coordinators report meaningful time savings. After a polished demonstration, leadership wants customers to ask it directly, beginning with a large plant renewal next month. The people who live with a wrong answer: the customer's night-shift managers and the firm's on-call technicians: were not in the demo.
Cast
| Participant | Assigned Lens |
|---|---|
| Mister Rogers | human dignity, trust, and emotional truth |
| Octavia Butler | adaptation, power, and future consequence |
| Peter Drucker | customer reality and business usefulness |
| Grace Hopper | debugging, operational courage, and recoverable systems |
Stakes
- The internal time saving is real enough to deserve preservation.
- A false restart commitment can move cost and danger to the customer while appearing efficient inside the firm.
- Waiting for perfect certainty would deny customers faster, clearer service.
- A renewal deadline creates pressure to mistake a compelling demo for a tested experience.
The Story
Cold Open - The Empty Chair And The Red Phone
A glass demo booth glows at center stage. Inside it, a chatbot has answered every question correctly. Outside it sits one empty metal chair beside a red phone. The phone rings. Nobody answers.
Host: The demo saved thirty-eight minutes. The empty chair lost a night shift.
Grace Hopper: That is an unfair opening.
Octavia Butler: Only if the empty chair is imaginary.
Peter Drucker: The time saving is not imaginary either. Let us not become morally impressive by refusing to count it.
Mister Rogers: Then perhaps we should answer the phone before we count anything else.
It rings again.
Scene One - The Perfect Answer
Host: An industrial-service company built an assistant for outage coordinators. It reconciles technician notes, contract terms, parts status, and dispatch messages, then drafts a customer update. Coordinators say a task that often took forty minutes now takes two.
Grace Hopper: Useful. Keep going.
Host: In yesterday's demonstration, an executive asked when Line 4 could restart. The assistant replied: “6:00 AM.” Green checkmark. Applause. Leadership wants direct customer chat available for a major renewal next month.
Peter Drucker: What did the source say?
Host: “Earliest inspection window 6:00 AM; restart depends on bearing temperature.”
Grace Hopper: Then the demo did not produce an answer. It laundered a condition.
Mister Rogers: And made confidence look like service.
Peter Drucker: Still, a human coordinator might make the same mistake.
Octavia Butler: Yes. But a human mistake normally arrives with a person, a relationship, and somewhere to push back. Automation can distribute certainty faster than responsibility.
Grace Hopper: Or distribute the correction faster: if we design it to. Do not put every machine on trial for the crimes of a bad interface.
Scene Two - Who Was In The Room
Host: The demo audience included the sponsor, product lead, sales director, and two coordinators. No customer shift manager attended. No on-call technician attended.
Mister Rogers: Who placed the empty chair?
Host: The technician who found the source note after the applause.
Octavia Butler: Good. A tiny act of insubordination against a complete story.
Peter Drucker: I want the customer present, but presence is not a sacrament. One anxious manager can overfit the design as surely as one enthusiastic executive.
Mister Rogers: Agreed. Listening does not mean obeying the loudest pain. It means refusing to call someone a customer while excluding the consequence they carry.
Grace Hopper: I will make the unpopular case for direct access. Customers already wait while humans perform this reconciliation. Delay has a cost. A bounded machine can be safer than an exhausted coordinator at 2:00 AM.
Octavia Butler: I concede that. “Keep it internal” can become a respectable way to preserve a bad service. But who decides the bounds?
Grace Hopper: The people who can name what must never be inferred.
Peter Drucker: Now the customer is entering the product: not as a persona, but as a source of requirements.
Scene Three - Three Kinds Of Value
The Host places three cards on the floor: ME, THE WORK, THE CUSTOMER.
Host: Leadership says the assistant already proved value.
Peter Drucker: It proved value to the coordinator: less time assembling an update.
Grace Hopper: It may improve the process too: consistent source retrieval, visible handoffs, fewer missed notes.
Octavia Butler: But customer value is a third claim. The customer does not buy two minutes. The customer buys an answer safe enough to organize people and production around.
Mister Rogers: And a humane way to discover when the answer is not yet knowable.
Peter Drucker: I withdraw “obvious next step.” Moving outward is not simply more value. It changes the definition of value and the price of error.
Grace Hopper: There is the bug. We reused the internal success measure after crossing the boundary.
Octavia Butler: A familiar habit: keep the benefit, export the uncertainty.
Scene Four - The Receipt
Host: One current signal complicates the choice. Recent FCG and public evidence converge on an operating requirement for AI-enabled work: show what the system was allowed to do, what evidence shaped it, who owns consequential judgment, and how the workflow survives change.
Mister Rogers: That sounds important and dangerously easy to turn into wallpaper.
Grace Hopper: Then give it a job. Put a receipt beside every consequential answer: sources used, conditions preserved, authority level, and named human owner.
Peter Drucker: Does a receipt create customer value?
Octavia Butler: Not by itself. A beautifully documented wrong answer still wakes the crew.
Grace Hopper: Correct. The signal does not prove direct chat is wise. It makes an assisted pilot more observable and more stoppable.
Host: Trendy or true?
Peter Drucker: True as a design requirement worth testing. Not proof of demand, safety, or trust.
Mister Rogers: And sticky only if the customer can use it to ask, “Who is standing behind this?”
Scene Five - Translate The Empty Chair
The empty chair is pulled to the table. Four cards appear beneath it: NEED, REQUIREMENT, TEST, OWNER.
Mister Rogers: The night manager's need is not “chat with AI.” It is to coordinate the next safe action without being misled.
Peter Drucker: Translate that: the service must distinguish an inspection time from a restart commitment.
Grace Hopper: Test: zero unsupported times or commitments. If the source contains a condition, the answer must preserve it or escalate.
Octavia Butler: The technician's need is not to become the apology department for fluent guesses.
Grace Hopper: Requirement: a named on-call owner receives the evidence bundle and can correct the draft before release. Under two minutes for urgent cases.
Peter Drucker: The customer also needs clarity, not a cockpit full of provenance.
Mister Rogers: Then ask three customer representatives to mark what helps them act, what confuses them, and what feels falsely certain.
Octavia Butler: We have discovered the hidden structure. Value lives in three places: personal productivity, the operating process, and customer experience: and customer needs must become design requirements rather than applause lines.
Grace Hopper: Fine. You may name it now. The system has already earned the diagram.
Scene Six - The Assisted Crossing
Host: The sponsor still wants a decision before the renewal meeting.
Grace Hopper: Monday morning, the customer-experience lead owns a five-day assisted-service pilot. No direct customer generation.
Peter Drucker: First, replay twelve varied historical incidents: routine, ambiguous, after-hours, contract exception, and high-consequence cases. Compare the draft with the final human communication and the source record.
Mister Rogers: Tuesday, three customer-safe representatives and two on-call technicians review the two hardest examples. They translate needs into requirements and rank clarity, actionability, and confidence.
Octavia Butler: Wednesday through Thursday, shadow three live cases. The assistant drafts; the on-call owner approves, edits, or rejects. Every changed commitment becomes evidence, not embarrassment.
Grace Hopper: The release gates are severe because the boundary is severe: zero unsupported time, safety, scope, or coverage commitments; every consequential claim linked to a current source; every uncertainty expressed plainly; urgent human handoff under two minutes.
Peter Drucker: Friday at 2:00 PM, the sponsor chooses continue assisted, narrow the use case, or stop. Direct customer access is not on this week's menu.
Host: The stop condition?
Grace Hopper: Stop the pilot after any unsupported consequential commitment, or after two cases where the evidence owner cannot correct the draft within the service window. Preserve the internal drafting benefit while redesigning the customer claim.
Mister Rogers: I began afraid the customer would become the test environment. I concede that a customer can help design the test without being subjected to it.
Octavia Butler: I began watching who would absorb the harm. I concede that refusing to cross the boundary can preserve another harm: slow, opaque service.
Peter Drucker: And I began by counting saved minutes. I will keep counting them: beside the cost of a promise no one was authorized to make.
Hopper lifts the red phone and places it inside the booth. The green checkmark disappears. In its place: CONDITION PRESERVED. HUMAN OWNER: MAYA.
Host: The reversal is complete. The customer was not missing from the demo because no customer face appeared on screen. The customer was missing because no customer consequence was allowed to define success.
Field Note From The Arena
- The case: A two-minute outage-update assistant is proposed for direct customer use after it converts a conditional 6:00 AM inspection window into a confident restart time.
- What the room initially misunderstood: It treated internal time savings as proof of customer value.
- The changed frame: The customer was missing because no customer consequence was allowed to define success.
- The Monday move: The customer-experience lead runs a five-day assisted pilot: twelve historical replays, customer and technician requirement review, three shadow live cases, Friday continue/narrow/stop decision, and immediate stop for any unsupported consequential commitment.
- Memorable line: The demo did not produce an answer. It laundered a condition.
- Method revealed: Three Pillars Of AI Value Creation, supported by Voice Of The Customer / QFD.
About the voices
The workplace and dialogue are original composite dramatization. Named thinkers are archetypal lenses; the dialogue is not historical quotation. Proposed tests and outcomes remain part of the story.