Hey Sebastian & Philip, thanks for this really helpful post. I’m currently helping to run Yale EA through a CEA Community Grant and there were some great tips here. There are a couple of thing’s I’d be very interested to hear more about:
Would it be possible to see a copy of the survey which sought your members’ “views on key bottlenecks and promising projects”?
If you’d be willing to share, what was the project you didn’t end up doing after getting external advice on your prioritisation? Was it “to find and read resources (mainly blog posts) made by other community builders”? And, if so, what was the reasoning behind de-prioritising?
I think an example entry for the project prio spreadsheet would be really useful for me to get a clearer sense (and as a side note—do you think your fully filled-out prio spreadsheet would be applicable to other groups, or do you think it’s too Denmark-specific to be useful and thus seeing it might confuse / bias other group organisers’ prios? I imagine at least some of the columns would be somewhat constant between groups.)
Are there slides / instructions of some kind to potentially replicate the “interactive workshops on Productivity and Effective Learning”? Do have some sense of why your members found these so useful / positive aspects of these that other groups running workshops could replicate?
I’m still not entirely sure I understand what you mean by “Make batches of your projects”, and how this model differs from assessing each individual project, and ordering them in terms of the factors you described, then going down the list in order.
Hi Frankie! Happy to hear that Sebastian’s post was of use to you. Great questions also!
Here is a draft of the member survey. There were a few minor changes when it went into survey form, but nothing major.
The project that was de-prioritised was a sort of Nordic add-on to 80,000 Hours’ career advice. The idea was to identify career paths that seemed comparatively strong or weak in Nordic countries for those who aren’t willing or able to relocate to the traditional EA hubs. We also wanted to give location-specific actionable advice on how to follow high-impact career paths in the Nordics. I still think this is a valuable project, but was convinced that focusing on making EA Denmark a more engaging and sustainable community was much more pressing, and so it seemed more valuable to work on first.
Our prioritisation sheet is probably not suitable for sharing in its current form. It’s a mess not designed for other people to understand. As you mention, it’s also very context specific. I’ve pasted an example project into another tab in the sheet Sebastian linked to, though.
Sure, here are slides for workshop 1, slides for workshop 2, and a collection of useful resources on the topics. Regarding whether it’s possible to replicate: We did these workshops because they were reasonably low-hanging fruits for us. We’re both very interested in the topics and have spent hundreds of hours of our personal time learning about them (Sebastian is even co-author of a book on effective learning and personal productivity). However, succesful workshops can probably be carried out with much less effort than that. In those cases, I think the most important things to focus on are, a) encouraging a “hypothesis → test → revise hypothesis” approach from the participants to how they want to improve, b) providing at least some inspiration/ideas for forming such hypotheses, and c) making the workshops interactive in the sense that participants form their hypotheses on site and commit to testing them during some time period following the workshop.
Regarding batches: Many of our projects were running simultaneously since we couldn’t just do the most important project, finish it, and move on down the list. Often we had to wait for answers to surveys or feedback from others, so we had to do the 2nd or 3rd most important project during the downtime. Say you can commit to 1000 hours of work on Yale EA stuff. What we’re advocating here is that you don’t start 1000 expected hours worth of projects all at once, but instead start with a batch of, say, 2-300 expected hours worth of projects. The two main reasons for this are to combat planning fallacy and to give yourself a chance to update your priorities after the first batch.
Hey Sebastian & Philip, thanks for this really helpful post. I’m currently helping to run Yale EA through a CEA Community Grant and there were some great tips here. There are a couple of thing’s I’d be very interested to hear more about:
Would it be possible to see a copy of the survey which sought your members’ “views on key bottlenecks and promising projects”?
If you’d be willing to share, what was the project you didn’t end up doing after getting external advice on your prioritisation? Was it “to find and read resources (mainly blog posts) made by other community builders”? And, if so, what was the reasoning behind de-prioritising?
I think an example entry for the project prio spreadsheet would be really useful for me to get a clearer sense (and as a side note—do you think your fully filled-out prio spreadsheet would be applicable to other groups, or do you think it’s too Denmark-specific to be useful and thus seeing it might confuse / bias other group organisers’ prios? I imagine at least some of the columns would be somewhat constant between groups.)
Are there slides / instructions of some kind to potentially replicate the “interactive workshops on Productivity and Effective Learning”? Do have some sense of why your members found these so useful / positive aspects of these that other groups running workshops could replicate?
I’m still not entirely sure I understand what you mean by “Make batches of your projects”, and how this model differs from assessing each individual project, and ordering them in terms of the factors you described, then going down the list in order.
Cheers!
Hi Frankie! Happy to hear that Sebastian’s post was of use to you. Great questions also!
Here is a draft of the member survey. There were a few minor changes when it went into survey form, but nothing major.
The project that was de-prioritised was a sort of Nordic add-on to 80,000 Hours’ career advice. The idea was to identify career paths that seemed comparatively strong or weak in Nordic countries for those who aren’t willing or able to relocate to the traditional EA hubs. We also wanted to give location-specific actionable advice on how to follow high-impact career paths in the Nordics. I still think this is a valuable project, but was convinced that focusing on making EA Denmark a more engaging and sustainable community was much more pressing, and so it seemed more valuable to work on first.
Our prioritisation sheet is probably not suitable for sharing in its current form. It’s a mess not designed for other people to understand. As you mention, it’s also very context specific. I’ve pasted an example project into another tab in the sheet Sebastian linked to, though.
Sure, here are slides for workshop 1, slides for workshop 2, and a collection of useful resources on the topics. Regarding whether it’s possible to replicate: We did these workshops because they were reasonably low-hanging fruits for us. We’re both very interested in the topics and have spent hundreds of hours of our personal time learning about them (Sebastian is even co-author of a book on effective learning and personal productivity). However, succesful workshops can probably be carried out with much less effort than that. In those cases, I think the most important things to focus on are, a) encouraging a “hypothesis → test → revise hypothesis” approach from the participants to how they want to improve, b) providing at least some inspiration/ideas for forming such hypotheses, and c) making the workshops interactive in the sense that participants form their hypotheses on site and commit to testing them during some time period following the workshop.
Regarding batches: Many of our projects were running simultaneously since we couldn’t just do the most important project, finish it, and move on down the list. Often we had to wait for answers to surveys or feedback from others, so we had to do the 2nd or 3rd most important project during the downtime. Say you can commit to 1000 hours of work on Yale EA stuff. What we’re advocating here is that you don’t start 1000 expected hours worth of projects all at once, but instead start with a batch of, say, 2-300 expected hours worth of projects. The two main reasons for this are to combat planning fallacy and to give yourself a chance to update your priorities after the first batch.
Hope that helped. Feel free to ask anything else!