Author: Laurie Grenya

FMLA, State-Specific Leave, Sick Time, and Paid Leave: What Applies, What Stacks, and What Doesn’t 

Client: “I have an employee who needs time off for a medical issue. I know we may have FMLA, state leave, sick time, and maybe paid leave involved. I’m not sure what applies, what runs at the same time, and what we’re supposed to tell the employee. Help?” 

Consultant: Employee leave is a little like lasagna: lots of layers, and it only works if you know what is in each one. 

FMLA may be one layer. State-specific leave may be another. Sick time may provide pay. A paid leave program may provide wage replacement. Your own policy may add another layer. And somewhere in there, the ADA interactive process may need a seat at the table. 

The goal is not to memorize every leave law in the moment. The goal is to slow down, identify the layers, and understand which ones apply, which ones run together, and which ones must be tracked separately. 

Client: “So I shouldn’t just say, ‘You’re on FMLA’ and call it good?” 

Consultant: Correct. FMLA may be part of the answer, and it may not be the whole answer. 

Leave analysis starts with the reason for the absence. Is the employee out for their own serious health condition? Caring for a family member? Bonding with a new child? Managing pregnancy-related limitations? Requesting safe leave? Using sick time for a short-term illness? Each answer may point to a different layer. 

That is why the first response should usually be process-based, not conclusion-based. 

You might say: 

“Thank you for letting us know. We’ll review what leave options may apply based on the reason for your absence, your eligibility, and the information needed to support the request.” 

That buys HR the time needed to review the situation correctly without promising the wrong thing. 

Client: “Can you give me an example of the layers?” 

Consultant: Oregon is a great example because it shows how quickly this gets complicated. 

For Oregon employers, an absence may require review under several possible layers: 

• FMLA: federal job-protected leave. For private employers, FMLA generally applies at 50 or more employees; public agencies and schools are covered regardless of employee count.  

• Paid Leave Oregon: wage replacement and possible job protection. It applies broadly to Oregon employers and employees.  

• OFLA: Oregon job-protected leave. OFLA generally applies to employers with 25 or more employees.  

• Oregon Sick Time: paid sick time generally applies at 10 or more employees, or 6 or more employees if the employer has a Portland location. Smaller employers are required to provide protected, unpaid sick time.  

• ADA/Oregon disability accommodation: the federal ADA generally applies at 15 or more employees, and Oregon disability accommodation obligations generally apply at 6 or more employees.  

• Employer policy or union agreement: PTO, vacation, sick leave, benefit continuation, and return-to-work rules may add another layer.  

That does not mean every absence qualifies under every law. It means HR needs to review the possible layers before giving a final answer. 

Client: “If an employee qualifies for more than one leave, do they get all of them stacked on top of each other?” 

Consultant: Sometimes leave runs at the same time. Sometimes it does not. That is the tricky part. 

Some leave laws provide job protection. Some provide pay or wage replacement. Some provide both. Some may run together. Some must be tracked separately. 

Oregon gives us a good example: OFLA does not run concurrently with Paid Leave Oregon. So if an employee is using Paid Leave Oregon, they are not also using OFLA for that same time period. However, OFLA may still matter before or after Paid Leave Oregon, depending on the reason for leave and the employee’s eligibility. 

For example, an employee may use Paid Leave Oregon for a qualifying medical or family leave reason. Once that Paid Leave Oregon time is exhausted, the employee may still qualify for a separate OFLA-protected leave reason, such as sick child leave, bereavement leave, or pregnancy disability leave. 

A Paid Leave Oregon approval is important. It may address wage replacement and may include job protection depending on eligibility, and it does not end the employer’s analysis. HR still needs to review whether other layers apply, including FMLA, Oregon sick time, employer policy, collective bargaining agreement provisions, and disability accommodation obligations. 

That does not mean additional leave automatically applies. It means HR should not assume the leave analysis is finished just because one layer has been approved or used. 

Client: “What about sick time? Employees often say they want to use sick time first and save protected leave.” 

Consultant: That is a common misunderstanding. Sick time may provide pay. Protected leave may protect the time away from work. Those are different questions. 

A simple explanation is: 

“Sick time may apply to pay during your absence, and protected leave may also apply to the reason you are away from work. We are required to review whether the absence qualifies under applicable leave laws, even when paid time is available.” 

That helps employees understand it is not always either/or. 

Client: “What should managers do when an employee mentions a medical issue or need for leave?” 

Consultant: Managers do not need to become leave law experts. They do need to know when to pause and involve HR. 

A good manager response sounds like: 

“Thank you for letting me know. I’m going to connect with HR so we can make sure you receive the right information about leave options and next steps.” 

Managers should avoid promising approval, denying leave, asking for medical details, or telling employees they do not qualify unless HR has completed the review. 

Client: “So what is the practical takeaway?” 

Consultant: Use a leave map. It can be simple. For each leave request, identify: 

• The reason for the absence;  

• The employee’s work location;  

• The employer coverage thresholds;  

