AI summary by TwinMind
Scott Berkun | How Design Makes The World | Talks at Google
Talks at Google
58m 14s
Introduction and Book Overview
- Paulo Malibuo (YouTube ads UX lead, San Bruno) and Merlinich (UX design manager, Zurich) host Scott Berkun
- Berkun: author of 8 books including "Myths of Innovation," "Confessions of a Public Speaker," "The Year Without Pants"
- Current book: "How Design Makes the World" - accessible exploration of design impact and practitioners
- Mission: identify what holds back good design from reaching the world
- Goal: make design accessible through stories rather than mystical/magical art perception
Design as Verb vs Noun Concept
- Design field narrowly siloed by subcategories (interior, mobile, etc.)
- Most important designs overlooked: public transportation systems, political systems, policy writing
- Key insight: think of design as verb, not noun
- Opens recognition of design types with deep histories, knowledge bases, tactics, skills
- Mission: integrate design fields, increase cross-communication and shared recognition
Story 1: Notre Dame Cathedral Fire (May 2019)
- Fire alarm system well-engineered, million-dollar investment, expert specifications
- Failed to consider full design experience: user knowledge, assumptions, training
- Security guard (few weeks experience, double shift) received cryptic message: "ZDA 110-3-15-1"
- Second notification: "Addict nave sacry" (sacristy = storeroom)
- Guard unaware of multiple sacristies, went to wrong location
- 10+ minute delay before finding actual fire location in attic
- Fire became inferno due to wooden ceiling infrastructure
- Design flaw: system optimized for speed but created wide response window
Historical Design Failures
- Therac 25 radiation therapy machine (1970s): text-based, modal UI caused lethal radiation doses
- Robin Hood app (2020): young trader saw $730,000 margin debt display, took own life
- Interface didn't explain margin calls eventually resolve
- Pattern: expertise privilege creates gaps between designer knowledge and user reality
Design Community's Responsibility Gap
- Design literature/documentaries primarily reflective to design community
- Confusion between internal improvement resources vs. external education materials
- Need to close knowledge gaps through better outreach, not just internal improvement
- Sarah Little Turnbull example: N95 mask designer from 3M, adapted bra design shape for safety mask
- Design victories across society underrepresented in community discourse
Story 2: Norman Doors and Design Critique Culture
- Norman doors: affordance mismatch (pull handles that should be pushed)
- Design community makes fun repeatedly without asking legitimate "why" questions
- Usability problems less important to door buyers than designers assume
- Pattern: community critiques without understanding wider decision-making context
Design for Use vs Design for Sale
- Victor Papanek's "Design for the Real World" framework
- Design for use: UX community focus
- Design for sale: marketing, growth, profit focus
- Often animosity between designers and marketers/product managers/founders
- Both approaches involve design thinking: prototyping, evaluation, iteration, data-informed decisions
- Need recognition of shared design processes across disciplines
Four Core Design Questions
- Fits on index card (design constraint forcing clarity)
- Questions provide lens/tool applicable to anything
- More powerful than stories alone
- Designed to elevate thinking about design decisions
- Always subvertible by person with different values/goals
- Power structure ultimately determines implementation
Story 3: Missoula, Montana Urban Planning
- City center rotated 45 degrees, violating grid system logic
- 1880s frontier town with Old Country Road on diagonal
- Land ownership conflict: diagonal road investors vs. established judge (north-south grid preference)
- Bridge renovation decision put to vote: judge won north-south orientation
- Technical debt: didn't resolve existing diagonal infrastructure
- Result: "malfunction junction" - dangerous 5-way intersection (formerly 6-way)
- Lesson: even VP of Design role limited by previous power-based decisions
Power Dynamics in Organizations
- Most design decisions made by people with power, not design training
- Land owners in Missoula weren't trained architects/UX designers
- Power = decision-making authority regardless of qualifications
- Design professionals often relegated to cosmetic decisions (signs, not infrastructure)
- Reality of human group dynamics vs. idealized design process assumptions
- Culture defines power structure in every organization
Ambassadorship vs Evangelism
- Evangelism model: proselytizing with books/arguments
- Ambassador model: learn target culture's language, traditions, context
- Goal: fit in, be useful, gain context for effective persuasion
- Example: convincing marketing budget holder requires understanding marketing language/value system
- Not superficial knowledge but inherent understanding to participate in value system
Design Literacy Concept
- Basic awareness of good vs bad design
- Fundamental human factors knowledge
- Basic user research understanding
- Small curb of knowledge, not full designer expertise
- Fire alarm designers needed: talk to security guards, observe workflows, understand training
- Heavy lifting of ambassadorship through accessible stories/education
Practical Influence Strategy
- Ask: "Tell me about something you love to use" (5 minutes)
- Follow up: "Why do you love it?" (satisfaction, smoothness, reliability)
- Users naturally use UX design vocabulary without prompting
- Flip: "Tell me about something you hate to use"
- Same follow-up about frustrations, disappointments
- Reveal: "Gap between love/hate was designed by someone. My expertise helps teams make things people love"
- Creates personal connection, customer empathy, opens door for methods discussion
Organizational Navigation for New Designers
- Small shop: personal relationships with powerful people, direct influence
- Large organization: need allies, coalition building, social influence design
- Strategy: find recent successful project, interview team about process/chronology
- Map successful paths and how good ideas die
- Build arsenal of organizational stories and context
- Leverage: small design changes affect millions of users vs. thousands
Drive-by Design Criticism
- Tyler Thompson boarding pass redesign example
- Community tendency to shame organizations for bad design
- Hidden constraints: airline printer infrastructure across hundreds of airports
- Old, expensive-to-replace printer limitations drive design constraints
- Cost trade-off: $10 higher ticket prices for better boarding pass design?
- Maturity issue: extracting hard parts (politics, power, goals, constraints) when critiquing
- Need generosity toward other designers facing unknown constraints
Future of Design Post-2020
- Increased mediated experiences (Zoom, WebEx vs. in-person meetings)
- Design more central to all interactions
- Every UX nuance stressed differently
- Pervasive mute button UX problems
- Role more acute, need for design knowledge increased
- Success depends on better value explanation and invitation to see problems as design/UX/creative problems
Quantitative vs Qualitative Design Justification
- Data-driven organizations create pressure for quantitative design principles
- Data requires interpretation - doesn't provide single answer
- Analytics show clicks, not emotional states between clicks
- User could punch wall in frustration or celebrate joy - same click data
- Strategy: make analytics person ally, show limitations of quantitative data
- Fight on stronger turf than pure quantitative measures
- Qualitative observation reveals story between data points
