Hi Denis, thank you for your message and your offer to contribute, it is welcome. Since we are just starting out we still haven’t built all the capabilities we have envisioned. For example, and as mentioned above, we were planning a list of tractable problems and project ideas to guide potential project leaders, as well as a list of past/failed projects or lessons learned from projects to ensure the community as a whole is not just spinning its wheels (e.g. this metaproject has had similar iterations in the past..). But your idea for a wiki that not only provides problem areas and project ideas but also provides thought-through analyses, roadmaps, required skills lists, available resources and community input is a huge improvement over our current plan. So I don’t think the issue of not having project leaders identified upfront would be a critical problem, as long as you’re OK with your wiki being separate from the project database. Ideally entrepreneurial EAs will find your project write-ups on Impact CoLabs and then create a project from it (or people that are screened from the platform due to low-impact ideas can be directed to those pre-vetted ideas).
We definitely want the ultimate version of Impact CoLabs to be the central node for project creation, and we want the resources we provide to reflect that. The goal is to be a more high-volume/low-touch, top-of-the-funnel solution than the incubators/accelerators like Charity Entrepreneurship or other upcoming startup factories. But even if we are not going to shepherd projects personally and diligently, it doesn’t mean we can’t try to provide as detailed and well-researched guidance as possible.
My only slight hesitation for your approach is the effort involved in development and upkeep, we would rather offer a lower-value solution (just a list of ideas) that we can guarantee can be maintained than a higher-value solution (detailed wiki with required fields for each project idea) that has a large chance of being abandoned after a while. So it all depends on volunteer interest in contributing and/or how we set it up. Would love to chat about this more. If you want to take this offline we would recommend filling out our new team member form so we can get you more background info on the project, or alternatively you can just email info@impactcolabs.com.
Meanwhile I’ve set up my wiki, started thinking about the structure of the template I’d like to use for the project pages, and have started reading up on your Google Docs. It’s impressive how thoroughly you’ve already evaluated your project concept!
My “idea foundry” project itself will have its own page in its wiki with more information on my future plans. That’ll make it easier to reflect on whether the whole thing is sustainable. I haven’t thought about it sufficiently myself. I’ll only publish individual pages once I have proofread them for possible info hazards and have gotten feedback from some trusted friends too.
… as well as a list of past/failed projects or lessons learned from projects
Yeah, and there are also a lot of ostensibly brilliant project ideas in various lists that I think are subtly deleterious. No one has attempted to realize them yet (at least the ones I vaguely recall and to my knowledge) but a project database with just a bit more detailed thinking may help to keep it that way. (Or else may inspire someone to come up with a way to realize the project in a way that avoids the subtly deleterious bits.)
… as long as you’re OK with your wiki being separate from the project database
Totally. It feels like so far I’ve been wholly unconvinced by some 95+% of project ideas I’ve read about, so those should not end up on your platform. It would just be valuable – or essential – to be able to promote the top of the shortlist to potential founders.
My only slight hesitation for your approach is the effort involved in development and upkeep, we would rather offer a lower-value solution (just a list of ideas) that we can guarantee can be maintained than a higher-value solution (detailed wiki with required fields for each project idea) that has a large chance of being abandoned after a while.
I’m worried about that too. I’d be willing to risk it, pending further thinking. An alleviating factor is that the detailed reviews would be reserved for a small shortlist of projects. Most of them would just get a quick stub summary and the reason why I didn’t prioritize them.
I’ve read that you’re perfectly open to (for-profit) social enterprises and of course early-stage project in need of cofounders. But I see the term “volunteer” a lot in the materials. It has these particular associations with low commitment, low responsibility, no salary, nonprofits, etc. Is it the best synonym for the job? None of the alternatives I can think of is quite broad enough either – cofounder, collaborator, partner, talent, … – but I imagine that such word choices can influence what the platform will end up being used for. A platform for “cofounder matching” may end up being used for more high-value work than one for “volunteer matching,” maybe some sort of “Task Y” notwithstanding. But I’ve also heard that someone had the impression that cofounder matching is not a current bottleneck, which I found surprising.
I’ll get in touch through one of the channels you recommended.
Thank you for the kind words and the great feedback! You make a great point about ‘volunteering’, we will discuss that internally. I’m generally in agreement with your comments but would love to explore some of the nuance! Look forward to hearing form you, if you reach out and don’t hear back, please message me here to make sure we are being responsive.
Hi Denis, thank you for your message and your offer to contribute, it is welcome. Since we are just starting out we still haven’t built all the capabilities we have envisioned. For example, and as mentioned above, we were planning a list of tractable problems and project ideas to guide potential project leaders, as well as a list of past/failed projects or lessons learned from projects to ensure the community as a whole is not just spinning its wheels (e.g. this metaproject has had similar iterations in the past..). But your idea for a wiki that not only provides problem areas and project ideas but also provides thought-through analyses, roadmaps, required skills lists, available resources and community input is a huge improvement over our current plan. So I don’t think the issue of not having project leaders identified upfront would be a critical problem, as long as you’re OK with your wiki being separate from the project database. Ideally entrepreneurial EAs will find your project write-ups on Impact CoLabs and then create a project from it (or people that are screened from the platform due to low-impact ideas can be directed to those pre-vetted ideas).
We definitely want the ultimate version of Impact CoLabs to be the central node for project creation, and we want the resources we provide to reflect that. The goal is to be a more high-volume/low-touch, top-of-the-funnel solution than the incubators/accelerators like Charity Entrepreneurship or other upcoming startup factories. But even if we are not going to shepherd projects personally and diligently, it doesn’t mean we can’t try to provide as detailed and well-researched guidance as possible.
My only slight hesitation for your approach is the effort involved in development and upkeep, we would rather offer a lower-value solution (just a list of ideas) that we can guarantee can be maintained than a higher-value solution (detailed wiki with required fields for each project idea) that has a large chance of being abandoned after a while. So it all depends on volunteer interest in contributing and/or how we set it up. Would love to chat about this more. If you want to take this offline we would recommend filling out our new team member form so we can get you more background info on the project, or alternatively you can just email info@impactcolabs.com.
Hi Mats! That sounds splendid!
Meanwhile I’ve set up my wiki, started thinking about the structure of the template I’d like to use for the project pages, and have started reading up on your Google Docs. It’s impressive how thoroughly you’ve already evaluated your project concept!
My “idea foundry” project itself will have its own page in its wiki with more information on my future plans. That’ll make it easier to reflect on whether the whole thing is sustainable. I haven’t thought about it sufficiently myself. I’ll only publish individual pages once I have proofread them for possible info hazards and have gotten feedback from some trusted friends too.
Yeah, and there are also a lot of ostensibly brilliant project ideas in various lists that I think are subtly deleterious. No one has attempted to realize them yet (at least the ones I vaguely recall and to my knowledge) but a project database with just a bit more detailed thinking may help to keep it that way. (Or else may inspire someone to come up with a way to realize the project in a way that avoids the subtly deleterious bits.)
Totally. It feels like so far I’ve been wholly unconvinced by some 95+% of project ideas I’ve read about, so those should not end up on your platform. It would just be valuable – or essential – to be able to promote the top of the shortlist to potential founders.
I’m worried about that too. I’d be willing to risk it, pending further thinking. An alleviating factor is that the detailed reviews would be reserved for a small shortlist of projects. Most of them would just get a quick stub summary and the reason why I didn’t prioritize them.
I’ve read that you’re perfectly open to (for-profit) social enterprises and of course early-stage project in need of cofounders. But I see the term “volunteer” a lot in the materials. It has these particular associations with low commitment, low responsibility, no salary, nonprofits, etc. Is it the best synonym for the job? None of the alternatives I can think of is quite broad enough either – cofounder, collaborator, partner, talent, … – but I imagine that such word choices can influence what the platform will end up being used for. A platform for “cofounder matching” may end up being used for more high-value work than one for “volunteer matching,” maybe some sort of “Task Y” notwithstanding. But I’ve also heard that someone had the impression that cofounder matching is not a current bottleneck, which I found surprising.
I’ll get in touch through one of the channels you recommended.
Thank you for the kind words and the great feedback! You make a great point about ‘volunteering’, we will discuss that internally. I’m generally in agreement with your comments but would love to explore some of the nuance! Look forward to hearing form you, if you reach out and don’t hear back, please message me here to make sure we are being responsive.