How to recognize a status struggle within a team

The arguments run out, but the dispute continues

Two experts have spent half an hour debating a minor part of a process. Both solutions are workable, yet neither person will give way. Eventually one says, “I've been doing this longer than you,” and the other replies, “That's exactly why we need a new approach.” At this point the conversation is no longer solely about the solution. Each proposal signals whose experience and right to influence will be recognized. Compromise may then feel like a loss of position even if it changes little in technical terms. Status means relative respect and recognition within a group. It is not the same as formal authority. A person without a management title may have considerable influence because of expertise, seniority or relationships. Status conflict arises when people contest these positions. It is useful to distinguish it from task conflict, about the substance of the work, and process conflict, about how the work is organised. They can overlap in practice, so the presence of emotion alone is not enough to identify a status struggle. A status dispute may be concealed in technical language, but it should not be assumed merely because a discussion is intense. People can defend different solutions firmly for good reasons. Check whether arguments still refer to evidence and the objective, or increasingly to who has the right to speak. Remarks that undermine a person's experience, role or significance may indicate that the conversation is shifting to their position in the group. Also notice whether participants can accept a sound idea from someone of lower status. Recognizing a possible mechanism does not determine which proposal is better; the solution must still be judged on its actual merits.

Signs that position is also at stake

Bendersky and Hays introduced and studied status conflict as a distinct group process. Their findings indicated adverse links with team performance, partly because such conflict hindered information sharing. This does not mean that every discussion of influence is harmful. A group may genuinely need to revise an informal hierarchy that no longer reflects current expertise. What matters is how it does so. Bendersky and Hays, 2012. Observe whether participants respond differently to the same argument depending on its author. Is a proposal rejected and then accepted moments later when a higher-status person voices it? Does the dispute intensify in front of an audience? Do people invoke their right to speak instead of referring to evidence? These are signals to investigate, not proof of a hidden motive. They can support questions about roles and recognition without accusing people of inflated egos.

Team changes trigger a renegotiation of position

A new expert may bring knowledge the group previously lacked. The established authority must then find their place, while the leader clarifies how decisions will be made. Similar tension can arise when a former peer is promoted or departments merge. In our example, one expert's experience and the other's new specialism may complement each other. But if the organization implies that recognizing one person requires invalidating the other, a technical discussion readily becomes a defense of personal worth. Later work by Bendersky and Hays shows that the meaning of status conflict also depends on how team members perceive hierarchy. This is another reason to avoid the simple advice “never discuss position.” Unspoken discrepancies sometimes need to be surfaced and organised. A useful conversation should lead to clarity about cooperation, not a contest over who can publicly force others to recognize their superiority. Bendersky and Hays, 2017. An unclear division of responsibility can intensify a struggle for influence. If two people do not know who makes the decision, each may seek an advantage by winning the group over or undermining the other. A call for greater respect is necessary but insufficient: the scope of decisions, how expertise will be consulted and who is accountable for the outcome must also be agreed. The facilitator should not pretend every voice has an identical role in every matter. They can explain why a particular person decides and how others' arguments will be considered. Clarity about formal responsibility does not remove every tension, but it reduces the need to renegotiate position in each new technical dispute.

How a leader can separate the layers of the dispute

First return to the criteria for the task: what determines the choice of solution, what evidence is needed and who is accountable for the decision? Then discuss roles separately. If nobody knows who approves the project, people may try to gain influence by dominating the discussion. Clear authority does not remove the need for respect, but it reduces some uncertainty. Recognize the specific expertise of both sides without artificially suggesting that every opinion is equally valuable in every area. In an individual conversation, ask: “What makes this decision difficult for you to accept?” and “What recognition of your responsibility is missing?” Do not assume the answer. What looks like status conflict may conceal a genuine risk that has not been heard. If the leader labels the problem as ambition too quickly, important information may be lost. Check the substantive arguments first, and only then explore the additional relational layer.

How to keep a discussion from becoming public humiliation

Criticise the solution without challenging the person's right to participate. “This option does not account for the cost” differs from “you always make things complicated.” Give people credit for their ideas and allow them to change their minds without presenting it as surrender. Someone who says, “The evidence has convinced me,” should not be told they were defeated. A team needs a norm in which updating a position shows responsiveness to information rather than a loss of rank. After the discussion, acknowledge contributions fairly. Adopting one person's idea need not cast the other as the loser. Explain which objections improved the solution and what was checked because of them. This is not artificial praise, but an accurate recognition that valuable participation is not limited to authorship of the final proposal. It can reduce the need to defend status at any cost. If humiliation occurred, however, address it separately. A good technical outcome neither cancels inappropriate treatment of a colleague nor removes the need to agree standards for future discussion.

A status dispute can stall a conversation even when the technical solution is simple. It helps to separate task criteria, formal roles and the need for recognition. The goal is a way of working in which influence can be organised without stripping people of respect.

Empatyzer in preparing a conversation about influence

Empatyzer can help you prepare for contact in which different positions must be discussed without undermining the other person's worth. Comparison provides a starting point for examining two people's different ways of working, while How can they help you? supports reflection on how they may complement each other. Neither feature automatically assesses subject-matter expertise or grants anyone decision-making authority. In Talk to Em about a specific person, you can prepare questions about responsibility, the influence required and how concerns should be consulted. A useful message refers to the task and the rules of cooperation instead of accusing the other person of an ego battle. Em does not detect status conflict or establish a team's hierarchy. It helps structure the conversation; clarifying roles, evaluating arguments and responding to humiliating conduct remain decisions for the people responsible for the work. This allows differences to be discussed without reducing them to personal rivalry.