“The Model Isn’t the Problem. You Are.” — When Criticism Turns Personal

A review of a process model. Amira shows her work to Jonas.

— This model doesn’t hold up against the assumptions.
— Maybe read the assumptions before saying the model doesn’t work.
— I did. That’s exactly why I’m saying it doesn’t hold up.

The conversation starts with the quality of the model. Within moments, both people are hearing a judgment of their own competence.

What really happened

Jonas starts with a substantive criticism of Amira’s model. Amira quickly hears more than a statement about the model; she also hears a judgment of her competence. She responds not to the technical argument but to the way Jonas is speaking to her. Jonas reads that response as evidence that Amira cannot take criticism, and he too shifts from the work to the person. Within minutes the conversation is no longer about the model’s assumptions. It is about who is difficult, who is overreacting, and who behaves like an examiner. This is a classic change in the level of conflict: a disagreement about the task becomes a disagreement about the people.

What the research says

Team research distinguishes conflict about the content of the work from relational conflict — task conflict versus relationship conflict. Meta-analyses show that relationship conflict is clearly associated with poorer team functioning and that task conflict can spill over into relationship conflict (De Dreu & Weingart, 2003; Yu & Wei, 2025). An updated 2026 meta-analysis likewise reports that the major forms of team conflict are, on average, associated with poorer outcomes, although the size of the effect depends on context (Yuan, Yin, & Sun, 2026). None of this means teams should avoid disagreement. It means the disagreement needs to stay attached to its object before it starts defining the people involved.

How to handle it

Helena’s most useful move is to stop the exchange and ask about one specific part of the model. That restores a shared object of disagreement. Helpful language includes: “I’m challenging assumption X, not your competence,” followed by “What evidence would settle this point?” If there is also a problem with conversational style, handle that separately rather than mixing it into the technical decision. The general rule is: when a disagreement starts producing sentences such as “you always,” “you’re impossible to work with,” or “you don’t understand,” return to the specific decision, data, or assumption that was actually under discussion.

How Empatyzer and Em can help

Empatyzer can help stop this conflict before “the model doesn’t work” becomes “you are the problem.” Comparing Amira’s and Jonas’s profiles may show that one reacts more strongly to how criticism is delivered, while the other naturally separates evaluation of a solution from evaluation of the person. Before a review, Em can therefore prompt Jonas to anchor criticism in a specific assumption and evidence, while helping Amira check whether the criticism is actually about her work or about her competence. If similar clashes repeat across the team, the team view can show that the problem may be a collision of styles rather than a “difficult personality.” Micro-lessons reinforce a simple habit: criticize the object, name the criterion, and do not invent the other person’s intention.