Month: August 2026

Client: “I’m new to HR. I took the classes, got the certification, and I thought I understood the rules. But now I’m in the workplace, and employees and managers don’t follow the theory. HELP!” 

Consultant: First, welcome to real-life HR—where the textbook was helpful, the certification was valuable, and the people did not read Chapter 4 before arriving at work today. 

You are not doing anything wrong. This is the moment when HR shifts from “knowing the rules” to learning how to apply them with actual humans, competing priorities, different communication styles, and managers who may be learning right alongside you. 

Client: “That makes me feel better, but also…where do I even start?” 

Consultant: Start with the basics. When things feel messy, HR foundations are your friend. 

That means asking: 

Do we have a policy? 

Do we have a process? 

Do people know the process? 

Are we applying it consistently? 

Have we documented what happened? 

It sounds simple, and that is the point. When you are new to HR, it is easy to feel like every situation needs an advanced strategy. Most of the time, the first step is just getting back to the foundation. 

Client: “What if the manager says, ‘That’s not how we usually do it’?” 

Consultant: That sentence should make your HR antenna go up—not in a panic, but with curiosity. 

You can say: 

“I understand that may be how it has been handled before. Let’s look at the policy and the reason for the process so we can make sure we are being consistent.” 

This keeps the conversation calm and professional. You are not accusing anyone of doing it wrong. You are simply bringing the discussion back to the organization’s expectations. 

Client: “What if employees don’t understand why HR is asking for certain things?” 

Consultant: That happens all the time. Employees may experience HR processes as unnecessary steps, delays, or “extra paperwork.” They do not always see the compliance, fairness, or documentation reason behind the request. 

So explain the why. 

For example: 

“I know this feels like an extra step, and we use this process so requests are reviewed consistently and we have a clear record of what was discussed.” 

Or: 

“I’m asking for this information because it helps us understand what support may be appropriate and keeps the process fair for everyone.” 

You do not need to over-explain every legal concept. Just give enough context so the person understands this is not random HR confetti being thrown into their day. 

Client: “What about managers? I thought they would already know how to handle employee issues.” 

Consultant: Some do. Some don’t. Some are wonderful technical experts who were promoted and then handed people problems with very little training. That does not make them bad managers. It means they may need structure, coaching, and reminders. 

With managers, focus on practical guidance: 

“What happened?” 

“What have you already said to the employee?” 

“What does the policy say?” 

“What outcome are you looking for?” 

“What documentation do we have?” 

These questions slow the situation down and help move the manager from reaction to process. 

Client: “What if they want to jump straight to discipline?” 

Consultant: Then you help them pause. One of HR’s most helpful roles is asking, “Are we there yet?” 

You might say: 

“Discipline may be appropriate, and before we decide that, let’s make sure expectations were clear, the employee had an opportunity to respond, and we have the facts documented.” 

This does not block accountability. It strengthens it. 

Client: “I think I’m worried people expect me to know everything.” 

Consultant: They might and that does not mean you have to pretend you do. 

A strong HR response is not always immediate. Sometimes the best answer is: 

“I want to make sure I guide this correctly. Let me review the policy and follow up with you.” 

That is not weakness. That is good HR. 

The goal is not to be a walking encyclopedia. The goal is to be steady, thoughtful, and reliable. 

Client: “So I don’t have to have the perfect answer right away?” 

Consultant: Correct. Please release yourself from the fantasy that HR professionals have a magical binder labeled “Every Weird Thing That Could Happen at Work.” 

We wish. It would be laminated. 

What you do need is a habit of returning to the basics: policy, process, consistency, communication, and documentation. 

Client: “What should I focus on building first?” 

Consultant: Build a simple HR toolkit. Nothing fancy—just useful. 

Start with: 

A reliable employee handbook 

Clear forms for common requests 

A documentation template for manager notes 

A checklist for new hires and separations 

A process for complaints and investigations 

A calendar for key deadlines 

A habit of confirming important conversations in writing 

These tools help you respond consistently, even when the situation feels new. 

Client: “And what about the people side? Because that’s the part that feels unpredictable.” 

Consultant: It is unpredictable. Employees and managers are all different. Some need a lot of explanation. Some need reassurance. Some need boundaries. Some need to be reminded that “I didn’t know” is not a long-term strategy. 

