Juneteenth 2026: Freedom, Truth, and the Work of Moving Forward

On Friday, June 19, 2026, we observe Juneteenth National Independence Day, a federal holiday that commemorates June 19, 1865—the day Union troops arrived in Galveston, Texas, and announced that enslaved people there were free, more than two years after the Emancipation Proclamation had been issued. Today, Juneteenth stands as both a celebration of freedom and a reminder that freedom delayed is still injustice.  

Juneteenth carries deep historical meaning, and it also asks something of us in the present. It invites us to remember that progress is not always immediate, and that truth matters even when it arrives later than it should have. The National Museum of African American History and Culture describes Juneteenth as a time to celebrate, gather, reflect on the past, and look to the future. That feels especially important in organizations, where culture is built not only through policies and procedures, and through honesty, respect, recognition, and a willingness to keep improving.  

For many people, Juneteenth is a day of celebration—family gatherings, music, food, storytelling, and community. And it is also a day of education and reflection. It honors resilience, recognizes the contributions of Black Americans, and reminds us that history should be understood fully, not selectively. The holiday has long been celebrated in Black communities, and its growing national recognition creates a wider opportunity to learn, listen, and engage with greater care.  

In the workplace, Juneteenth can prompt useful reflection without turning into “messaging of the month”. Organizations do not need perfectly polished words as much as they need sincerity. This can be a moment to acknowledge the significance of the day, encourage learning, and consider whether the organization’s daily practices reflect fairness, dignity, and opportunity. A holiday post is nice. A culture that values truth, access, consistency, and respect is better. 

That is where the meaning of Juneteenth can connect to organizational life in a very real way. Freedom and inclusion are not abstract ideas when people are making decisions about hiring, development, communication, pay practices, employee relations, and who feels heard. Healthy organizations keep asking important questions: Are expectations clear? Are opportunities fair? Are concerns addressed? Are people treated with dignity? Those questions will not solve everything in one grand gesture, and they are part of how meaningful progress happens over time. 

Juneteenth reminds us that milestones matter, and so does the work that comes after the milestone. Recognition matters. Education matters. Action matters. And in organizations, that often looks less like a dramatic announcement and more like steady, values-based choices repeated over and over again. 

As we observe Juneteenth 2026, may we take time to celebrate freedom, honor history, and continue the work of building organizations and communities where people are respected, included, and able to move forward with confidence. 

 

The Skills No One Taught Us: Why Emotional Intelligence Matters More Than Ever

When most people think about professional development, they often think about technical skills. 

Learning new software. 

Understanding regulations. 

Improving project management. 

Developing industry expertise. 

And while those skills absolutely matter, they are only part of what determines success in today’s workplace. 

The reality is that many workplace challenges have less to do with technical ability and more to do with how we interact with others. 

Think about the situations that create the most stress, frustration, and conflict at work: 

  • Miscommunication between coworkers
  • Difficult conversations with employees 
  • Navigating organizational change 
  • Giving and receiving feedback 
  • Managing emotions during stressful situations 
  • Building trust within teams 
  • Responding professionally when we disagree 

These are not technical challenges. They are emotional intelligence challenges. 

What Is Emotional Intelligence? 

Emotional intelligence (EQ) is the ability to recognize, understand, and manage our own emotions while also understanding and responding effectively to the emotions of others. 

In simple terms, emotional intelligence helps us respond thoughtfully instead of reacting emotionally. 

It helps us become more self-aware, more adaptable, and more effective in our relationships with others. 

Individuals with strong emotional intelligence are often better able to: 

  • Communicate effectively 
  • Build trust 
  • Manage conflict 
  • Navigate change 
  • Demonstrate empathy 
  • Lead others 
  • Work collaboratively as part of a team 

These skills are valuable regardless of your title. Whether you are an individual contributor, supervisor, manager, executive, or business owner, emotional intelligence influences how others experience working with you. 

Why Emotional Intelligence Matters More Than Ever 

For years, organizations often promoted employees based primarily on technical expertise, experience, or even longevity. 

Today, that is changing, it has to! 

As artificial intelligence continues to automate routine tasks and provide information faster than ever before, the skills that make us uniquely human are becoming increasingly valuable. 

Recent research suggests that employers are placing greater emphasis on leadership capabilities such as adaptability, resilience, emotional intelligence, communication, and relationship-building. As technology becomes more sophisticated, employees are looking to leaders for something technology cannot provide: trust, empathy, clarity, and connection. 

