How To Win Arguments At Work

Have you ever tried convincing someone to try your new idea, only to hit a brick wall?

Here’s the thing: just having a strong argument and lots of data isn’t always enough to win people over. Sometimes, it can actually make things worse!

When people resist your ideas, there’s usually something deeper going on – something they’re not telling you directly.

The natural response might be to pile on more evidence and keep pushing your point. But that’s like trying to force a door that’s stuck – you might just end up breaking it. Instead, what if you tried to understand why the door is stuck in the first place?

To do this, you need to ask the right questions.

Think of it like having a master key that can unlock any door – once you know how to use it.

Example 1: The “What’s Wrong With Them?” Moment

Let’s say you’re a product manager who has carefully studied how people use your app for several months. Your research shows that users find it hard to navigate the app. Based on this data, you suggest a simpler layout that could reduce user frustration by 40%.

However, when you show this idea to the senior design team, they don’t agree with your changes.

They say the current design is too important to the brand to change.

Chances are you’ll feel frustrated and think, “Why won’t they listen to the data? Why are they so set in their ways? Don’t they care about making things better for users?”

Instead of getting frustrated, try to understand their point of view. Ask questions to learn more about their concerns. For example, you might ask:

• “What made you choose the current design?”
• “Which parts of our brand are most important to keep?”
• “What happened when we tried to change things before?”
• “What have users told you about our current design?”
  

Maybe a similar change three years ago caused problems, or perhaps certain design features help with accessibility.

Understanding what’s been done before, why it was done, and how it shapes people’s viewpoints will help you create a better plan that addresses both past issues and current needs.

Example 2: When Things Get Heated

Picture the scene, you’re leading an important presentation for a new client in the tech industry. Your team has just won a big account, and everyone wants to make a great first impression.

You think using new, interactive presentation tools will make your pitch stand out. However, your experienced colleague disagrees, preferring a traditional approach with lots of data.

The discussion gets heated.

You both start talking over each other, voices get louder, and everyone looks tense.

When things get heated, it’s important to slow down and really listen to each other. One way of doing this is to pause, repeat back what you’re hearing from your colleague, and ask for more info. For example, you might say:

• “I want to understand your point of view. You’re saying that from your experience, tech leaders prefer presentations focused on data because it helps them make better decisions. Did I get that right?”

Or…

• “Let’s take a moment to step back. You’ve had success with traditional presentations before. Could you tell me more about what worked well?”
  

By reframing their concerns and asking deeper questions, you’ll often find you can diffuse the situation and incorporate the best of both ideas into one solution.

Example 3: The Dead End

Imagine you’re leading a software development team that needs to finish a big project soon. You asked to hire two temporary developers to help, showing how much it would cost and how it would help. Your manager said no because there isn’t enough money, and didn’t suggest any other solutions.

The problem seems impossible: you have to deliver good software on time, but you don’t have enough people to do it. Your team is already working as hard as they can, and you can’t remove any features because of agreements with the client.

Instead of getting frustrated, try to turn this into a chance to work together and find solutions. For example, you could ask your boss the following questions:

• “I know we can’t hire more developers. Since we have this deadline and our team is already busy, I’d like to hear your ideas about how we could handle this. What has worked before in situations like this?”
• “If you were running this project with these limits, what would be the first three things you’d do to fix the timeline?”
  

This approach might help you find unexpected answers, like borrowing developers from other teams for a while, changing which projects are most important, or finding better ways to work that could help get things done faster.

Next time you face pushback on your ideas, take a breath, get curious, and ask questions that open doors instead of closing them.

You might be surprised at how much better your original idea becomes when you bring others along for the journey.