• The employee’s eligibility;  

• Whether the leave is paid, protected, or both;  

• Whether leaves run together or separately; and  

• What communication or documentation is needed.  

That small step can prevent big mistakes. 

Client: “So the bottom line is: don’t guess, identify the layers?” 

Consultant: Exactly. Employee leave has layers. FMLA, state-specific leave, paid leave programs, sick time, employer policy, union agreements, and accommodation obligations may all show up in the same conversation. That does not mean they all work the same way. 

Leave administration is one of those HR areas where “close enough” can create real problems. A good process helps employees receive the protections and pay they are entitled to, and it helps the organization apply the rules consistently. 

And if your leave layers are starting to slide around the pan, we can help. HR Answers can assist with leave mapping, policy review, manager training, and practical tools to help your team understand what applies, what stacks, and what needs to be tracked separately. When there is a lot to consider, or you’re just not sure- we are here to help. 

Client: “We have a student who wants experience, and we were thinking of bringing them in as an unpaid intern. We’ve also tossed around calling a few roles ‘volunteer’ positions to help with staffing. That should be okay as long as everyone agrees, right?” 

Consultant: Be careful! Organizations can get themselves in trouble fast. A person is not automatically an unpaid intern or a volunteer just because everyone uses that label. If the person is really functioning like an employee, wage and hour laws may treat them like one. Under federal law, for-profit employers generally must pay employees, and unpaid internships at for-profit organizations are evaluated using the U.S. Department of Labor’s “primary beneficiary” test. (DOL) 

Client: “Okay, so what makes an unpaid internship legitimate?” 

Consultant: For a for-profit organization, the question is whether the intern is the primary beneficiary of the relationship. The Department of Labor points to seven factors, including whether there is a clear understanding there is no expectation of pay, whether the internship looks like an educational experience, whether it is tied to coursework or academic credit, whether it works around the academic calendar, whether it is limited to the learning period, whether the intern complements rather than displaces paid staff, and whether there is no entitlement to a paid job at the end. No single factor controls, and the analysis depends on the full picture.  

Client: “So if they’re mostly helping us catch up on filing, answering phones, or covering regular work, that’s probably not great?” 

Consultant: Correct. Once the “internship” starts looking like free labor for work you otherwise would assign to employees, your risk goes up. One of the biggest warning signs is when the intern is doing productive work that replaces or reduces the need for paid staff rather than receiving a structured learning experience.  

Client: “What about nonprofits or public organizations? Can they use volunteers more freely?” 

Consultant: They have more flexibility, and there are still rules. Federal guidance recognizes true volunteers in charitable, religious, civic, humanitarian, and public-service settings when the service is offered freely and without expectation of compensation. The guidance also says volunteers typically should not displace regular employees or perform work that would otherwise be done by regular workers.  

Client: “That sounds promising. We are a non-profit.  Could we have an existing employee volunteer a few extra hours in the same department?” 

Consultant: That is one of the classic traps. Federal guidance says paid employees of a nonprofit and public agencies generally cannot “volunteer” to do the same type of services for their employer on an unpaid basis. 

Client: “What if the person says they don’t mind not getting paid because they just want experience?” 

Consultant: Intent helps explain the relationship, and it does not override the law. A friendly agreement does not make an unlawful unpaid arrangement lawful. If the role functions like a job, the organization may owe wages regardless of what the person agreed to. That is why structure matters so much.  

Client: “What should we be asking before we launch any internship or volunteer role?” 

Consultant: Start here: 

• Who primarily benefits from the arrangement—the learner or the organization? 

• Is there a real educational component with defined learning goals? 

• Is it tied to a school program, academic credit, or a training plan? 

• Is the work limited in duration and built around learning? 

• Are we avoiding using this person to fill a staffing gap? 

• If this is called a volunteer role, is it truly voluntary and appropriate for our organization type? 

• Is this person already our employee doing the same kind of work? 

If those answers get fuzzy, the safer path is often to make it a paid role. 

Client: “We’re in Oregon. Is there anything else we should keep in mind?” 

Consultant: Yes. Oregon BOLI says bona fide internships and training programs may be exempt from minimum wage and overtime requirements, and civil rights protections still apply. BOLI also says that student learners whose work experience does not meet the criteria for trainee status are employees entitled to the full protections of Oregon wage laws. That means the label matters far less than the facts. (Oregon) 

Client: “So the real lesson is don’t use ‘intern’ or ‘volunteer’ as a budget strategy?” 

Consultant: Exactly. “Unpaid” is not a shortcut. It is a classification decision with real legal consequences. When organizations get this wrong, the risk can include unpaid wages, overtime exposure, recordkeeping issues, and a messy explanation for why someone doing real work was never treated like an employee in the first place. The better approach is to design the role intentionally, document the purpose, and pressure-test it before the person starts. (DOL) 

Client: “That makes sense. So the key is to evaluate the relationship, not just the title?” 

