Only One Deliverable Matters
summary
Argues that only the shipped product matters and shows concrete alternatives: using a plain-text spreadsheet wireframe (O’Reilly/Railway Media example) to define content priority, skipping full-page comps by stubbing components in the browser, authoring design tokens that drive Sketch and CSS, and a Puzzle Tokens plugin demo that updates Sketch from SASS. Shows UXPin syncing real React components into the design tool, promotes code commits over redlines, and reports faster delivery, less wasted rework, and fewer thrown-away artifacts.
AI-written summary · about
chapters (22)
- 0:00Introduction and provocation
- 3:35Only one deliverable matters
- 8:03Origins of design artifacts
- 10:05Do less to do better
- 12:10Words over wireframes
- 18:06Push production downstream
- 21:56Code commits over red lines
- 26:45Design tokens in action
- 33:27Code as the source of truth
- 36:55Design systems as collaboration
- 39:20Proper use of design tools
- 41:31Q&A begins
- 42:14Puzzle tokens and Figma
- 43:58Lessons learned over time
- 46:06Convincing stakeholders
- 48:52Distributed teams and process
- 53:25Remote work shifts
- 56:13Challenges of estimation
- 59:04Scaling to organizations
- 1:01:10Agile vs waterfall
- 1:04:18Prototyping and usability testing
- 1:05:20Closing remarks and thanks
