When to Design for Emergence — Kasey Klimes
kaseyklimes.com · 2,318 words · saved by 1 readers
In order to meet long-tail user needs in a market context, designers must move beyond user-centered design and instead design for emergence.
For years, I’ve heard some variation of the following lament from clients, collaborators, and friends with startups: “There’s so many use cases we could solve for, but every user we talk to wants something different, and we just don’t know which ones to focus on.” or, “We’ve designed for all the common and important user needs and now we’ve hit a ceiling. How do we grow without bloating our product with minor features?” Both statements describe what we can call the long-tail problem. It’s very common—I’ve seen the long-tail problem at tiny two-person startups and at Big Tech corporations…
saved by
related reading
- When to Design for Emergencerhizomerd.substack.com
- When to Design for Emergence - by Kasey Klimes - Primitivenewsletter.rhizomerd.com
- lecture5-market-wireframing-design.pdfspark-public.s3.amazonaws.com
- A Comprehensive Guide To Product Design — Smashing Magazinesmashingmagazine.com
- Excuse me, is there a problem?longform.asmartbear.com
- The biggest bottleneck for large language model startups is UX | by Davis Treybig | Innovation Endeavors | Mediummedium.com
- The emergence of the growth designeradobe.design
- The end of incrementalism: how AI will reward maximalist start-upsphilipjclark.substack.com
- Effective Startup Ideationbenjaminfspector.com
- How Design Tools Like Figma and Canva Are Impacting Designers | Futurefuture.a16z.com
- 10 things I learned from 10 years at Figmaclairebutler.substack.com
- Extensible Software in the age of LLMs | Jeremy Morrelljeremymorrell.dev