Karl Koch | Write-first design
karlkoch.me · 1,406 words · saved by 2 readers
Write-first, build later: Ensures clear, documented decisions, preventing costly missteps in design and engineering.
Most design teams decide things in Figma. A direction gets explored and refined, and somewhere in that process it quietly becomes the plan. Nobody agreed to it. It simply accumulated. We work the other way round. The decision gets written down before anyone opens a design file. Writing is the first design tool. The pixels come later. I think of this as; write-first, build later. It runs through the whole design process, and it changes what design feels like to do. Why writing comes first A mockup is a persuasive object. It looks resolved even when the thinking underneath it is not. You can spe
saved by
related reading
- How to think in writing - by Henrik Karlssonhenrikkarlsson.xyz
- On Writing #1thezvi.substack.com
- Charlie Deets | Presenting design workcharliedeets.com
- Design Docs at Googleindustrialempathy.com
- Why Figma Wins - kwokchainkwokchain.com
- What is First Principles Thinking?fs.blog
- How to Write an Effective Software Design Documentrefactoringenglish.com
- Writing a good design documentnews.ycombinator.com
- Writing a good design documentgrantslatton.com
- Karri Saarinen on X: "Design is a search" / Xx.com
- Code-first vs. Product-firstthezbook.com
- The Kool Aid Factory :: Writing In Public, Inside Your Companykoolaidfactory.com