Hide table of contents

Crossposted on The Field Building Blog's Substack, subscribe here.

The aim of this blog is to share knowledge among community builders.

There are good resources on CB in the form of resource centres, talks, and guides. Still, I feel none of these really show “how the sausage is made” the same way one can go down a rabbit hole when they want to read about take-off speeds. I have found myself explaining the same considerations about funding, heavy-tailed impact, retreats and the like to new community builders many times. In its least ambitious version, this blog will at least serve as a place where I can point people to.

I think the most valuable conversations on field building are happening when people share their hot takes at conferences, retreats, or between staff members of fieldbuilding orgs that are just a bit too edgy to write up for the EA forum. The aim of this blog will be to host such conversations, talk about big-picture strategy in fieldbuilding and share my work experience of the space from the past years. I want to help new community builders to peek behind the curtain, and experienced ones to share their thoughts unapologetically. I also want to improve epistemics around field building and help people become better calibrated in assessing its value.

About me

My name is Gergő, and my academic background is in psychology. I’m the director at the European Network for AI Safety and founder of Amplify, a marketing agency dedicated to helping fieldbuilding projects. My journey into communitybuilding started in 2019 with organising EA meetups on a volunteer basis. 

I started doing full-time paid work in CB in 2021 when I founded an EA club at my university (it wasn’t supposed to be full-time at least at the beginning, but you know how it is). This grew into a city group and eventually into a national group called EA Hungary. We also spun out an AIS group in 2022, which I’m still leading. AIS Hungary is one of the few AIS groups that have 2+ FTE working for them. 

Previously I was a volunteer charity analyst and analysis coordinator for SoGive, an experience I think of fondly and I’m grateful for. I have also done some academic research in psychology.

Why should you care?

As the title suggests, this blog will be most useful for current and aspiring fieldbuildiers, but I will also cover AIS strategy, fundraising and careers to some extent. I will also aim to keep posts brief so that it’s possible to do most readings in 5-10 minutes. To help you decide whether you want to stick around, here are some of the content I’m planning on publishing:

  • Why I think EA and AIS fieldbuilding is bottlenecked by marketing
  • Whether or not you should hold socials
  • How to optimise your introductory courses
  • Doing fieldbuilding as a long-term career path
  • Why city groups are hard to organise
  • Why I think CEA has been scapegoated for all things wrong in EA space and communitybuilding
  • My thoughts on Bluedot’s relationship to the rest of the AIS fieldbuilding ecosystem

I will also bring interviews and guest posts from all the fieldbuilding organisations that you know and love. For now, I have commitments from PIBBS, Apart Research, and Bluedot but I’m planning to cover other organisations such as CEA, Arkose, FAR AI, Kairos and more.

I hope the posts to come will bring you value. I would really love for you to engage with this content by sharing your thoughts in the comments and asking questions. Your feedback is highly appreciated throughout this journey, so please don’t hesitate to share any by emailing me at gergo[at]enais.co, or through this form, (anonymously if you wish). If you are working in fieldbuilding and would like to write a guest post, be interviewed about your role or collaborate in some other form, feel free to reach out at gergo[at]enais.co.

37

0
0

Reactions

0
0

More posts like this

Comments3


Sorted by Click to highlight new comments since:

Interesting topic ideas, thanks in advance Gergő!

Quick question: why not write on the EA Forum? I am not convinced by "the most valuable conversations on field building are happening when people share their hot takes at conferences, retreats, or between staff members of fieldbuilding orgs that are just a bit too edgy to write up for the EA forum". Is it just a better "writer experience"?

To be clear, I am interested enough in your views that I went to Substack and subscribed to your newsletter! It seems to me that for your topics, there are much stronger reasons to stay on the forum than for leaving it: I suppose you'll get more readers; it will be more convenient for said readers; there's a good comments system; the audio transcription; there are previous of within-forum links; and probably other important things I'm forgetting.

If you want people to take your writings less seriously, and to be able to write without spending hours reviewing your texts, maybe you could use the "quick takes"?

(super interested to hear what was in favor of Substack! :) )

hey! Sorry, I missed this until now.

Quick question: why not write on the EA Forum?

Thanks for this question, I realize it's worth clarifying what I mean exactly: I think there are a lot of valuable conversations happening that never end up being shared on the forum, even though they should be. I think this is because 1) lack of time 2) small demand (there are not that many fieldbuilders) and 3) and potential authors worrying about how the author is going to be perceived if they share their thoughts without much filtering. (e.g. it is easy to come across as elitist when talking about CB, and it takes a lot of time to explain a nuanced take on these issues)

I'm definitely post my writings on the forum! (one can just cross-post from substack)

It seems to me that for your topics, there are much stronger reasons to stay on the forum than for leaving it: I suppose you'll get more readers; it will be more convenient for said readers; there's a good comments system; the audio transcription; there are previous of within-forum links; and probably other important things I'm forgetting.

(super interested to hear what was in favor of Substack! :) )

More from gergo
Curated and popular this week
LintzA
 ·  · 15m read
 · 
