Part 1 Content Management Systems promise so much: content is easier to publish, easier to update, and easier to find and use. Lots of promises, but do CMSs really deliver? Masood Nasser examines why Content Management Systems often fail and shows how Information Architecture can come to the rescue.
Can components come to the rescue for executive dashboards? Much like IKEA uses interchangeable islands, counters, and cupboards to create a custom kitchen, by Joe Lamantia shows how it’s possible to use a modular approach for executive dashboards.
In part one of “Metrics for Heuristics,” Andrea Wiggins discussed how designers can use Rubinoff’s user experience audit to determine metrics for measuring brand. In part two, Wiggins examines how web analytics can quantify usability, content, and navigation.
Web analytics typically provide intelligence for executives and marketers, but the real value comes from evaluating the online experience. Andrea Wiggins shows how designers can use analytics to quantify the user experience.
Information architects, afraid to step on designers’ toes, may actually render wireframes unusable. Stephen Turbek talks about Verizon, the similarities between wireframes and iPods, and how to get real.
Evaluating Low Spatial Frequency Compositions
Icons that are difficult to tell apart can lead to disastrous consequences. Queen shows us how studying the way the human visual system encodes information can lead to more effective icon design.
We know a product has a lifecycle, but does the language we use for that product also have a lifecycle? From TiVo to the Internet Superhighway, Rice shows us how the metaphors we use have an evoluation all their own.
Catering to the unique needs of each customer is the dream of any business. Technology can help us get there but we need to know how to please users without intruding their privacy. This article presents a set of guiding principles for personalization design.
User State-Trace Analysis
Interaction modeling makes design decisions explicit. In principle it’s simple: record what users “should” do, what they actually do, and then explain the differences between the two. Of course there’s more to it than that, and Matt Queen gives us all the details in this story.