Database Reference
In-Depth Information
The
Collaboration model
shows each collaboration event discovered during the inter-
view, including who interacted with whom to achieve what and what was shared, done or
discussed.
The
Identity model
showsthedifferentobservationsofsourcesofpride,self-esteem,and
value that emerged during the interview. As the team sees these observations cluster they
maystarttocomeupwithnamesforcoherentidentityelementsthatarerelevanttothepro-
ject focus.
The
Sequence model
lists the detailed steps the user took to accomplish a task. Multiple
sequence models may be captured.
The exact models to capture vary based on project focus. The above models are gen-
erally useful, but if the project seeks to support decision making, the team may capture a
Decision Point model
*
to show the factors working for and against a particular decision.
And if a particular physical environment is especially important (such as the interior of a
car when analyzing automotive information systems) the team may do a rough sketch of
the environment in a
Physical model
.
Capturing these models in the interpretation session make it possible for the team to de-
scribe and analyze aspects of the user work practice in a concrete, shared, tangible way.
They also automatically teach the design team how to see more when in the field, and this
expandedfocushelpsthemavoidoverwhelmorfocusingonlyonproblemsduringthefield
interview.
Because technology has made participating remotely so easy, interpretation sessions
may be distributed. Remote participation is a way to involve interested parties who are not
local so that they can touch the detailed user experience as it is collected—another immer-
sion opportunity.
Every designer in the room has a job to do, so each has to process the data and think
about its implications. This combination of listening, inquiring, thinking, and drawing or
writing the implications creates the immersion in the data that results in real understanding
and insight. By the end of the interpretation session, all participants “own” the data and
have incorporated it into their view of the user and the project.
*
EvenAgile!AgileDevelopmentmerelyassumesthatdirectionisavailablefroma“customer”role—which
is informed by Contextual Design.
*
The Decision Point model is a variant of Contextual Design's original Cultural model. We find this useful
for products looking at buying or choosing as a primary focus. The Artifact model may still be useful, but
as paper artifacts were transformed and put online over the years we find that use of this model became
rare.
