Hey, I encourage you to keep track of “did anyone end up actually doing any project”
My priors are that often lists-of-things are started in EA, many people think it would be useful-for-someone-else or something-that-”should”-be-done (because “others will probably use it”) but few-if-any use it themselves
And my priors from “the lean startup” are that the first version of a product won’t fit the customers, and that the main way to get product-market-fit is to talk to lots of users and watch them trying to use your product. What usually happens, on those priors, is the founder discovers surprising things important to users that were importantly different from the ideas during the “vision” stage. For example, maybe the founder focuses a lot on table-filters but the users care about “it’s scary to send an email to whoever proposed the project”
I’m not saying that your specific project is bad, and I’m sorry if this turns out discouraging. My intent is to share my priors. Just like if I’d want to open a for-profit startup, then I hope my friends would tell me about things that often go wrong there, in case I haven’t heard of them
Great advice, Yonatan! This is actually baked into the original plan—build a minimum viable product, find some users, find the sticking points, iterate and improve. “Build a feedback form” is on the to-do list, and I’m always open to suggestions for better design and sharing.
Also, honestly, even if nobody else benefits from this, I’ll be glad to have it available. Initially the thing that drew me to David’s post was my frustration at not knowing where to look for quick-win opportunities to benefit EA. I figured someone had done something like what I wanted, and I was delighted to find that someone did. Even if it completely flops, I won’t regret the time spent collecting and organizing project ideas, and I’ll probably keep using the list as a reference for years.
Hey, I encourage you to keep track of “did anyone end up actually doing any project”
My priors are that often lists-of-things are started in EA, many people think it would be useful-for-someone-else or something-that-”should”-be-done (because “others will probably use it”) but few-if-any use it themselves
And my priors from “the lean startup” are that the first version of a product won’t fit the customers, and that the main way to get product-market-fit is to talk to lots of users and watch them trying to use your product. What usually happens, on those priors, is the founder discovers surprising things important to users that were importantly different from the ideas during the “vision” stage. For example, maybe the founder focuses a lot on table-filters but the users care about “it’s scary to send an email to whoever proposed the project”
I’m not saying that your specific project is bad, and I’m sorry if this turns out discouraging. My intent is to share my priors. Just like if I’d want to open a for-profit startup, then I hope my friends would tell me about things that often go wrong there, in case I haven’t heard of them
Good luck
Great advice, Yonatan! This is actually baked into the original plan—build a minimum viable product, find some users, find the sticking points, iterate and improve. “Build a feedback form” is on the to-do list, and I’m always open to suggestions for better design and sharing.
Also, honestly, even if nobody else benefits from this, I’ll be glad to have it available. Initially the thing that drew me to David’s post was my frustration at not knowing where to look for quick-win opportunities to benefit EA. I figured someone had done something like what I wanted, and I was delighted to find that someone did. Even if it completely flops, I won’t regret the time spent collecting and organizing project ideas, and I’ll probably keep using the list as a reference for years.