Mock answer: resolving a conflict

Use a disagreement about architecture, scope, priority, risk, or people—not a trivial misunderstanding. Both sides should have a defensible goal.

• Who was affected
• What each side optimized
• Cost of delay or wrong decision
• Your role and authority

Show how you learned the other perspective and restated the shared goal. Jumping straight to winning signals poor collaboration.

• One-on-one discovery
• Constraints you had missed
• Shared success criterion
• Areas of agreement

Use a prototype, benchmark, customer data, written decision record, or reversible experiment to move the disagreement from status to facts.

• Options compared
• Measurement
• Risk and reversibility
• Decision owner

Once a decision is made, make the handoff and accountability clear. A good result includes the ongoing relationship and a better decision process.

• What changed technically
• What changed in delivery
• Relationship outcome
• Reusable process

Prepare what you would do if the evidence had favored the other option, where you were wrong, and whether the same person would work with you again.

• Why escalation was or was not needed
• Your mistake
• Alternative result
• Later collaboration