Vikram Read Every Book and Watched Every Technique Fail
Vikram runs the product team at a mid-sized software company in Bengaluru. He has eleven people reporting to him. Two of them, Neha and Arjun, have been in a slow, grinding conflict for four months.
Every sprint review ends with one of them challenging the other's estimates. Every stand-up has a moment where the air in the room changes and everyone else goes quiet.
Vikram does not ignore this. He reads. He attends a two-day mediation and conflict resolution workshop that his company pays for.
He takes notes. He learns about active listening. He learns about separating the person from the problem.
He learns about creating psychological safety. He practices restating what the other person has said before responding. He learns the exact phrases: 'What I hear you saying is...' and 'Help me understand...'
He is applying the techniques. He is doing what the books say to do.
In a one-on-one with Arjun, Vikram asks the question the workshop said was an ideal tool for understanding: 'Why did you push back on Neha's estimate in today's review?'
Arjun goes quiet for two seconds. Then he says: 'I did not push back. I asked a question.'
The conversation does not go anywhere useful after that. Arjun is defensive. Vikram tries to explain that he is not accusing him.
Arjun says he knows, but his body language says something different. By the end of the conversation, Arjun feels surveilled and Vikram feels like he failed at something he studied for.
He tries again with Neha. Same question, different words: 'I want to understand why the timeline feels unrealistic to you.' Neha gives him a technical answer about dependencies and third-party APIs. It is accurate and useful and it does not touch the actual conflict at all.
She is telling him the reasonable professional version. She is not wrong. She is just not at the level where the conflict actually lives.
Vikram tries the group session. He gets Arjun and Neha in a room. He facilitates.
He uses the structure from the workshop: each person states their view, the other person reflects it back, then they identify common ground. Neha says the timeline is unrealistic. Arjun reflects it back correctly.
Then Arjun says the timeline is the only one that meets the client commitment. Neha reflects it back correctly. They have each heard the other. Nothing has changed.
Vikram is doing everything the playbook says and the playbook is not reaching the conflict. He is not failing at technique. The techniques are simply operating at the wrong level.
This is the point where standard conflict resolution training stops. It has given you the tools. If the tools do not work, the assumption is that you need more practice, or better tools, or a different workshop.
What the training rarely says is that the tools are designed for a level of conflict that is not where conflict actually lives.
The standard view of conflict resolution techniques holds that if you ask the right questions, stay neutral, and create space for each side to be heard, resolution follows. The question 'why' seems ideal for this: it invites explanation and signals curiosity. What it actually does is something different entirely.
Why 'Why' Is the Wrong Question and What Happens When You Ask It
Antano Solar John describes 'why' as an exceptionally ambiguous question in the language. When you ask someone 'why did you do this,' they face an immediate problem: they do not know what you are asking. The single word 'why' can mean at least four different things depending on context, tone, and relationship.
It can mean: what was your purpose? It can mean: what was your intention? It can mean: what triggered you to act?
It can mean: what satisfaction or benefit did you get from this? Four different questions. One word.
The person being asked has to guess which of these four you mean. And because they are in a conflict context, they are already primed to expect accusation. So they guess the one that sounds like an accusation: what satisfaction did you get from doing this to me?
That is not a conscious process. It happens in the time it takes to inhale. The person has already answered the wrong question before they have said a word.
Then notice what the word 'because' does when it arrives in the answer. 'Because' nearly always precedes an excuse rather than high-quality information. Not because the person is dishonest. Because the structure of the question has already set up a frame where they are defending themselves. You asked 'why.' They heard an accusation. 'Because' is the word that starts the defense.
Try it with a child who comes home two hours late. Ask: 'Why did you do this?' Watch what happens. The child does not respond with a clear account of their reasoning.
They respond with either a defense or silence. The dynamic is not a feature of childhood. Adults run the same pattern.
The question triggers the same response in a product manager as it does in a twelve-year-old.
This is not a communication skill problem. Vikram was not asking 'why' in an accusatory tone. He was genuinely curious.
The tone did not matter because the word itself carries the ambiguity and the ambiguity carries the threat.
Now contrast this with a different question. Not one you ask the other person out loud. One you ask yourself silently before the conversation: what could be this person's intention? What are they trying to protect?
That question does something entirely different inside you. It sends your attention somewhere different. It is not searching for evidence of bad behavior.
It is searching for what they are trying to accomplish. And what it finds is nearly always something recognizable. Arjun is trying to protect the client commitment.
Neha is trying to protect the team from an impossible deadline. They are both trying to protect something real. They are not enemies. They are two people protecting the same thing from two different angles.
This is what Antano Solar John describes as parts integration. At the behavioral level, two parts are in conflict. Arjun's behavior and Neha's behavior appear to be directly opposed.
But at the level above behavior, at the level of intention and goal, they are not in conflict at all. Both of them want the product to ship well. Both of them want the team to succeed.
The conflict is at the level of strategy. The alignment is at the level of goal. Standard conflict resolution techniques never reach the level of goal because they stay at the level of strategy and behavior.
The question 'why' keeps everyone at the level of behavior and defense. The question 'what could be their intention' shifts the search to the level where the alignment already exists.
The Distinction Between Addressing Behavior and Finding the Level Above It
Vikram has been trying to resolve a conflict between two behaviors. That is what the workshop taught him to do. Get the two behaviors to co-exist more peacefully.
Find a compromise at the level of position. Create a process that manages the friction. Every technique in the standard toolkit is designed for exactly this: working with the visible, behavioral surface of the conflict.
What Antano Solar John teaches is something different. The conflict between Neha and Arjun is real. But it is not where it appears to be.
It appears to be about the timeline. It is actually about two people trying to protect the same thing using incompatible strategies.
Neha is protecting the team. She has watched people burn out on impossible timelines. She knows what a failed sprint does to morale.
She is not being obstructionist. She is being protective.
Arjun is protecting the client relationship. He made a commitment. The company's reputation is attached to that commitment.
He is not being inflexible. He is being responsible.
Both of them want the product to ship. Both of them want the team to function well afterward. Both of them want the client to be satisfied.
The alignment is complete at that level. The conflict is only at the level of the strategy each has chosen to protect those shared goals.
When Vikram stops asking 'why did you do that' and starts asking himself 'what is this person trying to protect,' his internal state shifts before he says anything. He is no longer approaching Neha as someone who is creating a problem. He is approaching her as someone who is protecting something real.
That shift is not invisible. It is visible in the way he enters the room. It is visible in what questions he asks. It is visible in what he does not say.
He goes to Arjun not to get Arjun to accept Neha's timeline but to find out what Arjun is protecting. Arjun tells him about the client commitment in a way he has not described it before, because Vikram is not defending or challenging. He is genuinely locating what Arjun is trying to protect.
Then Vikram goes to Neha. He is not mediating. He is not presenting Arjun's position for Neha to rebut.
He is asking what she is protecting. The conversation is different because the question is different.
What emerges is not a compromise. It is a recognition. Both of them are protecting the same outcome from different angles.
Once that is visible to both of them, the conversation about the timeline becomes a shared problem rather than a contested position. They still have to solve the problem of a tight deadline and a risk-averse team member. But they are solving it together now.
The problem has not changed. The level at which they are engaging with it has changed.
This is what parts integration means in practice. You are not mediating between two adversaries who each need to give up something. You are finding the level at which they are already aligned and making that level visible.
Once the alignment at the level of intention is visible, the conflict at the level of strategy becomes a logistics problem rather than a personal one. Logistics problems have solutions. Adversarial conflicts at the behavioral level often do not.
The standard toolkit stays at the level of behavior because that is the level that is visible. What is visible is where the standard frameworks are built. But the visible level is not where the conflict lives.
What Changes When This Becomes a Capability and Not a Technique
There is a version of Vikram who knows all of this intellectually and a version of Vikram who has it operating automatically. They are not the same person in a conflict situation, even though they have access to exactly the same information.
The first Vikram remembers to ask about intention after the conversation has already gone somewhere he did not intend. He is fifteen minutes into a difficult exchange and he recalls: I am supposed to ask what they are trying to protect. He tries to pivot.
The pivot is visible. It feels calculated. The other person senses the technique being applied and adjusts accordingly.
The second Vikram enters the conversation already curious. He is not applying a technique mid-conversation. He is already at the level of intention before the first word is exchanged.
When Arjun says something that could be taken as a challenge, Vikram's automatic response is curiosity about what Arjun is protecting. Not because he remembered to be curious. Because curiosity about intention is now the state he enters conflict with.
The difference in outcomes between these two versions of Vikram is not small. The first version applies techniques to a conflict that has already escalated. The second version rarely allows escalation because the state he brings into the room is not the state that generates escalation.
This is what Antano Solar John and Harini Ramachandran describe through Excellence Installation Technology. The distinction is between something installed at the level of capability and something learned at the level of technique. A technique requires recall.
You have to remember it and apply it. A capability runs automatically. You do not have to remember to walk when you are moving through a room. The capability runs without your attention on it.
When the curiosity-about-intention pattern is installed as a capability rather than memorized as a technique, conflict resolution techniques become less necessary. Not because you have better techniques available. Because the internal state that generates the kind of conflict that requires those techniques has less material to work with.
You are entering interactions with people differently. The cues that used to trigger a defensive or adversarial response are now triggering a different search: what is this person protecting?
That search finds something. It nearly always finds something recognizable. And what it finds changes the conversation before the conversation has technically begun.
This does not mean conflict disappears. It means the conflict that does arise is at the level of logistics rather than at the level of identity and position. Logistics-level conflict is solvable.
It has concrete variables. It responds to information. Position-level conflict often does not respond to information at all because information is not what is actually being disputed.
Vikram, three months after the work described above, reports that he no longer needs to structure mediation sessions between Neha and Arjun. They are not best friends. They still disagree about estimates in sprint reviews.
But the disagreements are now arguments about data. They end with a decision. They do not leave residue.
Watch the capability, not the technique
The video series shows Antano Solar John working with conflict patterns directly. Watch what changes when the question shifts from behavior to intention.
Resolve Conflict