Careers

Too Nice for Its Own Good: When a Culture of Politeness Gets in the Way of Work

09/14/2026
Too Nice for Its Own Good: When a Culture of Politeness Gets in the Way of Work

In some teams, open conflict is rare: managers try to deliver feedback carefully, and after a failed project, people choose their words deliberately so that criticism does not turn into a personal offense. Working in this kind of environment is usually more pleasant than being somewhere every meeting carries the risk of a public dressing-down. But a team's ability to maintain good relationships is truly tested during difficult conversations-for example, when a strong employee needs to be told that they have been underperforming for the past several months, or when someone needs to challenge a manager who has become too invested in a weak idea.

In situations like these, respect for another person can easily be confused with a desire to avoid an uncomfortable conversation at all costs. A manager can spend months softening feedback so as not to demotivate an employee, while colleagues quietly redo that person's work. A team can avoid challenging a leader in a meeting and preserve a pleasant atmosphere, only to face the consequences several weeks later of a decision that many people believed was flawed from the start.

In August 2026, Harvard Business Review devoted an article specifically to this issue. Its authors, Ron Ashkenas and Gali Cooks, examine companies where the desire to preserve harmony gradually displaces direct conversations about performance, accountability, and difficult decisions. The problems in these organizations do not disappear; they simply become harder and harder to discuss.

So where is the line between a healthy work environment and a culture in which no one is allowed to upset anyone?

When Good Relationships Require Too Much Caution

A culture in which people try to treat one another thoughtfully is hardly a problem in itself. But when preserving good relationships becomes an unspoken condition of every work-related conversation, uncomfortable information has to be softened until much of its original meaning disappears.

A manager who is unhappy with an employee's performance may spend weeks talking about "areas for growth," even though the person's work has already been falling short of expectations for several months. After a failed presentation, the team may discuss what still needs to be improved in the concept even though several people believe the original idea itself is flawed; those doubts remain unspoken during the meeting, only for the manager's decision to be dissected at length afterward, once the manager is no longer in the room.

As a result, only the formal meetings remain calm. Disagreements move into private conversations and separate message threads, where people can no longer influence the decision that has already been made, while the manager receives a much more reassuring picture than the one the team is actually discussing among themselves.

01

When Alan Mulally, who had spent many years at Boeing, took over as CEO of Ford in 2006, the automaker was in serious financial trouble and losing billions of dollars. Mulally introduced weekly meetings in which executives had to classify the state of their business areas by color: green if everything was on track, yellow if problems had emerged, and red if there was a serious unresolved issue. Yet during the first few weeks, nearly every report remained green. Mulally could not understand how the company was losing billions while every executive appeared to be doing just fine.

One of the first executives to show a red status was Mark Fields, then head of Ford's North American business: a technical problem had forced the company to delay the launch of the new Ford Edge. His colleagues expected a harsh response because, under the previous culture, admitting to a serious problem without already having a solution could come at a significant cost to an executive.

Instead, Mulally began applauding, thanked Fields for being candid, and asked the rest of the group who could help. At subsequent meetings, the number of red and yellow reports increased considerably.

If someone repeatedly sees that bringing bad news leads to irritation, loss of trust, or damage to their career, no explicit prohibition is necessary: they begin deciding for themselves which problems are safe to raise in a group setting. Forbes describes a similar dynamic in teams where employees assess before a meeting which doubts are safe to voice and which are better kept to themselves.

Why Psychological Safety Does Not Mean Constant Comfort

Caution in difficult conversations is sometimes explained as a matter of psychological safety: employees should feel secure, should not be afraid of making mistakes, and should know that a manager will not humiliate them over a poor result. But psychological safety does not mean the absence of uncomfortable emotions. It means being able to discuss mistakes, doubts, and disagreements openly without fearing punishment simply for having that conversation.

Harvard Business School professor Amy Edmondson, who has studied psychological safety in teams for several decades, defines it as an environment in which people can ask an uncomfortable question, admit a mistake, express doubt, or disagree without fearing consequences simply for speaking up. In 2025, Edmondson and researcher Michaela Kerrissey addressed a common misconception that a psychologically safe team should above all be a pleasant place where people try not to upset one another. Instead, the authors connect psychological safety with the ability to speak candidly, including when people in the conversation disagree.

A team in which an employee can calmly tell a manager that they do not understand a decision or believe it is risky is closer to a psychologically safe environment than one where everyone tries to protect the boss's good mood. The same applies to feedback from managers to employees: a leader can state plainly that a result was weak without making it personal or turning a mistake into an opportunity for humiliation.

In 2011, Netflix co-founder Reed Hastings decided to separate the company's streaming service from its DVD rental business, spinning the latter off under a new brand called Qwikster. By then, Netflix had spent years building its corporate culture around employee autonomy and direct feedback. The idea provoked a strong backlash from customers, and within weeks the company abandoned the new brand. Hastings later began asking executives why no one had tried harder to talk him out of the decision earlier and discovered that many people had serious doubts. One manager thought the name Qwikster itself was a bad idea but stayed silent because no one else seemed to object; another admitted that when Hastings became deeply enthusiastic about one of his own ideas, arguing with him could feel almost pointless.

