How do you announce a product redesign without upsetting users?

Lead with what did not change -- their data, settings and daily workflow -- before showing anything new. Opening on the new interface confirms in four seconds exactly what users feared, which is that everything they know is gone.

What should a migration demo show?

Where the button they use fifty times a day moved to, how to reach the old view if it exists, what breaks and on what date, and what they personally must do -- ideally nothing, said explicitly rather than left to inference.

Should a migration announcement lead with the benefits?

No. To an annoyed audience, benefit-led framing reads as justification. Answer the practical questions completely first, then state the improvement once at the end.

← Back to blog

Demoing a Change to People Who Did Not Ask for One

August 22, 2026

Announcing a redesign, a migration or a new version means demoing to people who already pay you and did not want anything to change.

Every instinct from sales demos is wrong here. This audience is not weighing options; they are calculating what the change will cost them personally.

Lead with what did not change

The first fear is that everything they know is gone. Opening on continuity — their data, their settings, the workflow they use daily, still there — buys you the attention to show what is new.

A demo opening on the exciting new interface confirms exactly what they were afraid of, in the first four seconds.

Show the thing they will look for first

Where the button they use fifty times a day moved to. This is the single most-asked question and it is usually answered last.
How to get back to the old view, if that exists, said plainly.
What breaks and when, with dates, rather than implied.
What they have to do, ideally nothing, said explicitly rather than left to inference.

Do not sell the benefits first

Benefit-led framing reads as justification to an audience that is annoyed, and it is heard as "we did this for us and are telling you it was for you".

Answer the practical questions completely, then state the improvement once, at the end. The order matters more than the content here, and getting it wrong turns a routine update into a support week.

Where the demo pays for itself

Migration announcements generate a predictable wave of identical tickets — where did X go, do I need to do anything, is my data safe. A demo attached to the announcement answers all three before they are asked.

It also gives support one link to reply with for the following month, which is worth more than the announcement itself.

Frequently asked questions

How do you announce a product redesign without upsetting users?: Lead with what did not change -- their data, settings and daily workflow -- before showing anything new. Opening on the new interface confirms in four seconds exactly what users feared, which is that everything they know is gone.
What should a migration demo show?: Where the button they use fifty times a day moved to, how to reach the old view if it exists, what breaks and on what date, and what they personally must do -- ideally nothing, said explicitly rather than left to inference.
Should a migration announcement lead with the benefits?: No. To an annoyed audience, benefit-led framing reads as justification. Answer the practical questions completely first, then state the improvement once at the end.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →