Persona

Posted at: 11:04 AM by Marianna

There is a thin line between designing a web site to increase the company's sales and to increase the users' experience.

A clients' main reason for creating a web site or redesigning their existing web site is to increase profit/company sales, which can happen by improving the web site's traffic.

Sometimes Information Architects have the dilemma of whether to design with focus on a client's or a user's needs. Don't get me wrong, both should be taken into consideration, but some circumstances dictate more attention should be given to one than the other.

If we create a new user experience that should strongly promote services and products (Picture 1), persuading more and more people to engage with the page, we have to design a web site with authority, give examples of what other users do and add user testimonials. In general, we should enhance understanding, create persuasive visual design, generate confidence and stimulate desire (How to manipulate website visitors). On the other hand, if we are more user-focused (Picture 2) we should for example: avoid blinking imagery (though it could drive user attention to a service or a product), have no more than one animation per page and provide users with a sense of control.

As Spencer Gerrol and Kim Snedaker discussed at UPA 2008 there is a difference between what users "can do" (usability) and what users "will do" (persuasion) while visiting a website. I believe the best approach, is to ensure that users will have access to all the possible options before proceed to the desired action.

Picture 1

Picture 2

Labels: experience, ia, usability

Posted at: 9:18 PM by Hammad

It's not often that I come across a bit of industry lingo that I haven't heard before, but whilst working with a partner agency recently, I came across just that.

A Silent Corridor.

Now apparently the phrase was coined by somebody at BT and it refers (at least in the world of Information Architecture anyway) to a column on a page that becomes completely empty under certain circumstances.

For example. It's commonplace to use a 3 column layout for a web site, with the right column used for related links etc. However, what happens if a page/template no longer needs to use this area as defined? It's not always as simple as allowing the central column to 'flow' into this open space, as it's often restricted by a series of inherited template definitions (especially if the site is developed on a Content Management System; aka CMS). This actually happens quite a lot, like on Privacy policies or Sitemap pages. It can also be relevant during an e-commerce/shopping process, when you want to strip back on the hard-sell and keep people focused on what happening on the core real estate.

The result is a silent corridor; a complete end-to-end column that is empty and has nothing to offer anybody wandering into it. If you try to use it, you will go unheard.

It's not actually a bad thing to happen though, despite the eerie name it has become Christened with.

Template and layout consistency is very important for a good user experience and so by using a silent corridor effectively, you can keep your users focused on the important content on a page, instead of ramming unnecessary links and promos in their face and making them claustrophobic.

(oh dear, I think the hospital connotations are starting to take over!).

Labels: experience, ia, theory