A redesigned billing hub landed as a loss in the customer community. The team fixed the announcement before touching the screens.
Somewhere in our customer community last week, a thread started growing. We had shipped a redesigned billing hub, and the posts had a shape you’ll recognize if you’ve ever moved a tab: where did the insurance section go, why is this 2 clicks now, who asked for this.
The easy reading is that the redesign missed. The team’s reading, once they dug into who was posting, was more specific. The new hub has a dashboard with prompts that walk you to the top tasks, and the customers complaining hadn’t engaged with any of them. The customers who had been shown the dashboard, in a support call or a walkthrough, understood it and liked it. The design was landing, and the introduction of it was where the gap was.
So the decision on Tuesday was about the message. A community post that says “here’s where everything moved” confirms the loss and hands people a map back to the old mental model. The post the team is writing instead says “we built you a new dashboard,” and shows it. Same product, same screens, and one framing asks customers to mourn a tab while the other invites them to try something. Longer term, the team is building jobs-to-be-done collateral: short pieces that start from the task (“I need to check whether this claim paid”) and show the new path, rather than a changelog that starts from the UI.
Announce the gain. A map back to the old screen just confirms the loss.
I’d count this as part of the design work, right alongside the hierarchy of the screen. We spend weeks on how a page reads and then let the hierarchy of the announcement happen by default. Loss aversion is real, and “here’s what moved” is a loss-shaped sentence.
Two adjacent calls from the same launch-readiness review are in the same spirit.
The guided walkthrough for the premium tier opens on a customer testimonial, before a single feature gets explained. Someone who looks like you saying this saved them real time every week does more for the next screen than the next screen does for itself. (Worth calling out: the time-savings claim went to legal for approval before it went anywhere near a customer, which is the boring step that makes the exciting one possible.)
The walkthrough for the base tier got cut. It duplicated in-app prompts already in the queue, and nobody argued. Launch-readiness reviews are where you find out which of your deliverables were for the customer and which were for the plan.
One more moment from that review stuck with me. A goal the team set back in January, one that seemed lofty at the time, got confirmed as hit, and the person who delivered the news did it in the flattest possible tone, like reading the weather. The PM running the meeting said they’d been hoping for a bigger, more grandiose speech. I’m with them. When launch is 2 weeks out and the pressure is high, it’s easy to let the wins read like status updates. Make a little noise. The team will need it in September.
The teachable part
When customers experience a redesign as loss, check whether they’ve seen the new thing before you doubt the design. Then lead the announcement with what they gained. The message hierarchy is design work.