Thursday, August 10, 2006

More on Why Major Relaunches are a Bad Idea

More on site relaunch...

"Republishing our 2003 article, The Quiet Death of the Major Re-Launch ,touched off a surprising amount of discussion, much more than when we originally published it.
Changing Architectures

Some of the comments were about separating out a change in the look and feel of a site from the underlying architecture. People argued that changing the internals, such as implementing a new content management system, search capability, or advertisement management system, can be difficult to do in a piecemeal fashion, making it very tempting to do an entire overhaul of the site.

This could be true. I’ll be the first to admit that I have very little exposure to that side of the business. However, when we watch our large clients, such as Yahoo!, NetFlix, and Amazon do their work, we know that they’ve had architectural changes that didn’t require a major redesign of their entire sites, at least that any user noticed. So, it’s possible to make those changes under-the-covers, without affecting what the user experiences.

I do realize that possible does not equal inexpensive. Costs may make doing this prohibitive. However, design is all about trade-offs. What’s the trade-off of the costs to support multiple architectures in a staged-roll-out versus the costs of the user experience disruption that comes from a sudden major redesign? That’s the question that needs asking."   (Continued via UIE)               [Usability Resources]


Post a Comment

<< Home

<< Home