There’s an underlying tension where CEA struggles to be both “top down” and “bottom up” at the same time:
Apply now, and please err on the side of applying!
But we get thousands of submissions so “it’s not the best use of our time to give feedback [on rejections]…these things are subjective.”
(When I say “you” further in this comment, I am referring to CEA generally and not the author specifically.) Tl;dr see four recommendations below.
From the “bottom up” vantage point, CEA wants to grow the community. You want more people working for and funding EA interventions. You appreciate that diverse worldviews bring to light overlooked areas, and you can’t predict where breakthroughs come from. You recognize the benefits of broadening the EA tent to match talent including management and line workers.
From the “top down” vantage point, CEA wants high quality programs and events: a position of thought leadership, a high epistemic standard, optimal 1-1 networking, and influence over policy, talent and funding to do the most good. Therefore, you reasonably choose to gate conferences, classes and programs. You don’t want to dilute the core principles or attract bad actors.
It feels to me like CEA chooses to apply the “top down” or “bottom up” lens as appropriate for itself in most situations. However, this can be confusing or misleading to the bulk of the EA community who works alongside CEA but is unaffiliated with it.
As I’ve previously commented in Open EA Global, EA is a personal choice/identity. It’s not a job title earned or a license you receive through a license board. So when people are turned away from events or courses—that they are excited to attend or pay for—with unsigned form letters and vague calls-to-action—it feels like a value-based judgment even when it is not.
I pursued four unrelated programs[1] and all of these applications were lengthy and personal. I felt like CEA took my trust and willingness to provide detailed personal information for granted. I’ve encountered only a few organizations (graduate degree programs come to mind) that came close to asking for that level of qualitative detail—and in those cases I found more clarity on what the bar was and what the upside could be. So I can see where feelings of frustration or dissatisfaction are compounded when folks don’t receive commensurate feedback.
Slight aside, based on my professional expertise in branding and customer service, it’s not obvious that the risks of “bad actors” attending events/programs outweighs the risks of “disgruntled ex-EAs” diluting the EA brand in other venues. It’s been suggested that more public criteria for applications might allow people to “game the system,” but you can also motivate good actors to do what’s necessary to qualify next time. I’m not sure if the visible cost of bad seeds at an event is higher than the invisible cost of people being turned away who might sour on EA altogether. If not handled with care, rejected applicants become vectors of negative publicity throughout the nonprofit landscape and beyond. Measuring and understanding this could be a useful research project.
Here are four actionable recommendations to improve this process (in no particular order):
Don’t call everything an “application.” As silly as it sounds, just calling something an application sets expectations that the process will be painful and there will be a harsh judgment of “accept/reject.” EAs could, for instance, more softly “request an EAG slot,” “petition to join a seminar,” etc.
Don’t encourage all folks to apply to high-bar programs. If you already have high rejection rates, casting a wider net alienates more people. You can still use targeted outbound communications to nudge relevant folks.
Allow EAs to vouch for other EAs. By the author’s admission, the staff often makes mistakes—there’s just too much information and too few resources (time, staff) to process it. Rely on the trust of others in the community to make the process smoother. If someone is motivated enough to get several references, we probably want them involved.
Make CEA assets (EAG keynotes, Virtual Program syllabi) more discoverable. E.g. dozens of EAs present hour-long keynotes at EAG conferences, but for most of these folks, only a few thousand people will ever see them! If CEA cultivates this content and makes it more prominent across owned assets and communications, there’s an alternate path for EAs to engage without needing to apply to constrained programs.
Thanks for listening. I acknowledge that gatekeeping EA programs is a thankless job. I’m interested in making the process better both as a marketing leader with relevant experience and as a community member who sees opportunities for CEA to overcome its own hurdles to doing more good! Feel free to take or leave any of my suggestions and DM me if you want to dig deeper on anything.
- ^
Intro EA Virtual Program and 80k Hours Advising (accepted), EAG DC and EAGx Berlin (rejected).
Thanks for sharing this! Helpful in understanding the quality and trends of EAG. More “actionable” dimensions for your consideration and analysis:
Welcomeness: first-time EAG versus repeat attendee?
We could plot “welcomeness” for first time EAGs relative to the general attendee base.
Hopefully everyone averages above a 9, but if the new attendees are lower, then it’s an avenue for further exploration (e.g. did the event not meet expectations?) and action (e.g. how can we make folks feel welcome?).
Application/attendee dropoff: US-based versus outside US?
We could plot app/attend demographics (including POC) for US-based versus non-US separately, or create disjoint groups based on geography.
Two folks mentioned at EAG that they suspected fewer POC (i.e. dropoff from application to attendance) because of the reduction in travel grants. If there are relatively more POC in non-US regions, the distance could be explanatory.
It’d be great to know if a third correlated variable (distance from the event) is more predictive here. Hopefully the dropoff is independent of demographic within the US, if not then it’s worth pursuing.
Thanks again!
(P.S. I am unable to access the underlying data at the moment of writing this comment, nbd)