Browse the book & resources

Chapter 05 / 20

5. Delivery & Execution: Are We Working on the Right Promise?

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

Consider a familiar but illustrative problem: the sprint board is green, every ticket has an owner, and several closed early. The promised customer result is still late. The missing step may be an approval that no team owns, a requirement that changed without being discussed, or a feature that shipped but cannot solve the customer's job. A status summary is not a substitute for finding out which.

Start with a promise stated in the customer's language: "A creator can publish an episode and know when listeners can play it." Translate it into observable steps and a date for checking them. Then ask what work is already in progress, what must be decided before implementation, and where a smaller batch could reach a real user sooner. This is product and engineering work together; AI cannot decide what matters simply by summarizing the backlog.

An assistant can compare a proposal with past decisions, surface likely dependencies, or help split an oversized change. The alternative may be a ten-minute conversation between product, engineering, and the team that approves releases. Either intervention is successful only if it improves the promised result, not if it fills a sprint with more carefully worded tickets. In the Spotify release-process account, manually triggered stage transitions sometimes added hours. Automating condition-checked transitions shortened the average release cycle, while regression and crash gates remained. That is measured delivery improvement; customer adoption was not measured in the account.

When work slips, resist the temptation to ask who failed to work hard enough. Ask whether the queue was predictable, whether a necessary safety gate was resourced, whether a late product decision invalidated earlier work, and whether the next promise can be narrowed. A plan that requires permanently heroic effort is not predictable delivery. Let the team renegotiate scope when the evidence changes.

At the junction: For one promised outcome, write its acceptance condition, its customer-visible date, and the next unavoidable handoff. Compare the last three similar pieces of work by elapsed time, not just coding time. If the highest delay is a decision, schedule the decision before buying another coding tool.

Sources cited in this chapter

  1. https://engineering.atspotify.com/2026/2/how-we-release-the-spotify-app-part-2

Browse all references →