How to Make ERGs an Easy "Yes" for Middle Managers

Middle managers get blamed for a lot in ERG work.

They are the ones employees say "won't let people attend." They are the ones ERG leaders say "don't support the program." They are the ones HR and DEI teams side-eye when engagement is low, attendance is inconsistent, or employees quietly admit they feel weird stepping away from work for ERG activities.

And sometimes, the frustration is valid.

Some managers are dismissive. Some managers do not understand the value of ERGs. Some managers make comments that cause employees to feel guilty for participating. Some managers treat ERG engagement like a distraction from "real work," even though the company is sponsoring the ERG in the first place.

But if we make the middle manager the entire problem, we miss the bigger issue.

A lot of companies have (or should have) positioned ERGs as an employee benefit without doing the operational work to define how employees are supposed to access that benefit.

That is where the middle starts to freeze.

The company says ERGs matter. The company promotes ERG events. The company includes ERGs in onboarding, culture decks, employer branding, engagement surveys, heritage month calendars, and belonging strategies. The company asks ERG leaders to build community, drive connection, support employee engagement, and create spaces where people feel seen.

But then no one answers the practical questions.

Can employees attend ERG programs during work hours? How often? Does that apply to hourly employees? What about call center employees? What about frontline teams? What about billable employees? What about people whose work is measured in coverage, queue time, utilization, shifts, tickets, client hours, or customer response times? How should that time be logged? Who pays for it? What happens when ERG participation conflicts with a deadline or business need? What is the manager supposed to do?

If those questions are not answered, the ERG benefit exists in theory, but not in the workflow. And when the workflow is unclear, the manager becomes the policy.

That is the real issue.

The problem is not always manager support.

Most companies talk about ERGs as if they are part of the employee experience, but operationally, many ERG programs are treated like informal perks.

That distinction matters.

A true employee benefit needs an access model. People need to know what the benefit is, who can use it, how they can use it, when they can use it, what limitations exist, and what process they should follow.

Without that clarity, participation becomes personal.

One employee gets to attend because their manager is supportive. Another employee skips the same event because their manager makes participation feel like a burden. One ERG leader gets protected time to plan. Another is expected to do all ERG work on top of their regular workload. One department treats ERG involvement as development. Another treats it like a distraction.

That inconsistency is not just a manager attitude problem.

It is an access problem.

ERG participation should not depend on whether an employee has the "right" manager. If the company sponsors ERGs, promotes ERGs, and benefits from ERGs, then access cannot be left up to individual manager interpretation.

That does not mean every employee can attend everything. It does not mean business needs disappear. It does not mean managers have no say in workload planning.

It means the organization has to stop being vague.

Because vague support creates inconsistent access. Inconsistent access creates employee frustration. Employee frustration creates manager tension. Manager tension creates the appearance of a "middle manager problem," when the deeper issue is that the company never defined how the benefit should actually work.

The deeper reality: managers protect what the company makes consequential.

Middle managers did not create the modern corporate operating system. They did not invent productivity pressure, lean teams, quarterly goals, utilization targets, performance ratings, staffing constraints, or the endless expectation to do more with less.

But they are often the layer responsible for enforcing those realities.

Managers are the ones who have to make the team calendar work. They are the ones who answer when a deliverable is late. They are the ones who get questioned when coverage drops. They are the ones who have to explain why productivity slipped, why the queue was backed up, why the client work stalled, or why the team missed a target.

So when managers deprioritize ERG participation, they may not be saying, "I do not value ERGs."

They may be saying, "I know what I will be held accountable for, and it is not low ERG participation."

That is the uncomfortable truth.

The organization may say ERGs matter, but managers learn what matters through consequences. Miss a deadline and someone asks about it. Miss a target and someone asks about it. Never mention the ERG calendar and, in many organizations, nobody says a word.

The system does not have to say "ERGs are not important" for managers to learn that ERGs are less important than productivity.

This is why "please support ERGs" rarely works on its own. It is too vague. It asks managers to support something without clarifying what support should cost, what it should look like, how to manage tradeoffs, and who backs them up when support creates operational tension.

The solve is not to guilt managers into caring harder. The solve is to build an ERG access model.

The ERG Access Model: 6 things companies need to define

If ERGs are an employee benefit, companies need to define how employees access that benefit across different roles, work models, and business realities.

Here is the practical operating model.

1. Put the different ways to participate somewhere easy to find.

Most companies do not need a 40-page ERG handbook to explain participation. Managers are not digging through that. Employees probably are not either.

What they need is a simple, high-level ERG intranet page that answers the basic question:

"How can I actually participate in ERGs here?"

That page should explain, in plain language:

What ERGs are. A short explanation of what ERGs are, why the company has them, and who can participate.

The different ways employees can participate. For example, employees might attend events, join an ERG community channel, watch recordings, volunteer for an activity, join a mentoring circle, or serve in an ERG leadership role.

The expected time commitment for each option. Attending one event may be one hour. Joining an ERG leadership team may require a few hours per month. Planning a major program may require more time during certain seasons.