In other words, employees are not simply looking for answers. 

They are looking for leaders who can help them navigate uncertainty. 

Emotional Intelligence Is Not Just for Leaders 

One of the biggest misconceptions about emotional intelligence is that it only matters for people in leadership positions. The truth is that emotional intelligence affects every workplace interaction and at every level. 

It influences: 

  • How we respond to feedback 
  • How we handle stress 
  • How we participate in meetings 
  • How we resolve disagreements 
  • How we support coworkers 
  • How we build credibility and trust 

Strong emotional intelligence helps us become better coworkers, better team members, better communicators, and better problem-solvers. 

It can even influence career growth. 

Often, the people who are promoted are not simply the most technically skilled. They are the individuals who can work effectively with others, navigate difficult situations, build relationships, and create positive influence. 

The Good News: Emotional Intelligence Can Be Developed 

Unlike personality traits, emotional intelligence is not fixed. 

It can be learned. 

It can be practiced. 

It can be strengthened over time. 

It is a muscle that can be flexed and developed over time as long as you keep working on it. Developing emotional intelligence begins with a willingness to reflect on our own behaviors, reactions, strengths, and growth opportunities. 

The most emotionally intelligent individuals are not perfect. They are simply committed to learning, growing, and becoming more intentional in how they respond to the people and situations around them. 

A Question for Reflection 

As you think about your own professional growth, consider: 

Which area of emotional intelligence would have the greatest positive impact on your effectiveness at work right now

  • Self-awareness? 
  • Managing emotional reactions? 
  • Motivation and resilience? 
  • Empathy? 
  • Relationship management? 

The answer may provide a valuable starting point for your development journey. 

We invite you to join us. HR Answers is excited to offer our new five-part learning series: 

The Skills No One Taught Us: Emotional Intelligence for Work and Leadership 

Beginning July 22, 2026, this series explores the five core components of emotional intelligence: 

  • Self-Awareness 
  • Self-Management 
  • Motivation 
  • Empathy 
  • Relationship Management 

Whether you lead others or contribute as part of a team, emotional intelligence is one of the most valuable investments you can make in your professional growth. 

Learn more and register here: https://hranswers.trainercentralsite.com/all-courses 

The future workplace will continue to evolve. Technology will continue to advance. 

But one thing remains true: 

As work becomes more automated, the ability to connect, communicate, understand, and lead people will only become more valuable. 

#EmotionalIntelligence #LeadershipDevelopment #ProfessionalDevelopment #WorkplaceCulture #LeadershipSkills #FutureOfWork #HumanSkills #WorkplaceSuccess #EQMatters 

HR Operations & Maintenance: Hiring and Onboarding Processes

Hiring problems don’t usually start with the offer. They start earlier—when processes are rushed, expectations are unclear, or onboarding is treated as an afterthought instead of a system. 

Most organizations hire people. Fewer maintain their hiring and onboarding processes with the same care they give to pay, performance, or compliance. Over time, shortcuts become habits, and habits become risk. 

That’s why hiring and onboarding belong in HR Operations & Maintenance (O&M). These are not one-time events. They are repeatable systems that deserve regular attention. 

 

What We Mean by Hiring and Onboarding Maintenance 

Maintenance in this area is not about hiring more often or onboarding more thoroughly every time. It’s about ensuring the process works consistently, regardless of who is doing the hiring or when it happens. 

At a high level, maintenance asks: 

  • Are hiring decisions made using clear, job-related criteria? 
  • Are processes applied consistently across roles and locations? 
  • Do new employees understand expectations early? 
  • Are compliance steps completed reliably, not retroactively? 

When these answers depend on the manager or the urgency of the hire, the system needs attention. 

 

Where Hiring Systems Commonly Drift 

Drift often shows up in subtle ways: 

  • Interview questions vary widely by interviewer 
  • Hiring criteria live in conversations, not documentation 
  • Background checks or references are handled inconsistently 
  • Offers are rushed without clear approval steps 
  • Job descriptions used for hiring don’t match the role being filled 

Over time, this creates inconsistency, risk, and frustration—especially when hires don’t work out as expected. 

 

Onboarding Is More Than Orientation 

Orientation introduces someone to the organization.
Onboarding integrates them into it. 

