Author: Laurie Grenya

Client: 
“I just learned that a manager gave an employee incorrect information, directly contradicting what’s clearly stated in our handbook. The employee is confused, frustrated, and questioning whether they can trust what we say. I need to fix this without undermining the manager or increasing risk. How should this be handled?” 

Consultant:
This is a critical moment and it’s one where how you respond matters just as much as what you say. 

There are really two separate responsibilities here: 

1. Correcting the information and repairing trust with the employee, and
2. Addressing the manager’s behavior through retraining and accountability 

Those conversations should be handled separately. Blending them creates confusion, erodes trust, and increases risk. 

Client:
“My first instinct is to explain that the manager misspoke. Is that the right approach?” 

Consultant:
It’s better to focus on clarity rather than explanation. 

When you talk with the employee, anchor the conversation to the handbook and the organization’s expectations, not the manager’s error. 

You might say:
“I want to clarify something and make sure you have accurate information. Our handbook states [X], and that is the expectation we follow.” 

This approach: 

• Reinforces the handbook as the source of truth 

• Avoids publicly undermining the manager 

• Restores clarity without assigning blame 

The goal of this conversation is repair, not justification. 

Client: 
“What if the employee says, ‘That’s not what my manager told me’?” 

Consultant: 
That’s a natural response and it doesn’t change your role. 

You can acknowledge the confusion without validating the incorrect guidance:
“I understand why that was confusing. I want to be clear about what applies going forward so you have the right information.” 

You don’t need to reconcile different versions of the story. You need to confirm the correct one. 

Client:
“Should I tell the employee that I’ll address this with the manager?” 

Consultant:
You can reassure them without committing to outcomes or sharing internal actions. 

For example:
“We take consistency seriously, and we’ll make sure expectations are reinforced.” 

That keeps the focus on accurate guidance while preserving appropriate boundaries around internal management discussions. 

Client: 
“Okay, then how do I handle the manager conversation?” 

Consultant: 
Separately and directly. 

This conversation is about alignment, not intent. Even well-meaning responses can create risk if they conflict with established guidance. 

With the manager, focus on: 

• What was communicated 

• How it differed from the handbook 

• Why consistency matters 

• What needs to change moving forward 

You might say:
“When guidance conflicts with the handbook, it creates confusion and risk. Going forward, it’s important that responses align with what’s written, or that you pause and check before answering.” 

This is coaching. Depending on the situation, it may also involve corrective action. 

Client:
“What if the manager says they were ‘just trying to be helpful’?” 

Consultant:
That’s common, and it still needs to be addressed. 

Good intent doesn’t offset risk. Managers act on behalf of the organization, and their guidance carries weight. When something feels unclear or uncomfortable to answer, the right response is to pause and escalate not reinterpret policy in the moment. 

Reinforcing that boundary protects everyone. 

Client: 
“How do I reduce the chances of this happening again?” 

Consultant:
Through retraining and accountability. 

That may include: 

• Reviewing relevant handbook sections 

• Clarifying decision-making authority 

• Reinforcing when to escalate questions 

• Documenting the coaching or correction, when appropriate 

This isn’t about punishment. It’s about consistency, credibility, and risk reduction. 

Client: 
“So let me make sure I’ve got this. I correct the information with the employee by anchoring to the handbook. I don’t explain or assign blame. Then I separately address the manager through retraining and accountability—without mixing the two conversations.” 

Consultant:
Exactly. When those conversations stay separate, you: 

• Repair trust with the employee 

• Reinforce the handbook as the source of truth 

• Coach or correct the manager appropriately 

• Reduce legal and consistency risk 

That’s leadership—not cleanup. 

The Foundations Behind This Approach 

Situations like this sit at the intersection of communication, accountability, and compliance. 

Human Relations Foundations 

• Clarity over explanation – Employees need accurate guidance, not background details 

• Professional boundaries – Manager coaching should not happen publicly or indirectly 

• Trust repair – Consistent, calm communication restores confidence 

• Role clarity – Managers apply policy; they don’t reinterpret it 

