When to Redesign vs. When to Iterate

Clients often come to us saying they need a complete redesign. Sometimes they're right. Often, they're not.

Signs you need a redesign

If your product has accumulated years of design debt, if the underlying architecture can't support new features, or if your brand has fundamentally changed — a redesign makes sense. Also: if users consistently can't complete core tasks, something structural is broken.

Signs you should iterate

If your product works but feels dated, if conversion rates are declining gradually, or if you're adding new features that don't fit the current layout — iterative improvements are usually faster, cheaper, and less risky.

The hybrid approach

What we often recommend is a phased approach: redesign the core experience (onboarding, key workflows) while iterating on secondary features. This gives you the impact of a redesign with the safety of iteration.

The worst outcome is a redesign that takes so long it's already outdated by the time it launches. Ship improvements continuously, even during a larger redesign effort.