Organizations love to mislabel power conflicts as communication problems.
The roadmap fight becomes “we need better alignment.” The pricing dispute becomes “we need clearer messaging.” The process complaint becomes “we need stakeholder management.” The cross-functional tension becomes “we should have an honest conversation.”
Sometimes that is true. Sometimes people really are missing context, using different words, or reacting to incomplete information.
But often the conflict is not primarily about communication. It is about power.
Who gets to decide? Whose goals outrank whose? Who pays the cost? Whose expertise counts? Who controls the resource? Who owns the risk? Who gets credit if it works? Who is exposed if it fails?
If you treat that as a communication issue, you will make the conflict more polite and less solvable.
Conflict reveals contested power
Conflict often appears when two or more legitimate powers collide.
Product has roadmap authority. Sales has revenue pressure and customer access. Engineering has technical-risk knowledge. Security has veto power. Finance has budget constraints. Customer success has renewal risk. The CEO has strategic context. The team doing the work has capacity reality.
The conflict is not proof that one side is bad. It is proof that the power architecture is under-specified for the tradeoff being made.
A useful operator question is: what power is being contested here?
- decision rights;
- resource allocation;
- priority ranking;
- expertise legitimacy;
- risk ownership;
- customer truth;
- agenda control;
- credit;
- workload;
- timing;
- exception authority.
Naming the contested power does not solve the conflict, but it prevents fake solutions.
Surface issue, underlying power
Consider a team arguing about launch timing.
On the surface, marketing wants a date, engineering says the product is not ready, sales has committed to customers, and support is worried about volume. It sounds like coordination failure.
Underneath, several power questions are active:
- Who has authority to set the launch date?
- Who can veto based on quality risk?
- Who owns the customer commitments already made?
- Who decides whether revenue urgency outweighs operational risk?
- Who absorbs the consequences if support volume spikes?
- Whose definition of “ready” is legitimate?
A better meeting agenda would not be “align on launch.” It would be “decide launch authority, quality veto criteria, customer-commitment handling, and risk ownership.”
That is a different conversation.
“More transparency” is not enough
Transparency helps when the problem is missing information.
It does not solve conflicts where interests, authority, or costs differ.
Two teams can see the same facts and still disagree because they are accountable for different outcomes. Sales may value speed because delay risks a quarter. Engineering may value stability because shortcuts create long-term drag. Legal may value caution because downside risk is asymmetric. Customer success may value customer trust because they will live with the promise after the deal closes.
The conflict is not irrational. It is structured.
Operators should avoid shaming people for defending the thing they are accountable for. Instead, make the tradeoff explicit and route it to the right decision owner.
Power conflicts get worse when unnamed
Unnamed power conflicts produce bad behavior.
People escalate privately. They weaponize process. They slow-roll work. They gather allies without disclosing intent. They use data selectively. They reframe decisions after the fact. They interpret every move as political because the actual power question has no legitimate place to be answered.
Naming the power dynamic often lowers the temperature.
Try language like:
- “I think we are mixing input rights and decision rights.”
- “This sounds less like a messaging issue and more like a priority tradeoff.”
- “Security has veto power here; let's define the criteria and timeline.”
- “Sales owns the customer commitment, but product owns roadmap sequencing. We need an escalation path for when those collide.”
- “The team absorbing the workload has not been part of the decision; that is a legitimacy problem.”
This is not aggressive. It is clarifying.
Conflict is data, not drama
Operators should treat conflict as information about the system.
A recurring conflict may reveal unclear decision rights. A sudden conflict may reveal hidden scarcity. A personal conflict may reveal mismatched incentives. A loud conflict may reveal that a silent group is paying the cost. A conflict that never reaches leadership may reveal fear, fatigue, or learned helplessness.
Do not rush to smooth the conflict before you understand what it is telling you.
Harmony can be a sign of health. It can also be a sign that power has already silenced dissent.
The conflict-power readout
When conflict emerges, ask:
- What is the stated disagreement? What do people say the conflict is about?
- What decision is actually being made? Is there a hidden decision under the debate?
- Who has formal authority? Is it clear and accepted?
- Who has informal power? Who can shape, block, delay, or escalate?
- What resource is scarce? Time, headcount, budget, attention, quality, risk capacity?
- Who pays the cost? Which team absorbs work, risk, blame, or opportunity cost?
- Whose legitimacy is challenged? Expertise, role, process, customer knowledge, executive mandate?
- What would resolve the power question? Clear decision owner, tradeoff call, veto criteria, escalation, resource allocation?
- What behavior is becoming unhealthy? Side channels, blame, delay, public performance, information withholding?
- What ethical guardrail is needed? No credit theft, no punishment for dissent, no hidden veto, no manipulation.
This readout turns conflict into operating data.
Do not romanticize conflict
Conflict is useful only when it helps reveal reality and make better decisions.
Some conflict is just ego, poor behavior, unclear expectations, or lack of skill. Naming power does not excuse disrespect. It does not mean every objection is noble. It does not mean every stakeholder gets equal decision weight.
The point is not to celebrate conflict. The point is to stop misdiagnosing it.
A well-run organization does not eliminate power conflict. It gives power conflict legitimate channels: explicit decision rights, escalation paths, risk criteria, resource tradeoffs, and norms for dissent.
One warning: do not use “this is really about power” as a clever way to dismiss substance. Sometimes the quality concern is real, the customer risk is real, the architectural objection is real, and the person raising it is doing the organization a favor. The operator move is to separate the substance from the power question, then resolve both.
The hard truth
When important people are fighting about “alignment,” they may really be fighting about power.
Strong operators do not panic when conflict appears. They read it. They ask what authority, resource, legitimacy, or decision right is contested. Then they make the power question explicit enough to resolve.
