All articles

Toxic positivity: why problems need to surface early and how to raise them

Why problems arrive late when everything has to be green, and how to raise one clearly.

By Daniel Schmeiß5 min read
  • Team dynamics
  • 5 Dysfunctions of a Team

In the weekly status meeting, the project is green. Six weeks before the release, a developer says: "The interface from the other team is still missing. We can't test without it. I estimate we need two more weeks."

The project lead replies: "The other team has promised the interface is coming. Let's not start painting doom scenarios, it just brings the mood down. We've pulled off much harder things." A few people nod. The status stays green.

Three weeks later, it turns red. The release slips by a month. In the next status meeting, the developer doesn't say anything.

When optimism becomes mandatory

This pattern is called toxic positivity. It means the expectation that everyone stays upbeat, whatever the situation. Anyone who raises a problem is quickly seen as negative, or as someone who doesn't believe in the team.

The term usually comes up around feelings, such as a "Chin up, it'll be fine" to someone who is struggling after bad news. At work, the pattern often shows up in deadlines and status reports.

Optimism helps a team get through hard weeks. But "We'll make it" says nothing about how.

Three signs tell you whether your team works this way:

  • Everyone agrees in the meeting, and the discussion continues afterwards in small groups.
  • The status goes straight from green to red, with no amber in between.
  • Risks only show up in the status report once they have already happened.

In his model of the 5 Dysfunctions of a Team internal Reflacto page, Patrick Lencioni describes a related pattern, fear of conflict: the team avoids open disagreement and preserves artificial harmony.

Why toxic positivity does harm

In the example, the damage shows up in four places.

The options shrink. When the developer raised the problem, there were six weeks left. The team could have talked to the other team or cut the scope. At worst, by her estimate, the release would have come two weeks later. Three weeks on, the only option left was to push it back by a month.

Others decide on the wrong basis. As long as the status was green, everyone who depends on the release planned with the old date. With an honest status, they could have chosen early between a smaller scope on time and the full scope a month later.

People who spot problems early learn to stay quiet. The developer found out that she gets slowed down when she raises a problem early. Next time, she waits until it can't be overlooked. When several people on a team do this, the project lead only hears about problems once they are no longer small.

The status loses its value. Anyone who has seen a green project turn red three weeks later trusts the next green status less.

That's why, to me, good collaboration means treating everyone involved as adults and trusting them with reality. People who know where a project stands can think along and help decide.

When you see a problem

Maybe you know this: you see a problem and hesitate because you don't want to be the one slowing things down. Without a leadership role, you often lack the weight to put a risk on the agenda on your own.

A question to the whole group helps here. The psychologist Gary Klein described the premortem opens in a new tab for this: the team imagines the project has already failed and collects reasons why. In a status meeting, it can sound like this:

"Let's imagine we missed the date. What caused it?"

With this question, anyone can name a risk without coming across as the pessimist.

When you raise the problem yourself, don't attack anyone. "The other team dropped the ball again" names the problem, but the other side defends itself, and nobody talks about the interface anymore. Instead, say three things: what is going on, what follows from it, and what you propose.

"The interface has been missing for two weeks. If it isn't here by the 15th, we won't finish testing in time, and the release slips by about two weeks. I suggest we check with the other team today when it will arrive."

The developer in the example named the situation and the consequence. Adding a proposal makes it harder to brush the warning off with "It'll be fine," because the conversation is then about a concrete next step.

When you get brushed off anyway

Sometimes even a clear warning gets brushed off with "It'll be fine" or "Let's not paint doom scenarios." Often the person saying it is under pressure themselves: the date has been promised, a red status ends up in the report upwards, and they don't have a solution yet either. The sentence buys them time.

Then this question helps: "What do you need to report this upwards?" Offer to write down the consequences with dates and effort, so the project lead can pass them on. How to describe a request in the other side's terms is in the post Speak the language of the people you want to reach internal Reflacto blog post.

If the reassurance stays, it helps me to turn the optimism into a commitment:

"Does that mean we'll hit the date with the full scope? Then we need the interface by the 15th. Who will sort that out with the other team?"

If no clear answer comes back, ask for a decision between two options:

"We can cut the scope and keep the date, or push back by two weeks. Which one should we prepare?"

After the meeting, send a short message with the problem, the consequence and the date. Then everyone has the same information, including people who weren't there. If nothing happens after that, talk to the person one-on-one. How I deal with the reluctance beforehand is in the post Through the pain, not around it internal Reflacto blog post.

When someone brings you a problem

Whether the developer speaks up next time was decided by the project lead's reply.

I try to say thank you first and then ask:

"Thanks for raising this. How long has the interface been missing, and by when would we need it to make the date?"

You can still be optimistic afterwards, this time with a plan. The status is then amber, and everyone knows what the team is working on.

The first step

In your next status meeting, ask the premortem question: let's imagine we missed the date, what caused it? If someone names a problem, thank them first and then work out together what happens next.