Cross-posted to Lesswrong Introduction Several developments over the past few months should cause you to re-evaluate what you are doing. These include: 1. Updates toward short timelines 2. The Trump presidency 3. The o1 (inference-time compute scaling) paradigm 4. Deepseek 5. Stargate/AI datacenter spending 6. Increased internal deployment 7. Absence of AI x-risk/safety considerations in mainstream AI discourse Taken together, these are enough to render many existing AI governance strategies obsolete (and probably some technical safety strategies too). There's a good chance we're entering crunch time and that should absolutely affect your theory of change and what you plan to work on. In this piece I try to give a quick summary of these developments and think through the broader implications these have for AI safety. At the end of the piece I give some quick initial thoughts on how these developments affect what safety-concerned folks should be prioritizing. These are early days and I expect many of my takes will shift, look forward to discussing in the comments!  Implications of recent developments Updates toward short timelines There’s general agreement that timelines are likely to be far shorter than most expected. Both Sam Altman and Dario Amodei have recently said they expect AGI within the next 3 years. Anecdotally, nearly everyone I know or have heard of who was expecting longer timelines has updated significantly toward short timelines (<5 years). E.g. Ajeya’s median estimate is that 99% of fully-remote jobs will be automatable in roughly 6-8 years, 5+ years earlier than her 2023 estimate. On a quick look, prediction markets seem to have shifted to short timelines (e.g. Metaculus[1] & Manifold appear to have roughly 2030 median timelines to AGI, though haven’t moved dramatically in recent months). We’ve consistently seen performance on benchmarks far exceed what most predicted. Most recently, Epoch was surprised to see OpenAI’s o3 model achi
Dr Kassim
 ·  · 4m read
 · 
Hey everyone, I’ve been going through the EA Introductory Program, and I have to admit some of these ideas make sense, but others leave me with more questions than answers. I’m trying to wrap my head around certain core EA principles, and the more I think about them, the more I wonder: Am I misunderstanding, or are there blind spots in EA’s approach? I’d really love to hear what others think. Maybe you can help me clarify some of my doubts. Or maybe you share the same reservations? Let’s talk. Cause Prioritization. Does It Ignore Political and Social Reality? EA focuses on doing the most good per dollar, which makes sense in theory. But does it hold up when you apply it to real world contexts especially in countries like Uganda? Take malaria prevention. It’s a top EA cause because it’s highly cost effective $5,000 can save a life through bed nets (GiveWell, 2023). But what happens when government corruption or instability disrupts these programs? The Global Fund scandal in Uganda saw $1.6 million in malaria aid mismanaged (Global Fund Audit Report, 2016). If money isn’t reaching the people it’s meant to help, is it really the best use of resources? And what about leadership changes? Policies shift unpredictably here. A national animal welfare initiative I supported lost momentum when political priorities changed. How does EA factor in these uncertainties when prioritizing causes? It feels like EA assumes a stable world where money always achieves the intended impact. But what if that’s not the world we live in? Long termism. A Luxury When the Present Is in Crisis? I get why long termists argue that future people matter. But should we really prioritize them over people suffering today? Long termism tells us that existential risks like AI could wipe out trillions of future lives. But in Uganda, we’re losing lives now—1,500+ die from rabies annually (WHO, 2021), and 41% of children suffer from stunting due to malnutrition (UNICEF, 2022). These are preventable d
Rory Fenton
 ·  · 6m read
 · 
Cross-posted from my blog. Contrary to my carefully crafted brand as a weak nerd, I go to a local CrossFit gym a few times a week. Every year, the gym raises funds for a scholarship for teens from lower-income families to attend their summer camp program. I don’t know how many Crossfit-interested low-income teens there are in my small town, but I’ll guess there are perhaps 2 of them who would benefit from the scholarship. After all, CrossFit is pretty niche, and the town is small. Helping youngsters get swole in the Pacific Northwest is not exactly as cost-effective as preventing malaria in Malawi. But I notice I feel drawn to supporting the scholarship anyway. Every time it pops in my head I think, “My money could fully solve this problem”. The camp only costs a few hundred dollars per kid and if there are just 2 kids who need support, I could give $500 and there would no longer be teenagers in my town who want to go to a CrossFit summer camp but can’t. Thanks to me, the hero, this problem would be entirely solved. 100%. That is not how most nonprofit work feels to me. You are only ever making small dents in important problems I want to work on big problems. Global poverty. Malaria. Everyone not suddenly dying. But if I’m honest, what I really want is to solve those problems. Me, personally, solve them. This is a continued source of frustration and sadness because I absolutely cannot solve those problems. Consider what else my $500 CrossFit scholarship might do: * I want to save lives, and USAID suddenly stops giving $7 billion a year to PEPFAR. So I give $500 to the Rapid Response Fund. My donation solves 0.000001% of the problem and I feel like I have failed. * I want to solve climate change, and getting to net zero will require stopping or removing emissions of 1,500 billion tons of carbon dioxide. I give $500 to a policy nonprofit that reduces emissions, in expectation, by 50 tons. My donation solves 0.000000003% of the problem and I feel like I have f