What should I do when an engineer pushes back on every decision I make?

A capable engineer challenges most decisions, slowing progress and creating tension in the team.

Separate healthy challenge from habitual resistance. You want challenge that improves outcomes, not friction that stalls them.

Start by acknowledging the value: I want your input . Then set a boundary: but we need to move. Introduce a simple rule—debate, decide, commit. Give space for input up front, time-box the discussion, then make a clear decision.

If pushback continues after a decision, address it directly. Once weve decided, I expect alignment. If you disagree, we can revisit with new data, not reopen the same argument.

Also check why theyre pushing back. It can signal unclear strategy, lack of trust, or previous decisions that didnt land well. If the pattern is justified, fix the root cause. If not, its a behaviour issue.

Reinforce what good looks like: contribute early, commit after. Consistency matters more than winning individual debates.

• Set a clear

debate, decide, commit expectation

• Time-box decision discussions
• Call out post-decision resistance explicitly
• Invite input earlier to reduce late-stage pushback
• Address root causes (trust, clarity) if present

Avoid shutting down all challenge. Youll lose valuable input and create silent disengagement.

Gives you structured prompts to prepare for difficult conversations, capture decisions made, and reflect on patterns of challenge vs resistance over time.