HR Technical Foundations (Laws, Rules, and Risk) 

• Handbook as source of truth – Written guidance must be applied consistently 

• Agency risk – Managers speak on behalf of the organization 

• Consistency obligations – Conflicting guidance increases exposure 

• Documentation standards – Manager coaching or correction should be recorded when appropriate 

• Training expectations – Managers must understand the policies they enforce 

Handled correctly, these moments strengthen credibility, reinforce structure, and reduce risk—without damaging relationships. 

Need a Sounding Board? 

If you’re navigating a situation where a manager gave incorrect guidance—or you’re unsure how to separate clarification from accountability—we’re here to help. 

If we can help with this or anything else, just give us a call.

503-885-9815

Client: 
“I try to give coaching feedback, and it immediately turns into defensiveness. Explanations, crossed arms, and a lot of ‘Well, others do this too.’ I’m not trying to start a fight, and I also can’t stop giving feedback. How do I keep coaching from turning into conflict?” 

Consultant: 
You’re describing a very common coaching moment and one that can go sideways fast if you’re not intentional. When feedback triggers defensiveness, it usually means the employee feels exposed, compared, or unfairly singled out. 

The key shift is this: coaching is about expectations and impact, not comparison or judgment. 

Client:
“So defensiveness doesn’t automatically mean the feedback is wrong?” 

Consultant:
Not at all. Defensiveness often shows up because: 

• The feedback is unexpected 

• The employee feels embarrassed or threatened 

• They don’t clearly understand the expectation 

• They believe the standard isn’t applied consistently 

Your role isn’t to remove emotion it’s to keep the conversation productive when emotion appears. 

Client:
“What usually causes the conversation to turn into a fight?” 

Consultant:
Two things: arguing intent and allowing comparisons. 

Once the conversation becomes: 

• “That’s not what I meant” 

• “You’re taking this personally” 

• “Well, so-and-so does it too” 

the focus shifts away from expectations and toward fairness debates. That’s when coaching stalls. 

Client:
“How should I respond when an employee starts pointing out others who ‘do the same thing’?” 

Consultant: 
That’s the moment to reset the frame. 

You might say:
“I’m not talking about anyone else right now. I want to stay focused on the expectations for your role and what I’m seeing here.” 

This keeps the conversation grounded and prevents it from turning into a comparison exercise. 

Client:
“But what if they insist it’s unfair because others aren’t being coached?” 

Consultant:
This is where reassurance and boundaries matter at the same time. 

You can acknowledge the concern and reinforce consistency without debating specifics. For example:
“I hear your concern about fairness. Consistency is important, and we address issues as they come up. Right now, I want to focus on what’s expected of you and what needs to change moving forward.” 

This reassures the employee that standards are applied consistently without turning the conversation into a discussion about other employees. 

Client: 
“What should I do in the moment when defensiveness shows up?” 

Consultant:
Slow the conversation down and refocus on behavior and impact. 

Try:
“I’m not questioning your effort or intentions. I want to focus on what I’m seeing and how it’s impacting the work.” 

Separating the person from the behavior lowers the temperature and keeps the conversation professional. 

Client:
“What if they keep interrupting or explaining why it’s not their fault?” 

Consultant:
That’s a cue to bring structure back in. 

You might say:
“I hear your perspective. Let’s come back to the expectation and what needs to happen moving forward.” 

You don’t need agreement on the past to set expectations for the future. 

Client: 
“How do I keep coaching from feeling like criticism or punishment?” 

Consultant:
Consistency matters more than tone. 

When feedback only shows up during problems, it feels punitive. When coaching is part of regular conversations—recognition and redirection—it feels developmental. Surprise is one of the biggest drivers of defensiveness. 

Client:
“And if the defensiveness doesn’t stop and the behavior doesn’t change?” 

Consultant: 
Then the conversation needs more structure. 

If coaching conversations repeatedly stall and expectations aren’t met, it may be time to move toward Corrective Action. That shift isn’t about punishment, it’s about clarity, documentation, and accountability. 