A maintained onboarding system helps new employees understand: 

  • What success looks like in their role 
  • How decisions are made 
  • Where to go for support 
  • What policies and processes actually matter day to day 

When onboarding is inconsistent, new employees fill in gaps on their own—and those assumptions can last a long time. 

 

Why Hiring and Onboarding Are Linked to Retention 

Early experiences shape expectations. 

Clear hiring processes: 

  • Set realistic job previews 
  • Reduce misalignment between role and reality 
  • Support equitable selection decisions 

Strong onboarding: 

  • Builds confidence and connection 
  • Reduces early turnover 
  • Reinforces performance and accountability systems 

Maintenance here is preventive work—it reduces issues before they need correction. 

 

Quick Self-Check: Hiring and Onboarding 

This is a snapshot, not an audit. 

Ask yourself: 

  • Do we use consistent criteria to evaluate candidates for the same role? 
  • Are job descriptions actively used during recruitment and selection? 
  • Do managers know what steps must happen before an offer is made
  • Is onboarding structured beyond the first day or week? 
  • Do new employees understand expectations within their first 30–60 days? 

If most of these feel solid, your system is likely being maintained.
If several raise questions, that’s a signal that a tune-up may be due. 

 

Best-Practice Guardrails for Maintenance 

Organizations with durable hiring and onboarding systems tend to: 

  • Use structured, job-related interview approaches 
  • Document hiring decisions and approvals 
  • Coordinate HR, payroll, and IT steps in advance 
  • Provide managers with onboarding guidance and timelines 
  • Revisit onboarding content as roles and expectations change 

Consistency does not eliminate flexibility. It creates fairness and clarity. 

 

For Those Wearing the HR “Hat” 

If HR is one of several responsibilities you manage, hiring can feel especially urgent—and onboarding can fall behind quickly. 

A maintenance mindset helps by: 

  • Reducing last-minute decision-making 
  • Giving managers clear steps to follow 
  • Supporting compliance without slowing hiring 
  • Helping new employees get up to speed faster 

You don’t need a perfect process. You need one that works reliably. 

 

For Experienced HR Professionals 

For seasoned HR practitioners, hiring and onboarding maintenance is about alignment. 

Well-maintained systems: 

  • Support equitable hiring decisions 
  • Reduce early performance issues 
  • Strengthen documentation and defensibility 
  • Improve manager confidence and consistency 

This is foundational work that shapes outcomes long after the hire is made. 

 

How Support Can Help 

Hiring and onboarding support can include: 

  • Recruitment process reviews 
  • Interview and selection training 
  • Onboarding framework development 
  • Manager toolkits and timelines 
  • Advisory support for complex or high-risk hires 

Sometimes the most effective improvement is not doing more—it’s doing the same things more consistently. 

 

Looking Ahead 

Hiring and onboarding set the stage for everything that follows. In the next post, we’ll turn to Documentation and Recordkeeping Systems, and why maintenance in that area supports compliance, clarity, and continuity. 

Strong hiring systems don’t rely on luck.
They rely on structure—and maintenance keeps that structure working. 

— HR Answers 

Heat, Breaks, and Safety

Client: “We’re a small construction contractor with crews on several job sites. When it gets hot, employees start asking for extra breaks or saying it’s too hot to keep working. I want to keep people safe, and I also have deadlines. When does this become an HR issue?” 

Consultant: It becomes an HR issue the moment heat starts affecting employee safety, break practices, supervisor decisions, scheduling, documentation, communication, or consistency across job sites. 

In construction, heat safety is not just “drink some water and tough it out.” Oregon has specific heat illness prevention requirements that apply when employees work in indoor or outdoor environments where the heat index equals or exceeds 80°F. Oregon’s rules address shade, drinking water, high-heat procedures, rest break schedules, emergency planning, acclimatization, written plans, and training.  

For a smaller contractor with multiple projects, the challenge is not only knowing the rule. It is making sure the foreperson at Site A, the lead at Site B, and the project manager at Site C are all applying it the same way. 

Client: “So if someone says, ‘It’s too hot,’ do we have to stop the whole job?” 

Consultant: Not automatically. And you do need to take the concern seriously. 

