Do Not Try to Win Against People Who Hit You with 'Logical Truths'—Work Techniques for 'Changing Structures' Seen by a 20-Year PM

To be honest.

Twenty years ago, when I was hit with a logical truth, I would hit back with a logical truth.

“Isn't that a lack of confirmation on your company's part?” “The spec change is due to your convenience, right?” “It says this in the PMBOK.”

——Everything was correct. Everything was a logical truth.

And everything made the situation on the ground even worse.

It's different now. When I'm hit with a logical truth, I don't get as angry as I used to. I find myself thinking more often, 'Ah, this person is anxious, too.'

And, rather than blaming people, I change the structure.

After 20 years in the field, that is what I always come back to.

Chapter 1 | Logical truths are not necessarily the correct answer

When you stand on the front lines of a project, logical truths are scattered everywhere.

Improve quality. Meet the schedule. Reduce costs.

They are all logical truths. None of them are wrong.

However——you cannot do them all at the same time.

Anyone who has worked as a PM knows this trilemma firsthand. If you try to improve quality, costs will balloon. If you try to cut costs, the schedule will extend. If you try to tighten the schedule, quality will drop. This is the absolute fundamental of project management: the 'QCD trade-off'.

A project is a world where logical truths collide with one another.

Nevertheless, there is always someone who appears on the scene who 'insists on bringing in logical truths as the absolute correct answer.'

They say, 'Quality cannot be compromised,' while also saying, 'The budget cannot be changed.' They say, 'The schedule is absolute,' while also saying, 'Please add these additional requirements.'

It is contradictory. But each one is a logical truth.

The troublesome part is that it is difficult to argue against them. I can't exactly say, 'Quality should be compromised.' I can't say, 'You don't have to meet the schedule.' If I try to argue against a logical truth head-on, I become the person who 'wants to lower quality' or 'doesn't want to meet the schedule'.

If you start fighting logical argument against logical argument without realizing this trap, the workplace will become a war of attrition.

A lesson as a PM: A logical argument is not about 'what is correct,' but about 'what to prioritize.' Before fighting logical argument against logical argument, bring the discussion to the level of priorities.

Chapter 2 | The Goal of 'Logical Argument' Dominance is Not 'Problem Solving'

Having observed the field for 20 years, I have realized something.

People who use logical arguments to dominate are not trying to solve problems.

They want to show that 'they are right.'

They may appear to be saying 'we should improve quality,' but in reality, they want to say 'I am a decent person who is strict about quality.' They may appear to be saying 'it is natural to keep to the schedule,' but in reality, they want to say 'I have professionalism.'

In other words, the logical argument has become a 'means of self-proof' rather than a 'means of assertion.'

That is why if you counter-argue, it becomes a war.

For the other party, it is not a 'discussion about quality' but an 'attack on their identity.' The moment you say 'that is realistically difficult,' they hear 'you are a person who disregards quality.'

You just want to solve the problem, but the other party is trying to protect their identity. The goals are fundamentally mismatched.

If you do not understand this structure and think 'you should just return a logical argument to a logical argument,' you will continue to be exhausted for the rest of your life.

A lesson as a PM: The person using logical arguments to dominate does not want to 'solve the problem' but 'wants to be thought of as correct.' If you counter-argue without understanding this motive, you will destroy the relationship rather than solve the problem.

Chapter 3 | Actually, the More Anxious a Person Is, the More They Brandish Logical Arguments

If we dig a little deeper, there is 'anxiety' behind the logical argument dominance.

The most troublesome person I have thought of in 20 years was not someone who yelled. People who raise their voices are still easier to understand because their emotions are on the surface.

The most troublesome person is the logical arguer who harbors anxiety.

Inside such people, there is usually a voice like this.

'I don't want to take responsibility,' 'I don't want to be scolded by my boss,' 'I don't want to be thought of as having failed,' 'I don't want to be thought of as incompetent.'

They cover that anxiety with armor called logical arguments.

Therefore, there is more meaning in the act of stating a correct argument than in the content of the argument itself. 'The version of myself that kept saying to improve quality' remains on the record. This allows for the later excuse that 'the drop in quality was because the PM was weak-willed'.

This is a structure for avoiding responsibility.

And the most troublesome part of this is that it is difficult to point out. You cannot say, 'You are avoiding responsibility.' After all, the other person is stating a correct argument.

Lesson as a PM: When you understand the anxiety behind a correct argument, the anger disappears. The moment you think, 'This person is scared too,' calm handling begins.

Chapter 4 | Therefore, You Must Not Fight

So, what should you do?

First, let's organize what you must not do.

Examples of NG responses

'But realistically...' 'That is wrong.' 'Isn't that your company's responsibility?' 'This is what the PMBOK says.'

These are all correct arguments. But they are all counterproductive.

Because they take the form of denying the other person's identity, a defensive reaction occurs. It leads directly to the assessment that 'this person doesn't understand' or 'this PM is useless.' At worst, it leads to all-out war.

So, what do excellent PMs do?

First, say, 'You are absolutely right.'

This is not fawning. By sending a signal that you have 'received their correct argument as a correct argument,' you deactivate their defensive reaction.

And then, say this:

'Given that premise, how should we handle the priorities?'

Shift the discussion from 'right vs. wrong' to 'what should we choose?'

