Month: August 2026

Client: “We are a customer-focused organization, and our teams do a great job serving the public. The problem is, some of those same great service skills don’t seem to show up when they’re working with other departments. How do we shift that?” 

Consultant: This is more common than people think. We often talk about customer service as though it only happens when we are helping the public, a client, or a community member. But internal customers come first. If departments do not communicate well, respond timely, and support each other’s work, the external service experience eventually feels it. Great customer service starts inside the organization. 

Client: “That’s exactly it. They’re polite and helpful with customers, but internally it can feel like, ‘That’s not my problem.’” 

Consultant: That’s where expectations come in. Internal customer service needs to be clearly named as part of the job, not treated like a nice extra. Responding to coworkers, meeting internal deadlines, sharing information, and solving problems across departments are all part of serving the organization. 

You might say: 

“We serve our customers best when we serve each other well internally. Timely communication, respectful problem-solving, and follow-through across departments are expectations of how we work here.” 

Client: “I like that. But how do we make it more than just a nice statement?” 

Consultant: Managers and supervisors have to model it first. If leaders roll their eyes at another department, ignore requests, blame other teams, or treat internal requests like interruptions, employees will follow that lead. 

Leaders should be asking: 

“Are we responding to internal requests the same way we expect employees to respond to the public?” 

If the answer is no, that’s the place to start. 

Client: “So this is really a culture issue?” 

Consultant: Yes, and culture shows up in daily behavior. It shows up in whether emails get answered, whether handoffs are clear, whether departments talk to each other with respect, and whether people follow through when they say they will. 

The message should be simple: internal customer service is not about one department serving another department’s ego. It is about helping the whole organization function well. 

Client: “What if one team feels like another team is constantly making unreasonable requests?” 

Consultant: That’s an important distinction. Internal customer service does not mean saying yes to everything. It means responding professionally, clarifying priorities, explaining timelines, and working toward a solution. 

Instead of ignoring the request or getting defensive, employees can say: 

“I understand what you need. Here is what we can do, here is the timeline, and here is what I need from you to move it forward.” 

That kind of response is respectful, realistic, and accountable. 

Client: “What if we have specific employees or supervisors who are part of the problem?” 

Consultant: Then it needs to be addressed directly. If someone is consistently dismissive, unresponsive, or difficult to work with, that is a workplace behavior issue. Start with coaching, but be clear. 

You might say: 

“I’ve noticed a pattern of delayed responses and frustration in your communication with other departments. I want to be clear that internal service is part of your role. We need you to respond professionally, communicate timelines, and help resolve issues rather than creating barriers.” 

Client: “And if they say they’re too busy?” 

Consultant: Being busy may explain a delay, but it does not excuse poor communication. A quick response that says, “I received this and will get back to you by Friday,” is still service. Silence creates frustration. So does making another department chase you for information. 

Client: “How do we hold people accountable without making it feel heavy-handed?” 

Consultant: Build it into regular expectations. Talk about it in team meetings. Include it in performance conversations. Recognize employees who collaborate well across departments. And when there are problems, address them the same way you would address poor service to the public. 

You might say: 

“Our expectation is that we treat internal customers with the same professionalism we provide externally. When that does not happen, we will coach it, document it if needed, and hold people accountable.” 

Client: “So the key is to define internal customer service, have leaders model it, and follow through when behavior does not match the expectation?” 

Consultant: Exactly. Internal customer service is not fluff. It is how work gets done. When teams communicate well, respect each other’s roles, and follow through, the whole organization gets stronger. 

And if the customer is calling from inside the house, we still answer professionally. 

Client: “My boss says we need an HR audit. I don’t know why, and honestly, I think I’m doing everything right. Should I be worried?” 

Consultant: I understand why that would feel unsettling. When someone says “audit,” it can sound like they are looking for mistakes. But an HR audit does not automatically mean something is wrong. In many cases, it means the organization wants a clearer picture of what is working, what needs attention, and where risk may be hiding. 

Client: “That makes sense, but it still feels like they don’t trust what I’m doing.” 