What employees should do before participating. This could include adding the event to their calendar, giving their manager a heads-up, checking coverage needs, or following a timekeeping process if they are hourly or billable.

Where to go with questions. Employees and managers should know whether to contact the ERG Program Manager, HRBP, ERG lead, or another internal owner.

This page should not be written in heavy corporate language. It should be clear, quick, and practical.

Because the goal is not to impress people with an ERG philosophy. The goal is to remove confusion.

If employees do not know the ways they can participate, and managers do not know what those participation options require, everyone starts guessing. And once people start guessing, access becomes inconsistent.

2. Define how much time employees can reasonably use.

A lot of organizations avoid this because they do not want to sound restrictive. But vague generosity is not the same as access.

If the company says, "We support ERG participation," but does not clarify what reasonable participation looks like, the manager has to define the limit. That is where inequity creeps in.

A clear time allowance can be modest and still be powerful.

For some companies, it may be one hour per month. For others, it may be one hour per week for professional development, with ERG programming included as an eligible use. For ERG leaders, there may need to be a separate monthly allocation based on role expectations. For major heritage month events or company-sponsored ERG summits, there may be a different approval path.

The exact number matters less than the clarity. A clear one-hour-per-month policy is stronger than a vague "we support ERGs" message that employees cannot safely use.

This is especially important for hourly, frontline, call center, and billable employees. A salaried corporate employee may be able to block a calendar and keep it moving. That is not the reality for everyone.

If the company wants ERG access to be equitable, it has to define the time.

3. Define access by employee type.

This is where a lot of ERG strategies become too corporate-office centered.

ERG access does not look the same for every employee.

A salaried employee may need calendar norms and workload expectations. An hourly employee may need to know whether the time is paid and how to log it. A call center employee may need queue coverage. A retail or warehouse employee may need shift-specific participation options. A billable consultant may need a charge code or clarity on whether ERG time counts as internal development. A global employee may need recordings or async participation because the live event happens outside their working hours.

If the access model only works for salaried corporate employees, then the ERG program is not as inclusive as the company thinks it is.

Companies need to build participation pathways for the employee populations they actually have. That may include different instructions for salaried employees, hourly employees, frontline teams, billable employees, queue-based teams, global employees, and ERG leaders.

This does not need to be overly complicated, but it does need to be real.

For example, hourly employees should not have to guess whether they can attend an ERG session while clocked in. Billable employees should not have to guess where to code their time. Call center employees should not have to choose between participation and queue coverage with no guidance. ERG leaders should not have to absorb major planning responsibilities invisibly and then get judged when regular work feels stretched.

Different work models require different access paths.

4. Define how time is logged, coded, or covered.

This is the part companies love to skip because it is operationally annoying.

If an hourly employee attends an ERG event, how should they log that time? If a billable employee participates in ERG programming, where does the time go? If a call center employee steps away for an ERG session, who covers the queue? If an ERG leader spends three hours planning a major program, is that recognized anywhere, or is it invisible labor?

Without these answers, participation becomes risky.

Employees may avoid ERGs because they do not want to create payroll issues, billing confusion, utilization problems, coverage gaps, or manager tension. Managers may discourage participation because they do not know how to account for it.

Companies should define the timekeeping code, billing code, cost center, coverage expectation, or professional development category connected to ERG participation. If the answer is different by employee type, say that.

This is not glamorous work, but it is the work that determines whether ERG participation is actually accessible.

5. Define the manager's role as benefit administrator, not personal gatekeeper.

Managers should not be positioned as the people who personally decide whether ERGs are legitimate. The company already made that decision when it sponsored the ERG program.

The manager's role should be to help employees access the benefit responsibly while managing real business needs.

A personal gatekeeper says, "I decide whether this matters." A benefit administrator says, "The company has defined this as part of the employee experience, and my role is to help make it work within the guidelines."

That does not mean managers have to approve everything. It means they need a framework for making decisions. Managers should know what participation is allowed, what process employees should follow, what to do when work conflicts arise, what language to use, what not to say, and when to escalate a question instead of inventing the answer themselves.

This protects employees from having to convince every manager that ERGs matter. It also protects managers from being forced to improvise policy in the moment.

6. Define the workload conflict protocol.

ERG participation will sometimes conflict with work. That is not automatically a failure. The failure is having no protocol for what happens next.

When ERG participation conflicts with a business need, managers should not have to default to a vague yes or no. They should have a decision-making process. A practical workload conflict protocol should ask:

• Is this approved ERG or professional development time?
• Is the employee within the reasonable participation allowance?
• What specific work need is at risk?
• Can coverage be planned?
• Can the work be shifted, delegated, or rescheduled?
• Can the employee participate another way, such as through a recording, recap, async discussion, or future session?
• Is this a one-time conflict or a recurring access issue?
• Does this reveal a broader barrier for this employee population?

That final question is important. If one employee cannot attend one event because of a specific deadline, that may be a normal business conflict. If an entire employee group can never attend live ERG programming, that is not a scheduling issue. That is an access design failure.

