Enabling User-Centered Navigation

Organizing site navigation based on user needs versus based on internal organization structures is a major step towards creating an effective user experience and enhancing findability.  However, it can create some security/ownership complexities.  This is why organizations rarely bother doing it.  They might understand the benefits to their audience, but they can't stomach what is required to think through these complexities or how to support them.  They would much rather align their content to their internal departments, so they can simply apply security permissions using people from within those departments.  Practically, it can be very difficult to both a) organize content based on user needs/tasks and b) use departments to define content ownership.

In researching this dilemma, I came across some great articles from Step Two Designs:

Based on these articles and my own experiences, here is a practical approach I would recommend to clients:

  1. Identify just a few key roles from each department that will be responsible for content authoring/review
  2. Fill these roles with real people (this will change over time as people leave, change roles, or the organization is restructured)
  3. Create a 'community of practice' made up of these people and an intranet manager
  4. Train the members of this community: a) get them intimately familiar with the task-based organization of the site (what goes where & why it is important); b) grant them fairly significant content authoring access (they need shared ownership of the site content); c) help them understand the implications of their raised security permissions (risks & responsibilities)

So, move forward with that site redesign.  Maybe you already knew that you should organize it based on user tasks, but now you know how to make it happen!


Ellen at: 7:27 AM said...

Why have I not been reading your blog before now?! Great stuff - More people should know this exists.

Post a Comment

Aaron Hursman
Aaron Hursman is a passionate user-advocate who is lucky enough to do what he loves for a living. As a user experience architect, he applies user-centered design principles and techniques including user research, persona development, information architecture, storyboards, wireframes, prototyping, visual design, graphic design, interaction design, and usability. Aaron has a background in web development, enterprise applications, and the social web. At nGame, he is applying his craft to design and build the next generation of enterprise software. Aaron is available as a speaker and author upon request.
Disclaimer: The information in this website is provided "as is" with no warranties, and confers no rights. This website does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my own personal opinion. Inappropriate comments will be deleted at the authors discretion. All instructions and code samples (if any, ever) are provided "as is" without warranty of any kind, either express or implied.