Business.com aims to help business owners make informed decisions to support and grow their companies. We research and recommend products and services suitable for various business types, investing thousands of hours each year in this process.
As a business, we need to generate revenue to sustain our content. We have financial relationships with some companies we cover, earning commissions when readers purchase from our partners or share information about their needs. These relationships do not dictate our advice and recommendations. Our editorial team independently evaluates and recommends products and services based on their research and expertise. Learn more about our process and partners here.
9 to 5 is for green, not red and blue.

Dr. Ben Baran is an associate professor at Cleveland State University and co-founder of Elevating What Works.
Conversations about politics can be tricky — and in the workplace, you don’t want them to create conflict. It’s likely that people on your team have differing viewpoints on a variety of issues and candidates, and if those differences turn into arguments, you may have a real problem on your hands.
The big issue is that high-performing teams need people who trust each other, and arguing about deeply held political positions can damage that trust. They may even avoid each other completely. This may even happen if people simply know about another person’s views; they don’t even have to be arguing about it openly.
So what might be some ways to get ahead of this potential problem?
Researchers recently provided a number of insights to guide your efforts. You can do this, they suggest, by remembering ART — Acknowledge, Respect, and Trust:
Some circumstances might call for you to address political polarization in your team head-on. As a general rule, if it’s affecting performance or engagement, step in. When you do, address the topic in a caring way.
Agreeing to disagree on political issues is totally acceptable, so long as all parties involved continue to work together respectfully.
This article first appeared in the b. Newsletter. Subscribe now!