Hi Michael, as you mention—the issue of accurately defining our scope is still an important open question to us. I’m happy to share our current thinking about this, but we expect this thinking to evolve as we collect feedback and gain some more hands-on experience.
I think it’s worth making a distinction between two versions of this question. The first is the longer-term question of what is the set of all cause areas that should be within scope for this work. That’s a difficult question. At the moment, we’re happy to use the diversity of views meaningfully held in the EA community as a reasonable proxy—i.e. if there’s a non-negligible portion of EAs that believe a certain cause area is promising we think that’s worth investigating. As such, all three of the examples you mention would be potentially in-scope in my view. This is not, in and of itself, a cohesive and well-defined scope, and as I mentioned, it is likely to change. But I hope this gives at least an idea of the type of scope we’re thinking of.
The second version of this question is what we actually intend to work on in the upcoming months, given that we are just getting started and we are still constrained in time and resources. This question will dominate our actual decisions for the foreseeable future. Within the large scope mentioned above, we want to initially focus on areas based on two criteria: First, unmet needs within the EA community, and second, cause areas that are easier to evaluate. Both of these are very weak signals for where we want to focus long-term, but drastically influence how quickly we can experiment, evaluate whether we can provide significant value, and start answering some of our open questions. As a concrete example, we believe the Global Health & Development fits this bill quite well, and so at least part of our first career paths will be in this space.
I hope this helps clarify some of these questions. I apologize if there are more open questions here than answers—it’s just really important to us to experiment first and make long-term decisions about priorities and scope afterwards rather than the other way around.
I apologize if there are more open questions here than answers—it’s just really important to us to experiment first and make long-term decisions about priorities and scope afterwards rather than the other way around.
Yeah, that totally makes sense. And no need to apologise! I think sharing your current thinking at this stage seems like a really good move, and that necessarily means having lots of remaining uncertainties (indeed, that’s part of why it’s a good move). So I wouldn’t at all want to disincentivise that by demanding that someone has all the details figured out when they first post on the Forum about a project :)
Hi Michael, as you mention—the issue of accurately defining our scope is still an important open question to us. I’m happy to share our current thinking about this, but we expect this thinking to evolve as we collect feedback and gain some more hands-on experience.
I think it’s worth making a distinction between two versions of this question. The first is the longer-term question of what is the set of all cause areas that should be within scope for this work. That’s a difficult question. At the moment, we’re happy to use the diversity of views meaningfully held in the EA community as a reasonable proxy—i.e. if there’s a non-negligible portion of EAs that believe a certain cause area is promising we think that’s worth investigating. As such, all three of the examples you mention would be potentially in-scope in my view. This is not, in and of itself, a cohesive and well-defined scope, and as I mentioned, it is likely to change. But I hope this gives at least an idea of the type of scope we’re thinking of.
The second version of this question is what we actually intend to work on in the upcoming months, given that we are just getting started and we are still constrained in time and resources. This question will dominate our actual decisions for the foreseeable future. Within the large scope mentioned above, we want to initially focus on areas based on two criteria: First, unmet needs within the EA community, and second, cause areas that are easier to evaluate. Both of these are very weak signals for where we want to focus long-term, but drastically influence how quickly we can experiment, evaluate whether we can provide significant value, and start answering some of our open questions. As a concrete example, we believe the Global Health & Development fits this bill quite well, and so at least part of our first career paths will be in this space.
I hope this helps clarify some of these questions. I apologize if there are more open questions here than answers—it’s just really important to us to experiment first and make long-term decisions about priorities and scope afterwards rather than the other way around.
Thanks, that all sounds reasonable to me.
Yeah, that totally makes sense. And no need to apologise! I think sharing your current thinking at this stage seems like a really good move, and that necessarily means having lots of remaining uncertainties (indeed, that’s part of why it’s a good move). So I wouldn’t at all want to disincentivise that by demanding that someone has all the details figured out when they first post on the Forum about a project :)