Start by checking the actual conditions at the site. Oregon’s heat rule is based on heat index, not just the temperature on the weather app. Heat index considers temperature and humidity, and site conditions can vary. A roofing crew, asphalt crew, framing crew in direct sun, or crew working in an enclosed structure without ventilation may experience very different heat exposure than someone unloading materials in partial shade. 

You might tell your supervisor: 

“Do not debate whether someone is being dramatic. Check the heat index, look at the work being performed, confirm water and shade are available, and follow the heat illness prevention plan.” 

That gives supervisors a process instead of leaving them to make judgment calls in the moment. 

Client: “What are the Oregon basics we need to remember?” 

Consultant: In Oregon, when the heat index reaches 80°F, employers must provide shade that is immediately and readily available to outdoor workers, located as close as practical to the work area, and large enough for employees on rest or recovery periods. Employers must also ensure a sufficient supply of cool or cold drinking water, at no cost, and enough for employees to consume up to 32 ounces per hour.  

When the heat index reaches 90°F, high-heat practices come into play. Those include communication procedures, observation or check-in systems, emergency medical planning, and a written heat illness prevention rest break schedule. Oregon’s rule requires employers to choose one of three rest break schedule options, and the breaks are only required during the time the heat index equals or exceeds 90°F.  

A simple way to explain it to supervisors is: 

“At 80, we are in heat prevention mode. At 90, we are in high-heat procedure mode.” 

That is not the full legal analysis, and it is a helpful operational reminder. 

Client: “What about breaks? My supervisors are worried people will take advantage of this.” 

Consultant: That is where structure helps. Heat illness prevention breaks are not “whenever anyone feels like disappearing behind the equipment trailer.” They are part of a safety plan. 

Oregon allows employers to use one of three written rest break schedule options. One Oregon OSHA fact sheet describes the employer-designed minimum schedule as at least 10 minutes every two hours when the heat index is 90°F or greater, and 15 minutes every hour when the heat index is 100°F or greater, while noting that breaks may need to be longer or more frequent depending on PPE, work clothing, humidity, indoor or outdoor conditions, work intensity, and direct sun exposure. Oregon’s simplified schedule increases the break schedule as the heat index rises, including 20 minutes every hour at 95°F or greater, 30 minutes every hour at 100°F or greater, and 40 minutes every hour at 105°F or greater.  

So yes, breaks are required under certain conditions. And no, they should not be random, inconsistent, or dependent on whether a particular supervisor “runs a tough crew.” 

Client: “If the heat break happens during a regular paid rest break or meal period, does that count?” 

Consultant: It can, if the timing lines up and the break actually meets the heat safety purpose. Oregon’s rule allows heat illness prevention rest breaks to occur at the same time as other meal or rest periods required by policy, rule, or law when the timing coincides. The time must actually be spent in shade and not performing work, other than very limited “rest” or “light” work in a temperature-controlled setting. Except when the heat break coincides with an existing unpaid meal break, Oregon treats the heat illness prevention rest break as a work assignment.  

That matters for HR and payroll. The break schedule needs to be understood by supervisors, tracked consistently enough to demonstrate compliance, and handled correctly for pay purposes. 

Client: “We move crews between job sites. How do we manage this without making it a paperwork circus?” 

Consultant: Create a simple site-based heat checklist. Not a binder that lives in the office and has never seen daylight. Something your foreperson can actually use. 

For each project site, confirm: 

  • Who is responsible for checking the heat index?  
  • Where is the shade located?  
  • How is water supplied and replenished?  
  • Which rest break schedule applies?  
  • How are employees encouraged to drink water?  
  • How do workers contact a supervisor if they feel symptoms?  
  • Who can call emergency services?  
  • How are new or returning employees acclimatized?  
  • How are employees trained before heat exposure begins?  

Oregon’s rule requires a written heat illness prevention plan that includes training, symptom recognition and response, water, hydration encouragement, shaded or cool recovery space, rest break scheduling, and acclimatization procedures for new employees or employees returning after absences of seven or more days.  

For a small contractor, the goal is not to make this complicated. The goal is to make it repeatable. 

Client: “What about the federal rules? I keep hearing OSHA is working on heat standards.” 

Consultant: Federal OSHA has proposed a national heat injury and illness prevention rule, and the public hearing process concluded in 2025. As of now, OSHA describes the federal rule as proposed, not finalized. The proposed standard would apply broadly to outdoor and indoor work in general industry, construction, maritime, and agriculture where OSHA has jurisdiction.  

