Browse the book & resources

Chapter 01 / 20

1. Faster Is Not the Destination

Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.

On June 24, 2026, video podcast episodes that normally appeared on Spotify within minutes took hours to reach listeners. Creators reported that episodes were missing. Some tried uploading again, adding more work to the queue. Their problem was plain: they had published something for an audience, and the audience could not play it. The incident report does not say how many creators were affected or how long any one episode waited. It does say that some creators heard from their audiences before they heard from Spotify.

The delay had more than one cause. Transcoding had too little spare capacity for a surge in new content. A scheduled batch job was using some of that capacity to reprocess older episodes. A quality improvement had increased the processing needed for each video, and a scheduling bug was leaving roughly ten percent of available throughput unused. Internal alerts first fired at 13:30 UTC. Engineers stopped the batch job at 16:35; the first creator report arrived at 17:31; formal incident response began at 17:34. A scheduler fix went out that evening, more capacity came online after midnight, and the queues cleared at 01:02 on June 25. Spotify itself points to the roughly four hours between the first alerts and formal response as a gap it needs to close.

There is a limit to what this account tells us. It records a customer-facing delay and the operational steps taken to clear it; it does not provide per-episode queue times, engineer work logs, a financial loss, or an experiment isolating each cause. Nor was this an AI-caused incident. Its place at the beginning of a book about AI is deliberate. It shows what the organization owes people when it says work is going faster: an outcome they can actually use, not a tally of activity upstream.

The wrong end of the stopwatch

Engineering leaders have good reasons to care about speed. A shorter path to a safe change can let a team repair harm sooner or learn from customers while a choice is still reversible. The error is to start the stopwatch at the easiest point to measure and stop it before the intended result arrives. An AI license is an input. A generated patch or merged pull request is an output. A shorter release cycle is a delivery result. A creator's episode reaching listeners as expected is a customer outcome. These measures can form a chain, but the links are not automatic.

Consider what happens if the first link gets cheaper. A developer can now submit a change in half the time. A reviewer still needs to understand its purpose; tests must exercise its failure modes; another team may need to approve a deployment; someone must notice whether the customer can use the result. If submissions arrive faster than those downstream steps can process them, the work waits somewhere else. The author feels faster while the customer may not.

That is not an argument against AI. In three field experiments across 4,867 developers, researchers found an average 26.08 percent increase in completed tasks in the pooled analysis among developers given access to a coding assistant. Random assignment makes this stronger evidence for that task result in those settings than an enthusiasm survey. The experiments did not establish a 26 percent gain in customer benefit, profit, or every individual's output. We should value the task finding without asking it to answer a different question.

Salesforce describes the next link in the chain. In its engineering account, code volume rose by about 30 percent, pull requests often grew beyond 20 files and 1,000 changed lines, and review latency rose. Senior reviewers were switching among large changes; the company worried that the time spent on the biggest reviews was no longer enough for meaningful scrutiny. Salesforce reports the problem and its response, not a controlled estimate of AI's effect on customer outcomes or additional reviewer hours. Even so, the decision is concrete: making authoring cheaper had not made human attention abundant. A second AI tool for review might help, but only if it helps reviewers find consequential errors without turning their approval into a formality.

There is a more careful way to shorten a wait. In a separate Spotify workflow—releasing the main app, not processing podcast videos—engineers used time-series data to locate release delays. They found blocking bugs and App Store approval among the largest waits; manually advancing a ready release could add up to twelve hours when a stage finished outside working hours. A condition-checking release conductor reduced the average release cycle by about eight hours. Regression sign-off, build checks, crash thresholds, and external App Store review remained part of the process. The release account measures delivery time, not eight hours of additional customer use. The lesson is not to automate every gate. It is to distinguish a manual transition from a check that protects people.

Find the recipient before choosing the tool

For the podcast publishing problem, the recipient was a creator whose episode should have become playable to an audience. A useful starting measure is upload-to-playable time, segmented by new versus reprocessed episodes and by the affected creator population. Queue age and available capacity help explain that measure; a timely notice tells creators what is happening. These are proposed measures for investigating a similar workflow, not metrics Spotify reported as the result of an AI pilot.

The options are not confined to "more AI" and "no action." Spotify reports adding headroom, improving monitoring, and giving new content priority over background work. In a different organization, an AI-assisted alert summary might help a responder connect early signals to a growing queue. That is a hypothesis to test against a simpler threshold, better capacity planning, or a clearer escalation path. The first trial should ask whether the right person notices and acts sooner, then whether the customer-visible delay actually shrinks. Faster alert prose would not count if episodes still arrive hours late.

Now widen the view. A customer gains when the result arrives reliably. The company may protect trust and revenue, but this incident report supplies no figure for either. A team gains if it can detect and recover without quietly transferring more work to another rotation. An individual gains if they have the context and authority to act without becoming the permanent human patch for an unexamined system. Those are four distinct questions, not four ways to rename PR throughput. We will examine them in the next chapter.

A trail marker is useful at a junction because it identifies the destination and the hazard without dictating every footstep. For a leader considering AI, the first marker is the person and result that matter. The second is the wait or failure that blocks them. The third is the evidence that would show whether the chosen intervention helped without worsening another part of the journey.

At the junction: Pick a recent customer result that arrived late or failed after launch. Ask a product partner and the receiving engineering or operations team to trace it backward from first successful use. Mark active work, waiting, necessary safeguards, and missing timestamps. Which change would you try first: an AI intervention, a non-AI workflow fix, or better observation? What result would make you change your mind?

Sources cited in this chapter

  1. https://engineering.atspotify.com/2026/7/content-ingestion-and-podcast-video-incident-report
  2. https://www.microsoft.com/en-us/research/publication/the-effects-of-generative-ai-on-high-skilled-work-evidence-from-three-field-experiments-with-software-developers/
  3. https://engineering.salesforce.com/scaling-code-reviews-adapting-to-a-surge-in-ai-generated-code/
  4. https://engineering.atspotify.com/2026/2/how-we-release-the-spotify-app-part-2

Browse all references →