ERGs That Actually Matter: Structure, Support and Space

Every failed employee resource group fails on the same curve. A launch announcement with genuine enthusiasm. A first meeting with thirty people. A second meeting with twelve. Six months later, two exhausted volunteers are planning events on their lunch breaks for a group the company mentions in recruiting materials but has never funded, and the Slack channel's last message is a month old.

The curve is not caused by lack of interest. It is caused by treating an ERG as a vibe instead of an organization. Organizations need charters, leaders with defined terms, sponsors with actual power, money, a home, and a way to know whether they are working. This guide covers each of those, with numbers and scripts, for companies from 50 people to 5,000.

What an ERG is — and the three things it gets confused with

An employee resource group is a voluntary, employee-led group organized around a shared identity or experience — women in engineering, Black employees, LGBTQ+ staff, veterans, working parents, employees with disabilities, first-generation professionals — with a mission that serves both its members and the company. The standard mission has three legs: community (belonging and mutual support), development (mentorship, visibility, career growth for members), and counsel (a perspective the company can consult — voluntarily and within limits we will get to).

Three common confusions, worth settling before you write anything down:

• An ERG is not a social club. Clubs (climbing, board games, film) are wonderful and deserve space too, but they need no sponsor, no budget line beyond pizza, and no impact reporting. Mixing the two categories in policy means either underfunding ERGs or over-bureaucratizing the chess club.
• An ERG is not a committee. Committees are appointed by the company to do the company's work. ERGs are led by members, set their own agenda, and can decline requests. A "DEI committee" staffed by assignment is a different, also-legitimate structure; do not label it an ERG.
• An ERG is not the diversity strategy. This confusion is the most damaging. ERGs can inform strategy; they cannot substitute for one. When leadership's answer to every inclusion question is "we have ERGs," members correctly conclude they are being used as cover, and the best ones leave first — the group, then sometimes the company.

One more definitional point: ERGs work in remote and hybrid companies at least as well as in offices, arguably better, because they replace the hallway serendipity that distributed underrepresented employees lose first. A remote employee who is the only woman on her team might be one of forty in the company-wide ERG. Making that group real is part of the broader project described in Building Real Culture on a Remote Team.

Standing one up: the minimum viable ERG

Do not start with a policy document. Start with a demand test and a charter.

Step 1: Test demand honestly

An ERG needs a critical mass of people willing to do things, not just join things. A practical threshold: at least 8–10 committed members and at least 2 people willing to co-lead. In a 60-person company that may mean your first "ERG" is a working-parents group of nine; that is fine. What kills groups is launching on a membership list of forty where thirty-eight joined a channel and muted it. Run a short interest form: "Would you attend monthly? Would you help organize? Would you co-lead?" Count only the second and third columns.

Step 2: Write a one-page charter

The charter is the difference between a group and a chat channel. One page, five sections:

1. Mission — two sentences, naming the community served and the three legs (community, development, counsel) with the group's own emphasis.
2. Membership — who it is for, and the allyship policy (more below).
3. Leadership — roles, how they are chosen, term lengths.
4. What we do — the recurring commitments: e.g., monthly gathering, quarterly event open to the company, an annual feedback session with leadership. Keep it to three.
5. What we do not do — the boundary section everyone skips and later regrets skipping. Example lines: "We advise on policy when asked and when we choose to; we do not approve or own company policy." "We are not a crisis-response resource; here is who is."

The charter is written by the founding members, not by HR. HR reviews for legal landmines; members own the content. This ordering is not a nicety — it is the difference between employee-led and company-branded.

Step 3: Decide the allyship question before launch, not during a controversy

Every ERG faces it: can people outside the identity join? There are three workable answers. Open membership (anyone joins, allies welcome at everything), open with member-only spaces (allies attend public programming; certain meetings and the private discussion space are members-only), and closed (membership limited to the community, with occasional public events). The middle option is the most common steady state and the one to default to: it preserves a space where, say, LGBTQ+ employees can talk candidly without performing for an audience, while giving allies a genuine way to show up. Whatever you choose, write it in the charter with the reasoning, so the answer exists before someone's feelings are attached to the question.

Step 4: Launch with a specific first ask

Announce the group with one concrete, dated, low-commitment event — "First gathering: Thursday the 14th, 45 minutes, agenda: introductions and choosing our first quarter's focus" — rather than an abstract invitation to join a movement. Groups that launch with an event get attendance; groups that launch with a manifesto get channel members.

Leadership: paid work, defined terms

ERG leadership is real work — event planning, facilitation, vendor wrangling, emotional labor, and being the person leadership calls after every relevant news event. Companies that pretend otherwise burn out exactly the people they claim to be supporting. Four structural rules:

Co-leads, always. Never one chair. Two or three co-leads share load, cover vacations, and prevent the group from collapsing when one person changes jobs. For groups over ~50 members, add role owners: an events lead, a comms lead, a membership lead.

