In conflicts, prioritize project success over being right by asking if you want to win. Focus on solutions, be flexible, and seek mutual benefits rather than proving points. Choose battles wisely and frame discussions around shared goals for better outcomes.
Last edited by
Related Synced
Related Synced
Choosing Outcomes over Egos in Business Disputes
TL;DR
Ask yourself "Do you want to be right, or do you want to win?" when conflicts arise
Focus on project success and client satisfaction rather than proving your point
Use this approach for scope changes, missed deadlines, and unclear briefs
Strategic thinking beats emotional reactions every time
Being flexible often leads to better outcomes than being stubborn
Main Content
The Power of Asking the Right Question
When you're knee-deep in a project dispute, ask yourself one simple question: "Do you want to be right, or do you want to win?"
This isn't about abandoning your standards or letting clients walk all over you. It's about staying focused on what actually matters. Your ego might want to prove that the client's brief was unclear, but your business needs the project to succeed.
When to Use This Approach
This mindset works particularly well in these situations:
Scope creep discussions
The client wants extra features that weren't in the original brief. You could spend hours proving they're wrong, or you could focus on finding a solution that works for everyone.
Timeline disputes
A deadline gets moved because of delays on their end. You can argue about whose fault it is, or you can work out a new schedule that keeps things moving.
Feedback rounds
They want changes you disagree with. Sometimes it's worth picking your battles and focusing on the changes that really matter.
How to Put This Into Practice
Pause before reacting
When frustration kicks in, take a moment to think about your real goal. Is it to feel vindicated or to deliver a successful project?
Reframe the conversation
Instead of "You didn't tell me this in the brief," try "Here's how we can handle this new requirement."
Look for mutual benefits
Find solutions where both parties get something they need. This often means being creative rather than rigid.
Pick your battles
Not every hill is worth dying on. Save your energy for the issues that genuinely impact quality or feasibility.
FAQs
Doesn't this just mean letting clients push me around?
Not at all. It means choosing when to stand firm based on what really matters for the project's success, not just your pride.
What if I'm genuinely right about something important?
Being right about technical issues or project constraints is different from being right about who said what in a meeting. Focus on the impact, not the blame.
How do I explain this to clients who are being unreasonable?
Frame everything around shared goals. "We both want this project to succeed, so here's how we can make that happen."
Can I use this approach with team members too?
Absolutely. It works just as well for internal disputes about design decisions, deadlines, or processes.
Jargon Buster
Scope creep - When a project gradually expands beyond its original requirements without proper planning or budget adjustments
Mutual benefits - Solutions where all parties involved get something valuable out of the arrangement
Pick your battles - Choosing which issues are worth fighting for and which ones you can let slide
Wrap-up
Next time you feel that familiar surge of "but I'm right!" in a business dispute, remember this question. Your ego might want the satisfaction of being proven correct, but your business will benefit more from finding solutions that work.
The clients who respect you most aren't the ones you've proven wrong. They're the ones who see you as someone who gets things done, even when the path gets complicated.