Your job is not to make everyone respond the same way. Your job is to create enough structure that different people can still move through the same fair process. 

Client: “That helps. So the answer is not that theory was wrong—it’s that theory is only the starting point?” 

Consultant: Exactly. The classes and certification gave you the map. The workplace gives you weather, detours, potholes, and occasionally someone who insists they have always driven through the flower bed and it has been fine. 

That is where HR judgment develops. 

You will learn when to coach, when to document, when to slow things down, when to escalate, and when to say, “No, we are not doing that.” 

Client: “So what should I remember when I feel overwhelmed?” 

Consultant: Remember this: HR is learned in layers. 

You do not need to master every situation on day one. Start with the foundation, ask good questions, use your resources, and keep people moving toward fair and consistent practices. 

And when theory meets reality, take a breath. You are not behind—you are becoming an HR professional. 

And if you ever need help sorting through the “this was not in the textbook” moments, we’re here to support you. 

Client: “We have an employee who disagrees with their performance rating, and now they’re comparing themselves to others. They’re saying things like, ‘I do more than they do,’ or ‘Why did they get a higher rating than me?’ How do we handle that without getting pulled into a debate about everyone else?” 

Consultant: This is such a common performance review challenge. When employees are disappointed or frustrated, comparison can feel like their strongest argument. The key is to acknowledge what they are saying, but redirect the conversation back to their own performance, goals, and measurable expectations. 

Client: “So I shouldn’t respond to the comparison?” 

Consultant: You don’t want to debate another employee’s performance, rating, workload, or manager feedback. That’s not information you can appropriately discuss, and it usually takes the conversation in the wrong direction. 

You can say: 

“I hear that you have concerns about how your performance compares to others. I can’t discuss another employee’s review or rating. What I can do is walk through your goals, the expectations for your role, and the specific reasons for your rating.” 

That keeps the conversation respectful, but firmly centered where it belongs. 

Client: “What if they say the rating is unfair?” 

Consultant: Then go back to the foundation of the review: pre-defined goals, known measures of success, and documented examples. A rating should not feel like a mystery or a personality judgment. It should connect to what was expected and what actually happened. 

You might say: 

“Let’s look at the goals we set for this review period and the measurements we agreed would show success. My intent is to make sure you understand how the rating was determined, even if you don’t agree with it.” 

This helps move the discussion from emotion to information. 

Client: “What if they bring up specific coworkers and say, ‘I know I did better than them’?” 

Consultant: Stay neutral. Don’t confirm, deny, or compare. Instead, redirect. 

Try: 

“I understand that it may feel natural to compare your performance with others. For this conversation, we need to focus on your role, your goals, your outcomes, and what success looks like for you moving forward.” 

If they keep pushing, you can repeat the boundary: 

“I’m not able to discuss another employee’s performance. I am prepared to discuss yours in detail.” 

Client: “That sounds firm, but I don’t want to dismiss what they’re telling me. What if their comparison actually points to a bigger issue?” 

Consultant: That’s an important point. Redirecting the conversation does not mean ignoring the information. Sometimes an employee’s comments may reveal something worth reviewing later, such as inconsistent expectations, unclear measurements, rating inflation, favoritism concerns, or a need for better manager calibration. 

You can say: 

“I’m going to keep today’s conversation focused on your review. I also hear that you’re raising a concern about consistency, and I will make note of that separately so we can determine whether there is anything we need to look at in our process.” 

That way, you are not letting the insight disappear, but you are also not turning their review into a group comparison exercise. 

Client: “What if they say, ‘Well, what do I need to do to get a higher rating next time?’” 

Consultant: That’s the opening you want. Shift the conversation from defending the rating to defining the path forward. 

You might say: 

“That’s a good question. For the next review period, let’s identify what meeting expectations and exceeding expectations look like in specific terms. That way, you know what we’ll be measuring, and we can check in along the way.” 

Then get specific. Are they being measured on accuracy, deadlines, customer service, leadership, project completion, teamwork, communication, productivity, or technical skill? The clearer the criteria, the easier it is to coach and the harder it is for the conversation to drift into opinion. 

Client: “What if they still refuse to accept the rating?” 

Consultant: They do not have to love the rating for the organization to finalize it. The goal is to make sure they understand the basis for it, have had an opportunity to respond, and know what is expected moving forward. 

