Modeling Concepts ~ IA Summit 2009
by Daniel Brown on Mar 23, 2009
- 10,273 views
Information architects need better tools for dealing with complex design problems like faceted browsing, template-driven displays, and content management systems. Site maps show a web site’s underlyi...
Information architects need better tools for dealing with complex design problems like faceted browsing, template-driven displays, and content management systems. Site maps show a web site’s underlying structure, but render every page literally. Such views of the site are hopelessly obsolete before they reach the printer. They do not account for modern approaches to designing navigation systems. Database- and CMS-driven sites, for example, offer greater flexibility in storing and displaying content. Our deliverables must be able to keep up.
Concept models offer an alternative that better approximate the underlying structures of today’s web sites. By documenting a site’s foundation at a greater level of abstraction, concept models provide designers better insight into the user experience.
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 74
- Downloads
- 0
- Comments
- 2
- Embed Views
- Views on SlideShare
- 10,230
- Total Views
- 10,273
1–2 of 2 previous next
•Site maps tend to represent basic navigation experience
•Flows focus on activities
•Flows have a distinct beginning and end
•Flows must show a transformation
•comparisons
•Establish design direction
▼Clarify domain or context
•Sensemaking
•Design synthesis
▼Clarification
•with stakeholders
•with self
•Approval
•Relationships by linking
•Concepts = nouns
•up to 3 dozen concepts
•Core diad, triad, or quad
•Value proposition backbone
•Focus on relationships (eg: user experience model)
•Anticipate iteration
•Ideal for domain mapping: lightbulb
•Operational model: gears
•Anticipate iteration
•Ideal for domain mapping: lightbulb
•Operational model: gears
•Anticipate iteration
•Ideal for domain mapping: lightbulb
•Operational model: gears
▼
Audience
•Trash business/technical distinctionguys with gears/$/paintbrush pointed at them, crossed out
▼Think in terms of characteristics
•detail-orientedguy with magnifying glass
•eager to contributeguy carrying stuff
•able to abstractthought bubble
▼
PurposePurpose: structure, domain
•Describe structure of site
•Illustrate underlying domain
▼
Message
•The domain is more/less complex than we imagined
•There are important relationships here not readily apparent
•
Maintenance
•
Collaboration
▼
Type: What kind of model should I make?
•
▼
Scope: What concepts should I include?
•Start with too many or start with what you know
•Add as many as you can
•Refer to planning decisions to quantify scope
•When in doubt, take it out: focus on legibility, show simpler versions initially, add elaboration later
•
Detail: How much information should I include?
▼
Abstraction: At what level should the concepts be?
•To what extent are you going to analyze or synthesize concepts?
•Force yourself to identify narrower and/or broader concepts
▼
Relationships: Which aspects of the network should I highlight?
•Find compelling relationships: passive voice and belonging are mundane
▼
Visual Language for Concepts
•Identify opportunities to imply relationships through placement
•Dont' be afraid to repeat concepts as they get further away from the central ideas, but be sure to use consistent visual language to draw
the connection
▼
Visual Language for Relationships
•Belonging relationships are easily communicated through placement
•Domain understanding
•Requirements definition
•No specialized visual language
•No surrounding context/explanation
•Not normalized: redundant concepts, redundant/non-existant relationships
•Strong emphasis on clarifying unfamiliar items through relationships
•Context-setting: Here's where the product fits
•Scope-setting: Here's what we're focusing on
•Vision-setting: Here's what the product will look like
•Strong emphasis on the product itself -- maybe mentioned explicitly
•Lack of detail
•Strong emphasis on relating familiar items with unfamiliar items
•Describe site structure or content strategy
•Describe operational structure
•Content/template-focused
•Roles incorporated: icons showing different jobs pointing at person
•Focused on familiar items only, though expressed differently (press release -> article template)
•Relationships describe navigation between templates
•Relationships describe ways concepts impact/influence each other (for interactive systems): soccer ball
▼
Two-by-two: Concept models in context
▼Characteristics
•Relationships implied by comparisons
•Relationships driven by criteria
▼Quantities are relative, not absolute
•If you start plotting points, you're into quantitative
▼Variations
•Adding a third dimension: scale (size of circle)
•Four kinds of X in the world
▼When to use 2x2
•Comparing concepts
•Key dimensions/criteria are salient
•Drive decisions based on criteria
▼
Comics
▼Characteristics
•Panel-based
•Multiple aspects of a single set of concepts
•Usually linear
▼Variations
•Non-human comics
▼When to Use Comics
•Relationships are narrative
•Relationships are relative perspectives on a central idea
•Break an idea into component parts
▼
Illustration models
▼Characteristics
•Less explicit relationships
•Relationships by relative placement (vs. linking)
•Less rigid noun-verb distinction
•1 dozen concepts
▼When to use illustration models
•elaborating on a node model
•Relationships are more abstract
•Relationships are self-evident or not as crucial