Good feedback starts early

Many teams say they value candour. Far fewer know how to practise it.

What usually happens is more familiar. Something lands badly. A sentence sounds sharper than intended. A decision feels excluding. A behaviour starts to grate. But instead of naming it early, people hold it. They wait. They interpret. They add motive. They replay the moment privately until a passing irritation acquires a full backstory.

By the time it finally emerges, it is no longer a thought. It is an emotion with a case attached to it.

That is when feedback becomes expensive.

My rule is simple: raise it while it is still a thought.

Not every passing feeling needs to become a conversation. But if something matters enough to change your behaviour, your trust, your willingness to collaborate or the quality of the work, it should be voiced before it turns into passive aggression, distance or politics. Harvard Business Review's summary of Joseph Grenny's work makes a similar point: strong teams create cultures where peers address concerns immediately, directly and respectfully rather than leaving everything for the manager to sort out.

Feedback fails when it arrives too late

Most poor feedback is not too honest. It is too delayed.

"Most poor feedback is not too honest. It is too delayed."

The delay matters because delay changes the emotional chemistry of the conversation. If I tell you something close to the event, we are usually discussing a behaviour, a decision, a misunderstanding or a moment. If I wait three weeks, I am far more likely to arrive with a pattern, a judgement, a story about your motives and a visible charge that makes it harder for either of us to think clearly.

This is one reason teams drift into passive aggression. Not because people are uniquely immature, but because there is no strong norm of early clarification. Without that norm, irritation goes underground and comes back out as sarcasm, coolness, territoriality, delay or overcorrection in the work.

The better alternative is not endless confrontation. It is earlier conversation.

Gallup's research points the same way. Employees who receive weekly, meaningful feedback are four times more likely to be engaged than those who do not, yet only 21% strongly agree they received meaningful feedback from their manager in the previous week. That is not just a frequency problem. It is a timeliness problem.

Start with good intent, but do not stop at politeness

A useful feedback culture begins with an assumption of good intent.

That does not mean being naive. It means resisting the urge to leap straight from impact to motive. A rushed Slack message becomes disrespect. A missed loop-in becomes politics. A clumsy comment becomes character evidence.

Sometimes those interpretations are right. Many times they are premature.

This is why assuming good intent is such a practical discipline. It keeps the conversation in the territory of observable reality for longer. It lets you ask: did you mean it that way? Was there context I missed? Did something land differently from how you intended it?

That is usually a better starting point than accusation.

This is also where psychological safety matters. Google's Project Aristotle work found that teams with stronger psychological safety are safer places for interpersonal risk-taking: admitting mistakes, asking questions and raising issues that might otherwise stay buried.

Good intent, then, is not softness. It is a way of keeping the door open long enough for truth to emerge.

Trust is built through urgency, care and constancy

None of this works without trust.

And trust is not built by saying "my door is always open" once and hoping people believe you. It is built through behaviour that repeats often enough to become credible.

For me, the three ingredients are urgency, care and constancy.

Urgency means things are raised while they are still live, not archived until resentment has had time to organise itself.

Care means the point of the conversation is improvement, not domination. The other person should be able to feel that you are trying to solve something with them, not perform superiority at them.

Constancy means this is not a once-a-quarter burst of honesty. It is part of the team's normal operating rhythm. Small clarifications happen regularly, which means fewer relationships become quietly distorted by avoidance.

Gallup's research is useful here too. In one recent summary of meaningful workplace conversations, 59% of managers strongly agreed they gave recognition, while only 35% of employees strongly agreed they received it. Only 51% of managers strongly agreed they gave feedback every week. That perception gap is the point: communication is not the act of saying something. It is the other person actually receiving it.

"Communication is not the act of saying something. It is the other person actually receiving it."

Good feedback is specific, developmental and calm

When people say they value candour, they sometimes confuse it with bluntness.

Bluntness is easy. Good feedback is harder.

Good feedback stays close to specifics. It names what happened, why it mattered and what effect it had. It avoids amateur psychoanalysis. It avoids sweeping claims about personality when a cleaner description of behaviour would do. It does not inflate one incident into total identity.

Gallup puts it plainly: feedback should be meaningful, timely, authentic and actionable. It should help people learn, grow and do their jobs better. Google's guidance for managers similarly emphasises specific and timely feedback inside regular one-to-one coaching conversations.

That is the standard.

The point is not to discharge your feelings. The point is to improve reality.

A useful rule for giving feedback is this: describe the behaviour or moment clearly; explain the impact without melodrama; check your interpretation before asserting it as fact; say what would need to change; stay calm enough that the other person can still think.

If the other person leaves with shame but no clarity, it was probably not good feedback.

Receiving feedback is a separate skill

Most feedback advice focuses on the giver. The receiver matters just as much.

Receiving feedback well does not mean agreeing with every word, nor does it mean becoming endlessly self-questioning. It means staying open long enough to understand what the other person is trying to tell you before deciding what is true, what is distorted and what needs to change.

That requires restraint.

It requires resisting the urge to litigate every detail in real time. It requires asking for examples. It requires distinguishing between "this is uncomfortable" and "this is wrong". It requires owning your part without performing false guilt for things that are not yours.

It also requires maturity from leaders in particular. If you react defensively to the first honest thing someone tells you, you teach the whole team that upward feedback is unsafe. Once that happens, people do not become more honest. They become more polished.

"If you react defensively to the first honest thing someone tells you, you teach the whole team that upward feedback is unsafe."

That is why the reaction matters so much. Trust follows when people see that honesty changes something useful, not when leaders simply announce that feedback is welcome. Gallup's recent work on trust in leadership makes the broader point: trust grows when leaders create clarity, manage change well and act in ways that support performance.

Strong teams clarify early

One of the best markers of team maturity is not whether conflict exists. Conflict exists everywhere. The marker is how quickly the team can return confusion to clarity.

Can people say, quickly and cleanly, "I think that landed oddly — can we check it?"

Can they ask, "I may be telling myself a story here, but did you mean it this way?"

Can they say, "Something has been off between us since that meeting, and I would rather sort it now than let it grow"?

That is a strong team.

Not because it enjoys conflict. Because it knows that unclarified tension is one of the fastest ways to degrade trust, collaboration and decision quality.

The goal is not a culture in which people constantly process each other. That becomes exhausting in its own right. The goal is a culture in which people do not leave important ambiguity to rot.

"The goal is not no friction. The goal is no rotting ambiguity."

A simple standard

If it matters enough to change behaviour, raise it while it is still a thought.

Assume good intent before you assign bad motive.

Be specific enough to be useful.

Keep the purpose developmental.

Build the trust that allows people to bring things early.

And when feedback comes to you, do not punish the first imperfect version of the truth.

That is how good teams stay clean.

Not by avoiding friction, but by making sure friction gets turned back into clarity before it becomes politics.