Someone who agrees then undermines needs to see the gap between what they accepted in the decision room and what they did afterward. Bring the decision record, the later message, and the work that stopped or split. Ask whether new evidence appeared. Then require one public path for disagreement, with a named owner and a date to inspect the next decision.
What exactly counts as undermining?
Disagreement after a meeting is not automatically undermining. Engineers should reopen a choice when material new evidence appears. The concern is saying yes to a decision, then privately advising another team to ignore it, restarting the same argument in Slack without new facts, or withholding implementation while others believe the plan is active.
Prepare the sequence. On Tuesday, the group chose event streaming after reviewing two options. The engineer said they could support the choice. On Wednesday, they told the data team that batch processing remained the real plan and asked them not to start. On Thursday, both teams paused because authority was unclear. That chain is concrete enough to discuss.
How do you open the 1 on 1?
Say: “I want to discuss the gap between Tuesday's decision and your messages afterward. In the meeting, you agreed to implement event streaming. The next day, you asked the data team to wait because you said the decision was still open. They stopped work. What changed for you after the meeting?” The question leaves room for new evidence.
Do not begin by calling them disloyal. They may have believed their meeting response meant only that they had heard the decision. That interpretation still needs correction, but it is different from intentional sabotage. Clarify what agreement meant, what authority made the choice, and what route remained available for concerns.
How should new evidence be handled?
Ask for the fact, when it became known, and how it changes the chosen tradeoff. A production measurement that invalidates capacity assumptions deserves prompt review. A repeated preference presented as new evidence does not. Record the distinction so future disagreement is evaluated by substance, not by who is most persistent.
Create a rapid route for real risk. The engineer can post the evidence in the decision channel, tag the owner, and request a review by a named time. Until the owner pauses the decision, the public plan remains active. This protects both technical dissent and coordinated execution.
What public path should you require?
The short ask can be: “If you believe an agreed decision must change, bring the concern and evidence to the decision owner in the shared channel. Do not tell another team that the plan is different before the owner changes it.” Ask the engineer to repeat the route and identify the current owner.
Public does not mean performative conflict. Sensitive people issues stay private, and a quick private check can precede a shared correction. The final work direction must be visible to everyone affected. Parallel private versions force other teams to choose whose authority to trust.
Which records should you compare?
| Moment | Record | Question |
|---|---|---|
| Decision | Choice and owner | What was agreed? |
| Later concern | Message and evidence | What changed? |
| Work response | Pause or rework | Who was affected? |
| Correction | Shared update | Is one plan visible? |
Use the decision note and messages rather than recollection alone. Tone may matter, but direction matters first. An apparently polite private message can still split execution. A blunt public concern may be appropriate if it follows the agreed route and names real risk.
How can the decision process be repaired?
- Restate the original choice and authority.
- Identify any evidence that appeared later.
- Decide whether the choice is paused.
- Publish one current direction.
- Name work that must restart or change.
- Confirm the route for future dissent.
- Review the next decision on a set date.
The manager may discover that the meeting itself invited false agreement. Perhaps a senior leader closed discussion abruptly or nobody asked for objections. Improve the decision ritual by recording dissent, naming the owner, and asking each affected lead whether they can execute. Better process does not excuse later private contradiction, but it reduces ambiguity.
What if they say they never agreed?
Read the decision record and ask what words they used. If “sounds fine” was interpreted as commitment while they meant no objection, acknowledge the ambiguity. Then define the future standard: agreement to execute means they will follow the plan while using the stated route for new concerns. Ask for an explicit answer before leaving future decision meetings.
If the record shows a clear commitment, do not argue endlessly about private intention. State how the group reasonably understood the response and what happened afterward. The work standard concerns reliable signals. An engineer is responsible for correcting a misunderstanding before acting against the shared plan.
How do you address private coalition building?
It is reasonable to seek technical advice. It becomes a problem when the engineer recruits another team to resist a decision without telling the owner or affected peers. Name the specific messages and the resulting confusion. Ask what outcome they were trying to create and why they avoided the decision route.
Require them to repair the split with the people they contacted. The correction can say that the recorded decision remains active, the concern has been sent to the owner, and no alternate direction should be followed unless a shared update appears. You should support the correction without writing a false apology for them.
What should happen at the next check?
Choose the next planning or architecture decision as the test. Observe whether the engineer states disagreement in the room, records any concern, gives an honest commitment, and uses the public route if evidence changes. Meet within one day while the sequence is fresh. Do not wait for another team to report confusion weeks later.
If the behavior changes, recognize the direct dissent and reliable execution. You want the engineer to challenge decisions well, not become silent. If the same private contradiction repeats, state that trust in their commitments is now a performance concern and follow the appropriate process with evidence.
How can meetings make honest disagreement easier?
Ask for concerns before closing the decision, especially from people who argued for another option. A direct prompt such as “What risk makes this hard to support?” is more useful than “Are we all aligned?” Record the answer even when the owner proceeds. Visible dissent lets the engineer preserve technical integrity without pretending enthusiasm, and it gives future evidence a known place to attach.
Distinguish consent, commitment, and awareness. A person can understand a decision without endorsing it. They can disagree and still commit to execute it. Use explicit language: “The owner chose event streaming. Can you implement this plan, and is there any risk that should be recorded?” A vague round of nods creates weak signals that people later interpret according to preference.
After the meeting, publish the choice, owner, dissent, assumptions, and review trigger. A review trigger might be latency above a threshold or a missed dependency date. This gives the engineer a legitimate route to say that conditions changed. It also makes clear that repeating the old argument without the trigger is not new evidence.
If the engineer has low trust in the decision owner, address that relationship separately. They may believe concerns are heard only after they recruit allies. Ask for examples, examine whether decisions are explained, and improve access where needed. Still require them to use the visible route. Distrust can explain covert behavior without making parallel direction safe.
At follow up, inspect whether the team experienced one plan. Ask the affected partner what direction they received, whether any concern was clearly labeled, and whether they knew who could change the choice. Do not ask partners to judge the engineer's loyalty. The evidence is coordinated execution with an honest dissent path.
Recognize a future moment when the engineer disagrees openly, commits accurately, and later raises real evidence through the owner. That is not reluctant compliance. It is mature engineering participation. Your response should show that direct dissent remains welcome, because punishing the first honest objection will send the disagreement back into private channels.
What if the manager is not the decision owner?
Do not imply authority you do not have. Bring the recorded owner into the repair and describe the conflicting directions factually. Your role may be to coach the engineer, protect your team's work, and ensure that the person with authority publishes one plan. If another leader privately encouraged the alternate direction, the issue is larger than one engineer. Ask the leaders to resolve it directly instead of forcing the engineer to choose which private instruction is safer. Even then, examine how the engineer responded. They could have surfaced the conflict rather than presenting one instruction as settled. Set the future requirement: when two people with apparent authority give different directions, pause the affected work, name the conflict in the shared route, and request one owner by a specific time. This is not permission to freeze every disputed task. It is a controlled response to genuine authority ambiguity. At follow up, inspect whether leaders honored the route too. Managers who continue giving private exceptions cannot fairly demand perfect public alignment from engineers. The conversation succeeds when dissent, evidence, and authority are visible enough that another team does not need personal relationships to discover which decision counts.
What are common questions?
Is reopening a decision always undermining?
No. Reopen it when material new evidence appears, using the visible route and named decision owner.
What should agreement mean?
It means the engineer will execute the recorded plan while raising later concerns through the agreed process.
Should private technical advice be banned?
No. Advice is useful, but alternate work direction must not be built through private messages.
How should the engineer repair confusion?
They should publish the current direction, route their concern to the owner, and tell affected teams which plan remains active.
When should you follow up?
Review the next real decision within one day, using the meeting record and any later messages.
Related: having a difficult conversation with an engineer, talk to someone who puts themselves first, talk to a strong engineer who hurts the team.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.