The Employees You Call Troublemakers May Be the Ones You Need Most

Every organization has someone who asks the question nobody seems eager to answer.

Why does this approval need three signatures? Why are two departments reviewing the same information? If customers keep reporting the same problem, why are we treating each complaint as an isolated incident?

Sometimes those questions are welcomed. Sometimes they earn the employee a reputation.

Difficult. Negative. Resistant. Not a team player.

But those labels tell us little about whether the employee is right.

When A Question Becomes A Reputation

Consider an illustrative situation: a manager is reviewing a proposed process redesign. An employee interrupts to question why a request still has to pass through three separate reviews. They suspect that two departments are checking much the same information, adding days without improving the decision.

It may be a valuable observation. It may also overlook a necessary control. The answer requires looking at actual workflow steps, handoffs, decision rights, and elapsed time. But before anyone examines those things, the room goes quiet. The delivery was abrupt.

Later, someone says the employee was confrontational. A second person agrees that they always seem to have a problem with everything. By the next meeting, the employee is introduced, implicitly or explicitly, as someone who resists change.

Notice what happened. The organization moved from evaluating an observation to interpreting a person.

The employee may have communicated poorly. That matters. But it does not settle the question they raised. If two reviews duplicate one another, the work continues to circulate unnecessarily whether the observation was diplomatically expressed or not. If both reviews are essential, leaders should be able to explain what each one protects. Either way, the concern deserves examination rather than a reflexive label.

This is where leadership judgment becomes important.

Three Questions, Not One

When a concern is raised awkwardly, leaders need to separate three issues that are often bundled together.

Is the substance valid? What is the employee observing? Can the problem be verified? What does the evidence show about cost, time, quality, risk, or customer experience?

Is the presentation effective? Was the concern communicated in a way others could reasonably understand and act on? Does the employee need coaching on timing, tone, or how to frame a recommendation?

What assumptions are being added? Are leaders responding to what was actually said, or assigning motives such as disloyalty, resistance, or a desire to undermine authority?

These questions can lead to different answers. An employee might have identified a real problem, presented it badly, and been unfairly assigned an intention they never held. Good leadership can recognize all three without excusing behavior or discarding useful information.

The Cost Of Confusing Agreement With Alignment

Organizations routinely ask employees to identify waste, improve customer experience, and challenge outdated practices. Yet the same organizations can become uncomfortable when someone questions a familiar decision or a senior leader's preferred approach.

The result is predictable. People learn which concerns are safe to raise, which phrases are acceptable, and which issues are better left alone.

Meetings become smoother. Reports become more reassuring. The underlying problems do not necessarily improve. A redundant approval can keep extending cycle time. Poorly defined ownership can keep generating rework. Repeated customer complaints can be treated as isolated exceptions while the same breakdown continues. These costs do not disappear when the employee who notices them stops speaking up.

Agreement may make a meeting easier to conduct, but it is not evidence of alignment. Real alignment requires a shared understanding of the outcome, the constraints, and the decisions needed to get there. Employees who expose a gap in that understanding may be contributing to alignment, even when their challenge is inconvenient.

Listening Does Not Mean Accepting Every Objection

None of this means the person who challenges a process is always correct. Some observations rest on incomplete information. Some proposals create costs or risks elsewhere. Some behavior is genuinely disruptive and requires direct feedback.

Leaders still have to make decisions, set boundaries, and hold people accountable for how they participate.

The distinction is that accountability for presentation should not substitute for an examination of substance.

A practical response can be straightforward: “I want to understand the issue you're pointing to. Show me where the delay occurs and what changes if we remove that step. Then let's talk about how to raise it so the team can work with it.”

That response neither rewards incivility nor ignores the signal. It investigates the operational question and addresses the communication issue separately.

Turn The Concern Into A Decision

Listening is only the beginning. A concern that is acknowledged and then forgotten teaches employees almost as much as one that is dismissed outright.

A useful management discipline has four steps:

1. Capture the concern. Record the specific process, decision, or customer outcome being questioned, not a judgment about the employee who raised it.
2. Validate the evidence. Examine the work as it actually happens. Check the handoffs, reasons for each control, available timing information, and effects on downstream teams.
3. Assign decision ownership. Identify who will decide whether the process changes, what trade-offs that person must consider, and when the decision will be made.
4. Communicate the outcome. Explain what was learned, what will change or remain, and why. When the original observation is not supported, say so with the same clarity.

The result need not be agreement. It should be a reasoned decision that leaves the organization better informed.

A Better Test Of Leadership

Before a concern is dismissed because of its source, a leader can ask:

• What specific breakdown is this person describing?
• What evidence would confirm or disprove it?
• If someone with a different reputation raised the same issue, would we respond differently?
• Are we coaching the employee's communication, or using it as a reason not to investigate?
• What could this concern teach us about the way our organization actually works?
• Who is accountable for deciding what happens next, and how will the outcome be communicated?

There is a difference between someone creating problems and someone making existing problems visible.

Organizations that cannot tell the difference risk losing more than an employee's enthusiasm. They lose access to information that could help them perform better.

The next time someone is described as a troublemaker, a useful first question may be: What trouble are they actually making, and what trouble are they trying to reveal?