Coaching and corrective action are connected. Coaching sets the expectation. Corrective action reinforces it when needed. 

Client:
“So let me make sure I’ve got this. When someone gets defensive or starts pointing at others, I shouldn’t argue or retreat. I refocus on expectations, behavior, and impact, reassure that consistency matters, and if coaching doesn’t work, I move to corrective action.” 

Consultant:
You’ve got it. Coaching doesn’t require agreement. It requires clarity and follow-through. When expectations stay front and center, feedback stays productive—and doesn’t turn into a fight. 

The Foundations Behind This Approach 

Defensive reactions are human. Managing them well requires both relational skill and technical awareness. 

Human Relations Foundations 

• Behavior over comparison – Coaching is about expectations, not who else does what 

• Psychological safety – A calm, neutral tone reduces escalation 

• Active listening – Acknowledging concerns without conceding expectations 

• Consistency – Regular feedback reduces surprise and resistance 

HR Technical Foundations (Laws, Rules, and Risk) 

• Clear, job-related expectations – Employees must understand what success looks like 

• Documentation readiness – Coaching conversations may later support corrective action 

• Corrective action principles – Coaching first, corrective action when needed 

• Fair application – Similar behaviors should be addressed consistently, even if not in the same conversation 

• Retaliation awareness – Feedback must remain job-related and non-punitive 

Handled well, coaching strengthens performance and trust. Handled poorly, it becomes personal and that’s when fights start. 

Need a Sounding Board? 

If coaching conversations keep turning defensive or you’re unsure when it’s time to move from coaching to corrective action, we’re here to help. 

If we can help with this or anything else, just give us a call 503-885-9815. 

Client: 
“Our handbook feels like it’s been added to over time, usually when a specific issue comes up. Someone asks, ‘Do we have a policy for that?’ and suddenly a new section appears. Most of those situations never happen again, but the language sticks around. How do we figure out what actually belongs in the handbook—and what doesn’t?” 

Consultant:
This is how handbook whiplash usually starts, with good intentions. A discreet issue comes up. A solution is needed. Language gets added to address that moment. Then everyone moves on, and the handbook quietly grows. 

Over time, the handbook becomes a collection of one-off fixes instead of a clear, structured guide for how the organization actually operates. 

Client:
“So the issue isn’t occasional updates, it’s how and why we’re adding things?” 

Consultant:
Exactly. Not every workplace issue deserves a permanent place in the handbook. 

Handbooks work best when they: 

• Establish consistent, repeatable expectations 

• Explain how common situations are handled 

• Support supervisors in day-to-day decisions 

They work poorly when they try to solve rare, highly specific situations that are unlikely to occur again. 

If a policy exists only because of a single incident, it may belong in a procedure, manager guidance, or case-by-case documentation—not the handbook. 

Client: 
“We used to Google policies when something came up. Now people are also asking OpenAI for language. Is that any better?” 

Consultant:
It’s a different tool, and it needs the same discipline. 

Using OpenAI or the internet without context is a bit like standing in the middle of a packed sports arena and asking everyone in attendance their opinion. You’ll get a lot of answers. None of them know: 

• Your organization 

• Your culture 

• Your state or local laws 

• Your size, structure, or risk tolerance 

That doesn’t make the tool bad. It means it should not be treated as a plug-and-play policy generator. 

Client:
“So when is OpenAI helpful in handbook work?” 

Consultant:
It’s very effective once the substance is already right. 

Good uses include: 

• Evening out tone across the document 

• Rewriting policies in plain language 

• Aligning voice and style 

• Reducing overly legalistic phrasing 

Where risk shows up is using it as a research shortcut instead of first identifying legal requirements, organizational practices, and risk tolerance. 

Unless the tool is guided with those considerations, it can’t distinguish between what sounds good and what actually applies. 

Client: 
“So whether it’s Google or OpenAI, the problem is copying without context?” 

Consultant:
Exactly. The tool isn’t the issue. The absence of context is. 

Copied language can quietly create: 

• Commitments you didn’t intend 

