When to Design for Emergence - by Kasey Klimes
rhizomerd.substack.com · 2,233 words · saved by 1 readers
Market applications on the long-tail of user needs
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…
related reading
- When to Design for Emergencekaseyklimes.com
- When to Design for Emergence - by Kasey Klimes - Primitivenewsletter.rhizomerd.com
- No More Boring Apps | !Boringandy.works
- Do Things that Don't Scalepaulgraham.com
- Do Things that Don't Scalepaulgraham.com
- The Tyranny of the Marginal User - by Ivan Vendrovnothinghuman.substack.com
- Invisible asymptotes - Remains of the Dayeugenewei.com
- The Farmer & Farmer Review . Mastery and Mimicry . The Heart of the Builderfarmerandfarmer.org
- Do Things that Don't Scalepaulgraham.com
- No More Boring Apps | !Boringnotboring.software
- A Comprehensive Guide To Product Design — Smashing Magazinesmashingmagazine.com
- Why Figma Wins - kwokchainkwokchain.com