That does not mean federal OSHA is ignoring heat. OSHA continues to treat excessive heat as a serious workplace hazard, and its heat guidance encourages water, rest, and shade as prevention and response measures. OSHA also states that employers should provide cool drinking water, encourage workers to drink about one cup every 20 minutes while working in heat, and increase rest breaks as heat stress rises.  

So the practical message is this: Oregon employers already have specific state requirements. Federal OSHA also remains focused on heat hazards, even while the national rulemaking process continues. 

Client: “What should I tell supervisors who think employees just need to be tougher?” 

Consultant: I would be very direct. 

You might say: 

“Heat illness is not a toughness issue. It is a safety issue, a compliance issue, and a project management issue. We can plan for it, or we can react to it after someone gets sick.” 

Heat stress can move quickly from discomfort to a medical emergency. Oregon OSHA describes heat exhaustion symptoms as including dizziness, headache, rapid pulse, nausea, and vomiting, and heat stroke symptoms as including high body temperature, confusion, and convulsions. Heat stroke can be fatal.  

Supervisors do not need to diagnose anyone. They do need to recognize warning signs, respond quickly, and avoid creating a culture where employees are afraid to speak up. 

Client: “What if one crew is following the heat plan and another crew says they don’t have time?” 

Consultant: Then you have a consistency problem and a safety problem. 

This is where HR, operations, and project management need to work together. Heat safety cannot depend on which job site an employee is assigned to or which supervisor they happen to have that week. 

For multiple project sites, consider a simple daily communication: 

“Today’s expected heat index is ____. Crews must confirm water, shade, and the applicable rest break schedule before work begins. Supervisors must monitor employees for signs of heat illness and follow the heat illness prevention plan.” 

That message does a few things. It reminds supervisors of the requirement, creates a record of communication, and reinforces that heat prevention is part of the work plan — not an optional add-on when everyone is already overheated and cranky. 

Client: “What if employees refuse to take water or breaks?” 

Consultant: Supervisors need to encourage and enforce the safety process. Oregon requires employees to have ample opportunity to drink water and requires training that includes the importance of frequent consumption of small quantities of water, up to 32 ounces per hour, when the work environment is hot and employees are likely sweating more than usual.  

If employees resist, the supervisor can say: 

“I understand you want to keep moving. We are following the heat illness prevention plan. Take the break, drink water, and then we will get back to work safely.” 

This is no different than requiring fall protection, hard hats, or equipment safety procedures. Employees do not get to opt out of safety because they feel fine in the moment. 

Client: “So HR’s role is policy, training, and documentation?” 

Consultant: Yes, and also coordination. 

For a smaller construction contractor, HR may not be standing on every job site. And HR can still help build the system supervisors use. That includes: 

  • Updating the heat illness prevention plan.  
  • Making sure training happens annually and before employees are exposed to heat risk.  
  • Confirming training records are retained.  
  • Helping supervisors understand paid break implications.  
  • Creating simple job-site checklists.  
  • Coordinating with payroll when heat breaks affect timekeeping.  
  • Supporting consistent expectations across projects.  
  • Helping managers respond appropriately when employees report heat symptoms or safety concerns.  

This is one of those areas where HR does not replace operations. HR helps operations do the people, safety, communication, and compliance parts well. 

Client: “What’s the bottom line?” 

Consultant: Heat safety needs to be planned before the hot day arrives. 

For Oregon construction employers, “it’s too hot” is not just a comfort complaint. It may trigger specific obligations around shade, water, communication, rest breaks, emergency response, acclimatization, training, documentation, and consistent supervisor practices. 

The best approach is simple: know the heat index, prepare each job site, train supervisors, communicate expectations, and take employee concerns seriously. Crews can still get work done. They need to do it in a way that protects people first. 

And if you need help building a practical heat illness prevention plan, training supervisors, or creating job-site tools that work outside the office and in the actual dirt, dust, and deadlines of construction, we’re here to help. 

 

2026 FUN Series: U = Understanding Does Not Require Agreement

U = Understanding Does Not Require Agreement 

Before we go any further, a reminder of what FUN means in this series. 

FUN is not about forced smiles, mandatory participation, or trying to make work something it isn’t. FUN is about creating workplaces where people are allowed to be human — where emotions are acknowledged, curiosity replaces assumptions, and connection is offered without pressure. 