Consultant: Exactly. If it is truly a learning experience, build it that way. If it is really work that helps your organization operate, pay for it accordingly. Clear planning on the front end is much easier than cleaning up a misclassification problem later. 

And if you need help reviewing an internship idea, pressure-testing a volunteer model, or deciding whether a role should really be paid, we’re here to help. Reach out anytime.  

Client: “Employees have started asking about Summer Fridays, alternate schedules, and other summer flexibility ideas. I like the thought of doing something positive for morale, and I am worried it is going to become a fairness fight the minute not every job can do the same thing.” 

Consultant: That concern is valid, and honestly, it is a good sign. It means you already see the issue clearly. Summer flexibility sounds simple until it lands in a workplace where coverage still matters, service still matters, and employees have strong opinions about what fairness should look like. 

That is why this is less about Summer Fridays and more about seasonal flexibility planning. 

Client: “That feels like a better way to frame it. Summer Fridays sound fun until everyone starts measuring who got what.” 

Consultant: Exactly. Once flexibility starts sounding like a benefit, many employees naturally shift into “everyone should get the same thing” thinking. The challenge is that work is not always the same, and trying to force identical flexibility onto very different roles can create more frustration than goodwill. 

So the better question is not, “How do we give everyone the same summer perk?”
The better question is, “What kinds of flexibility can our organization realistically support, and how do we plan for that in a way that is clear and consistent?” 

Client: “So where do we start?” 

Consultant: Start with the work, not the wish list. 

Before offering seasonal flexibility, identify what still has to happen no matter how sunny the weather gets. Ask: 

• What hours must be covered? 

• What services must remain uninterrupted? 

• What work is time-sensitive? 

• Which roles require an in-person presence? 

• Which duties have more flexibility in when the work gets done? 

Those answers matter because flexibility that creates service gaps, coverage gaps, or coworker resentment is not really flexibility. It is delayed frustration. 

Client: “That sounds like where managers can get into trouble if they just start saying yes one person at a time.” 

Consultant: Exactly right. If managers solve it one request at a time, employees will compare notes, and soon the issue is not flexibility. The issue is favoritism, inconsistency, and who had the boldness to ask first. 

This is why organizations need a framework before the summer schedule chatter turns into workplace mythology. 

Client: “What kind of framework?” 

Consultant: One that answers a few practical questions before anyone starts leaving at noon on Fridays. 

For example: 

• What flexibility options are actually on the table? 

• Are they temporary or ongoing through the season? 

• Are they role-based, team-based, or individually approved? 

• What level of performance and dependability is required? 

• Who reviews and approves the request? 

• Under what circumstances can the arrangement be adjusted or ended? 

This keeps flexibility tied to work realities instead of manager mood or employee negotiation skills. 

Client: “I like that. It also feels less risky than announcing Summer Fridays and hoping for the best.” 

Consultant: Hope is not a scheduling strategy. 

A smarter approach is to think more broadly. Seasonal flexibility can take many forms depending on the work. It might include adjusted start and end times, compressed schedules, rotating lighter Fridays, fewer internal meetings on Fridays, occasional remote work where duties support it, or short-term pilot arrangements with clear expectations. 

The point is to ask, “What could work here?” instead of “How do we copy the same arrangement everywhere?” 

Client: “That seems like a better message for employees too.” 

Consultant: It is, because it is more honest. Not every role will flex in the same way, and pretending otherwise usually backfires. Employees do not need a fairy tale. They need a process that makes sense. 

You might say: 

“As we look at seasonal flexibility, we are reviewing operational needs, service expectations, and the nature of each role. Our goal is to identify flexibility options that support the work and apply a consistent process when determining what may be possible.” 

That gives people a grown-up explanation instead of a vague promise. 

Client: “What about fairness? That word is going to come up.” 

Consultant: Of course it is. Fairness is always in the room when schedules are involved. The important thing is to define fairness carefully. Fairness does not always mean identical outcomes. It means using a consistent process, tied to real business needs, and communicating clearly about how decisions are made. 

That is a much sturdier foundation than trying to avoid all discomfort by making everything look the same. 

Client: “And I assume we need to watch for whether flexibility for one person creates more work for someone else.” 

Consultant: Absolutely. This is one of the biggest traps. If a flexible arrangement means the same dependable employees are always covering phones, greeting the public, staying late, or cleaning up unfinished work, you have not created flexibility. You have just moved the inconvenience to quieter people. 

Managers need to pay attention to workload distribution, coverage impact, responsiveness, and whether the arrangement is working for the team as a whole, not just for the employee who requested it. 

Client: “So the real lesson is: think bigger than Summer Fridays, and plan before you promise.” 

Consultant: Exactly. Seasonal flexibility can be a great tool for morale, retention, and trust. It can also become an instant source of side-eye if it is rolled out casually. Start with the work. Build a framework. Communicate clearly. And remember that flexibility works best when it is designed on purpose, not handed out in reaction to the loudest request. 

And if your organization wants help thinking through a seasonal flexibility approach that supports morale and still keeps the work covered, we can help. 

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. 

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.