'Improving quality is correct. Meeting the schedule is also correct. Keeping costs down is also correct. It is difficult to do all three at the same time. Could you help me decide which one to prioritize?'

With this, the other person is no longer 'having their correct argument denied' but is now 'on the side of deciding together.' You can bring them into a structure where the responsibility for the decision is shared.

Do not deny correct arguments, do not fight, and change the structure of the discussion. This is the core of how to deal with 'correct argument mounting' that I have learned over 20 years.

PM Lesson: After signaling that you have 'received' their logical argument, pivot to the question of 'what is the priority?' Change the playing field of the discussion without fighting.

Chapter 5 | Don't Change People, Change the Structure

Having written this much, I will tell you the truth.

You cannot change someone who uses logical arguments to assert dominance.

In my 20 years of experience, I have almost no memory of seeing someone who 'constantly blames others with logical arguments' change. The root of that person's anxiety often cannot be solved within the project. It might be organizational culture, their relationship with their boss, or career anxiety—all of which are outside a PM's jurisdiction.

That is why I stopped trying to change people. Instead, I poured all my energy into changing the structure.

Specifically, this is what I mean.

Change the meeting structure. Logical argument dominance is prone to happen in meetings where everyone is present. People want to prove themselves in a 'watched' environment. Important discussions should be held in small, closed settings.

Keep meeting minutes. 'He said, she said' creates opportunities for logical argument dominance. Clearly state decisions, pending items, and assignees, and have everyone confirm them. Before someone can say 'It's your responsibility,' leave a record saying, 'We decided on this matter this way, didn't we?'

Clearly define priorities in writing. If you only say 'Quality is the top priority' verbally, someone will inevitably come out later saying, 'I thought the schedule was the top priority.' Document that 'In this phase, Q is the top priority among QCD.' Document it even when changing it later.

Involve a third party. When it's just the parties involved, it easily becomes a battle of logical arguments. By bringing in a steering committee or external reviewers, the 'third-party perspective' acts as a buffer.

These are all approaches not to 'deal with the person saying logical arguments,' but to 'create a structure where logical arguments cannot be used as a weapon.'

PM Lesson: Do not try to change people; change the structure. Meeting structures, minutes, documenting priorities, and utilizing third parties—these are the most realistic ways to 'minimize the damage of logical argument dominance.'

Epilogue | In the End, It Is Not the 'Most Correct' Person Who Saves the Project

Over 20 years, I have heard many logical arguments.

About quality, about cost, about schedule, about where responsibility lies. Everything was correct. None of it was wrong.

But in the end, the person who saved the project was not the most correct person. Nor was it the most senior person.

It was the person who listened to others the most. It was the person who organized priorities the best. It was the person who looked at the structure the most.

I stopped getting angry at people who hit me with logical arguments, not because they were wrong, but because I came to understand that they were wearing the armor of 'logical arguments' because they were anxious, too.

Blaming anxious people solves nothing. It is much faster to change the structure that creates that anxiety.

This is what I've learned over 20 years.

When you are hit with logic, I want you to try just one thing starting today.

“You are absolutely right. Now, how should we handle the priorities?”

There will surely be days when this one sentence prevents a war from starting.

Related Articles

Field PM's Practical Notes (Free Articles/Thinking Methods)

Full Table of Contents | The job of a PM is something no one teaches you—Everything I've learned in 20 years on the job (Available for free)
https://note.com/quiet_emu2080/n/nc727b32351ab

PM's Mindset—What 20 years have taught me that you can't learn from a body of knowledge
https://note.com/quiet_emu2080/n/n2b23c914ea67

The first job a PM should do—Agreeing on a 'Meeting Design Document' with the client before the kickoff
https://note.com/quiet_emu2080/n/n10b6804b54b7

Field mediation protocols to scope out fruitless adjustments
https://note.com/quiet_emu2080/n/n3a49f518e1d2

Individual plugin negotiation techniques to avoid psychological deadlocks
https://note.com/quiet_emu2080/n/n5e84c129a0b1

The boss who doesn't get angry (Free)
https://note.com/quiet_emu2080/n/ne8ec973a6e19

PMs who crush their subordinates vs. PMs who nurture them
https://note.com/quiet_emu2080/n/nb9663002771b

Career, Mindset, and the Aesthetics of Effort

Why you fail if you work based on your job title—That way of working is lowering your market value
https://note.com/quiet_emu2080/n/nff1b906accea

Is effort about quantity or quality?—Why this debate is off the mark
https://note.com/quiet_emu2080/n/ne7bbc096de54

That effort is being wasted because of your environment
https://note.com/quiet_emu2080/n/n373a5cc65323

There are worlds you can't reach without companions—What =LOVE, Abe Reiji, and PM work taught me
https://note.com/quiet_emu2080/n/n7f82e4d646bb

▼ For those who want to deepen their field operations

If you can build a foundation in the first two weeks, you can then move on to planning for the next three months to a year.
From handling project fires, stakeholder management, and remote PM work to mentorship theories, I have systematized the techniques that actually worked in the field, complete with 8 Excel templates. I hope you use this as a practical roadmap for a long career as a PM.
・A complete practical index packed with all the techniques of a 20-year PM (¥2,980)
https://note.com/quiet_emu2080/n/nd22c7c98908c