Design Thinking for Rubyists
summary
Design thinking claims that developers can learn a repeatable, human-centered process championed by IDEO and Stanford’s d.School to turn observations and interviews into usable products. It maps empathy, define, ideate, prototype, test onto familiar dev practices (pairing, TDD, pull requests), uses lo‑fi prototypes and user sessions to fail fast, and treats feedback as a constraint that sharpens scope. The result is clearer product decisions and higher adoption when prototypes are iterated and validated early — prototype like you know you're right test as if you know you're wrong.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:29What a good time for personal anecdote!
- 15:49what exactly is Design Thinking?
- 18:57The secret to doing anything is believing that you can do it.
- 27:09Maybe too much talking to humans?
related talks
28mDesign thinking
41mDesign Thinking? Be Bold, get Radical
59mPutting the Design Back in Architectural Design
02mDesign thinking is in tech writing all along
42mDesign Thinking for teams who want to create their own products
38mEnough Design
41mThe Designers Are Coming
40mIs Design Thinking the Magic Wand for your product success?