• Policies that don’t match practice 

• Language that doesn’t apply in your jurisdiction 

• Inconsistencies that undermine credibility 

Once it’s in the handbook, it’s no longer a draft it’s an expectation. 

Client:
“We also struggle with knowing when to update. It feels reactive.” 

Consultant:
That’s where a planned and structured approach makes all the difference. 

Instead of updating only when something goes wrong, handbook maintenance should be driven by clear triggers: 

You review or update sections when: 

• Laws or regulations change 

• Workplace practices change (remote work, scheduling, pay practices) 

• Supervisors are applying things inconsistently 

• Employees keep asking the same questions 

• A policy no longer reflects reality 

A full handbook review should happen at least annually and not everything needs to change every year. What matters is that what stays is still accurate and usable. 

Client: 
“So updates shouldn’t be emergency reactions, they should be intentional?” 

Consultant: 
Exactly. Planned updates prevent whiplash. 

When organizations use a structured review process, they can: 

• Remove outdated or one-off language 

• Confirm legally required sections are current 

• Align policies with actual practice 

• Decide intentionally what belongs in the handbook—and what doesn’t 

That discipline keeps the handbook from becoming a running archive of past problems. 

Client: 
“Let me make sure I’ve got this. The handbook shouldn’t grow every time something unusual happens. We should update it intentionally, focus on common situations, and use tools like OpenAI to refine, not define our policies.” 

Consultant:
You’ve got it. A strong handbook is built on purpose, not reaction. 

The Foundations Behind This Approach 

Handbook whiplash happens when organizations lose clarity about purpose and process. 

Human Relations Foundations 

• Clarity – Employees need guidance they can understand and apply 

• Credibility – When policy matches practice, trust increases 

• Consistency – Supervisors rely on the handbook to support fair decisions 

• Usability – If it’s too long or too specific, it won’t be used 

HR Technical Foundations (Laws, Rules, and Risk) 

• Jurisdiction-specific compliance – Policies must reflect applicable federal, state, and local laws 

• Policy vs. procedure distinction – Not every issue belongs in the handbook 

• Avoiding unintended promises – Poorly sourced language can create legal obligations 

• Documentation hierarchy – Handbooks, policies, procedures, and manager tools serve different purposes 

• Planned review cycles – Regular, structured reviews reduce risk and confusion 

Used well, tools like OpenAI support clearer writing. Used without structure, they can quietly increase exposure. 

Want to Get This Right? 

If your handbook feels cluttered with one-off fixes—or stitched together from too many sources—it may be time for a reset. 

Our upcoming training, The ABCs of Handbooks, begins May 12, 2026 and walks through how to build and maintain a handbook that supports compliance, culture, and connection—without the whiplash. 

Learn more and register at www.hranswers.com 

And as always, if we can help with this or anything else, just give us a call. 

Client: 
“I was just promoted, and now I’m supervising the same people I used to work alongside. Some of them are supportive. Some are skeptical. I want to start strong, but I don’t want to overcorrect or pretend I’m someone I’m not. What should I be focused on in those first 90 days?” 

Consultant:
That first 90-day window matters more than people realize. Not because you need to prove authority—but because you’re quietly setting expectations, credibility, and consistency that will stick long after the promotion announcement fades. 

Your goal isn’t to be perfect. It’s to be clear, steady, and intentional. 

Client:
“It feels awkward to suddenly be ‘the supervisor’ with people who used to be my peers. How do I handle that shift?” 

Consultant:
By acknowledging it—without over explaining it. The role has changed, even if the relationships haven’t disappeared. 

What helps most is role clarity. Be upfront about what’s different now: 

• You’re accountable for team outcomes 

• You’re responsible for addressing issues 

• You still value collaboration and respect 

Trying to act like “nothing has changed” creates confusion. Acting like everything has changed creates distance. The balance is naming the shift and moving forward professionally. 

Client:
“I’m worried about credibility. Some people have more experience than I do.” 

Consultant:
Credibility doesn’t come from knowing everything—it comes from how you show up. 

