‘Note: Page numbers followed by “f” indicate figures, “t” indicate tables and “b” indicates boxes.’
Abstract
vs. concrete data,
51–54Activity Explorer Focus Area,
447during construction,
129fcreating distribution technology and relationships,
237fBackground project information,
270Brick Cognitive Style,
491Christmas Lights Thinker Cognitive Style,
492–493Classic product structure errors,
363bCoherent
“system of support”,
4b, 308designing background representation,
194–195finding key collaboration activities and generating insight,
192–194interaction-centered Collaboration Model,
195–197, 196fstory-based consolidation,
197Commercial off-the-shelf products (COTS products),
451bUser Environment Design and,
451bTraditional Contextual Design Model,
209abstract
vs. concrete data,
51–54experienced motives
vs. reports,
54–55summary data
vs. ongoing experience,
51Contextual Design,
, 37b, 43, 45, 68, 96–98, 104–105, 138, 243, 278, 286, 320, 365, 367b, 391, 396, 400b, 415, 444, 461–462, 471b, 484, 489–490, 496–497, 499cross-functional teams,
245designing business products,
group ideation process,
233product planning and strategy,
405–410project planning and execution,
410–414prototyping and other methods,
400–403software applications,
step-by-step process,
7–8technology interaction,
traditional product design,
UX,
gathering user data,
22–23contextual interviews,
44fmaster/apprentice model,
45–49collecting collaboration data in,
191bcollecting data for relationship model in,
183bgathering identity data in,
171bContextual techniques,
391Conversation
Cool Concepts,
361, 10–11, 13–14, 67, 70, 113, 123–124, 131–132, 136–137, 247, 267, 295, 307, 311, 325, 379b, 383, 445–446, 452in Contextual Interview,
74–75Creativity, creating focus for,
259–262Cross-sectional approach,
477building into consolidation,
138choosing message and stories,
160–161collecting observations into framework,
159–160creating graphic framework,
159Delivering services,
471bDesign,
, 61, 253, 277–278, 304–305, 315, 331, 336, 351–352, 365, 501thinking,
15–19, 143, 145, 253–254, 256, 258, 296, 309, 312, 351–352, 413–414, 495validation
mockup of a cell phone interface,
419fsample paper prototype,
418fDistribution and business model readiness,
236–237on teams meaning better design,
246bDucks-in-a-Row planner Cognitive Style,
466–467“Edit Slide” screenshot,
340Engineering-driven design,
15–16Enhancement database,
405
contextual design experience models,
147–148Experienced motives
vs. reports,
54–55Expert/novice relationship model,
58–59entertainment systems,
65focus reveals and conceals,
67–70setting project focus,
66–67Graphic framework creation,
159collecting observations into,
159–160Guest/host relationship model,
59High-level Interaction Patterns,
311–312Human-technical practice,
234Identity
data gathering in Contextual Interview,
171bcollecting observation into potential,
176–177putting in background sections,
178–179from travel Identity Model,
176fcollecting observation into potential identity elements,
176–177identity element from travel Identity Model,
176fputting elements in background sections,
178–179Information architecture,
335fInteraction
Airbnb’s Interaction Pattern,
375fbuilding from User Environment Design,
383–388component of Airbnb search results page,
371fInteraction-centered Collaboration Model,
195–197, 196fInterpersonal dynamics management,
101–104Interpretation principle in prototype interview,
426Interpretation principle,
60–64listening for “no”,
63–64Interpretation session(s),
41, 81bbuilding shared understanding,
82–84conversation and mutual inquiry,
82Relationship Model, capturing during,
185sequence model, capturing during,
211, 212finterviewer/interviewee relationship model,
58extremely focused task,
477Intrapersonal triggers,
68Inventing next product
challenge of design for life,
247–249Contextual Design’s group ideation process,
233corporations splitting up job,
234invention of design team,
233people part of secret sauce,
244–247user data drives innovation,
241–243Iterative prototyping process,
440Legginess in user Environment Design,
363bLife, keeping coherent,
305Links, in Focus Areas,
339Lower-level usability issues,
209
Market(ing),
460, 15–16, 19, 32, 38, 38b, 83, 85, 203, 245–246, 255–256winning with planning,
241bMaster/apprentice model,
45–49Meaningful structure,
143Metaphors in Visioning,
261Mobile
Multiple perspectives on problem,
497for scanning device,
421fParallel design process,
367bParticipant role in Interpretation Session,
91Participatory Design,
401Partnership principle,
55–59avoiding other relationship models,
58–59withdrawal and return,
57–58from shopping project,
225fPoker role in Visioning,
281Primary filters on AirBnB website,
371driving concurrent implementation,
459–463infrastructure development,
472planning business processes,
461–462planning services and support,
460–461software implementation,
460partitioning release for implementation,
455–459planning series of releases,
445–454Product
relationship between UX and,
455bship themes supporting intent,
408–410Product design,
, 8–9, 8b, 48, 60, 96, 297, 304, 328b–329b, 333, 498–499scenario reasoning
vs. structural reasoning,
308–312Project
cross-functional team formation,
466–468service and UX design,
471binterpretation session,
435bFunction Deployment process,
497–498Real-time project information,
270capturing during interpretation session,
185, 186fand Collaboration Models,
148relationship information capturing,
184fRequirements
Retrospective account,
52–54Role-centered Collaboration Model,
194–195Secret sauce, people part of,
244–247Section, Interaction Pattern,
373–374collecting, interpreting, and using data in affinity,
202–203capturing during interpretation session,
211, 212fSequential design process,
367bShared understanding,
82–84Shipping User Environment Design,
452–453Slogan, in Visioning,
260Software as a service (SaaS),
462Standard requirements techniques,
32–33Story-based consolidation,
197completing model consolidation,
197managing critique with Mom Response,
328b–329bvision and product concepts,
320introducing yourself,
429Summary data
vs. ongoing experience,
51System of support,
4b, 308Systems-based reasoning,
308Technology
Tight cross-functional partnership,
408bTraditional Contextual Design Models,
207, 272–275techniques for consolidation,
209Transition from overview to Contextual Interview,
72challenge of design data,
32–34traditional techniques,
38–39User Environment Design,
387b, 310, 315, 325, 331, 353f, 356f–357f, 363b, 365, 368, 393, 418–419, 444, 445b, 448f–449f, 452, 456, 496focus area defining editing screen,
338fInteraction Patterns building from,
383–388screen from PowerPoint,
338f
User experience (UX),
, 62, 145, 294b, 295, 304, 310–311, 332, 349–351, 366–368, 383, 410, 443–444, 453, 496relationship between product management and,
455bUser-centered
driving design conversations with,
396–400VisiCalc, first spreadsheet,
241–242creating a common direction,
285–289identifying product concepts,
289–291positives, negatives, and design ideas for travel vision,
288fvision for travel product created by team,
282fTraditional Contextual Design Models,
272–275Weekly process checks,
484Withdrawal and return,
57–58cross-functional team,
95–96designing creative team culture,
104–105managing interpersonal dynamics,
101–104structure design meetings for creativity,
96–101