Status Updates From Communicating the UX Vision...
Communicating the UX Vision: 13 Anti-Patterns That Block Good Ideas by
Status Updates Showing 1-30 of 42
André
is on page 310 of 329
13. Not defending hard enough
・Toyoda's 5 Whys
・defend delighters: low biz/high UX value
・why biz lacks user-research?
・stakh talks abt user as power user (=himself) or novice (overcaution)→have personas avail
——
14. ur anti-patterns
15. Relaxation (Yoga,…)
16. Group Design Techniques [Howtos]
・design product box
・role-play a service before drawing
・elevator pitch
・biz model canvas
・personas- & product moodboards
・…
— Dec 29, 2019 04:51PM
Add a comment
・Toyoda's 5 Whys
・defend delighters: low biz/high UX value
・why biz lacks user-research?
・stakh talks abt user as power user (=himself) or novice (overcaution)→have personas avail
——
14. ur anti-patterns
15. Relaxation (Yoga,…)
16. Group Design Techniques [Howtos]
・design product box
・role-play a service before drawing
・elevator pitch
・biz model canvas
・personas- & product moodboards
・…
André
is on page 240 of 329
11. Responding to tone, not content
・culture→tone
・delay response, or u'll respond to initial percept. of their tone
・coffee break
・"No, because…"→Other person looking for reasons to reject; "bc…, therefore No"
12. Defending too hard
・ppl find ways around bottleneck-you
・perception, design is subjective=dismissable
・choose battles
・prepare: crucial assets?
・get to whys: stakh. express biz concern by proposing design
— Dec 28, 2019 02:11PM
Add a comment
・culture→tone
・delay response, or u'll respond to initial percept. of their tone
・coffee break
・"No, because…"→Other person looking for reasons to reject; "bc…, therefore No"
12. Defending too hard
・ppl find ways around bottleneck-you
・perception, design is subjective=dismissable
・choose battles
・prepare: crucial assets?
・get to whys: stakh. express biz concern by proposing design
André
is on page 210 of 329
9. Assuming others don't get design
・understanding design ≠ underst. how to create it
・not understandable = fails purpose
・user research+co-design ᐳ intuition+experience
・openness avoids us-VS-them
10. Insisting on perfection
・how much is about product, or self-validation?
・expectation mgt: [strategic jargon], socialize vision (paper on walls)
・user/biz goals ᐳ individuals (dis)like
・MVP
・ship @90%
・design / UX debt
— Dec 23, 2019 02:04PM
Add a comment
・understanding design ≠ underst. how to create it
・not understandable = fails purpose
・user research+co-design ᐳ intuition+experience
・openness avoids us-VS-them
10. Insisting on perfection
・how much is about product, or self-validation?
・expectation mgt: [strategic jargon], socialize vision (paper on walls)
・user/biz goals ᐳ individuals (dis)like
・MVP
・ship @90%
・design / UX debt
André
is on page 166 of 329
7. Throwing deliverables over the fence
・don't take/pass docs missing whys & hows
・reject project plans that force creatives into silos, find collab pattern
・moodboard w/ stakeh⇒emo investment
8. Polishing deliverables too early too high
・changes seen as destruction
・stakeh. feel only choices are accept or reject whole piece
・time unused for feedbk & keeping rework easy & cost low
・solving ᐳ artifacts
・5-User Friday
— Dec 06, 2019 02:00AM
Add a comment
・don't take/pass docs missing whys & hows
・reject project plans that force creatives into silos, find collab pattern
・moodboard w/ stakeh⇒emo investment
8. Polishing deliverables too early too high
・changes seen as destruction
・stakeh. feel only choices are accept or reject whole piece
・time unused for feedbk & keeping rework easy & cost low
・solving ᐳ artifacts
・5-User Friday
André
is on page 118 of 329
5. Being in the room but not present:
・avoid silos
・agile > waterfall
・being concentrated/headphones vs continuously available to team
・[osmotic communication]
・walking meetings, …
6. Not having a consistent design language:
・processes, deliverables, features
・differing defs=debate
・put a label on it or they do (many labels)→own the process
・"mental model" doc ignored ('why' missing)→present in context
・method cards
— Nov 24, 2019 06:42PM
Add a comment
・avoid silos
・agile > waterfall
・being concentrated/headphones vs continuously available to team
・[osmotic communication]
・walking meetings, …
6. Not having a consistent design language:
・processes, deliverables, features
・differing defs=debate
・put a label on it or they do (many labels)→own the process
・"mental model" doc ignored ('why' missing)→present in context
・method cards
André
is on page 76 of 329
4. Presenting w/o contextualizing:
・we spend lot of time w/ the work but only show it stakeholders periodically→context imbalance→shallow feedback
・extra hour for preso-prep→quality feedb. [cheaper than wrong impl]
・whole picture first before feedb step-by-step
・(product) personas, story/process/empathy/experience maps, custmr life cycle, …
・explain, don't mail
・"Bigger logo!"→unpack underlying concern→more solutions
— Nov 10, 2019 03:24PM
Add a comment
・we spend lot of time w/ the work but only show it stakeholders periodically→context imbalance→shallow feedback
・extra hour for preso-prep→quality feedb. [cheaper than wrong impl]
・whole picture first before feedb step-by-step
・(product) personas, story/process/empathy/experience maps, custmr life cycle, …
・explain, don't mail
・"Bigger logo!"→unpack underlying concern→more solutions