In the first 90 days, credibility is built by: 

• Following through on what you say 

• Applying expectations consistently 

• Listening before reacting 

• Being willing to say, “I don’t know yet, but I’ll find out” 

You don’t need to out-expert your team. You need to be fair, predictable, and engaged. 

Client:
“What about expectations? I don’t want to overwhelm people right away.” 

Consultant:
Clarity early prevents problems later. That doesn’t mean changing everything—it means naming what matters. 

Early conversations should focus on: 

• What success looks like in the role 

• How communication will work 

• How feedback will be given and received 

• What accountability looks like 

Unspoken expectations are where frustration grows. Clear expectations are a gift—even when they’re uncomfortable. 

Client:
“I’m afraid of being inconsistent while I’m still figuring things out.” 

Consultant:
That’s a real risk in the early months. New supervisors often react case-by-case instead of pattern-by-pattern. 

Consistency doesn’t mean rigidity. It means: 

• Similar situations are handled in similar ways 

• Decisions align with stated expectations 

• Adjustments are explained, not random 

If you need to course-correct, say so. Transparency builds trust faster than pretending you’ve always had it figured out. 

Client:
“So the first 90 days are less about big changes and more about how I lead day to day?” 

Consultant:
Exactly. People are watching: 

• How you handle pressure 

• Whether you avoid hard conversations or address them 

• How you balance empathy and accountability 

• Whether your words and actions line up 

Those signals matter more than any formal announcement or policy shift. 

Client: 
“Let me see if I’ve got this. I don’t need to prove myself overnight. I need to be clear about my role, consistent in how I show up, and intentional about expectations and follow-through.” 

Consultant:
You’ve got it. When new supervisors focus on clarity, credibility, and consistency early, they set themselves—and their teams—up for long-term success. 

The Foundations Behind the First 90 Days 

This transition works best when supervisors understand both the human side of leadership and the technical realities of the role. 

Human Relations Foundations 

• Role clarity – Teams need to understand what changed and what didn’t 

• Trust-building behaviors – Follow-through, listening, and fairness matter 

• Emotional intelligence – Managing relationships while setting boundaries 

• Consistency – Predictability builds confidence 

• Communication – Clear, respectful dialogue prevents misalignment 

HR Technical Foundations (Laws, Rules, and Expectations) 

• Supervisory responsibility – Supervisors act on behalf of the organization 

• Fair and consistent application of policy – Especially for attendance, performance, and conduct 

• Documentation basics – Knowing when and how to document conversations 

• Legal compliance awareness – Understanding when issues implicate leave laws, accommodations, or protected activity 

• Performance management fundamentals – Coaching first, accountability when needed 

Understanding these foundations helps new supervisors lead confidently without overstepping—or under-managing. 

Want Support During That First 90 Days? 

Stepping into supervision—especially over a former peer group—is one of the hardest transitions in the workplace. Skills like setting expectations, giving feedback, handling conflict, and staying consistent can be learned and strengthened. 

Our Building Blocks for Supervisory Success: New and Growing Leaders live webinar series begins May 7, 2026 and runs for 8 sessions. The program is designed to support supervisors through exactly these challenges, with practical tools, real-world scenarios, and time to practice between sessions. 

If you’re ready to build a strong foundation—or support someone who is—this series provides structure, guidance, and confidence right when it matters most. 

Learn more and register at www.hranswers.com 

Client: 
“I want to say yes to an employee’s request—it makes sense in this situation. My worry is that the minute I do, it becomes, ‘Well, you let them do it.’ How do I approve an exception without accidentally creating a new rule?” 

Consultant:
This is one of the most common—and most misunderstood—management challenges. The short answer is: you can say yes, and you can still protect the organization. The key is being intentional about how the decision is framed, documented, and communicated. 

An exception is a decision. A precedent is a pattern. Confusing the two is where trouble starts. 

Client:
“So what actually turns an exception into a precedent?” 

Consultant:
Silence and repetition. 

When an exception quietly happens—or happens more than once without explanation—it starts to look like a rule. Others notice, stories get simplified, and suddenly the narrative becomes, “They’re allowed to do that.” 

