PUBLISHED: October 21, 2025

Needs vs. Rights: Managing Workplace Wants Across Generations

This month’s newsletter theme, “Managing in a Multi-Generational Workplace,” is a daily reality for every municipal HR leader. The challenge often isn’t open conflict, but a quiet friction of mismatched expectations.

Think about a few requests that may land on your desk:

  • A senior ‘Boomer’ manager, who is “driven” and values a strong team presence, asks for a return to more standardized in-office hours, concerned that new flex policies are eroding the “all-hands-on-deck” culture.
  • A ‘Gen X’ employee, who is “balanced” and “sceptical” of corporate hype, asks to be excused from “mandatory” team-building events to focus on core project deadlines.
  • A ‘Millennial’ team lead, who thrives on “inclusive” relationships, requests a budget for weekly team coffees, seeing it as essential for collaboration and psychological safety.
  • A new ‘Gen Z’ employee asks if they can use a “mental health day” not as a formal sick day, but as a preventative measure to avoid burnout.

As an HR professional, you know that none of these are clear requests for accommodation under the Ontario Human Rights Code (the “Code”). They are not legal “rights”.

So, the easy answer is to point to a workplace policy manual. But in the context of a multi-generational workforce, a flat “no” could create unintended ripples. These requests are “identity-based needs”—core values potentially shaped by their generational viewpoints. Outright dismissal could make the Boomer feel disrespected, the Gen X feel that their workflow doesn’t matter, and the Millennial and Gen Z employees feel the workplace is rigid and unsupportive.

This is how friction builds. It’s not a legal problem yet, but it leads to disengagement, turnover, and a culture where employees feel misunderstood.

The solution is not to create new rights for every “want”, but to borrow the robust process we already use for legal accommodation.

The Accommodation Process: A Tool for Engagement

When you receive a Code-based request, you have a legal duty to engage in a collaborative process. You assess the need, explore solutions, and document efforts.

While the legal obligation is tied to protected grounds, the process itself—assess, collaborate, explore, document—is one of the most effective management tools available. It signals respect, fairness, and a willingness to find a solution.

Applying this process to generational “wants” is not about ceding management rights. It’s a strategic way to demonstrate objective, fair-minded management—the very things that defend against a later claim of a poisoned work environment.

How to Apply Accommodation Principles

Here’s how you can distinguish between a legal “must-have” and a managerial “nice-to-have,” all while using the same proven framework.

Step 1: Triage the Request (The “Why”) When an employee makes a request, understand its origin. Is this a Code-based need (e.g., “I need this schedule for childcare”)? If yes, the legal duty to accommodate is triggered. Or is this a “want” stemming from a generational preference (e.g., a desire for “balance” or “inclusion”)? If it’s the latter, you have a managerial opportunity.

Step 2: Engage and Explore (Don’t Just Deny) If it’s a generational “want,” don’t lead with a flat “no.” Use the language of accommodation.

  • For the manager concerned about culture: “Help me understand what you’re seeing. Let’s look at the team’s output and explore other ways to foster that ‘all-hands’ feel, like a core-hours policy.”
  • For the employee skipping team-building: “I understand the project pressure. Can we compromise on you attending just the kick-off portion?”
  • For the team lead wanting a coffee budget: “The request makes sense. While we can’t fund it weekly, let’s budget for a monthly event.”

Step 3: Maintain Operational Discretion (The “Line”) This is the critical legal distinction. In a Code accommodation, you must provide or work towards a reasonable solution up to undue hardship. When managing a “want,” the municipality retains its ultimate operational discretion. By engaging in the process, you are not promising the outcome.

Step 4: Document the Rationale (The “Defence”) If the answer is ultimately “no” (e.g., for the ‘Gen Z’ mental health day), explain it with a transparent reason. “We appreciate the need for preventative rest, but we can’t implement that as a formal policy right now. Here are the EAP resources we have, and let’s talk about using your existing personal days for this.” This feels objective and supportive, not arbitrary.

This approach addresses the identity-based needs of a multi-generational workforce, fostering trust that management acts with respect and fairness — exactly the kind of evidence an employer wants on its side if a dispute ever arises.

Written by: By Jordan Bailey, Zubas Flett Liberatore Law LLP

Share this story...

ARTICLE PRESENTED BY

Search Insights

Insights Categories

Insights Archive