Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »


 

Designing the structure for a website is never a lockstep 1-2-3 process, and different designers will approach it in different ways.

It’s always good, however, to start with some knowledge. In The research phase in Chapter 3, we described how some basic user research (such as contextual inquiry, open card sorts, and tree-testing the existing site) can give us a head start.

If we’ve done the research, we are not starting with a blank slate:

  1. We know our users.
    Our initial discussions with stakeholders defined who our target audiences are, and some basic research determined what they want and how they go about it.

  2. We know our content.
    A content audit has determined which topics we’re keeping, updating, adding, and deleting.

  3. We know what’s right and wrong with the existing structure.
    A benchmark tree test has shown us which parts of the existing site tree work well (and should be reused) and which parts perform poorly (and need to be changed).

  4. We have new ideas to try out.
    An open card sort has given us ideas about how users mentally group our content and which terms they use.

We can now sketch out some new structures to test. Let’s take a look at the most common ways sites are organized, and some common tactics that can help us create our own trees.

 

Roughing out alternative trees

When we “rough out” a site tree, it means that we create a quick-and-dirty site structure in an hour or less.

The point of this is to do the minimum work to convey an idea to others, so we can then decide whether it’s worth fleshing out enough to test. We don’t want someone to spend an entire day creating a detailed site tree, only to have the team decide that they’re going a different direction.

To rough out a site tree:

  • We only create 2 to 3 levels of the tree, even if we know there will be more sublevels. We can create the sublevels later if the tree survives our triage process.

  • We don’t get stuck on wording, especially for the lower levels. At this point we’re looking more for variety than exact terminology.

  • We do a quick coverage pass to make sure we’ve accounted for all the content the site will include, but again, if we miss something, we can fix it later.

  • ss of rough trees

 


Next: Picking candidates to test

  • No labels