That’s why FUN stands for Feelings · Understanding · No Pressure

And today, we return to Understanding. 

 

Understanding Does Not Require Agreement 

One of the quickest ways conversations shut down at work is the belief that understanding means agreeing

It doesn’t. 

Understanding means being willing to listen, ask questions, and acknowledge another perspective — even when the final decision stays the same. 

FUN organizations know that respect survives disagreement when curiosity leads. 

 

Where This Often Breaks Down 

In many workplaces, disagreement triggers: 

  • Defensiveness 
  • Position-taking 
  • Talking over one another 
  • A rush to “solve” instead of listen 

When people feel unheard, they stop contributing. They comply, disengage, or withdraw altogether. 

Understanding keeps people at the table. 

 

What FUN Looks Like with Disagreement 

In FUN organizations: 

  • People explain their reasoning without being dismissed 
  • Different views are explored before decisions are made 
  • Respectful disagreement is treated as a strength 
  • Tone matters as much as content 

Understanding lowers the emotional stakes of disagreement. It allows conversations to stay professional and human at the same time. 

 

The FUN Challenge: Understanding (Without Agreement) 

This month, practice listening to understand — not to respond. 

Try: 

  • “I don’t see it the same way, and I appreciate hearing your perspective.” 
  • “That helps me understand where you’re coming from.” 
  • “I hear what you’re saying, even though we’re going a different direction.” 

Say it.
Mean it.
Then move forward. 

 

Why This Matters 

People don’t need consensus to feel respected.
They need to feel heard. 

When understanding becomes the goal, trust grows — even in moments of disagreement. And when trust grows, FUN continues to exist without pressure. 

 

Coming Up Next in the FUN Series… 

Next, we move to N = No Pressure — and why participation is not the same thing as performance. 

 

2026 FUN Series: F = Appreciation Is a Feeling, Not a Program

F = Appreciation Is a Feeling, Not a Program 

Before we go any further, a reminder of what FUN means in this series. 

FUN is not about forced smiles, mandatory participation, or trying to make work something it isn’t. FUN is about creating workplaces where people are allowed to be human — where emotions are acknowledged, curiosity replaces assumptions, and connection is offered without pressure. 

That’s why FUN stands for Feelings · Understanding · No Pressure. 

And today, we’re back to Feelings

 

Appreciation Is a Feeling, Not a Program 

Most organizations value appreciation.
Many even have a recognition program to prove it. 

And still — appreciation often misses the mark. 

That’s because appreciation is not a process, a platform, or a once-a-year event. Appreciation is a feeling, and feelings don’t respond well to scripts. 

FUN organizations understand that appreciation works best when it feels real, timely, and personal. 

 

Where Appreciation Goes Sideways 

Appreciation loses impact when it becomes: 

  • Generic 
  • Delayed 
  • Transactional 
  • Tied only to outcomes 

“Great job, everyone” is kind.
“I noticed how you handled that difficult conversation” lands differently. 

One acknowledges effort.
The other acknowledges humanity. 

 

What FUN Looks Like with Appreciation 

In FUN organizations: 

  • Thanks are specific 
  • Effort is noticed, not just results 
  • Appreciation shows up in ordinary moments 
  • Recognition feels natural, not performative 

This kind of appreciation doesn’t require approval or a budget. It requires attention. 

 

The FUN Challenge: Feelings (Appreciation Edition) 

This month, offer one piece of appreciation that focuses on how someone showed up. 

Try: 

  • “I really appreciated how thoughtful you were in that meeting.” 
  • “Thank you for staying steady when things got stressful.” 
  • “Your follow-through made a difference.” 

Say it.
Send it.
Then move on. 

No announcement.
No scoreboard.
No pressure. 

 

Why This Matters 

People don’t need constant praise.
They do want to know they matter. 

When appreciation is felt, not performed, it strengthens trust. And when trust grows, FUN has room to exist — quietly and consistently. 

 

Coming Up Next in the FUN Series… 

Next, we shift to U = Understanding — and why respect can hold steady even when people disagree. 

Brilliant and Brutal (managing a high performer who’s harming the team)

Client: 
“I have an employee who is incredibly good at their job. They hit goals, solve problems fast, and honestly, they’re one of the strongest performers on the team. The problem is… they leave a trail of damage behind them. They’re dismissive, impatient, and people are starting to avoid working with them. How do I deal with a high performer who’s harming the team?” 

