Aligning Expectations in Community Work

Expectations are powerful. When they are clear and shared, they motivate, guide, and inspire. But when expectations exist without explanation, context, or support, they quietly become a source of pressure. Over time, that pressure turns into disappointment, burnout, and even depression. I’ve seen this play out in tech more times than I can count. When reality doesn't match expectations, the gap feels personal, even when it isn't. It’s the silence after a contribution, the delayed response, or the false assumption that everyone else has it figured out.

There's a saying I come back to often: ‘Expectation without explanation leads to disappointment’. In community work, this couldn't be more true.

The Human Behind the Pull Request

From the outside, community work looks simple: we build, ship features, and celebrate releases. But behind every pull request or brilliant idea are people, people with limited time, different pressures, and very human limits. When we focus only on the output and ignore the people behind it, even the best work eventually falls apart. Community work is about translating intent and creating shared understanding. Without that care, technical excellence amounts to very little. If the people burn out or feel unseen, the work comes to nothing. That is where real community work begins.

The Cheerful Megaphone vs. The Shield

The common expectation is that community managers are just cheerful megaphones. In reality, you are the bridge, the buffer, and often the firefighter. Take Google Summer of Code as an example. The expectation is that new contributors will join and make high-impact contributions immediately. The reality? Repositories are flooded with "Can I work on this?" comments. Maintainers, already stretched thin, find themselves on the verge of burning out from the noise. In this moment, you become the shield. You redirect eager students to onboarding docs and facilitate office hours to answer the same question for the 50th time, all to ensure core maintainers aren't buried under a mountain of notifications.

Natural Alignment vs. The Translator

There is a belief that maintainers, contributors, and users naturally align. In reality, everyone is operating under different pressures. As a community manager, you feel them all. Your job is to help everyone understand each other without causing conflict. You are:

• Part Translator: Helping newcomers understand project norms.
• Part Supporter: Reminding contributors to open issues before PRs.
• Part Coordinator: Helping maintainers set healthy boundaries.

Growth via Posting vs. Fixing Friction

Some assume community growth comes from "posting more." The reality is that growth comes from fixing what doesn't work. You might share an exciting update that gets great engagement, but when people join, they get stuck. Onboarding friction, unlabeled issues, and unresponsive reviews kill momentum. You don't fix this by posting more; you fix it by rolling up your sleeves, identifying the bottleneck, and rallying triagers to patch the gaps. This is the unglamorous work that makes communities sustainable.

The Fuel: Passion and Curiosity

Creativity doesn't exist in a vacuum. As I’ve explored before, passion and curiosity are the fuel for everything we build. Without genuine curiosity about how people use the project, creativity blocks. You cannot innovate a community strategy if you are exhausted from just "keeping the lights on." Passion gets us through the firefighting mornings. Curiosity allows us to build a house that doesn't catch fire in the first place. When we stop being curious about the human stories behind GitHub IDs, we stop being able to create structures that help them thrive.

Why We Stay

So, why do we choose to stay? Because when it works, when people collaborate and support each other, the community becomes the project's heart and soul. You witness strangers transform into teammates, ideas evolve into features, and contributors grow into leaders. You see people find a sense of belonging, sometimes for the first time. A meaningful community is not created by chance; it emerges through the messy, human, and imperfect work that happens behind the scenes. It is built by people who genuinely care.