Day 264 of the Daily · Product Management

Working Backwards

5 min read · 4 principles · apply it by lunch

Morning. The launch announcement is usually written last — when it’s far too late for it to change anything.

The question

Your team is building something right now that nobody outside the building has heard of yet — so on the day it ships, when the announcement goes out with the customer named, the problem stated and the reason anyone should care in two plain sentences, will a stranger read that and want the thing, or read a list of capabilities and feel nothing at all?

The idea

Colin Bryar and Bill Carr each spent more than a decade inside Amazon — Bryar as Jeff Bezos’s technical adviser, the job the company calls the shadow; Carr building and running its digital music and video businesses. In Working Backwards (2021) they set out the practice that decides whether a new product gets built there at all: before anyone writes code, someone writes the press release. One page, dated to the launch, in language a customer would read — who has the problem, what it costs them, what this does about it, and a quote you’d only publish if you meant it. Under the release sits the FAQ: the customer’s awkward questions first, then the internal ones — what it costs to build, what could break, what has to be true for any of the numbers to work. The room reads the whole thing before anyone speaks, then argues with the document rather than with the presenter. The trap is writing the announcement last, as a marketing job, once the thing exists and the money is gone — at which point its purpose is to make what got built sound exciting, not to test whether it deserved building. Written first, it’s cheap to throw away.

In the Daily · 4 principles and a template

Working Backwards is Day 264 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Product Management

The next four in the course.

All 22 Product Management frameworks
Day 274 · Product Management

User Story Mapping

Your team has committed to a release next: could one real customer start at the very beginning and get all the way through to the thing they actually came for using only what’s above the line — or does it stop somewhere in the middle, polished at step one and missing entirely at step four? A backlog sorted by priority almost always slices the wrong way.

See the framework →
Day 283 · Product Management

Brooks’s Law

Think about the last project that ran late on you: when the extra people arrived, who stopped doing their own work in order to bring them up to speed, how many weeks went by before the newcomers were producing more than they were consuming, and did anyone put either of those two costs on paper before the decision got made?

See the framework →
Day 293 · Product Management

The Five-User Test

Have you ever sat behind someone who’d never seen your product, handed them a real task and then stayed silent while they failed at it — or is everything you believe about how the thing gets used assembled entirely from your own hands on your own keyboard?

See the framework →
Day 302 · Product Management

Affordances and Signifiers

Somewhere in your product sits a control that needed a tooltip, an onboarding step and a help article wrapped around it before anybody could work out what it did — so if all three were deleted tomorrow and nothing else changed, how many of your customers would still know where to click? The explaining is the part you can count. The control underneath it is the part somebody would have to fix.

See the framework →