Logline: An AI service assistant wins applause for speed while customers quietly learn that the fastest path to help is to escape it.
The Case
An anonymized service organization has declared its internal AI pilot a success: usage is high, demonstrations are polished, and routine replies are faster. Yet complaints are rising and experienced employees maintain a hidden exception queue. The apparent choice is to scale the popular pilot or distrust adoption itself.
Cast
| Participant | Assigned Lens |
|---|---|
| Ada Lovelace | human-machine possibility and symbolic systems |
| Peter Drucker | customer reality and business usefulness |
| Jane Jacobs | lived systems and local knowledge |
| Sherlock Holmes | evidence, inference, and missing facts |
Stakes
- Scaling commits budget, operating design, and executive credibility.
- Employees are absorbing invisible correction work.
- Customers receive faster replies but less reliable resolution.
The Story
Cold Open - The White Rectangle
A floor plan fills the Arena wall. Every room is labeled: DATA, MODEL, SECURITY, TRAINING, LAUNCH. One white rectangle sits at the end of a corridor. It has no door and no name.
A printer wakes and produces a dashboard headed PILOT SUCCESS. Sherlock Holmes takes the page. Jane Jacobs ignores it and studies a battered red notebook on the table.
HOST: The sponsor wants approval by Friday.
Sherlock Holmes: Seventy-eight percent weekly use. Forty-one percent faster first response. An enviably healthy corpse.
Ada Lovelace: You have diagnosed death from two numbers and a font.
Sherlock Holmes: No. From the celebratory adjective. Evidence rarely arrives already applauding itself.
Jane Jacobs: This notebook is labeled “Odd Ones.” Who kept it off the map?
Peter Drucker: Before the notebook: what result was the pilot hired to produce?
HOST: Faster service.
Peter Drucker: That is an activity wearing a result’s coat.
Scene One - The Demonstration
HOST: The assistant handles a simple address change in eleven seconds. It retrieves the correct policy, drafts a courteous response, and routes the update.
Ada Lovelace: Good. Let us not punish competence because the plot requires suspense.
Jane Jacobs: Nobody is punishing it. I want to see Tuesday at 4:50, when the address change belongs to a customer moving after a flood, the account contains two households, and the policy uses a word the customer does not.
Ada Lovelace: That is a different task.
Jane Jacobs: It is the same button.
Peter Drucker: And perhaps a different definition of success.
Sherlock Holmes: The demonstration proves the assistant can complete the demonstration.
Ada Lovelace: Sherlock, your gift for reducing statements to tautologies could power a small city.
Sherlock Holmes: Only if the city reports electricity by counting light switches.
The Host opens the red notebook. Its pages list nicknames: DOUBLE OWNER. POLICY SAYS YES, CUSTOMER HEARS NO. CLOSED BUT NOT DONE. HUMAN PLEASE.
HOST: Experienced service staff created this queue. It is not in the workflow. They check it between assigned cases.
Peter Drucker: Unmeasured labor protecting a measured result.
Jane Jacobs: A sidewalk.
Ada Lovelace: Or a temporary defect log. Do not romanticize every workaround as local wisdom.
Jane Jacobs: I don’t. Some sidewalks lead nowhere. But when people keep wearing a path through the grass, a planner should at least look out the window.
Scene Two - Three Pieces of Customer Evidence
HOST: The room receives three anonymized fragments.
Card one: “Your answer was fast. It was also for the wrong kind of account.”
Card two: “I replied twice. Each time I received a new summary of the same policy.”
Card three is only two words: “human please.” It appears forty-seven times this month, including in requests classified as routine.
Sherlock Holmes: The phrase is not proof the machine failed. It may indicate preference, impatience, prior experience, or poor interface design.
Jane Jacobs: Thank you for defending uncertainty. Now interview them.
Sherlock Holmes: Naturally.
Ada Lovelace: And sample successful cases, not only complaints. Otherwise Voice of the Customer becomes Voice of the Angriest Customer.
Peter Drucker: A concession from Ada to measurement and from Holmes to conversation. We may finish before winter.
Ada Lovelace: I never opposed measurement. I oppose measurements that mistake the edge of the instrument for the edge of reality.
Peter Drucker: Then answer this: if first response is faster and resolution is slower, which number belongs on the sponsor’s slide?
Ada Lovelace: Both. Joined by the cost of correction.
Jane Jacobs: And by who pays it.
Sherlock Holmes: There is the first missing room: consequence.
Scene Three - Proof Before Scale
HOST: A current signal complicates the decision. Across several recent AI efforts, the recurring constraint was not model capability but missing decision ownership, security or IP boundaries, quality points, and permission to move from prototype to operation. Public language is converging on evaluation, runtime policy, observability, and reconstructable decisions.
Sherlock Holmes: Fashionable terms, but the underlying demand is durable: show how you know.
Ada Lovelace: They could also become a new bureaucracy that measures the assistant until nobody improves it.
Peter Drucker: Then require only proof that changes a decision.
Jane Jacobs: Proof collected where? If the evaluation suite never enters the exception queue, it will certify the map and miss the city.
Ada Lovelace: Agreed. Test the system and the work around it together. The assistant’s reply, the employee’s correction, the customer’s next action, and the authority to stop.
Sherlock Holmes: You have just expanded the object of investigation.
Ada Lovelace: I have stopped pretending the machine acts alone.
HOST: Trendy-or-true / shiny-or-sticky disposition?
Sherlock Holmes: True enough to test, too trendy to repeat as an incantation.
Jane Jacobs: Sticky only if the people doing the sticking can challenge the result.
Scene Four - The Missing Room
Ada chalks seven headings around the floor plan without naming a framework: intended future, measures, information, mechanism, capability, authority, and use.
Ada Lovelace: The project has a mechanism. It has data. It has a launch date. What it lacks is not another technical component. It lacks agreement among these rooms.
Peter Drucker: The future says “better service.” The measure says “faster reply.” Those are not aligned.
Sherlock Holmes: The information set excludes the notebook that explains the exceptions.
Jane Jacobs: The capability plan trains people to accept drafts, while the best employees are learning when to disobey them.
Ada Lovelace: Governance approves access but does not name who may halt a bad pattern.
Peter Drucker: Adoption counts use without asking whether use creates value or merely becomes mandatory.
Sherlock Holmes: Seven rooms, then. Yet the white rectangle remains.
Jane Jacobs: Because the customer is not an eighth box on an internal diagram. The customer is the reason the rooms connect.
Peter Drucker: I would say the customer defines the business.
Jane Jacobs: And I would say customers are plural, situated, and occasionally contradictory. Your singular noun can hide as much as their dashboard.
Peter Drucker: Fair correction. The organization must discover which progress and harms matter across real customer situations, not invoke “the customer” as a ceremonial guest.
Ada Lovelace: Then the white rectangle is not the customer department.
Sherlock Holmes: It is the room where internal capability meets external consequence.
Scene Five - The Reversal
HOST: The sponsor’s binary was scale the pilot or reject adoption evidence.
Sherlock Holmes: The usage evidence is valid. The conclusion is not.
Ada Lovelace: People are adopting two systems: the visible assistant and the invisible rescue practice.
Jane Jacobs: The pilot did scale. It scaled correction work into the margins.
Peter Drucker: Then the project is not failing inside the rooms it mapped. It is succeeding according to them.
He turns toward the white rectangle.
Peter Drucker: It is failing inside the room it forgot to draw.
Sherlock Holmes: Customer consequence.
Jane Jacobs: And the human work required to repair it.
Ada Lovelace: I withdraw my earlier description of the notebook as possibly temporary. It is not proof of failure, but it is part of the operating system. Excluding it makes the model of success false.
Sherlock Holmes: A clean concession. I shall record the date.
Ada Lovelace: Use the red notebook. Apparently it is where this organization keeps reality.
Scene Six - The Monday Move
HOST: What happens Monday morning: not after a transformation program, but Monday?
Peter Drucker: Select twenty recent requests: ten apparently successful, five repeated contacts, five from the exception queue. Define success as resolved customer progress, not reply speed.
Jane Jacobs: Put one frontline employee and one customer-facing owner in the review. Ask what the dashboard could not see. Do not make them decorate a decision already made.
Sherlock Holmes: For each request, separate fact, inference, and dramatization: though in this room, dramatization is our department. Record the first reply, correction steps, repeat contact, resolution, and who carried the burden.
Ada Lovelace: Map each failure or success across the seven connected questions: intended result, measure, information, mechanism, capability, authority, and actual use. Change only one bounded workflow next week.
Peter Drucker: Name the decision owner and the stop condition before the test.
Jane Jacobs: And invite the “human please” customers to explain what they were trying to escape. The phrase may describe the interface: or a breach of confidence.
Sherlock Holmes: By Friday, choose among three honest dispositions: scale this bounded workflow, revise and retest it, or stop it. “Promising” is not a disposition.
Ada Lovelace: Keep the possibility. Earn the scale.
Jane draws a door into the white rectangle. The printer produces another PILOT SUCCESS page. Sherlock folds it into a paper doorstop.
HOST: The map was accurate. That was the problem. It accurately described the project the organization had chosen to see.
Field Note From The Arena
- The case: A popular AI assistant improved response speed while repeat contacts and invisible correction work rose.
- What the room initially misunderstood: It treated usage as one system’s adoption rather than evidence that employees were sustaining two systems.
- The changed frame: The pilot scaled correction work into the margins; customer consequence was the missing room.
- The practical move: Review 20 cases over five days with a frontline employee and customer-facing owner; decide Friday to scale, revise, or stop one bounded workflow.
- Memorable line: Keep the possibility. Earn the scale.
- Method revealed: AI Strategy Mosaic, supported by Voice Of The Customer.
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.