Consultant: That is a natural reaction. The first step is to find out the “why” behind the request. Your boss may be responding to growth, leadership changes, a Board request, a compliance concern, outdated policies, turnover, or simply a desire to strengthen systems. 

You might say: 

“I want to make sure I understand the goal of the audit. Is there a specific concern we are trying to address, or are we looking for a general review of our HR practices and compliance?” 

That question keeps the conversation constructive instead of defensive. 

Client: “What if there is a specific concern and they just haven’t told me?” 

Consultant: Then it is even more important to ask. You do not need to assume the worst, but you do need enough information to help the process succeed. 

Try this: 

“If there are particular areas you want reviewed, it would be helpful for me to know that upfront so I can gather the right materials and understand the priority.” 

This shows professionalism. You are not resisting the audit. You are helping define it. 

Client: “So what does an HR audit actually look at?” 

Consultant: An HR audit usually looks at the systems, documents, and practices that support employment decisions. Depending on the scope, that may include personnel files, I-9s, policies, job descriptions, wage and hour practices, leave processes, hiring practices, onboarding, performance management, supervisor documentation, and required training. 

It is not just about finding problems. A good audit also identifies what you are already doing well. 

Client: “That part helps. I think I’m worried they’ll find one missing form and decide I’ve failed.” 

Consultant: A helpful audit should not be a “gotcha” exercise. Most organizations have gaps somewhere. Sometimes the gap is a missing document. Sometimes it is an outdated policy. Sometimes it is an informal practice that works most of the time, but creates risk when a difficult situation comes up. 

The value of the audit is that it gives you a roadmap. It helps separate urgent compliance issues from lower-priority clean-up items. 

Client: “What should I ask before the audit starts?” 

Consultant: Ask a few practical questions so everyone is aligned. 

You might ask: 

“What is the purpose of the audit?” 

“What areas are included?” 

“Is this focused on compliance, process improvement, risk reduction, or all of the above?” 

“What will the final report be used for?” 

“What timeline are we working with?” 

“Who should be involved in gathering information?” 

These questions help turn a vague request into a manageable project. 

Client: “What if the audit finds things that need to be fixed?” 

Consultant: Then you have useful information. That is the point. Finding an issue in an audit is much better than finding it during a complaint, investigation, agency inquiry, employee dispute, or lawsuit. 

You can frame it this way: 

“I’m glad we identified this now. Let’s prioritize the items that create the most risk and build a practical plan to address them.” 

That response shows leadership and ownership. 

Client: “I like that. I don’t want to sound defensive, but I also don’t want people thinking HR is a mess.” 

Consultant: Exactly. The message should be: we are reviewing our systems because responsible organizations review their systems. Payroll gets reviewed. Finances get reviewed. Safety practices get reviewed. HR should not be different. 

An audit can confirm good practices, strengthen weak spots, and help leadership understand the resources HR may need. 

Client: “What do you mean by resources?” 

Consultant: Sometimes audits reveal that the issue is not effort—it is capacity. HR may be doing the best it can with limited time, outdated forms, unclear supervisor processes, or no centralized system. 

An audit can help leadership see where support is needed, whether that means updated templates, supervisor training, better tracking tools, policy revisions, or more realistic timelines. 

Client: “So it may actually help me explain what I’ve been trying to say?” 

Consultant: Absolutely. A well-done audit can give language and structure to things HR already knows. Instead of saying, “We need better documentation,” the audit may show where documentation is inconsistent, why that matters, and what steps will improve it. 

That is much easier for leadership to understand and act on. 

Client: “How should I respond to my boss now?” 

Consultant: Keep it calm, curious, and collaborative. 

You might say: 

“I’m open to the audit and want to make sure we get the most value from it. Can we talk about what prompted the request, what areas you want reviewed, and what you hope we will learn from the process?” 

That response shows confidence. You are not assuming blame. You are asking for clarity. 

Client: “So the key is not to panic, ask why, understand the scope, and use the findings as a roadmap?” 

Consultant: Exactly. An HR audit is not a declaration that something is wrong. It is a tool to understand where things stand and where they can be stronger. 

Audit is not a dirty word. Sometimes it is just the checkup your HR systems need before a real problem appears. 

