Diseño
Show the Job, Not the Feature
By Gagan Malik
6 min de lectura
I treat What's New modals like cold callers. The badge appears. I close it. I have never once finished the third bullet. They are boring on purpose. A little choir of features sings about Version 2.4, the new model, the improved export. None of which I asked to hear before breakfast. Then one morning the update had gone live overnight, and the modal that appeared did not say Version 2.4. It said think it through. Below it: a map with a day trip through London, then a recipe with servings you could adjust, then an email draft with three tone tabs. Not a hymn sheet. Three jobs. I tapped through, hit Got it, and only then wondered why every other product still opens by singing features at me.
A What's New modal works like a job board for the release. It is the first screen after a meaningful update: dismissible, marked seen, scoped to three concrete tasks a visitor might actually run this week. Not every patch earns one. Not before users have context for why the release matters. The modal replaces the wall of bullets with plan, create, refine (or your product's honest trio). For AI assistants and creative tools, value lives in the task, not the capability checklist. Design is what gets noticed first and second on the way to a job done, as I argued in Design Is Attention Control, Not Aesthetics. The seconds after return are the most valuable real estate in the whole product. You spend them once. You do not get them back after the visitor learns to dismiss without reading.
Changelog Walls Train the Wrong Exit
Release notes exist for reasons that have little to do with Monday morning. Engineering wants credit. The product team wants every line of copy crisp so the release looks punchy. A modal that lists thirty features satisfies that room. It does not satisfy the person who updated overnight and opened the app to finish one job before breakfast.
Feature lists teach a habit: scroll, skim, close, forget. The visitor learns that the first screen is homework. Homework gets dismissed. Dismissal becomes muscle memory long before anyone tries the new model, the new export, the new planner. The product pays for that training in silence: usage metrics that never move, support tickets that ask for things you already released, stakeholders who read the changelog and still ask what changed. The wall is honest about what went live. It is dishonest about what the visitor will do next.
Three Jobs Beat Thirty Bullets
I stumbled on Claude's update spotlight by accident. For the first time, I felt like reading it. The design looked purposeful: trip planning, recipe discovery, email drafting, each with a live preview rather than an abstract capability line. It was not perfect.
Each slide ends on one job button. Tabs switch the example. There is no Previous, no Got it, no mark-seen: the X closes the tour without teaching a return path. On the recipe slide, the same cake image was pasted three times, and a second white button (Start cooking) fought the footer CTA for the same click. Email tones were labelled A, B, and C, as if the visitor already knew what those letters meant. Claude showed the jobs. The chrome still asked you to launch one and leave, or close and forget. The same attention discipline I wrote about in Waiting Is a Design Surface belongs on return too.
What I Put in the Lab
I rebuilt the pattern and put my own sprinkle on what was missing. The demo below is that version: not a screenshot of Claude, my take. Carousel instead of top tabs. Ghost secondary for the contextual job, primary for the tour. Previous on slides two and three, blank on slide one. Next until the final slide becomes Got it and dismisses. Dismiss marks seen. Recipe thumbs that actually change the dish. Email tones with names instead of A, B, C. Desktop card and mobile action sheet share state. Ready for product and design leads to steal without archaeology.
In the Product
Desktop modal
What's New
Think it through
For big tasks or small ones, get help throughout your day.
Plan a day trip
London Docklands: A Day by the Thames
4 stops · 5 km · mostly walking
Morning
- 9:00 — Canary Wharf riverside walk
- 11:30 — Cutty Sark to Greenwich Market
Find new recipes
Traditional Greek tiganopsomo
Pan-fried bread with olive oil and herbs — crisp outside, soft within.
Servings4
Write a great email
Subject
Revised Timeline for Chimney Deliverable
Hi team, Could we move the Chimney deliverable to Friday 14 March? I need two extra days for QA on the checkout flow. Thanks, Alex
Mobile action sheet
What's New
Think it through
For big tasks or small ones, get help throughout your day.
Plan a day trip
London Docklands: A Day by the Thames
4 stops · 5 km · mostly walking
Morning
- 9:00 — Canary Wharf riverside walk
- 11:30 — Cutty Sark to Greenwich Market
Find new recipes
Traditional Greek tiganopsomo
Pan-fried bread with olive oil and herbs — crisp outside, soft within.
Servings4
Write a great email
Subject
Revised Timeline for Chimney Deliverable
Hi team, Could we move the Chimney deliverable to Friday 14 March? I need two extra days for QA on the checkout flow. Thanks, Alex
The cost shows up in rooms that prefer the changelog. A product manager I know released a modal last quarter with fourteen bullets and a link to Notion. Stakeholders screenshot it green. Users closed it in under two seconds. She still does not know whether anyone tried the feature the release was meant to highlight. That is not a copy problem. It is a surface problem. You chose the inventory list when the visitor needed keys.
Keys, Not the Inventory
When you move into a new flat, the landlord hands you an inventory: every fixture, every appliance, every scuff marked on a PDF. You file it. You do not live inside the PDF. What you need is three keys that open the rooms you will actually use: kitchen, bedroom, front door. The inventory protects the deposit. The keys start the life.
A software update is the same shape. The changelog is the inventory. The What's New modal is the ring with three keys. Trip, recipe, email are locks that turn: planning, creating, refining. Show one preview that looks like output, not a bullet that claims intelligence. Let the visitor turn the key once in the modal so they remember which door to open when the modal is gone.
Give the Objection Its Full Weight
Power users hate modals. They read changelogs. They want the audit trail, the semver, the breaking changes, the compliance footnote. Interrupting their flow for marketing theatre is a dark pattern when every patch nags, when dismiss does not stick, when the modal returns on every login until someone rage-quits. Release a carousel of kitchen verbs for a bugfix and you deserve the screenshot thread.
Take that objection seriously, including against this pattern. A What's New modal is abuse when the release did not earn it, when the previews lie, when Got it does not mark seen, when you hide the changelog the legal team still needs. Harry Brignull's Deceptive Patterns catalogue includes interruptive flows that manipulate without consent. His fake urgency type covers timers and counters that invent pressure the system cannot know. Modal fatigue is real. Gate return surfaces instead of banning them: meaningful release only, honest previews, dismiss that persists, changelog linked for the minority who need the inventory, never a fourth Next on the final slide. Presence without honesty is costume. Honesty without a first job is homework.
The Return You Designed
The first screen after update is a design surface like any other. Design the job, or the visitor will design their exit. She still does not know whether anyone tried the feature the release was meant to highlight.
¿Trabajamos juntos?
Consulta los planes, haz una pregunta o reserva una llamada.
