Before the day · Page 22
Context is the part everyone skips
For you only
User and goal feel obvious once you see the shape. Context is the piece people leave out, and it carries more than it looks.
The best story I know about this is Clay Christensen's milkshake study. A fast-food chain had flat milkshake sales and had already tried the obvious moves: thicker, sweeter, more flavours. Nothing moved. Christensen's team ignored the product and watched the car park instead, and found that a surprising share of milkshakes sold in the early morning, to people driving to work alone. The shake had a job: keep a bored commuter company for a long drive, with the one hand the steering wheel did not need, and hold off hunger until ten. Once you see that job, the answer is obvious and a bit funny: make it thicker so it lasts the whole drive, and move it to the front counter so the commuter is in and out fast. The question was never "how do we make a better milkshake". It was "what is this milkshake hired to do at 7 a.m.".
The "7:45 a.m." in the Zara brief is doing the same work the car park did. Take it out and an evening inspiration app, a browse-for-an-hour experience, becomes a fine answer. Put it back and every browse-heavy idea dies on contact, because nobody browses at 7:45 with a coffee in one hand. Context costs you a few characters and quietly kills a hundred wrong products before anyone builds them.
If you remember one thing from this chapter, make it this: the moment matters as much as the person. Not "a commuter", but "a commuter at 7 a.m. with one free hand".