Here is a previous post on EA crowdfunding. Not sure if anyone is working on it actively, but maybe it’d be possible to rope the author into a project. Here are some other vaguely related posts:
EA Funds, update, complaint, complaint
EA Hotel (writing this comment from the hotel dining room)
As Henry says, it seems like a lot of EA projects get started and then abandoned. It was just over a year ago that Peter Hurford wrote “I guess another important next step would be learning from why similar things like EA Ventures, Impact Certificates, and the Pareto Fellowship didn’t get more traction and were shut down.” (source). So if we zoom out a bit and view this “small scale EA funding” category broadly, it appears to be littered with abandoned projects.
The same appears to be true for various EA wikis that people have created. The EA community seems to have a very short collective attention span and/or a very high appetite for novelty; people rarely seem to realize that the thing they are trying to do was already proposed or implemented in prototype form by 6 other people before them. I wonder if the lowest-hanging fruit would be to try to write a history of either attempts to provide small-scale EA funding or attempts to create a wiki, interview people who were involved in every failed project, try to discern patterns and debug the problems. In any case, ironically this causes me to update away from funding small-scale stuff a bit, and towards funding any EA organization that’s proven it has some institutional staying power!
A lens which might explain why both EA wikis and EA peer funding are so hard: In both cases, the challenge is to establish a Schelling point. A wiki will have a hard time getting writers if it doesn’t have readers, and it will have a hard time getting readers if it doesn’t have writers. A funding platform will have a hard time getting projects if it doesn’t have funders, and it will have a hard time getting funders if it doesn’t have projects. So in addition to looking at failed attempts to establish Schelling points, it might also be useful to examine successful attempts. Here are some that come to mind:
This forum. I believe this forum evolved out of a group blog which was invite-only, Ryan Carey might know more.
EA Global. EA Global was originally called the EA Summit, and Geoff Anders told me that the first summit nearly did not happen because EA organizations were having trouble coordinating.
Less Wrong 2.0. There was a period of several years where LW was in a state of decline, and every few months someone would write a post about how LW was in decline and how maybe it could get fixed and how someone should really do something about it. Nothing happened until a few people (Matt Graves, Oliver Habryka, Ben Pace, Ray Arnold, others?) got together and got really serious about it, went around talking to lots of different people about why they weren’t writing for Less Wrong, got some funding from EA Grants, etc.
In the last two cases it seems like the Schelling point was established through intensive networking and finding a compromise that achieved everyone’s interests simultaneously. If I had an MBA I would probably call it “building consensus among stakeholders”. People who spend a lot of time thinking things through independently or building infrastructure without getting anyone’s input don’t seem to be as successful. If you want to create a city off in rural Utah, the first step is not to go off and build the city, the first step is to found a religion and wait until it has a bunch of members. (Though I could believe that thinking things through independently and writing up your thoughts might be useful to a networking expert who comes along later to spearhead your project. Same for creating Facebook groups which can later be used as coordination points, e.g. the “New EA hub search and planning” FB group, which gave me an opportunity to promote the EA Hotel. However, I think a failed shot at establishing a Schelling point can actually be harmful if it creates a self-fulfilling prophecy that creating a Schelling point is not feasible.)
Another point is that if someone is already working on something kinda similar to what you are working on, it might be best to glom onto their thing instead of starting your own thing. For example, with LessWrong 2.0, Matt Graves was the person officially in charge of revitalizing LessWrong, but I think he got a big boost when Oliver Habryka and others glommed on to that project. It’s always nice to be the leader so you get to do things your way and make all the important decisions yourself, but the entire challenge with establishing a Schelling point is to coordinate disparate interests. (And by extension, in the same way you yourself are going to be more motivated to work on a project that you feel you have a leadership role in, giving other people leadership roles in your project is maybe a way to get them feeling invested.) So if you’re unable to coordinate with a person who is already working on a similar project, due to networking ability that’s insufficient to discover them or compromise ability that’s insufficient to work with them, you are probably doomed anyway. In general, I think having multiple projects competing for resources is bad, e.g. I think LW 2.0 took off around the time Arbital finally threw in the towel.
(It may be that the most important thing is just to be persistent—in the same way startups are said to be an emotional roller coaster, I’ll bet nonprofit projects are the same way, and the planning fallacy means everything takes longer than expected. Hopefully this comment wasn’t too discouraging!)
EA Hotel (writing this comment from the hotel dining room)
Just a note on the EA Wiki (and on project abandonment in general): lots of projects seem to be really badly run. The EA Wiki was offline for months because of server issues, and until recently you couldn’t even register as a new user.
I’m not sure EAs have a shorter attention span than anyone else – I imagine most would maybe try a couple of times to get onto the wiki and then just give up. That’s part of the reason I’m not worried about project duplication: so many efforts are half-baked that we shouldn’t allow one party to have a monopoly on a particular idea.
Hmmm… One thought is that if projects are half-baked due to a shortage of work hours being thrown at them, consolidating all the work hours into a single project might help address the problem. I also think having more people on the project could help from a motivation perspective, if any given project worker feels responsible for fulfilling their delegated responsibilities and is motivated by a shared vision. But ultimately it’s the people who are doing any given project who will figure out how to organize themselves.