The 3Ps ofERG Success
Methodology · From The ERG Movement · ~ 12 min read
Most ERG programs aren't failing. They're floating.
They have ERGs. They have leaders. They have budget. What they don't have is an operating model — which is why the same three problems show up in every program that's stuck.
Missing Purpose.
The ERG program exists, but no one can explain why it exists. There's no defensible answer to "what's the business impact?" — and no shared link between what the ERGs do and what the company is trying to accomplish. Different ERGs tell different stories. Leadership starts questioning whether to keep funding it.
Missing Process.
There's no operating system underneath the program — no governance, no documented roles, no handbook, no decision-making structure. The program manager carries everything. ERG leaders guess at what's expected. Every new ERG starts from scratch and every leadership transition resets the work.
Missing Programming.
Heritage month panel. Movie night. Repeat. Activities are reactive instead of designed — no strategic mix of educational, cultural, and social events, no through-line back to Purpose. Engagement drops. The same five members show up. The program looks busy but can't prove impact.
None of these are people problems. They're structural problems. When an ERG program doesn't have an operating model, it defaults to motion — and motion isn't the same as progress.
Three Ps. One operating model.
Adapted from "People, Process, Product" — the business framework that's been running successful companies for decades — and rebuilt for what ERG program managers actually do. Each P answers one question. Together, they answer the only one that matters: does this program work?
Purpose
The reason the ERG program exists. The thread that connects every ERG, every event, and every decision back to the business — and gives executives a clear answer when they ask why this matters.
Process
The operating system that makes the program run. Governance, roles, handbooks, decision rights, data systems, and the infrastructure that lets ERGs operate consistently — without depending on any single person.
Programming
The activities and experiences the program delivers — live and asynchronous. The visible output of the operating model, and the only part of the program members actually see.
The 3Ps operates at the program level.
This is where most people get it wrong. The 3Ps isn't a framework for one ERG — it's the operating model for the entire program. Individual ERGs are local expressions of that model.
This is what the 3Ps applies to. The program is the business: it has a Purpose tied to company strategy, a Process for how ERGs are governed and supported, and Programming standards every ERG plugs into. The program manager runs this. Executive sponsors back this.
Each ERG inherits the same operating model. Same Purpose framework. Same Process infrastructure. Same Programming infrastructure. What changes is the flavor — the topics, the lens, the community being served. The structure stays identical.
The First P: Purpose
Purpose is the link between the ERG program and the business. It's the answer to "why does this program exist?" — but not the inspirational sentence on a kickoff slide. It's the operating answer that guides what the program invests in, what individual ERGs are allowed to focus on, and how the program defends itself when executives ask hard questions.
The most useful framing: an ERG program is an employee engagement initiative. Programs that frame themselves this way have a defensible business story, a clear set of metrics, and positioning that holds up across political climates. Programs that don't end up trying to be everything — and getting cut for being nothing in particular.
A clear Purpose isn't written once. It's an ongoing alignment between the program manager, executive sponsors, and the ERGs themselves.
What it looks like when it's there
- The program has one core metric that anchors its success story to leadership
- Every ERG can tie its work back to the same overarching Purpose
- Executive sponsors can articulate why the program matters in the same language the program uses
- The program can confidently say "no" to requests that fall outside scope — without it being political
- "What's the business impact of our ERGs?" has a clear, repeatable answer
The program becomes a collection of disconnected ERGs. Executives don't see the through-line. The program manager spends every quarter justifying budget instead of building the work.
The program has a North Star. Every ERG plugs into the same story. The business impact answer is rehearsed and ready. Funding conversations get shorter — and easier.
The questions every program manager has to answer
- What unique value does this program offer to employees?
- What unique value does this program offer to the business?
- How does this program support the company's broader mission?
- What's the one core metric the program is measured on?
- What's in scope for this program — and what's deliberately out?
The Second P: Process
Process is the operating system of the ERG program. It's the governance, the documented handbook, the roles and decision rights, the data infrastructure, and the automation that makes the program work consistently across every ERG and every leadership cycle.
Here's the part most program managers don't want to hear: ERGs are not employee-led. They're company-led — whether you call them that or not. The moment a program has budget, executive sponsors, and a program manager owning it, it stopped being employee-led. Treating ERG leaders like volunteers who should "figure it out themselves" isn't empowerment. It's abandonment dressed up as autonomy.
Strong Process means the program manager actually leads — sets standards, documents how things run, and gives ERG leaders a playbook clear enough that they can show up and execute.
What strong Process looks like
- Governance — documented rules for how the program is run and who has authority over what
- Handbooks & playbooks — clear documentation ERG leaders can reference instead of guessing
- Role definitions — specific responsibilities for leads, members, sponsors, and the program manager
- Decision rights — who decides what, what requires consensus, what escalates
- Data & reporting infrastructure — so engagement and impact can actually be measured
- Automation & tools — the operational layer that removes friction from leaders' day-to-day
The program manager is the bottleneck. ERG leaders are guessing. Every new ERG reinvents the wheel. Leadership turnover means the program restarts. Burnout is built into the operating model.
The program runs as a system, not on a person. ERG leaders inherit a playbook. New ERGs launch on rails. Data is available before anyone has to ask. The program scales because the infrastructure does.
The thing to remember: Process should be tight enough to be useful and loose enough to evolve. Programs grow. ERGs change. The operating system should grow with them — not collapse under it, and not strangle them with it.
The Third P: Programming
Programming is the activities, events, and experiences the program delivers — both live (events, workshops, panels) and asynchronous (communications, member projects, community moments inside Slack or Teams). It's the visible output of the operating model.
And it's where the program is judged. Members don't see Purpose statements. They don't see governance documents. They see the event last Tuesday. They see what hit their inbox this morning. Programming is where credibility is built — or quietly drained.
At the program level, Programming isn't about planning one event. It's about setting the standard for what good programming looks like across every ERG.
What strong Programming actually requires
- A balance of live and asynchronous — the community isn't built at the event, it's built in the channel
- Forced variety — across topics, formats, and the kinds of moments being offered
- Member-led design — built from what members ask for, not from what's easiest to schedule
- Defined success — every initiative has a stated outcome before it runs, and a debrief after
- A community facilitation skill set — leaders trained to facilitate, not assumed to be naturally good at it
Same five members at every event. Heritage month panel every year. Async channels used only for event promotion. Engagement metrics flat or dropping. No defensible story for what the program actually moves.
Variety across the year. Live and async working together. New faces showing up. Members spotlighting members. Engagement compounding instead of decaying.
The three questions for every program decision
- Does it serve the Purpose? If not, kill it — no matter how popular it sounds.
- Did members ask for it? Or is it being designed at them?
- How will we know if it worked? Define success before the calendar invite goes out.
One P is not enough.
This is the part most frameworks get wrong. The 3Ps aren't three buckets to fill in any order. They're a sequence. They depend on each other. Skip one and the entire program wobbles — predictably, and in exactly the same way every time.
You build fast.
Process and Programming work — for a minute. Then leadership turns over, priorities shift, and there's no anchor. The program drifts. Funding gets questioned.
You build on one person.
Purpose is clear and events are great — until the program manager (or a key ERG lead) burns out, leaves, or moves roles. The whole thing collapses with them.
You build a plan.
Beautiful Purpose. Tight Process. Empty rooms. The program exists on paper but not in the company's culture. Members can't feel it.
The 3Ps are sequential and inseparable. Purpose comes first. Process comes second. Programming comes last. Every functioning ERG program runs this loop — whether they've named it or not.
What changes when a program runs on the 3Ps.
Same team. Same company. Same budget. Different operating model. Here's what the difference looks like in practice.
The floating program.
- "What's the business impact of our ERGs?" gets different answers from different people
- The program manager is the bottleneck — every ERG depends on them
- ERGs operate inconsistently, with no shared standard
- Programming gets planned month-to-month, not year-to-year
- Leadership transitions mean starting over
- Success is measured in attendance counts — nothing deeper
- Burnout is treated as an individual problem, not a structural one
The anchored program.
- Every executive, sponsor, and ERG lead tells the same story about why the program exists
- The program runs as an operating system — not on any one person's calendar
- Every ERG inherits the same infrastructure — and customizes the flavor
- Programming is planned against an annual roadmap with named outcomes
- Leadership transitions follow a playbook, not panic
- Success is measured in engagement, belonging, and business impact — defensible to anyone
- Burnout drops because the system, not the person, is doing the work
Score your program on the 3Ps.
35 red flags pulled from 90 Days to Transformation. For each statement, rate how true it is of your program — from completely true to completely false. You'll get a health score for Purpose, Process, and Programming — plus the next step that fits where the program actually is.
- 1. ERG leaders aren't sure what their role entails.
- 2. No one can explain the program's overall purpose in one sentence.
- 3. Leaders are frequently burned out from unclear expectations.
- 4. There's constant turnover in ERG leadership roles.
- 5. Leadership roles are inconsistent across different ERGs.
- 6. Governance documents are scattered, outdated, or nonexistent.
Three ways to put the 3Ps to work.
Reading the framework is one thing. Building a program on it is another. Here are the three doors into the work — pick the one that fits where the program is right now.
Workshops & Keynotes
Bring The ERG Movement to the team. Live workshops walk program managers, ERG leaders, and executive sponsors through the 3Ps in one session — with frameworks, examples, and time to map it directly to the program.
Explore Speaking & Workshops →The Fresh Start Program
A guided rebuild for ERG programs that need real infrastructure. The Fresh Start program applies the 3Ps directly — Purpose alignment, Process build-out, and Programming roadmap — in 45 or 90 days.
See the Fresh Start Program →ERG Champs Community
Join the community of program managers and ERG leaders applying the 3Ps in real time. Discussions, resources, tour invites, and the people who've already built what's being built — all inside ERGs.io.
Meet the Champs →The 3Ps, answered.
Everything people ask about the framework, in one place.
From the blog
The 3Ps in practice.
The short read on why Purpose, Process, and Programming are the keys.
How the 3Ps replace the tired 4Cs pillar model most programs default to.
Why the 3Ps make a Commerce pillar unnecessary — and what to do instead.
ERGs.io is where the Programming P lives day-to-day — calendars, ideas, vendors, and co-lead collaboration.
Now you know the model.
The 3Ps is the operating system. Speaking, Fresh Start, and Champs are the three doors into it. Pick the one that fits where the program is — and start building the ERG program that's actually built to last.