Consultant:
When someone produces strong individual results, it is tempting to excuse the behavior that comes with it. After all, they are getting things done. The problem is that performance is not just about what gets done. It is also about how the work gets done and what it costs the rest of the team. 

An employee who damages trust, shuts people down, or creates tension is not really a high performer. They may be delivering in one lane while undermining the larger success of the organization. 

Client: 
“That makes sense, and I worry I may have let it go too long because their work product is so strong. How do I start addressing it now without sounding like I’m punishing excellence?” 

Consultant:
Start by separating output from behavior. You can acknowledge their strengths and be very clear that technical skill does not excuse conduct that hurts teamwork. 

You might say:
“You bring strong skills and valuable results to the team, and I want to be equally clear that how you work with others matters just as much. I need to talk with you about the impact your approach is having on the team.” 

That opening does two important things: it recognizes reality, and it signals that this is not a personality critique. It is a workplace expectation conversation. 

Client: 
“What if they say, ‘I’m just direct,’ or ‘I’m not here to babysit people’s feelings’?” 

Consultant:
That response is common. People who pride themselves on being blunt often frame the issue as everyone else being too sensitive. Do not argue about intent. Stay focused on impact. 

Try this:
“I understand that you may see your style as direct and efficient. What I need you to understand is that the impact is creating tension, shutting down collaboration, and making it harder for the team to work effectively. Regardless of intent, that impact needs to change.” 

That keeps the conversation grounded in observable workplace effects rather than a debate over personality. 

Client: 
“What kinds of behaviors should I be talking about? I do not want to be vague.” 

Consultant:
Specificity matters here. General statements like “people feel uncomfortable” are easy to dismiss. Focus on examples of observable behavior. 

For example: 

  • interrupting others in meetings 
  • dismissing ideas before discussion 
  • sending sharp or overly critical emails 
  • correcting coworkers in a way that embarrasses them 
  • refusing collaboration because they believe others are slower or less capable 

You could say:
“In the last two team meetings, you interrupted others before they finished their thoughts. I have also seen email responses that came across as dismissive rather than solution-focused. Those behaviors affect trust and teamwork.” 

The clearer you are, the harder it is for them to write it off as vague feedback. 

Client: 
“What if the rest of the team is quietly tolerating it because this person is so good at the work?” 

Consultant: 
That happens all the time, and it is exactly why this issue matters. Teams will sometimes adapt around a difficult high performer by avoiding them, withholding ideas, or keeping concerns to themselves. On the surface, things may still look productive. Underneath, you are losing collaboration, innovation, and psychological safety. 

This is where managers have to remember a foundational truth: performance is not only individual production. It includes contribution to the work environment. If one employee’s brilliance causes others to disengage, the team is paying a price. 

Client: 
“So I need to make it clear that teamwork is part of the job, not some bonus trait?” 

Consultant:
Exactly. 

You might say:
“Your role is not only to produce strong work. It also includes working in a way that supports the team’s success. Collaboration, professionalism, and respect are part of performance expectations here.” 

That helps reposition the conversation. You are not asking them to be less capable. You are asking them to be fully effective. 

Client:
“What if they push back and say the rest of the team just needs to perform at a higher level?” 

Consultant:
Even if there is some truth buried in that frustration, it does not excuse poor conduct. High standards and disrespect are not the same thing. 

You can say:
“If there are performance concerns with others, that is something management can address. What I am talking with you about today is your responsibility for how you communicate, collaborate, and contribute to the team dynamic.” 

This keeps them from hijacking the conversation and turning it into a complaint session about coworkers. 

Client:
“How do I avoid making this a one-and-done conversation that changes nothing?” 

Consultant:
You need to define what improvement looks like. “Be nicer” is too fuzzy. Give them concrete expectations. 

For example: 

  • allow others to finish before responding 
  • ask at least one clarifying question before disagreeing 
  • give feedback privately when possible 
  • use solution-focused language in meetings and email 
  • raise concerns without sarcasm, ridicule, or dismissal 

You might say:
“Moving forward, I need to see respectful communication, stronger collaboration, and a more constructive approach when you disagree with others. Let’s talk specifically about what that looks like in your day-to-day interactions.” 

This creates a path forward instead of just a warning. 

Client:
“Should I document this, even though they are technically a strong performer?” 

