Deliverables and Documentation

February 13th, 2006

Interaction Modeling

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.

The more automated our lives become, the less time we seem to have. And as an information architect, a lot of time is spent making sitemaps … by hand. How valuable are sitemaps to a project team and to clients? Would your time be better spent doing other tasks than hand building sitemaps? What if we told you, “now you can.” Find out how.

The recent rise in more powerful technologies that provide richer user experiences online has presented us with a challenge. As designers, we are moving from from designing for “PIAs” to designing for “RIAs.” Does our documentation style change with the technology? Will our standard ways do the job?

Page 4 of 7...23456...