02

After that experience, Netflix formalized a practice known internally as "farming for dissent"-deliberately seeking out opposing views before making an important decision. The principle remained in place years later: when Netflix updated its corporate culture memo in 2024, every employee was given an opportunity to comment on it, and the company received more than 1,500 pieces of feedback.

No one at Netflix had forbidden employees from disagreeing. On the contrary, leadership already considered candor one of the company's values. But saying "you can disagree with me" is not enough if people's past experience tells them that the leader is too committed to a decision or that an objection is unlikely to change anything. In that environment, the absence of disagreement can easily be mistaken for agreement, even when employees have simply decided that speaking up is not worth the effort or the risk to the relationship.

Psychological safety is revealed most clearly in the response to uncomfortable information. If an employee can be the first to say that they made a mistake in their calculations or that a project is behind schedule because they know they will be heard and the focus will remain on solving the problem itself, candor does not destroy working relationships. The same is true of disagreeing with a manager: the opportunity to object needs to exist before a decision is made, not several weeks later when the consequences already have to be fixed.

Who Ultimately Pays for Softened Feedback

An uncomfortable conversation rarely becomes easier after being postponed for several months. An employee who is genuinely struggling in a role will continue to believe there is no serious problem if all the feedback they receive consists of cautious hints. A later poor performance review or dismissal can then come as a complete surprise, even though the person might previously have had time to change how they worked, understand expectations more clearly, or make a decision about their own future.

But the person whose difficult conversation was avoided is often not the only one who pays the price. If one employee's weak performance has to be repeatedly compensated for by others, the additional workload falls on colleagues who have already done their own jobs. A manager's kindness begins to look very different when preserving one person's comfort requires everyone else to work harder for months.

Forbes describes this problem as a transfer of consequences: a difficult conversation may be avoided today, but later the burden falls on colleagues, HR, or the employee themselves, who learns how serious the situation is only once there are far fewer opportunities left to change it.

While a team avoids criticizing an idea because someone has invested a great deal of effort in it, the budget continues to be spent; while leaders postpone a conversation about an underperforming business area, other departments continue to deal with the consequences. The uncomfortable conversation is only avoided at the beginning. Eventually it returns, now accompanied by lost time, wasted money, or the need to repair a decision that has already been made.

Candor by itself, however, is no guarantee of anything either. The phrase "we tell it like it is here" can easily become an excuse for rudeness, public criticism, or a conversation that leaves the employee with no idea what they are actually expected to do differently. Feedback works when it is specific enough for the person to understand which result fell short, where expectations and reality diverged, and what needs to change.

Directness and respect are entirely compatible, but relying only on a manager's personality or an employee's courage is not enough. If speaking openly carries a personal risk every time, sooner or later some problems will once again remain outside the conversations where they actually need to be addressed.

How to Make Candid Conversation a Routine Part of Work

If candor depends every time on whether one particular employee is willing to challenge the boss, the people most likely to do it will be those with greater authority, stronger relationships with the manager, or simply a higher tolerance for conflict. Everyone else will continue weighing the risk, which is why simply telling a team to "speak openly" is rarely enough.

03

At Pixar, criticism has long been built into the filmmaking process itself. Ed Catmull, one of the animation studio's co-founders and its longtime president, has described the Braintrust-regular meetings in which directors show unfinished films to colleagues, who openly discuss what is not yet working in the story. These sessions began during the production of Pixar's earliest films and later became a permanent part of the creative process. Catmull explained the need for the practice quite simply: even the first versions of films that eventually become successful are far from the finished product audiences see in theaters, so weaknesses have to be identified while there is still time to fix them ().

Braintrust participants can be extremely candid in their assessment of the material, but they do not have the authority to tell a director exactly how to fix it. Colleagues identify the problem; the final decision remains with the filmmaker. Criticism therefore does not take control of the project away from its author, while at the same time no individual participant has to decide separately whether they are willing to initiate an uncomfortable conversation-the feedback is built into the rules of the meeting from the start.

Before an important decision, a manager can explicitly ask the team to formulate the strongest arguments against the preferred option and identify the conditions under which it would prove to be the wrong choice. After a project, it can be useful to review the decisions the team would make differently today, while a problem with an individual employee's performance is better discussed soon after it becomes apparent rather than postponed until an annual review.

When these conversations are built into the way work gets done, employees do not have to decide every time whether a problem is serious enough to justify risking a relationship with a colleague or manager. Disagreement remains uncomfortable, but it no longer feels like a violation of an unspoken rule that everyone must preserve the group's comfort.

Good relationships within a team are genuinely worth protecting: trust, respect, and the ability to make mistakes all make collaboration more resilient. But those relationships are surprisingly fragile if maintaining them requires people to constantly hide disagreements, soften bad news, and pretend that weak performance is perfectly acceptable. In a healthy work environment, colleagues are able to have a difficult conversation without turning it into a personal conflict-and then continue working together normally afterward.

Careers