Roshan Did Everything the HR Playbook Said and Got Exactly Nowhere
Roshan is a senior manager at a logistics firm in Chennai. He has been in the role for three years. In that time he has managed twelve people, navigated two reorgs, and built a team that his own manager describes as high-functioning. He is not a manager who ignores problems or waits for them to resolve on their own.
Deepa is one of his team leads. She joined fourteen months ago from a competing firm where she had built a pricing analytics function from scratch. She is technically excellent.
Her numbers are clean. Her team respects her. And she has a reputation that follows her everywhere on the floor: difficult.
In meetings, she challenges everything. Not occasionally. Every meeting.
She questions assumptions in presentations that have already been through two rounds of review. She pushes back on timelines that have been agreed on by people with more context than she has. She raises objections in the final ten minutes that reopen discussions everyone thought were closed. People in the room have learned to brace when she speaks.
When Roshan gives her feedback, she shuts down. Not dramatically. She becomes precise and minimal.
She answers questions directly and volunteers nothing. The one-on-ones that used to run forty-five minutes now end in twenty. She is compliant and absent at the same time.
When a decision comes down that she disagrees with, she goes silent. The silence is not just hers. It spreads to the two analysts on her team who sit near her.
By the end of the week after a contested decision, the corner of the floor where Deepa sits feels like a separate weather system. People from other teams notice it. Her skip-level manager has noticed it.
Roshan has not ignored any of this. He has done what every competent manager does. He addressed her behavior directly in a one-on-one three months into her tenure.
He named what he was seeing, described the impact, and asked for her perspective. She acknowledged it. She said she would work on it.
For six weeks, the meeting behavior softened. Then it returned.
He set clear expectations. He was specific: challenges should come with alternative proposals, objections should be raised before the final review, silence is not an acceptable response to feedback. She agreed.
She met the expectations for a month. Then the pattern returned, with slightly different surface expressions but the same essential quality.
He escalated once, when the silence after a contested decision lasted two full weeks and affected a project deadline. HR sat in on a conversation. Deepa was professional.
She committed to better communication. For three weeks, things were better. Then they were not.
Each intervention produces a period of compliance followed by a return to the exact same pattern. Roshan is not failing to apply the techniques. He is applying them correctly.
He is consistent, specific, and fair. He is doing what the playbook says to do and getting a result the playbook does not explain.
The problem is not that the techniques are wrong. The problem is that the techniques address behavior, and behavior is not the source of the difficulty. Every intervention Roshan has made lands at the output level.
The mechanism generating the output sits one level below where he is working. He never reaches it. The behavior returns because the pattern generating it has never been touched.
The standard playbook for handling difficult people runs on the assumption that difficult behavior is the problem. Address the behavior, and you address the difficulty. Set expectations, give feedback, escalate if needed.
This approach is coherent. It is also always operating at the wrong level.
The Behavior Is the Output. The Pattern Is the Source.
Deepa does not challenge everything in meetings because she is a difficult person. She challenges everything because a pattern is running. That pattern has a structure.
It has triggers. It has an intention at its source. And it runs automatically, regardless of whether the current context calls for it.
This is the mechanism Antano Solar John points to when he describes why responding at the behavior level consistently fails. The behavior is downstream of the pattern. When you address the behavior, you are addressing the output.
The pattern that generates the output remains untouched. You can suppress the output temporarily. The pattern resurfaces it because the pattern has not changed.
Think about what Roshan is actually doing each time he intervenes. He addresses the challenging in meetings. Deepa modifies her behavior.
The pattern that generates the challenging is still present. It is now finding a different exit. Six weeks later it is expressing through a slightly different behavioral channel.
The surface has changed. The structure beneath has not.
Deepa's pattern likely did not form in this job, in this company, in this meeting room. Patterns that produce the kind of consistent, automatic behavior Roshan is observing are usually much older than the situation in which they appear. A pattern of challenging everything may have formed in an environment where unchallenged decisions routinely caused real harm.
It may have formed in a context where being the person who asked the uncomfortable question was the only way to be taken seriously. It may have formed in a situation where silence after a contested decision was the only safe response available.
Whatever the origin, the pattern does not check the current context before executing. It runs. The current context is a logistics firm in Chennai in 2024.
The pattern was calibrated to a different context, in a different time, under different conditions. It runs anyway, because that is what patterns do. They are automatic.
They do not require deliberate activation. They fire in response to triggers that match the conditions under which they formed, even when the current situation is nothing like the original one.
This is the point where Roshan's frame becomes the central problem. His frame is: Deepa is a difficult person. Inside that frame, certain responses are visible and others are not.
The responses visible in that frame are: address the behavior, set expectations, escalate. He has tried all three. They are the complete menu available inside the frame he is using.
The frame shift Antano Solar John describes is this: Deepa is not a difficult person. A pattern is expressing itself through Deepa. That pattern has a logic.
It has an intention at its source. It can be understood.
When Roshan holds that frame, something changes before he says a word. He is no longer managing a difficult person. He is engaging with a pattern.
And patterns, unlike personality traits, can be read. They have structure. They have triggers.
They have a consistent internal logic that, once visible, makes the behavior make sense. Not acceptable necessarily, but sensible. And sensible behavior is something you can engage with at the level where it is being generated, rather than suppressing it at the output level and waiting for it to resurface.
The frame shift does not require Roshan to excuse Deepa's behavior or pretend the impact on the team is not real. The impact is real. The pattern reading does not eliminate the need for accountability.
It changes what accountability is aimed at. You are not holding the behavior accountable. You are engaging with the pattern that generates it.
Those are different interventions. One produces temporary compliance. The other, when done well, produces a change in the pattern itself.
What Roshan Can See in Frame A and What Opens Up in Frame B
In Frame A, Deepa pushes back hard in a meeting about a new routing algorithm that affects her team's workload calculations. Roshan manages his reaction. He stays neutral in the moment, redirects the meeting, and schedules a one-on-one conversation for later that afternoon.
In the one-on-one, he addresses the behavior. He describes what he observed. He explains the impact: the meeting ran over by twenty minutes, two other team leads looked visibly frustrated, the discussion that needed to happen got displaced.
He sets an expectation: challenges with no proposed alternative are not acceptable in that forum.
Deepa says she understands. The conversation has a professional resolution. Roshan leaves the meeting feeling like he handled it correctly, which he did, within the frame he is using.
Two weeks later, the behavior returns in a slightly different form. Deepa does not push back loudly in the next meeting. She sends a long message to the group channel the evening before the meeting, pre-emptively challenging the agenda item.
Same pattern, different channel. Roshan addresses that behavior too. The pattern finds another expression.
Inside Frame A, Roshan has three responses available to him: address the behavior, set clearer expectations, escalate to HR. He has tried all three. The menu is exhausted.
Now Roshan in Frame B. Deepa pushes back hard in the same meeting about the same routing algorithm. Something is different in how he receives it.
He notices a pattern. She pushes back hardest on decisions that affect the team she built, the pricing analytics function she constructed and led before joining his team. Every major objection she has raised in fourteen months traces back to decisions that touch that team's methods, data, or workload.
She is not challenging everything. She is protecting something specific. The pattern has a logic.
She built that function. She knows its dependencies better than anyone in the room. She has probably seen what happens when people who do not understand those dependencies make decisions that affect them.
The challenging is not random. It is targeted. It has been targeted since the first week she arrived.
With that read, Roshan's available responses expand immediately. He can acknowledge directly what she appears to be protecting: the integrity of the calculations her team produces. He can involve her earlier in the decision process on matters that affect her team's methods, before the meeting where the decision is being announced rather than made.
He can give her a role in implementing the change rather than receiving it, so that her protective instinct has a constructive channel.
Three responses in Frame A. Several in Frame B. The situation has not changed. The territory has changed because the frame has changed.
The distinction here is not just practical. It is a different relationship to Deepa. In Frame A, Roshan is managing a difficult person.
There is an adversarial quality to that, even when it is handled professionally. He is trying to get the difficult person to behave differently. In Frame B, he is engaging with someone whose pattern he can read.
There is no adversarial quality to that. He is not trying to change her. He is engaging at the level where her behavior is being generated.
That level responds to engagement. The behavioral level, addressed directly from outside, only produces compliance and then reversion.
Reading a pattern is not the same as excusing the behavior the pattern produces. Roshan still needs to address the impact that Deepa's behavior has on the people around her. But addressing impact is different from addressing behavior as if behavior were the source.
Impact can be addressed while simultaneously engaging with the pattern. Both conversations can happen. They are not in competition.
What changes is the sequence and the level at which the more important conversation happens.
When the Capability Runs Automatically, Conflict Can Deepen a Relationship
The claim in the video title is striking: conflicts are good, and workplace conflict can deepen relationships. This sounds wrong. Conflict tends to feel like something to get through, survive, or resolve as quickly as possible so that work can resume.
The idea that conflict could deepen a relationship requires a different context to make sense.
The context is this: when you can read the pattern behind someone's difficult behavior, you are meeting them at a level that their behavior rarely gets to. Deepa's behavior in meetings pushes people away. It generates frustration, avoidance, and eventually the label that follows her everywhere on the floor. What the behavior does not generate is any engagement with what is actually driving it.
When Roshan holds Frame B and engages with the pattern, something shifts in the relationship. He is the first person in her professional life at this company who has engaged with what she is actually doing when she challenges decisions. Not what the behavior looks like from the outside.
What the behavior is doing at the level of intention and protection. That level of engagement is rare. It registers. Not always consciously, but it registers.
The conflict that follows from that engagement is different in quality. It is not a conflict about whether Deepa is difficult or how her behavior affects the team. It is a conflict about routing algorithms, about data integrity, about how decisions that affect her team's work get made.
That is a useful conflict. It has content. It produces information. It can end with a better decision than would have been made without the challenge.
This is what Antano Solar John and Harini Ramachandran point to through Excellence Installation Technology: the conflict that is grounded in real engagement with real patterns produces something. The conflict that stays at the behavioral surface produces only friction and damage management.
There is a version of Roshan who knows all of this conceptually. He has read about pattern reading. He understands the frame shift intellectually.
When Deepa pushes back in a meeting, he remembers to try to read the pattern. He is mid-conflict, managing his own reaction, trying to run the meeting, and also trying to recall the framework. It is too much.
The recall fails. He addresses the behavior again. The same thing happens that has always happened.
There is another version of Roshan who has the capability installed. He walks into the meeting already curious about Deepa's pattern. He is not applying a technique.
Curiosity about what people are protecting is the state he enters the room with. When Deepa pushes back, the curiosity is already active. He is not managing a reaction to the behavior.
He is already reading the pattern. His available responses were expanded before the meeting began.
This is the level at which Excellence Installation Technology operates. Not at the level of giving you better techniques to apply when you remember them. At the level of installing a different default state.
The state that runs automatically in a room with a difficult person is the state that determines what responses are available to you. Change the state and the entire territory changes with it.
Roshan, in the version of this story where the capability is installed, does not need the conversation with Deepa to be a negotiation. He is not trying to get her to behave differently by explaining the impact of her behavior again. He is engaging at the level where the behavior is being generated.
The behavior changes because the pattern is being addressed, not because the output is being suppressed.
Three months after that engagement, Deepa's behavior in meetings has not become perfect. She still challenges decisions. But the challenges are arriving earlier in the process now, through channels that allow the information to be useful rather than disruptive.
The pattern has not disappeared. It is expressing through a different channel because the channel Roshan opened is one that fits the pattern's actual intention.
Read the pattern, not the behavior
The video series shows what changes when you engage at the level of pattern rather than behavior. Watch the frame shift happen in a real conversation.
Resolve Conflict