Personas and Mental Models (was DDD conflicts with Cooper GDD)
3 Jul 2007 - 3:39pm
8 years ago
> Michael Scharf said: > > But what do you do with the mental models of the different personas? > Do you formalize them? How do you communicate them to the developers? > Have you ever tried to let the developers create some > software that represents the mental model(s)?
At Cooper, we tend not spend a ton of effort "formalizing" our personas'
mental models. This is not because they're not important, but because
they are not typically well-defined in a logical sense, and therefore
not entirely well-suited for formalism.
We often express personas' mental models using narrative (text), but
there are certainly times when a diagram is helpful (like a mind map or
an affinity diagram),
Regardless of the form, and depending on the project, we are commonly
concerned with the following aspects of the mental model:
- The "objects" that the persona thinks in terms of (e.g. for a photo
sharing service, these might be photos and albums)
- The most important "attributes" of those objects (e.g. when the photo
- The persona's minimum expectations for the product capabilities and
user experience based upon past experiences in the domain
While, as I said, we don't spend a ton of effort formalizing and
communicating the personas' mental models, we do put considerable effort
into conveying the manifest model (or represented model) in as much
detail and formal rigor as possible. You'll recall from About Face that
the manifest/represented model is the actual behavioral face of the
product. This is hopefully quite close to the mental model, though it
may be different some ways (hopefully because it will end up being more
useful to users).
We typically convey the represented model through our design
specifications, and it often takes the form of screen renderings, tables
and various diagrams to illustrate the relationships between objects and