And if you need help defining the scope, gathering documents, or turning audit findings into a practical action plan, we are here to help. 

Client: “I have a new employee who has only been here about 30 days, and they’re already asking about a promotion. They’re doing well so far, but it feels really soon. How do I respond without discouraging them?” 

Consultant: First, take a breath. Ambition is not a bad thing. In fact, it is great when a new employee is excited about growth. The caution is making sure enthusiasm does not outrun your systems. 

A promotion should not be based only on early energy, a strong first impression, or the fact that someone is eager. It should be based on clear standards, demonstrated readiness, and an actual organizational need. 

Client: “That makes sense. I don’t want to shut them down, but 30 days feels way too soon to know if they’re ready.” 

Consultant: Exactly. At 30 days, you may have a promising start, but you probably do not have enough information to confirm sustained performance. A promotion means the employee has consistently demonstrated the skills, judgment, reliability, and results needed for the next level. 

You might say: 

“I appreciate your interest in growing with us, and I’m glad you’re already thinking about your future here. Since you’re still early in your role, our focus right now is making sure you have a strong foundation. Let’s talk about what readiness for future opportunities looks like.” 

That keeps the door open without making a premature commitment. 

Client: “What if they say they already know the job and are ready for more?” 

Consultant: That is where clear measurement matters. Promotion decisions should be tied to defined criteria, not confidence alone. What does the next role require? What skills, outcomes, behaviors, or certifications must be demonstrated? Has the employee shown those things consistently over time? 

You might say: 

“I’m glad you’re feeling confident. For us to consider a promotion, we look at specific readiness factors, including performance in the current role, consistency over time, ability to work independently, decision-making, teamwork, and the requirements of the next position. Let’s use those as our guide.” 

This shifts the conversation from “I feel ready” to “Here is how readiness is measured.” 

Client: “I also worry that if I talk about growth, they’ll think I’m promising a promotion.” 

Consultant: That is an important distinction. Development conversations are not promises. You can support an employee’s growth while being clear that promotions depend on both readiness and business need. 

Try this: 

“I want to support your development, and I also want to be clear that a promotion depends on two things: demonstrated readiness and an available position that meets the organization’s needs. We do not create a promotion simply because someone is doing well; we promote when the role exists and the person is ready for it.” 

That is honest, kind, and practical. 

Client: “So I should be clear that there has to be an actual opening?” 

Consultant: Yes. This is a big one. A promotion is not just a reward for good performance. It is movement into a different role or level of responsibility. If there is no vacant position, no approved structure, or no business need for the higher-level work, then it may not be the right time. 

You might say: 

“Right now, we do not have a vacant position at that level. That does not mean growth is off the table. It means our next step is to focus on development, continued performance, and preparing you for future opportunities when they become available.” 

This avoids creating a job that the organization does not actually need. 

Client: “What should I give them instead of just saying no?” 

Consultant: Give them a roadmap. Identify what they should focus on over the next several months. That might include mastering core duties, learning additional systems, taking on a project, improving technical knowledge, or building communication and problem-solving skills. 

You could say: 

“Here are the areas I’d like you to focus on first: consistently meeting expectations in your current role, building depth in our processes, and demonstrating independent problem-solving. We can check in again at your 90-day mark and talk about what progress looks like from there.” 

That gives them something productive to work toward. 

Client: “What if they keep pushing?” 

Consultant: Stay steady. You can acknowledge their ambition while reinforcing the process. 

Try this: 

“I appreciate your motivation, and I do not want to discourage that. At the same time, promotion decisions have to follow our process. We need enough time to assess sustained performance, and there must be an available position that matches the business need.” 

This keeps the conversation from becoming personal. 

Client: “So the key is to encourage the ambition, but bring it back to the system?” 

Consultant: Exactly. A promotion conversation should never be based on pressure, enthusiasm, or fear of losing someone. It should be based on clear standards, consistent measurement, and the organization’s actual staffing structure. 

When you respond with clarity, the employee learns something important: growth is welcome here, but it is thoughtful, fair, and tied to real readiness. 

And if you need help building promotion criteria or career path language, we’re here to support you. 

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.