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
- lecture5-market-wireframing-design.pdfspark-public.s3.amazonaws.com
- Excuse me, is there a problem?longform.asmartbear.com
- Malleable software: Restoring user agency in a world of locked-down appsinkandswitch.com
- The biggest bottleneck for large language model startups is UX | by Davis Treybig | Innovation Endeavors | Mediummedium.com
- A Comprehensive Guide To Product Design — Smashing Magazinesmashingmagazine.com
- Effective Startup Ideationbenjaminfspector.com
- The end of incrementalism: how AI will reward maximalist start-upsphilipjclark.substack.com
- Extensible Software in the age of LLMs | Jeremy Morrelljeremymorrell.dev
- The emergence of the growth designeradobe.design
- A New Kind of Startup Is Comingevery.to