mythsthe wider recordMcDonald's automated drive-thru2024quick-service restaurants

everyone assumed:

voice AI is ready to take customer orders unsupervised

what was actually true:

A model that produces the right answer most of the time is not the same as a model ready to be trusted without a person watching.

how it happened

  1. whoAI ordering3-year test
  2. the gapmisheard ordersstaff fixed them quietly
  3. the resulttest endedtechnology removed
the gap that let it happen the result

what everyone assumed

McDonald’s and IBM had a reasonable case. They had been working on automated order taking together since 2021, the drive-thru is one of the most repetitive scripted conversations in retail, and voice models had been getting better every quarter. If a machine could reliably handle “a number two, no pickles,” it would free crews crushed by peak-hour volume. More than 100 restaurants ran the test. The bet was that the technology was finally good enough to listen unsupervised.

what happened

For roughly three years the partnership advanced the way pilots do, location by location, refinement by refinement. The system worked well enough to keep expanding, which is the quiet part. Each correct order was evidence the bet was paying off. The orders it misheard were absorbed by staff at the window, smoothed over before anyone outside the restaurant would notice. The gap between “good enough to keep testing” and “good enough to trust alone” stayed invisible as long as humans kept catching the misses.

step by step

  1. an automated drive-thru pilot expands for three yearsEach correct order is read as progress.
  2. staff quietly fix the misheard ordersSo the gap stays invisible.the assumption breaks here
  3. the misses go viralUnwanted sweet teas, bacon on ice cream.
  4. June 2024the IBM test is endedSystems switched off by late July.

how it surfaced

The misses left the building. Videos of the drive-thru adding sweet teas it was never asked for, and bacon to ice cream, circulated widely enough that the failures became the public story of the program. In June 2024, McDonald’s confirmed it would end the IBM automated-order test and remove the technology from the restaurants running it, with the systems switched off by late July. The company said the work had given it confidence that voice ordering would be part of its future, just not in this form yet.

A model that produces the right answer most of the time is not the same as a model ready to be trusted without a person watching.

The distance between those two states is exactly the part a successful pilot tends to hide.

picture it at a company like yours

The company here is made up. The other two paths are not: they happened, and each links to the story.

your company
a normal dayYou pilot an AI system that takes customer orders.
the gap nobody seesStaff quietly fix its mistakes, so the numbers look good.AI output nobody checks
  1. in this story
    the day it mattersCustomers film the mistakes staff did not catch and share them.
    what it costs youThe pilot becomes a public joke and is cancelled.
  2. or it goes like this
    howA customer-facing bot promises something your policy does not offer.
    what leavesmoney you now owewho ends up with itthe customer, backed by a tribunal
    it happenedMoffatt v. Air Canada, 2024
  3. or it goes like this
    howA bot is talked into mocking your company and the chat is shared.
    what leavesyour reputation, in screenshotswho ends up with ita million strangers in a day
    it happenedDPD chatbot, 2024

sources

  1. McDonald's to end AI drive-thru test with IBM (CNBC, June 17, 2024)
  2. McDonald's ends IBM drive-thru voice order test (CIO Dive, June 2024)
  3. McDonald's is ending its drive-thru AI test (Restaurant Business, June 2024)

← all myths

your turn

what you can do about it

  1. this week

    Find the one AI-assisted task where a human is the last line of review, and ask what happens to the day its output goes out unchecked.

    Somewhere in your company an AI tool is producing output that is right most of the time, and a person is quietly fixing the rest before anyone notices. That arrangement works until the volume grows or the person looks away. The readiness you can see in a demo is not the readiness you need before you remove the reviewer.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.