Not much surprises me anymore. After more than a decade spent providing boutique services, followed by the last 6 or so years strictly in software, I’ve really earned the increase in grey hairs on my face and head. However, one thing I continue to find absolutely baffling is the way companies and designers often attempt to design their software from the bottom-up, screen-by-agonizing-screen. That approach is categorically wrong. Any design or redesign must start from the systemic level, from the top-down.
What does that mean? Consider an application that most of us are familiar with, iTunes. If Apple came to me and asked me to simply redesign the home page for Videos inside of iTunes, without regard for the rest of the product, they would be setting up me—and the redesign effort itself—for failure. The Videos home page is one screen amidst a veritable tsunami of information. Anything we do to that page will impact the user experience of the entire product. To redesign that screen, large and important as it may be, in isolation is an inherent fail. By changing it without changing the many pages around and relying on it, we would simply be buggering up the overall user interface, no matter how much better that spot redesign might be.