Commitment vs. Criticism
Some teams and individuals struggle to commit to decisions, and challenging what should be established common ground creates uncertainty. But how do leaders give welcome self-improvement a well-defined channel while finding a clear voice to address unwelcome disruption?
On the phone this weekend, a friend brought up an issue in his team. There's a person who retrospectively questions each and every decision made by the team - re-opening discussions that have been jointly closed, challenging assumptions and outcomes after the fact, and sometimes broadcasting claims that everything is being done wrong to audiences well beyond those who need to know. The person is unapologetic, convinced of their own superiority.
The consequence is stagnation and frustration. The team slows down, nobody is quite sure which decisions are actually final, and everyone wastes energy repeating discussions that were already resolved - living in quiet fear of unnecessary rework.
I've seen this type of team dysfunction happen quite a few times. Self-correction mechanisms are crucial for any organisation to evolve, but constant disruption breaks morale and stops progress. The tricky part is that leaders often struggle to address the behaviour directly because they can't easily link it to "performance" - and performance often feels like the only lever they have.
And leaders need to acknowledge an uncomfortable truth: that gap is frequently one leadership created. Most teams never explicitly agree on how decisions get made, who can change them, and through what channels. That ambiguity is sometimes convenient - it keeps power informal and flexible. But it also means that the disruptive person isn't always breaking rules. They're exploiting a vacuum.
To be honest with ourselves: in rare cases, you may end up with an individual where this truly can't be fixed. Moving on is sometimes the right call; and leaders should be careful not to burn a disproportionate amount of coaching energy on one person's behaviour at the expense of everyone else on the team.
More often though, alignment is what's actually missing - and fixing that creates real benefit all around. The disruptive person gets a channel where their input is constructive. The team regains shared understanding of what's actually decided. And the leader stops playing referee at the cost of doing everything else.
What alignment actually looks like
Even in teams that have worked together for years, if you interview each member individually about how the team makes decisions, communicates them, documents them, and revisits them - you'll get strikingly different answers. Who's allowed to change a decision? The project lead? A technical expert? Under what circumstances - any time, after a waiting period, only in specific meetings? Does challenging a past decision start in a private chat, seeding uncertainty in parallel streams, or does it start from a written record with openly shared context and data?
Get the team together and surface these differences. Not to embarrass anyone - to make visible something that everyone assumed was obvious and wasn't.
From there, work through the fundamentals. Agree on how and when issues are brought to the team: Is there a fixed recurring forum? What can wait, and what truly can't? What context is required before a discussion can start productively? For example, teams might commit that a pressing issue discovered mid-week first goes to the project lead as a short written briefing - context, expected impact, suggested path - and together they decide whether it goes to the full group or needs more analysis first. The format matters less than the fact that everyone has agreed to it.
Make sure everyone has the same working model for how decisions are made, communicated, and recorded. A project decision log isn't bureaucracy. It's the shared memory that makes disagreement legible and time-bounded. Define when it's valid to voice disagreement and when it isn't, in both timing and format. Disagreement belongs at the point of decision, or through a structured process if and only if the underlying facts have substantially changed - not as a recurring reaction to outcomes people didn't like. As so often, less is more: a single source of truth with enough context is better than fragmented logs, minutes, and memos.
Reduce the noise everywhere you can: fewer parallel chat streams, fewer status updates that only exist because nobody trusts the source of truth.
Why this changes the conversation
The next time someone sends a chat message challenging a past decision or pulls out the "here's why everything we're doing is wrong" presentation, you now have something concrete to point to. You can sit down with them and explain - specifically, calmly - how their behaviour doesn't follow the way the team has agreed to work, and ask them to use the process that everyone committed to.
That is a fundamentally different conversation from the one most leaders find themselves in, where the argument rests on vibes, frustration, and contested interpretation of past events. Process gives you ground to stand on.
And it's no surprise that going through this exercise periodically - twice a year is a reasonable minimum - builds confidence and effectiveness even when there's no active disruption to resolve. Clarifying how a team actually makes decisions, who owns what, and how it gets communicated is one of the more durable things a leader can do. It matters more than another performance framework, and considerably more than re-drawing the org chart so the new reporting lines will finally, somehow, fix everything with more oversight.