Start with the behaviour you can verify: what they challenged, where they did it, what evidence they offered, and whether the team still needed to act on the decision.
Do not make authority the opening argument. First decide whether the person is improving the work, exposing a weak decision process, asking for ownership, or repeatedly undermining an agreed direction.
Those are different management problems. Useful dissent needs room and a decision deadline. Weak process needs clearer criteria. Public undermining needs a direct conversation and a consequence if it continues.
Useful challenge and toxic challenge are not the same thing
Useful challenge usually has a clear pattern. The person asks hard questions, points to risks, and pushes on the decision because they want a better outcome. It may be uncomfortable, but it is still useful.
Toxic challenge looks different. The person devalues decisions in public, avoids responsibility for alternatives, or goes around you instead of speaking directly. That is no longer healthy disagreement. That is undermining.
Your job is not to silence disagreement. Your job is to keep the useful version and cut off the toxic one.
Context matters more than people admit
Before you decide what to do, ask one awkward question.
Are they reacting to the decision, or are they reacting to you?
If you are a new team lead, pushing rank too hard will usually fail. You need to show that you can listen, use data, own the process, and still make the call.
If you have led the team for a while, be honest with yourself. Have you started leaning too hard on authority? Have you stopped explaining decisions properly? Have you ignored signals or risks from the team? Sometimes the challenge is not rebellion. It is a response to sloppy leadership.
Before the 1:1, write down the decision, what input was invited, when the decision closed, and the behaviour that is now causing damage. That keeps the conversation out of a vague argument about attitude.
Diagnose how the person sees the situation
This is where the four-lens model is useful.
A person may challenge you mainly through Reasoning, Drive, Connection, or Capacity. In Cooperly's method, Reasoning is about criteria, facts, and proof; Drive is about ownership, boundaries, and decision-making; Connection is about tone, contact, and relational atmosphere; Capacity is about workload, timing, resources, and practical conditions.
That matters, because the same disagreement needs a different response depending on what is driving it.
If the person is mostly Reasoning-led, they often want better reasoning. Gaps in argument, weak criteria, and missing data will annoy them. With that person, speak in facts, trade-offs, risks, and decision criteria. Cooperly's method is very explicit here: Reasoning-led people respond better when you agree the success criteria, test assumptions in practice, and bring real evidence rather than vague confidence.
If the issue is mostly Drive, the person usually wants influence, ownership, or a stronger say in direction. Sometimes that becomes constructive leadership energy. Sometimes it turns into power games. The distinction matters. If the challenge is constructive, give them real ownership over a piece of work. If it is sabotage dressed up as confidence, set hard boundaries quickly. The method notes describe Drive as responsibility, boundaries, and movement to result, and warn that strong Drive without the right structure can turn into leadership conflict.
If the issue is mostly Connection, tone and respect may be carrying more weight than the decision itself. If it is mostly Capacity, the real objection may be practical: timing, load, cost, or whether the plan is realistic. Those are not soft objections. They are still part of the decision.
Your job is to protect challenge without losing authority
The goal is not blind agreement.
The goal is a team where people can question decisions usefully without turning every disagreement into theatre.
That means:
- keep healthy pushback
- cut off behaviour that damages trust
- adapt how you speak depending on the person in front of you
- make the decision path clear
The method docs are helpful here too: when there are lots of dependencies or vulnerable zones, dialogue matters; when you need speed and clarity, you need an explicit result mode with decision and criteria. A lot of team conflict comes from mixing those two modes without naming them.
Set the boundary in one sentence
If the challenge is useful, say where you want it: before the decision closes, with evidence and an alternative the person is prepared to help execute.
If the pattern is undermining, name the line directly: "I want you to challenge weak reasoning. Once we make the decision, I expect you to raise new evidence with me rather than reopen it in front of the team."
Ask them to explain what they believe is unresolved. Then decide whether the issue needs new evidence, clearer ownership, or a conduct boundary.
Close with the decision, what challenge is still welcome, what behaviour must stop, and when you will review the result.