Terms with endpoints. One year, renewable once, is a good default. Terms make leadership an achievement to rotate through rather than a life sentence, and they force succession planning. Put "shadow a co-lead for a quarter" on the pathway so the next leaders exist before they are needed.

Compensate the work. The strongest practice, increasingly common at larger companies: an annual stipend for ERG chairs (real programs land anywhere from several hundred to a few thousand dollars per year) or a formal workload allocation — 5–10% of work time, stated in writing and acknowledged by the chair's manager. If your company cannot fund stipends yet, the written time allocation plus performance-review recognition is the floor. What is not acceptable is the common default: unpaid, invisible labor that competes with the day job at review time. The check on whether you are doing this right: do ERG leads get promoted at the same rate as their peers? If leading an ERG is a career tax, your best people will rationally decline it.

Manager air cover. Send every chair's manager a two-line note from the sponsor: "Sam is co-leading the Veterans ERG this year; that is roughly four hours a week of company-valued work. Please plan capacity accordingly." That note costs nothing and prevents the most common quiet conflict.

Executive sponsorship: what sponsors are actually for

An executive sponsor is a senior leader — ideally within two reporting levels of the CEO — attached to one ERG. Done right, this is the highest-value cheap intervention in the whole model. Done wrong, it is a name on a slide.

What a real sponsor does, concretely:

• Moves money and unblocks. When the budget request stalls in finance or the event needs a room policy exception, the sponsor makes one phone call. This is 80% of the job: converting the group's requests into things the org actually does.
• Shows up. Attends the group's flagship events — present and participating, not dropping in for opening remarks. Attends one leadership sync with the chairs per quarter.
• Carries the group's perspective into rooms members cannot enter. When the exec team debates the return-to-office policy, the working-parents ERG sponsor is the person who says "here is what this does to school pickup, and here is what the group proposed instead."
• Spends reputation. Publicly credits the group's work, defends its budget in planning season, and lends weight when its counsel is unpopular.

What a sponsor does not do: run the group, set its agenda, or filter its message. The chairs lead; the sponsor amplifies and unblocks.

Choosing sponsors: shared identity with the group is a plus but not a requirement — commitment and organizational power matter more, and a majority-group sponsor for a minority-group ERG can be a feature when it widens the coalition. What is a requirement is willingness, stated in a real conversation. A workable ask script for the chairs or the program owner: "We are asking you to sponsor the group for one year. The time cost is roughly two hours a month: one sync with the chairs, our quarterly event, and being our escalation path. The real cost is that we will sometimes ask you to argue for things in rooms we are not in. Are you in?" A leader who hesitates at that framing is the wrong sponsor, and it is far better to learn that now.

Budgets: real numbers, simple rules

An ERG without a budget is a hobby the company takes credit for. The good news: meaningful budgets are small.

Benchmark: common practice ranges from roughly $50 to $150 per ERG member per year at mid-size companies, with a per-group floor so small groups can function — e.g., each recognized ERG gets a $2,000–$5,000 annual base plus a per-member amount. A 200-person company with three ERGs might spend $15,000–$25,000 a year total: visible in no P&L, transformative for the groups.

What budgets buy, in rough priority order: programming (speakers, workshops, event food), chair stipends if you fund them centrally, learning (conference tickets for members — a high-signal spend), community moments (heritage-month events, celebration budgets), and a small discretionary line for the unplanned.

Rules that keep it healthy: the group proposes an annual plan with costs; the sponsor approves it once; spending under a threshold (say $500) needs no further sign-off. Nothing kills volunteer energy like three approval layers for a $120 lunch. Track spending transparently inside the group. And never make ERG budgets the first cut in a downturn while recruiting pages still feature the groups — members notice, and the story travels.

The digital home: where the group actually lives

For a distributed company this is not an afterthought; it is the group. An ERG whose entire existence is a monthly video call plus a dormant channel has no persistent presence — no memory, no front door for new members, no place where the community is visible between events.

A functional ERG home needs five things:

1. A front door. A findable page or space stating the mission, the charter, how to join, and who leads. New-hire onboarding should link every ERG's front door in week one.
2. A discussion space with the right privacy. This is where the open/closed decision becomes software. Member-only conversation spaces must be genuinely member-controlled — visible enough to be joinable, private enough for candor.
3. An events surface. Upcoming gatherings with RSVP, past events with recordings and notes. RSVP data is also your attendance metric, captured for free.
4. A resource shelf. The mentorship signup, the book list, the notes from last quarter's leadership session, the charter itself.
5. A way to be seen by the wider company. Public-facing posts — event invitations, heritage-month spotlights, wins — that flow into the company-wide feed rather than staying inside the group.

