When “Stay Positive” Stops Honest Feedback
Encouragement helps teams, but enforced optimism can obscure problems. An editorial on honest feedback, useful language and responsibility at work.
A missed deadline does not become manageable because everyone describes it cheerfully.
Encouragement has a useful place at work. A colleague who is struggling may need reassurance that one mistake will not define their reputation. A difficult project may require confidence before all its uncertainties can be resolved.
The trouble begins when confidence becomes a condition for being heard.
Consider this invented exchange. An employee explains that a delivery date cannot be met with the available staff. The response is: “Let’s stay positive. We always find a way.”
The sentence sounds supportive. It supplies no additional staff, removes no requirement and identifies no alternative date. It also leaves the employee with a second problem: raising the practical objection again may now look like refusing the requested attitude.
The issue lies in what the response prevents the team from discussing.
Amy Edmondson’s research on team psychological safety examines whether people believe they can take interpersonal risks, including speaking about mistakes and uncertainty. Her 1999 study investigated the relationship between psychological safety and learning behaviour in work teams. It does not establish that every encouraging phrase is harmful. It offers a more useful question: what happens when someone reports an unwelcome fact? Harvard research repository.
Workplace language deserves attention because it helps determine which facts receive a response.
“We need solutions, not problems” can express a reasonable desire for action. Used too early, it can require employees to solve an issue before they are permitted to report it. Someone may recognise a defect without holding the budget, information or authority needed to repair it.
“Everyone is under pressure” can acknowledge a shared difficulty. It can also end a conversation about an unequal or avoidable workload.
Meaning depends on the response that follows. Does the manager ask for evidence? Reconsider the plan? Assign responsibility? Or does the exchange finish once the employee has adopted a more agreeable tone?
A better response to the invented deadline problem would be specific: “Which requirements are at risk? What can we remove? If we keep the full scope, what date can you support?”
These questions create options. They also place the decision with someone who can change the terms.
Candour carries responsibilities on both sides. Employees should distinguish an observed problem from a prediction, explain consequences and acknowledge what remains uncertain. Managers should avoid demanding a fully developed remedy from someone who lacks the authority to deliver it.
Disagreement also needs boundaries. Personal attacks, contempt and unsupported accusations do not become useful merely because they are blunt. A team can expect respectful conduct while allowing people to say that a plan is unrealistic or a decision has failed.
The practical test is modest. At the next project meeting, invite each person to identify one unresolved risk. Record who can act on it and when the decision will be reviewed. Then examine whether the reported risks led to changes.
The number of concerns raised is not, by itself, a measure of success. More reports might indicate greater confidence in speaking—or worsening conditions. Fewer might indicate improvement—or silence. Follow the issue through to its outcome.
Optimism becomes credible when people can see what supports it: a smaller scope, additional help, a corrected process or a realistic commitment.
A workplace should make room for encouragement. It should also make room for the sentence that complicates the plan. Sometimes that sentence is the most useful contribution anyone can make.