Just a quick post to this, I think most of the way information is
structure comes out of cultural norms or mental models.
If you went to a website, where are you most likely to find the
address. If it were me, I would likely go to the contact section.
So to answer your question, I think, technically, it is possible to
visually explain the reasoning, but it would be a long explanation.
I think it has to do more with user interaction behaviour. Perhaps
the best book I could recommend is "Don't Make Me Think" by Steve
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
You could try representing the architecture as wireframes then
illustrate the logic of the different user journeys based on the
target audiences / personas?
I derive a site's structure from the organization of the use cases
for that site.
First, I create the use cases, they can be name only (i.e., Consumer
adds item to shopping cart).
Then, I collect similar use cases into functional packages (or
folders). These functional packages then translate into the structure
of the site. I can then use the Use Case List to show why I structured
a site a certain way.
hope this helps.
solved, just a few charts of the card sorting, pre and post
restructuring! Thank you guys! the whole presentation is one hell of
a comic book!