The Courage to Design - Bob Baxley

Summary (Artistic / Creative Focus)

Bob Baxley delivers a keynote on “the courage to design.” He argues that design is a “wild” (uncertain) problem—one that can’t be fully tamed into rigid, engineering-style processes. Creativity, in his framing, is an ongoing leap of faith.

He also shares practical, culture-building methods he used to help design teams and organizations feel safe enough to explore openly and then decide with real conviction.

---

Artistic Techniques, Concepts, and Creative Processes Shown

1) Framing design as an untamable (“wild”) problem

• He uses metaphors—such as a lion in the wild vs. a lion behind bars—to show what gets lost when design is forced into rigid workflows.
• He contrasts tame problems with complex / wicked problems (drawing on Rittel & Webber) and places design closer to the unstructured end of uncertainty.
• He emphasizes that design involves ambiguity, iteration, and risk, not certainty.

The core idea: when you try to fully control design like a machine, you remove the conditions that allow creativity to operate.

---

2) Building courage through intertwined habits

Baxley proposes that what looks like “courage” comes from three traits acting together:

• Curiosity
• Vulnerability
• Conviction

He explains why each alone is incomplete:

• Curiosity can loop without end.
• Vulnerability can be mistaken for weakness.
• Conviction can harden into stubbornness.

---

3) Curiosity in practice: team learning through storytelling and shared context

At Apple, after expanding the team and encountering hostility, Baxley helped shift the culture by:

• Running an outreach event where team members shared personal “life stories.”
• Using mockups / historical references to show progress over time—so new hires could understand what came before their work.

Result: greater emotional safety, improved collaboration, and deeper creative immersion.

---

4) Vulnerability in practice: “design publicly” via ongoing process documentation

At ThoughtSpot, to reduce misunderstandings of design, the studio adopted public communication—described as a kind of “propaganda.” The goal was to make the work visible as it evolved.

Key practices included:

• Weekly Loom videos sent across the company.
• Sharing work-in-progress, not only polished outcomes:
  • photos from whiteboards
  • freehand sketches
  • multiple explored variations
  • internal iterations on key components (e.g., a design system element)

A “split audience” strategy ensured relevance:

• One track for features for “mere mortals” (business users), led by a manager/design lead.
• Another track for backend/specialist components (“hardcore” data engineers).

Outcome: design became a shared, visible effort, improving credibility and sparking interest from sales and leadership.

---

5) Conviction in practice: decisive “design principles” as hard boundaries

To prevent fragmentation and endless internal debate, Baxley describes using “design principles” (treated like dogmas) to guide decisions.

Origin / influence:

• He credits parts of the story to Roger Rosner and references Steve Jobs’ three Keynote principles:
  • make it difficult to create ugly presentations
  • use cinematic-quality transitions
  • focus on innovation, not PowerPoint compatibility

He stresses that these serve as clear lines that reduce debate.

Implementation strategy:

• Agree quietly with a small group of managers.
• Reinforce repeatedly across meetings (“infect the organization”).
• Keep principles active for day-to-day decisions.

Later enterprise-product adaptations (three added principles):

• Documentation is a sign of failure (don’t force users to read docs; design for business users).
• Users should choose their needed complexity (start simple; enable advanced “goodies”).
• The whole product should feel like it was created by one person (resist fragmentation into isolated feature teams; preserve holistic harmony).

---

6) Process philosophy: don’t algorithmize creativity

Across the talk, Baxley warns against turning design into:

• a checklist/process,
• an algorithm,
• or a fully managed pipeline.

Instead, he argues for embracing uncertainty as the place where “magic is born.”

---

Creators / Contributors Mentioned

• Bob Baxley (speaker)
• Heng (presenter mentioned at the start)
• Steve Jobs (referenced; influence on design principles)
• Horst Rittel (wicked problems)
• Melvin Webber (wicked problems)
• David Johansen (Towards a Design Theory of Problem Solving)
• Roger Rosner (Keynote/iWork connection)
• Robert Grudin (author; quote read at the end)
• Ajit Singh (founder referenced at ThoughtSpot)
• IDEO (mentioned via Ajit’s early Honeywell projects)
• Jason (designer at Apple during the team expansion)
• Kaushik Panchal (director at ThoughtSpot)
• Adam (salesperson at ThoughtSpot who recognized Baxley)
• Abhinav (manager Baxley asks about continuing the principles)
• Saul Bass (referenced via a designer’s background)
• Ansel Adams (referenced via a Yosemite logo connection)
• Jasper Johns (referenced via career background)
• Wu-Tang Clan (referenced via a roadie anecdote)
• Walmart (example of data scale for ThoughtSpot)
• Tableau (competitor referenced)