You can assemble this from four disconnected tools, or use a platform where it is one construct. In Openbook, this maps directly onto rooms: a Group room gives each ERG a member-run community with open or closed privacy, its own feed, and a roster people can join or leave themselves; add an Event room for RSVPs and a Docs or Wiki room for the resource shelf, all inside a space the chairs administer without filing IT tickets. The general shape — communities living alongside knowledge and tools in one intranet — is the pattern we cover in The Modern Intranet: What It Should Actually Do; see how the pieces fit at /product.

Whatever the tooling, assign a comms owner among the co-leads. Digital homes decay by default; someone has to post the recap, pin the next event, and welcome the new joiners by name.

Programming: a cadence that people actually attend

The programming trap is overreach: a launch-quarter calendar with six event types, followed by exhaustion. Sustainable programming for a typical ERG is exactly three commitments:

• Monthly member gathering (45–60 min). Rotating format: open discussion one month, a member's story the next, a themed topic the third. For distributed groups, alternate meeting times so no time zone always pays the cost.
• Quarterly flagship open to the whole company. A speaker, a panel, a workshop, a heritage-month event. This is the group's public face and the sponsor's must-attend.
• One development offering per year. A mentorship match cycle, a resume workshop, a sponsorship program pairing members with senior leaders. Development programming is what separates ERGs that advance careers from ERGs that host lunches — and it is what members cite years later.

Add async programming between events: a monthly discussion prompt in the group's feed, a running thread for wins, a book or article club. For remote-heavy companies, async is not the consolation prize; it is where most participation actually happens, since a working parent who cannot make the 4 p.m. call can still be a daily presence in the space.

Measuring impact without turning members into metrics

ERG measurement has a real tension: leadership funds what it can measure, but members did not join to be a dashboard. The resolution is to measure the program, not the people, and to report trends, not surveillance.

A four-part scorecard, reported by chairs to sponsor twice a year:

Dimension	Metrics	Healthy signal
Reach	Membership, growth, % of company; event attendance	Steady growth; flagship events draw beyond the membership
Activity	Events held vs planned; async engagement in the group's space	The three commitments actually happened
Member value	3-question annual member pulse: belonging, "worth my time," development value	Improving or high-stable; honest free text
Organizational influence	Counsel instances (policies consulted on, with outcomes); recruiting/onboarding contributions	Concrete list, even if short: "advised on parental-leave revision; two items adopted"

What to refuse: correlating individual ERG membership with retention or performance data at any granularity that could identify people, and any framing where the ERG's value must be justified in attrition dollars to survive. Directionally, engagement research does associate belonging with retention, and it is fine to cite that generally; it is not fine to run the study on your own twelve members. Aggregate, anonymized, opt-in — or not at all. The wider measurement toolkit, including how belonging fits among engagement drivers, is in Employee Engagement: What Moves the Needle.

One more reporting habit with outsized value: the annual one-page "year in review" post from each ERG to the whole company — what we did, what changed because of us, what is next. It is recognition for the volunteers, proof-of-life for the program, and recruiting material all at once.

Failure modes and their fixes

• The unpaid consultancy. Every product team wants "the ERG's take" on their launch; every crisis generates a request for a statement. Fix: the charter's "what we do not do" section, plus a simple intake rule — requests for counsel go to the chairs, who may decline, and substantial engagements (accessibility review, market feedback) are scoped and recognized like the real work they are, or politely refused.
• Diversity outsourcing. Leadership treats ERG existence as the inclusion strategy. Fix: the sponsor's quarterly sync includes one standing question — "what is the company doing that the ERG should not have to?" — and the answer goes in the sponsor's goals, not the group's.
• The launch cliff. Five groups launch in one enthusiastic quarter; two survive. Fix: stagger launches, require the demand test, and let groups die honorably — a wind-down post and an archived space beat a zombie channel.
• Chair burnout. Covered above, but the leading indicator is worth naming: when the same two names appear on every event for a year, intervene before they resign — from the group or the company.
• The compliance ERG. A group founded by HR to exist, with appointed leads and no member energy. Fix: do not. Fund demand where it exists; seed interest where it does not by hosting one open event and seeing who stays.

Standing up your first ERG: a 60-day plan

Days 1–14: run the demand test; identify two co-leads; draft the one-page charter with founding members. Days 15–30: recruit the executive sponsor with the explicit ask script; agree the year-one budget (base + per-member); set the chairs' time allocation in writing with their managers. Days 31–45: build the digital home — front door, discussion space with the chosen privacy model, events surface — and write the launch post. Days 46–60: hold the first gathering with a real agenda; publish the recap where the whole company can see it; put the quarterly flagship on the calendar. Then protect the three programming commitments for a full year before adding anything.

If the digital-home step is where you usually stall — IT tickets, another SaaS contract, a channel that is not really a home — Openbook gives each ERG a Group room with its own feed, privacy, and roster inside the workspace your company already uses, free to start. Set one up at openbook.work and give your first group a front door this week.