Skip to article
The Design Office of Nick Sloggett
WorkWritingExperimentsResumeEmail
Back
Essay·Nov ’23·3 min read

Design the rollback like a launch

My first pass at undo on Uber’s experimentation platform was a red Revert button that said nothing. The redesign treats a rollback like a launch: you pick how far, and the dialog redraws what that means before you commit.

Typeface

In my first pass at Uber’s experimentation platform, undo was a red Revert button at the bottom of a panel. It gave no word on what it would do. It was red, so it looked serious, and that was all it told you. It also sat at the bottom of a panel, so the most consequential action on the page was the last thing you reached.

At Uber a feature ramps behind a flag: to a few people, then more, with an experiment measuring what it does. A rollback changes what hundreds of thousands of people see. It’s a launch in reverse, and I had given it less design than the smallest launch got.

So I designed it like a launch. You pick how far to go back, and the dialog redraws what that means: everyone back to control, or only the one segment that is hurting while the rest stay in treatment, with how many people each choice moves. It says what happens to the experiment and to the alert. Only then do you confirm.

Undo has a size

Most undo is small. Take back a typed word and nothing else changes. That’s why the usual undo can be a keystroke with no dialog: its size is always one step.

A rollback is bigger than that, and its size changes with the choice. Pulling a flag back from everyone and pulling it back from one segment are different decisions. They move different numbers of people, and the dialog spells out what each does to the experiment and the alert. A Revert button folds all of that into one red rectangle and asks you to trust it.

Undo has a size, and the interface should show that size before anyone commits to it. The short version is the rule I took from XP: show the consequence before the commitment.

The redraw does the work

What makes the dialog work is that it redraws. Change how far you’re rolling back, and the count and the effects change with it while you’re still deciding. The size of the rollback is part of the choice you’re looking at, where a bare button would leave you to find it on a dashboard after the fact.

That changes what the person in the dialog is doing. With a bare button they guess, then check. With a dialog that redraws, they compare two sizes of the same decision. An owner paged in the middle of the night needs to be comparing. Sometimes the narrow rollback is right, and sometimes only the full one will do.

The same habit fits any destructive action with scale behind it, like a bulk delete or a permission change. If the action has a size, the size belongs in the control that commits it, and it should move when the choice moves.

The last step of the XP dialog is typing the flag’s name, a repeat I defended under WCAG 2.2 in October. That step works because of everything before it. By the time you type, you know what you’re agreeing to.

Newer← A key is a permanent promiseOlderThe repeat I’d keep under WCAG 2.2 →

© 2026 Nick Sloggett

EmailLinkedIn (opens in new tab)ResumeRSS