November 27th, 2007
As we continue our research into what separates the best design teams from the rest, we see one factor consistently bubbling to the top: an attention to the user’s entire experience. This attention comes in the way the team thinks about their design. Are the elements designed right? Do they account for where the user is coming from? Have they guided the user down the right path?
One method employed by many of the teams we’ve talked with is to have a framework to guide their design decisions. Each team developed their own framework, starting with their philosophies about design and then filled in with specifics, often from their own experience. For example, having received complaints that first-time users were struggling with an efficiency optimized command structure, the team made sure to consider infrequent usage in their design framework.
In today’s UIEtips, we provide Part II of the Seven Critical Considerations for Designing Effective Applications. I wrote this article by combining the essence of the frameworks we’ve seen in our tours of the best design teams, with the intent that your team could use it as a starting place for your own framework.
What considerations do you look for when creating your designs? Are there experiences you’ve had that now influence your future work? We’d love to hear from you. Leave your thoughts below.
[Critical design considerations are just part of what we'll be talking about at the upcoming Web App Summit, March 26-28, 2008 in San Diego, CA. You can be part of that event and receive your limited edition Web App Summit iPod nano by registering before 12/11. More details here.]Tweet