When to Design for Emergence - by Kasey Klimes

newsletter.rhizomerd.com · 2,361 words · saved by 1 readers

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 with billions of users. In the long-tail problem, all the opportunities in front of you live on the long tail of user needs. Collectively they represent many users, but individually none of them appear important enough to invest time or resources in. Common needs represent large markets, but the needs are largely met, and competition between solutions is fierce. Long-tail needs are often unmet and come

When to Design for Emergence Market applications on the long-tail of user needs Kasey Klimes Jun 08, 2022 83 8 5 Share 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 p

When to Design for Emergence - by Kasey Klimes

related reading