|
|
|
|
|
|
by shalmanese
1760 days ago
|
|
|
There's also #4 which is "What I definitely actually need". Tools that you build for other people have a market size of [0, everyone). Tools you build to scratch an itch and actually use have a market size of [1, everyone). That may not seem like a big difference but the scale is exponential, there's as much space between [0, 1) as there is between [1, Infinity). The next step, and one where people frequently fail, is to introspect and to ask why is it I find PMF with my tool, to what degree are those reasons personal vs universal and what are the minimal tweaks I need to make to expand the adoption of the tool by the next exponential factor? A trivial example would be like, a tool that you build for yourself doesn't need to have authentication but a public tool does. Various things that you hardcoded in because you built a tool that fit you like a glove instead need configurators and other things to fit other people as well. The most common form of failure with this approach is that people who build their own tools are very high variance from the population so you're likely to build something too niche or too obscure to reach sustainability but that's in many ways a better problem to have than a tool with zero adoption. |
|
|