Sharon:
Over the years I’ve watched my wireframes go from scribbles on the back of a napkin to architectural-looking blueprints complete with gradients and icons and detailed pagination mechanisms. And, truth be told, it saddens me. The spirit in which wireframes were intended, way back when we first realized that websites had to be planned out, was to get ideas for content down on paper before we started plodding away at development. They should inform, not dictate, the information architecture, content development, and visual design processes that follow.
Posted 11/16/2011 - 09:14
Dave:
For several years, we’ve been fusing the visual design and user experience design processes together more formally. And, in doing so, the end result is a more intuitive site with complementary functionality and aesthetics.
Posted 04/07/2011 - 09:31
Joshua:
Agile design is a given for software development; flexibility helps us better contain unforeseen technical challenges and pivot on formerly expected features when they’re deemed unnecessary.
Posted 02/14/2011 - 15:36
Dave:
We’ve all been to a website that’s overrun with advertising. Performance on these tends to be abysmal -- the slow loading time is mostly thanks to all those jumping, flashing, talking, moving, animated sidebars, headers, footers, and mid-page graphics screaming for our attention.
Posted 02/09/2011 - 10:01
// 1 comment
Mike:
Recently I tried a new, more collaborative approach to one of the critical processes involved with building a new CMS/website – wireframing. A colleague of mine pointed out a technique that was being used to help generate ideas for the redesign of drupal.org (Thanks to Leisa Reichelt’s great blog, Disambiguity !). The technique is simple and looked fun, so I gave it a try on one of my new projects.
Posted 10/02/2008 - 12:43
Kelly:
Visio 2007 is a powerful tool. But when using it again and again, I’ve found that some basic tactics save a tremendous amount of time.
Posted 09/26/2008 - 08:24
Dave:
In the age of information overload, no one wants to read through text-heavy requirements documentation. I’ve adopted a strategy of “show don’t tell” which requires less stakeholder effort while improving the quality of feedback and participation in the analysis effort. The cornerstone of this strategy is the wireframe – a universal communications tool that illustrates the user experience while providing implementation details that streamline the transition into the development effort.
Posted 02/01/2008 - 18:00
// 6 comments