You can say: 

“I understand you disagree with the rating. I’ve heard your perspective, and I’ll include your comments with the review. The rating will remain as issued, and our focus now needs to be on the expectations and goals for the next review period.” 

That gives them voice without handing over the decision. 

Client: “Should we let employees submit written comments?” 

Consultant: Yes, if your process allows it. It can be helpful to give employees a place to document their perspective without turning the review meeting into a debate. 

You might say: 

“You’re welcome to provide written comments if you would like your perspective included with the review. I would encourage you to focus those comments on your own performance, accomplishments, goals, and areas where you believe additional information should be considered.” 

That keeps the process professional and useful. 

Client: “So the key is to acknowledge the concern, redirect to their performance, and separately review whether their comments point to a bigger issue?” 

Consultant: Exactly. Performance reviews should be based on clear expectations, known measurements, and documented results. If an employee disagrees, listen and explain. If they compare, redirect. And if their comments reveal a possible process concern, take that seriously—but handle it outside of the individual review conversation. 

And if you need help strengthening your performance review process, rating definitions, or manager calibration, we’re here to support you. 

Client: “Every time I ask supervisors to document an employee issue, I get something that reads more like a personal diary than professional notes. I’m worried these notes could hurt the organization instead of help us. What should documentation actually look like?” 

Consultant: You are right to be concerned. Documentation should help the organization understand what happened, what was discussed, and what needs to happen next. It should not include venting, assumptions, labels, sarcasm, or personal commentary. 

The goal is not to “build a case” against an employee. The goal is to create a clear, factual record. 

Client: “What’s the difference between helpful documentation and documentation that hurts us?” 

Consultant: Helpful documentation is factual, specific, timely, and professional. 

Instead of writing: 

“Jordan clearly doesn’t care about this job and is always making excuses.” 

Try: 

“Jordan arrived 18 minutes late for the scheduled 8:00 a.m. shift. This is the third late arrival in the past two weeks. We discussed the attendance expectation and the need to notify a supervisor before the start of the shift if they will be late.” 

The first version gives us frustration and assumptions. The second gives us facts we can use. 

Client: “So supervisors should avoid writing how they feel about the employee?” 

Consultant: Exactly. Documentation is not the place to process frustration. Avoid labels like “lazy,” “rude,” “toxic,” “bad attitude,” or “doesn’t care.” 

Instead, document the behavior: 

“The report was not submitted by the Friday deadline.” 

“The employee interrupted two coworkers during the meeting.” 

“The employee left the front desk uncovered for 25 minutes without notifying the lead.” 

Behavior can be addressed. Labels create risk. 

Client: “How much detail do they really need?” 

Consultant: Enough that someone who was not there can understand the situation. Most notes should answer five basic questions: 

Who was involved?
What happened?
When did it happen?
What expectation was discussed?
What are the next steps? 

A simple note might look like: 

“Met with [Employee] on [Date] regarding [specific issue]. Reviewed [policy, expectation, or performance standard]. Employee shared [brief response, if relevant]. Next steps are [what needs to happen and by when].” 

That is usually enough for routine coaching notes. 

Client: “What should absolutely stay out of documentation?” 

Consultant: Personal opinions, medical assumptions, legal conclusions, jokes, sarcasm, and comments unrelated to the workplace issue. 

A good rule of thumb is this: write every note as if the employee, HR, an attorney, an investigator, or a decision-maker may read it someday. Because someday, they might. 

Client: “What if the employee shares something important during the conversation?” 

Consultant: Include it briefly and factually. For example: 

“Employee stated they were late because their childcare provider was delayed.” 

“Employee disagreed with the feedback and stated they believe the workload is unreasonable.” 

“Employee shared that a health-related issue may be affecting attendance. I paused the conversation and referred the matter to HR for follow-up.” 

You do not need every word. You need the relevant information. 

Client: “So the key is facts, not feelings?” 

Consultant: Exactly. Facts, expectations, employee response, and next steps. 

Good documentation helps supervisors follow up consistently, helps employees understand what needs to change, and helps the organization show that it acted professionally and fairly. 

So yes — no more diary entries. 

Dear diary, this is HR. Keep it factual, keep it professional, and keep it useful. 

And if you ever need help training supervisors on documentation that helps instead of hurts, we’re here to support you.  Reach out anytime.