HR's Role: Infrastructure Builder, Not Program Manager
Article 13 of 15 in the ERG Infrastructure Series | Breaking the Initiative Addiction Cycle
The VP of People & Culture sat in yet another stakeholder meeting explaining that engagement scores had improved. He was trying to convince the ERG leads that this was a positive result, despite the survey being mandatory and the cautionary message employees had to acknowledge on the front page stating that the results were not confidential. HR had launched multiple new initiatives in the past 18 months, alongside ERG programming:
Mentorship matching platform. A secondary level of leadership that sat between executives and middle managers. Quarterly executive roundtables. Unconscious bias refresher training. Diversity dashboard. ERG leadership development series. Heritage month toolkit. Cross-ERG collaboration events. Allyship certification program. Inclusive language guide. Flexible work policy update. ERG budget increase. Recognition awards program. Employee Benefit restructuring program.
Thousands of work hours. Significant budget. Minimal impact.
ERG leaders were more burned out than before. HR as a function was exhausted. Employees questioned whether survey participation mattered. Leadership was asking uncomfortable questions about ROI. And the VP was exhausted from constantly creating, launching, managing, and defending programs that didn’t seem to stick.
“I don’t understand,” he said. “We’re doing everything we should be doing. Why isn’t it working?”
Because he was solving the wrong problem.
The problem wasn’t that HR wasn’t doing enough. The problem was that HR was stuck in program mode when what organizations need is infrastructure.
The Program Addiction Cycle
Here’s the pattern I see in organizations globally:
Stage 1: Problem Surfaces
HR, ERG leaders, employees, or engagement data reveal a challenge: mentorship gaps, meeting dynamics, promotion barriers, recognition issues, burnout patterns.
Stage 2: HR Creates Program
HR responds by creating an initiative designed to address the problem: mentorship platform, meeting training, sponsorship program, employee appreciation week, wellness app.
Stage 3: Program Requires Management
The new program needs ongoing coordination: platform administration, training logistics, participation tracking, budget management, communication campaigns, evaluation surveys.
Stage 4: Results Don’t Stick
Initial participation happens. Then engagement drops. The underlying problem persists. New data reveals the issue hasn’t actually been solved; it’s just been temporarily addressed.
Stage 5: Repeat
Another problem surfaces (or the same problem in new form). HR creates another program. The cycle continues.
This isn’t because HR teams aren’t capable or committed. It’s because programs treat symptoms while infrastructure addresses root causes.
Why Programs Fail While Infrastructure Succeeds
Let’s be specific about the difference:
Programs Are Temporary; Infrastructure Is Permanent
Program thinking: “We’ll launch a mentorship initiative to address career development gaps.”
Infrastructure thinking: “We’ll build systematic career development into our talent architecture with 360 dashboards and clear advancement pathways are predictable, accessible, and equitable; making mentorship one component of a comprehensive system, not simply a one-off initiative that makes people feel like something is happening.”
What happens with programs: The mentorship initiative runs for 12 months. Some participants find value. Coordination requires ongoing HR management. When HR capacity gets tight, the program gets deprioritized. Six months later, employees are still citing gaps in career development.
What happens with infrastructure: Career development becomes built into performance management cycles, succession planning processes, and manager expectations. It doesn’t require HR to coordinate every interaction; it works because the system is designed to make it work.
Programs Add Work; Infrastructure Reduces It
Program thinking: “ERG leaders need support, so we’ll create an ERG leadership training series.”
Infrastructure thinking: “ERG leaders need the Universal Facilitator Guide and documented best practices so they can facilitate effectively without HR creating training for every new cohort.”
What happens with programs: HR designs curriculum, coordinates sessions, tracks attendance, evaluates effectiveness. When new ERG leaders emerge, HR creates the next training cohort. The work never ends.
What happens with infrastructure: HR builds the guide once. New ERG leaders use it. Experienced leaders refine it. HR’s role becomes maintaining infrastructure, not delivering training repeatedly.
Programs Depend on HR; Infrastructure Distributes Capacity
Program thinking: “We need better cross-ERG collaboration, so HR will organize quarterly all-ERG events.”
Infrastructure thinking: “We need systematic ways for ERG leaders to share learning, so we’ll create a documented knowledge-sharing protocol and regular touchpoint structure that ERG leaders run themselves.”
What happens with programs: HR becomes the bottleneck. Events happen when HR has capacity. ERG leaders wait for HR to coordinate. If the HR lead leaves, cross-ERG collaboration dissolves.
What happens with infrastructure: ERG leaders connect directly using established protocols. Knowledge sharing happens continuously, not quarterly. Infrastructure survives HR transitions.
The Role Transformation: What HR Should Stop Doing
Breaking the program addiction requires HR to consciously stop certain behaviours:
Stop: Creating programs in response to every problem
When ERGs surface challenges, HR’s first instinct shouldn’t be “What program should we create?” It should be “What systemic barrier needs to be addressed, and what infrastructure would prevent this problem from recurring?”
Stop: Doing ERG work for ERG leaders
When ERG leaders ask for help with facilitation, event planning, or member engagement, HR shouldn’t take over these functions. HR should build the infrastructure (guides, templates, frameworks) that enables ERG leaders to do this work sustainably.
Stop: Measuring success by program launch volume
HR’s value shouldn’t be measured by how many initiatives they create. It should be measured by whether the infrastructure they build generates intelligence that drives measurable organizational improvement.
Stop: Positioning ERG support as an HR service
ERGs aren’t internal customers receiving HR services. ERGs are strategic partners generating intelligence. HR’s role is infrastructure builder, not service provider.
Stop: Requiring HR approval for ERG initiatives
When infrastructure exists (facilitation guides, theme capture protocols, budget frameworks), ERG leaders shouldn’t need HR permission to move forward. They should operate within infrastructure that’s already built.
The Role Transformation: What HR Should Start Doing
Infrastructure building requires new behaviours:
Start: Designing systems that work without HR intervention
When ERG leaders ask “How should we facilitate our sessions?” HR doesn’t create a training program. HR provides the Universal Facilitator Guide and says “This framework has been proven across ten ERGs; use it, adapt the examples to your identity context, and share what you learn.”
Start: Building capacity across ERG leaders rather than doing work for them
When ERGs need theme capture support, HR doesn’t capture themes for them. HR builds the template, trains facilitators once, and creates documentation so knowledge transfers when leadership rotates.
Start: Creating comparable data systems
HR’s role is ensuring all ERGs use frameworks that generate comparable intelligence (Article 12). This means standardizing how belonging indicators are measured, how themes are captured, and how intelligence is translated; while allowing identity-specific content.
Start: Connecting ERG intelligence to talent strategy
HR stops treating ERG insights as “nice to have” feedback and starts integrating them into succession planning, performance management, compensation reviews, and organizational design decisions.
Start: Holding leadership accountable for using ERG intelligence
HR builds the accountability structures (Article 9) that ensure executive sponsors and senior leaders don’t just acknowledge ERG intelligence; they act on it and report back on outcomes.
The Behavioural Shifts in Practice
Here’s what these role shifts look like in real scenarios:
Scenario 1: ERG Leader Asks for Event Support
Program Manager Response:
“Sure, I’ll help you plan this. Send me your ideas and I’ll create the project timeline, coordinate with Facilities and Comms, and manage the budget tracking.”
Infrastructure Builder Response:
“Great initiative. Here’s the event planning template we use across all ERGs; it includes timeline frameworks, stakeholder coordination protocols, and budget management tools. Walk through it and let me know if you hit barriers I can help remove. Also, connect with [other ERG leader] who ran a similar event last quarter; they can share what worked.”
What changed: HR provides tools and connections, not project management. ERG leader builds capacity. Infrastructure enables replication.
Scenario 2: ERG Reports Promotion Barriers
Program Manager Response:
“This is concerning. Let me create a sponsorship program specifically for this ERG to help members advance.”
Infrastructure Builder Response:
“This intelligence suggests systemic issues in our promotion process. Let me work with Talent Management to analyze promotion velocity data across all populations. If this pattern appears across multiple ERGs (which Article 12’s comparable data will show), we need to address the promotion criteria and review calibration, not create ERG-specific programs that work around a broken system.”
What changed: HR treats ERG intelligence as signal of systemic problems requiring structural solutions, not individual programs.
Scenario 3: Multiple ERG Leaders Report Burnout
Program Manager Response:
“We need to show our appreciation. Let’s create an ERG Leader Recognition Program with quarterly awards and an annual appreciation event.”
Infrastructure Builder Response:
“Burnout signals infrastructure failure. Let me audit the cognitive load we’re placing on ERG leaders. We need distributed leadership roles (Article 7), protected time built into performance expectations, and systems that make their work sustainable, not recognition that thanks them for overwork we’re asking them to endure.”
What changed: HR addresses root causes (lack of infrastructure) rather than symptoms (need for appreciation).
The Capacity Reallocation
When HR shifts from program manager to infrastructure builder, capacity reallocates:
Less time spent:
Coordinating individual ERG events and initiatives
Creating one-off training sessions for each ERG leadership cohort
Managing mentorship platforms, tracking participation, and generating reports
Responding to individual ERG requests as they come in
Defending program ROI to leadership without systematic data
More time spent:
Designing replicable frameworks that work across all ERGs
Building theme capture and translation infrastructure
Analyzing comparable intelligence to identify systemic patterns
Partnering with executive sponsors on accountability and barrier removal
Connecting ERG intelligence to talent strategy and organizational design
The shift doesn’t reduce HR’s importance; it increases HR’s strategic impact.
Why This Transformation Is Hard
HR teams often resist this role shift for understandable reasons:
“Building infrastructure feels slower than launching programs”
It is slower initially. But programs require perpetual management. Infrastructure works independently once built. The time investment compounds differently.
“ERG leaders expect HR to do this work”
Because organizations trained them to expect it. When HR consistently provides infrastructure instead of doing work for ERGs, expectations adjust. ERG leaders develop capacity.
“Leadership wants to see visible initiatives”
Because leadership hasn’t been shown what infrastructure creates. When HR demonstrates how infrastructure generates comparable intelligence that drives strategic decisions, leadership’s definition of “visible impact” evolves.
“We don’t have capacity to build infrastructure while maintaining current programs”
True. Which is why the transition is incremental: Build one piece of infrastructure. Sunset one program. Repeat. Over 12 months, the capacity equation shifts.
The Question HR Should Ask
Not “What program should we create next?” but “What infrastructure would prevent us from needing another program?”
Not “How do we support ERG leaders?” but “What infrastructure enables ERG leaders to be effective without depending on HR?”
Not “Why aren’t our initiatives working?” but “Are we treating symptoms with programs when we should be addressing root causes with infrastructure?”
The organizations with the most effective ERGs aren’t the ones with the most ERG programs.
They’re the ones where HR built infrastructure that makes ERG work replicable, sustainable, and strategic; without requiring HR to manage every initiative.
About the Belonging First Methodology™
The infrastructure referenced throughout this article. Universal Facilitator Guides, theme capture templates, translation protocols, accountability frameworks; represents the systematic design that enables HR to shift from program manager to infrastructure builder. Organizations that license these materials stop layering on initiatives and start building systems that work.
Ready to transform HR’s role from program manager to infrastructure builder?
Contact: info@belongingfirst.com for organizational licensing information.
Tomorrow in this series: We reveal the complete replicable model. Article 14 walks you through the 10-session framework that works across all ERGs, creating systematic intelligence while honoring identity-specific experiences.
©Copyright 2025 Andrea Carter | Belonging First | Andrea Carter Consulting. All Rights Reserved.
No portion of this article may be reproduced without written permission.