Why UX is not only the Responsibility of the UX'er
summary
Argues that UX cannot be a last‑minute “fairy dust” fix and lists concrete failures: bringing UX in too late, with too little budget, or keeping it too detached from product teams causes flawed outcomes. Gives examples: a weather app that prioritizes graphics over missing core features, autoplay video on NFL that alienates users, and deceptive Java toolbars that break trust. Cites measurable UX constraints—0.1s unnoticed, 1s noticed, 10s abandonment—and promotes early field research, personas, remote asynchronous testing and embedding UX roles in teams.
AI-written summary · about
chapters (26)
- 0:00Intro
- 1:12About me
- 3:00Show of hands
- 4:15Interaction Designer VS Visual Designer
- 5:08LinkedIn
- 6:30Areas of specialization
- 8:16Im a fairy
- 8:59The scapegoat
- 9:40Too little
- 10:30Too late
- 11:30Too far away
- 12:59UX activities
- 16:00UX is not a bubble
- 17:08Maslows Hierarchy of Needs
- 18:56Data and Content
- 20:31Stakeholders
- 21:11Form fields
- 23:09Marketing
- 26:30Legal
- 27:33User Experience
- 28:32Visual Design
- 30:04QR Codes
- 31:03Content
- 32:05Performance
- 33:19Less is more
- 38:53Questions
related talks
34mUnderstanding UX (and UI) – a practitioner's perspective
25mIt's easy to create good looking products, but how about useful ones?
49mCo-creating with UX and Software
01h 14mBeyond the UX Tipping Point
41mIt’s easy to create good looking products, but what about useful ones
41mUX Problems Hidden Behind a Pretty UI
25mSize matters: Why some projects can't do UX well
28mIt’s Easy to Create a Good looking Product, but What About a Useful One?