Question 1

How do we know whether we need a refresh or a full redesign?

Accepted Answer

Look at whether people complete their tasks. A product that works but looks dated needs a visual pass, while a product where the same step fails every week needs structural work.

Question 2

How long does an audit take before we can decide?

Accepted Answer

Two to four weeks covers most products, including analytics review and a handful of user sessions. Anything faster tends to produce opinions rather than evidence you can act on.

Question 3

Should the app and the web product be redesigned together?

Accepted Answer

Share the tokens and the logic, then sequence the releases separately. Doing both at once doubles the support load in the same week, which few teams can staff.

Question 4

What happens to existing users during a redesign?

Accepted Answer

Plan for a period of visible frustration and budget support capacity for it. Keeping familiar entry points and offering a temporary way back turns most of that frustration into usable feedback.

Question 5

Can the team that built the original product run the redesign?

Accepted Answer

Often yes, and they bring context an outside team would spend weeks acquiring. Bring in outside review for the diagnosis stage if the team is attached to decisions it made earlier.

Question 6

How much should a redesign budget allocate to engineering?

Accepted Answer

More than most plans assume, especially when data migration is involved. Ask each supplier to estimate the engineering share before the design contract is signed.

Question 7

When is the wrong time to start this work?

Accepted Answer

Directly before a seasonal peak or a major sales push. Ship structural changes when usage is low, and the team has room to respond to what breaks.

App Design Agency vs Product Redesign Costs and Scope

Legal Pages

Important Pages

Legal Pages

Important Pages

Quick links