A retailer required registration before purchase to build its customer database, and lost the sales it was trying to capture data about.
CASE·001Case study · Ecommerce
Decision-focused write-ups. The point is the reasoning, including the options that were rejected.
10 entries
A retailer required registration before purchase to build its customer database, and lost the sales it was trying to capture data about.
CASE·001Case study · Ecommerce
A payments product added security badges and lost conversion, then recovered it by removing them and explaining what actually happens to the money.
CASE·002Case study · Fintech
A system team built a complete component library that nobody adopted, then changed the strategy from mandate to migration path.
CASE·003Case study · Design systems
A generous, modern-looking redesign made a dashboard slower for the people who used it all day.
CASE·004Case study · Data products
Hiding columns on small screens made the table tidy and removed the data field staff had opened it to see.
CASE·005Case study · Data products
A large share of searches returned nothing, and the fix was vocabulary rather than the search engine.
CASE·006Case study · Search
Every team that added a feature added a notification, and users responded by turning all of them off.
CASE·007Case study · Collaboration
A retention gauntlet kept subscribers for one more month and produced public complaints, regulatory attention and worse reactivation.
CASE·008Case study · Subscriptions
Splitting a long form into steps did not raise completion until the team also saved progress and let people come back.
CASE·009Case study · Forms
An accurate suggestion feature went unused until it explained itself and became easy to reject.
CASE·010Case study · AI products
The full contents of this section, so you can see the shape of it rather than only what a filter returned.