What creates precedent isn’t generosity. It’s lack of clarity. 

Client: 
“How should I explain an exception in the moment?” 

Consultant:
Name it as an exception, and anchor it to the specific circumstances. 

You might say:
“I’m approving this as an exception based on the circumstances you shared. This doesn’t change our overall expectations or apply automatically in other situations.” 

That one sentence does a lot of work. It signals flexibility and boundaries. 

Client: 
“What if the employee pushes back and asks why it wouldn’t apply to others?” 

Consultant:
That’s a reasonable question—and it’s also where consistency matters. 

You can respond with:
“Each request is evaluated individually. This decision is based on the details of this situation and doesn’t create a blanket rule going forward.” 

You don’t owe comparisons. You owe fairness and consistency in process—not identical outcomes. 

Client: 
“Do I need to document exceptions, even small ones?” 

Consultant:
Yes—especially the ones that feel reasonable. 

Documentation doesn’t have to be formal or punitive. A brief note about: 

• What was approved 

• Why it was approved 

• That it was an exception 

helps protect against future misunderstandings and keeps decisions consistent over time. 

Client:
“What if I say yes once and then have to say no the next time?” 

Consultant:
That’s okay—as long as the difference is explained. 

You might say:
“Last time, we approved an exception due to specific circumstances. This request doesn’t meet the same criteria, so we’re not able to approve it.” 

People handle no better when they understand the reasoning—even if they don’t love the answer. 

Client:
“Is there anything I should not use as the reason for an exception?” 

Consultant:
Yes—and this is a critical caution point. 

If the reason you’re giving for an exception is tied to a human characteristic—such as age, health status, family status, disability, religion, gender, or any other protected class—you may be heading into very risky territory. 

Even well-intended explanations like: 

• “Because they’re a parent” 

• “Because they’re older” 

• “Because of their medical situation” 

• “Because of cultural or religious reasons” 

can create legal exposure if they’re framed as discretionary exceptions rather than handled through the appropriate legal process. 

When the reason touches a protected characteristic, the conversation should shift away from “exceptions” and toward formal processes, such as leave laws, accommodations, or policy-driven protections. 

Client:
“So exceptions should be based on circumstances—not personal characteristics?” 

Consultant:
Exactly. Safe exceptions are grounded in business-related, situational factors, not who the person is. 

If the explanation starts to sound personal rather than operational, it’s time to pause and make sure the right framework is being used. 

Client: 
“Let me make sure I’ve got this. I can approve exceptions when it makes sense, as long as I clearly label them, tie them to the situation, document them, and avoid basing them on protected characteristics.” 

Consultant:
You’ve got it. Thoughtful flexibility is a strength—when it’s paired with discipline, clarity, and the right legal guardrails. 

The Foundations Behind This Approach 

This issue works best when managers understand both the human side of decision-making and the technical risks of inconsistency. 

Human Relations Foundations 

• Clarity – Naming something as an exception prevents confusion 

• Fair process – People want consistency in how decisions are made 

• Trust – Transparency builds credibility, even when answers differ 

• Communication – How the decision is explained matters as much as the decision itself 

HR Technical Foundations (Laws, Rules, and Risk) 

• Protected class considerations – Decisions based on protected characteristics require legal frameworks, not discretionary exceptions 

• Consistent application of policy – Similar situations should be evaluated using the same criteria 

• Avoiding implied contracts – Repeated exceptions can unintentionally create enforceable expectations 

• Equity and discrimination risk – Inconsistent approvals can raise fairness concerns if not well-documented 

• Documentation standards – Clear notes support defensible decision-making 

• Manager discretion boundaries – Flexibility should operate within policy, not outside of it 

Handled correctly, exceptions allow for humanity without quietly rewriting the rules—or creating unintended legal exposure. 

Need a Sounding Board? 

If you’re weighing an exception and wondering whether it’s reasonable—or risky—we’re happy to help you think it through. 

If we can help with this or anything else, just give us a call.