The goal is not to make ERG participation override every business priority. The goal is to stop making ERG participation lose by default because no one designed a better process.

The manager guide should become the access model.

A manager-facing ERG support guide is still one of the most important tools a company can build. But it should not be framed as a fluffy education document.

It should function as the ERG access model.

The guide should force the company to answer the questions managers and employees are already dealing with in the wild. What are ERGs? What counts as participation? How much time is reasonable? How does participation work for different employee types? How should time be logged? What should managers do when work conflicts arise? What language should managers use? What language should they avoid? How does ERG leadership connect to professional development? What does minimum viable support look like each quarter?

A strong guide should include:

• What ERGs are and are not. ERGs are not random social clubs, side projects, or replacements for HR. They are employee communities that support connection, learning, belonging, leadership development, and engagement.
• Types of ERG participation. General attendance, ERG leadership, event planning, professional development, async engagement, mentoring, and community discussions should be clearly distinguished.
• Participation scope and time allowance. Employees and managers should know what level of participation is considered reasonable.
• Participation pathways by employee type. Salaried, hourly, frontline, queue-based, billable, global, and ERG leader participation may require different instructions.
• Timekeeping, billing, or coding guidance. If there is a code, provide it. If the time is paid, say so. If participation falls under professional development, say so.
• The manager's role. Managers are not personal gatekeepers deciding whether ERGs matter. They are administrators of a company-sponsored benefit.
• The workload conflict protocol. Managers need a clear process so ERG participation does not lose by default.
• Scripts for common scenarios. Managers need language for attendance requests, workload conflicts, sensitive topics, fairness concerns, and development conversations.
• What not to say. Small comments can quietly discourage participation and create unnecessary risk.
• How ERG participation connects to development. Managers need to know how ERG involvement can build skills like facilitation, leadership, communication, project management, stakeholder management, and community building.
• A quarterly minimum viable support checklist. This gives managers a practical baseline, not an unrealistic expectation.

That guide is not just a document. It is the operating tool that turns ERG support from personal preference into consistent practice.

But do not solve access before you solve value.

Here is the part ERG teams need to be honest about.

If you build the access model, align managers, clarify time codes, create participation pathways, and make it easier for employees to attend, you may immediately expose another problem: the programming is not strong enough to justify the effort.

That is why "get more people in the door" may not always be the right first move.

If employees have to navigate coverage, log time correctly, use limited professional development hours, coordinate with a manager, or watch a recording after hours, the programming needs to be worth it.

People are not going to jump through operational hoops for a generic panel with no clear takeaway.

This connects directly to the third P of the 3Ps of ERGs: Programming.

Purpose tells the ERG program why it exists. Processes tell people how the ERG program works. Programming is where employees actually experience the value.

If the programming is weak, better access will not create sustained engagement. It may create temporary attendance, but not trust, connection, or repeat participation.

That is why companies may need to start by training ERG leaders to create better programming before they push hard on getting more people through the door.

Because once the access problem is solved, people will come in with expectations. If the experience is generic, poorly facilitated, too broad, or disconnected from what employees actually need, then you have just moved the problem down the line.

Now the issue is not "managers are blocking people from attending." The issue is "people attended and did not find enough value to come back."

That is a different problem, but it is still a problem.

So the better sequence may be:

1. Strengthen the programming. Train ERG leaders to design programs that are specific, relevant, facilitated well, and connected to real member needs.
2. Clarify the access model. Define how employees can actually use the ERG benefit across different roles and work models.
3. Drive participation. Once the experience is worth accessing and the access path is clear, then push for attendance, engagement, and manager support.

That sequence is important. Because the goal is not just more people in the room. The goal is more people in the room for an experience that makes them want to stay connected.

This is how you actually unfreeze the middle.

The middle manager problem is often not a manager problem first. It is an ERG access problem. Companies have positioned ERGs as an employee benefit, but many have not done the hard operational work to define how employees use that benefit across different roles, schedules, work models, and business realities.

So managers become the policy. And when managers become the policy, access becomes inconsistent.

Some employees participate because their manager is supportive. Some avoid participating because the process is unclear. Some participate and quietly pay for it later through workload, judgment, or missed opportunities. Some never even try because they know their role, schedule, queue, or utilization target makes participation feel impossible.

That is not a healthy ERG operating model.

The solve is not to tell employees to fight their managers. It is not to tell managers to magically care more. It is not to send another inspirational ERG email and hope the middle layer warms up.

The solve is to build the benefit properly.

Define the time. Define the scope. Define the process. Define the participation pathways. Define the manager role. Define the workload protocol. Define the timekeeping or billing process. Define the difference between accountability and discouragement. Define how ERG leadership connects to development.

Then make sure the programming is worth accessing. Because once you solve access, you still have to solve value.

That is why the 3Ps matter. Purpose gives the ERG program direction. Processes make the benefit usable. Programming makes the benefit worth using.

If any one of those is missing, the middle stays frozen. Not because managers are all villains. Because the company is asking people to believe in a benefit it has not fully built.