Consultant:
Yes. Absolutely. 

When behavior affects the team, documentation matters. Note the specific concerns discussed, examples shared, expectations set, and follow-up timing. Documentation is not only for poor technical performers. It is also for employees whose conduct is creating workplace problems. 

In fact, high performers can be harder to address later if there is no record, because people tend to point to the good results and overlook the interpersonal cost. 

Client: 
“What if they improve for a week or two and then slide right back into old habits?” 

Consultant:
Then you treat it like any other repeated performance issue. Coaching first, then accountability. Improvement has to be sustained, not temporary. 

You could say:
“We talked about the need for more constructive interactions, and I saw some early improvement. I am now seeing the same behavior patterns return. This needs to become a consistent change, not a short-term adjustment.” 

That reinforces that the expectation did not expire after the first conversation. 

Client:
“And if they still do not change?” 

Consultant: 
Then the organization has to decide whether it truly means what it says about culture, teamwork, and respect. If someone continues to harm the team after clear coaching, examples, expectations, and follow-up, the issue moves from coaching to corrective action. 

You might say:
“We have discussed the impact of your behavior, and I have not seen the consistent improvement needed. At this point, this is a performance issue, and continued concerns will lead to formal corrective action.” 

That is not punishing talent. That is holding someone accountable for the full scope of their job. 

Client: 
“So the bottom line is that strong results do not cancel out harmful behavior?” 

Consultant: 
Exactly. A truly strong performer adds value without making everyone around them pay for it. Managers get into trouble when they confuse technical excellence with overall effectiveness. 

The goal is not to lower standards. The goal is to make sure high standards and healthy workplace behavior can exist at the same time. That is where real team performance lives. 

And if you need help sorting out whether you are looking at a coaching issue, a conduct issue, or the beginning of formal corrective actions, we can help. 

Pride Month 2026: Respect Starts with Our Shared Humanity

June is Pride Month, and like many recognition months, it gives us a reason to pause and think a little deeper about people, history, and what it really means to create a workplace where everyone can feel seen, safe, and respected. 

There is real meaning in Pride Month. It reflects visibility, identity, advocacy, and the very real history behind why protected classes matter in the first place. Those protections did not appear because people were naturally doing a great job of treating one another fairly. They came into being because too many people were excluded, judged, dismissed, or treated as less than. That matters, and it should. 

And still, I find myself coming back to something simpler. 

We are all human. 

That does not erase difference, and it does not minimize the fact that people have different lived experiences, identities, and considerations. Those things are real, and they matter. They shape how people experience the world and, sometimes, how the world responds to them. 

And at the same time, I do not think the answer is found in creating more and more ways to sort ourselves into separate groups. I understand why labels matter. I understand why language evolves. I understand why visibility is important. I am not discounting any of that. 

I just believe there is a danger in getting so focused on labels, letters, categories, and synonyms that we accidentally feed an “us” and “them” mentality. That is not where belonging grows. That is not where connection grows. That is not where culture gets stronger. 

For me, the anchor is respect.  Simple to say. Not always easy to practice.  

Respect is how we talk to people.
Respect is how we listen.
Respect is how we respond when someone’s experience is different from our own.
Respect is how we handle disagreement without diminishing someone’s humanity.
Respect is how we build workplaces where no one has to wonder whether they will be treated fairly. 

To me, that is where the real work lives. 

Not in having the trendiest language.
Not in trying to keep up with every new term out of fear of getting something wrong.
Not in one month of polished messaging. 

The real work is in whether people experience dignity in the day-to-day. 

Do all people feel welcome?
Do all people feel safe?
Do all people feel like they can show up as themselves without being reduced to one characteristic?
Do all people believe they will be treated with professionalism and basic human decency? 

That is the test. 

An inclusive organization does not ignore history, and it does not ignore the need for legal protections. It does not pretend everyone has had the same experience. And it also does not lose sight of the bigger truth that every person deserves respect because they are a person. 

Pride Month can absolutely be a time of recognition and reflection. It can also be a reminder that while people may carry different identities and experiences, no one should be treated like an outsider, a problem to solve, or a category before a human. 

Respect is the standard. 

Because when respect is present, people are more likely to feel valued. When people feel valued, trust grows. When trust grows, culture gets stronger. And when culture gets stronger, the organization is better for every single person in it.