Cross functional communication breaks down most often because nobody owns the decision the conversation keeps circling. Teams meet, restate positions, and escalate without resolution. Better writing and more frequent updates will not repair that condition. The repair is naming who decides, who must be consulted, and when the question closes for good.
The Symptom Everyone Names and the Cause Nobody Does
Complaints about communication follow a recognizable script inside growing companies. Marketing reports that operations never shares anything until it is too late to respond. Operations reports that marketing commits to dates without asking whether those dates are possible. Both accounts are accurate, and neither one identifies the actual problem.
The question sitting underneath both complaints is who gets to set the launch date. Nobody has answered it, so each function assumes the answer that fits its own constraints. The resulting friction gets labeled a communication breakdown, because that label is available and accuses no one.
Genuine coordination between teams that depend on each other while reporting to different leaders rests on shared decision rules more than shared vocabulary. Two functions can understand each other perfectly and still deadlock for months. Understanding is not authority, and no quantity of clarity substitutes for a decision right.
A short diagnostic separates the two conditions reliably. Ask three people in the disputed area who makes the final call on the contested question. Different answers from those three indicate a decision rights problem wearing a communication costume.
Escalation behavior offers the other reliable tell for a diagnosis. When a disagreement travels upward, watch whether the senior person resolves the substance or simply repeats the instruction to collaborate. Instructions to collaborate are what leaders offer when they have not decided who wins. The teams return to the same argument with more resentment attached.
Frequency of contact often gets mistaken for the fix. Adding a weekly sync between two functions increases the surface area of the disagreement without changing its outcome. More contact produces more detailed accounts of why each side is right. The dispute becomes better documented rather than resolved.
The distinction matters because the two remedies share almost nothing. A communication problem responds to cadence, format, and better summaries. A decision rights problem responds only when somebody states out loud who decides and what everyone else may do about it.
Assign the Decision Before Improving the Message
Assigning a decision is a smaller act than most leaders treat it as being. It requires naming one person who decides, listing who must be consulted first, and stating when the window closes. Committees do not decide anything, because individuals decide after consulting committees.
Leaders avoid the naming step for understandable reasons. Assigning a decision creates a visible loser, and consensus language postpones that discomfort indefinitely. The postponement does not remove the conflict from the company. It relocates the conflict into every future meeting on the subject.
Much of what passes for the everyday practice of directing work through other people is decision assignment performed well. A manager who states the boundary, the deadline, and the escalation path has removed most of the ambiguity that generates friction. The skill looks like communication because it gets delivered in words.
The same pattern holds one level up the organization. Setting direction so that other people can act without checking back is mostly a matter of specifying which choices belong to whom. Vague direction is not a stylistic failure of the leader. It is an unmade decision, transmitted downward at speed.
Reversibility should shape how much process a decision earns. Choices that can be undone cheaply deserve a fast decider and very little consultation. Choices that lock in cost or reputation deserve a slower path with defined input. Applying identical ceremony to both is why some companies manage to feel slow and careless at once.
Consultation rights deserve as much precision as decision rights. Being consulted means the decider must hear the input before choosing, and nothing more than that. People who expected a vote and received a hearing will describe the outcome as poor communication.
Recurring Meetings Are Unassigned Decisions in Disguise
The clearest evidence of an unassigned decision is a meeting that recurs with the same agenda. The discussion is genuinely thoughtful every single time it happens. Nothing closes, because nobody in the room holds the authority to close it, and nobody has said so plainly.
Recurring meetings absorb a startling amount of senior attention across a quarter. The cost stays invisible because it arrives distributed in small pieces. Each session feels productive in isolation, and only the pattern across months reveals the waste.
Practical guidance on structuring a session so that it ends in commitments rather than discussion keeps arriving at the same requirement. Every agenda item needs a stated outcome and a named person who owns it afterward. Items that fail that test belong in writing rather than on a calendar.
The pattern repeats in written channels as much as on calendars. A message thread that runs for days without resolution is the same failure in a different medium. Length of discussion works as a reasonable proxy for missing authority, and it is easy to observe.
Closing a decision requires an explicit act rather than the passage of time. Somebody has to state the choice, name what was rejected, and say the question is now settled. Absent that sentence, participants leave believing the discussion merely paused for now. The reopening tends to arrive within a week or two.
Written norms carry the remainder of the load. Established conventions for how a company records what was decided and circulates it determine whether a closed question stays closed. A decision made verbally and never written will be reopened by the first person who was absent. Recording the decision, the owner, and the date is the cheapest defense available.
Clarity Is Structural Before It Is Stylistic
Communication training tends to concentrate on delivery. Tone, structure, brevity, and listening are all real skills worth developing seriously. They improve the transmission of a message and do nothing about its content when that content remains undecided.
This explains why strong writers inside a confused organization produce beautifully phrased ambiguity. The document reads well and commits to nothing, because committing would require authority the writer does not hold. Readers sense the evasion and respond by quietly ignoring the document.
Effective exchange that reliably leaves everyone with the same view of what happens next depends on somebody having decided what happens next. Format helps enormously once that condition is satisfied. Format cannot manufacture a decision that no one has made.
At the executive level the same pattern intensifies considerably. Speaking at the level where a few sentences reshape priorities across an entire company exposes unresolved ownership immediately. An executive who speaks in options rather than choices leaves every function to interpret. Interpretation across functions produces divergence, which then gets reported upward as a communication problem.
Audience assumptions cause a second and quieter failure. Writers describe what they decided without describing what the reader must now do differently. A decision communicated without a list of implications gets filed as news rather than instruction. Naming the required change is what converts information into action.
Silence carries meaning that writers rarely intend to send. When a decision goes unannounced, the people affected assume it went the way that favors the loudest party. Announcing a decision that disappoints somebody still beats leaving the field open to inference.
Smaller Companies Carry a Specific Version of This
Smaller companies experience the problem differently than large ones do. Decision rights are rarely written anywhere, because everyone assumes the founder decides everything worth deciding. That assumption holds until the company outgrows the attention one person can supply.
The transition is uncomfortable and therefore usually deferred. Growth adds decisions faster than it adds people authorized to make them. A queue forms at the top and the organization slows, while nobody can point at the specific failure causing it.
Advice on keeping information moving in a company where roles overlap and little is formalized often treats informality as a competitive advantage. The advantage is real and it has an expiry date. Informal coordination works while everyone can hear each other, and it fails quietly the moment they cannot.
Founders often resist distributing decisions on quality grounds. The concern is legitimate, because early decisions carry outsized consequences and judgment takes years to develop. Withholding every decision guarantees that judgment never develops anywhere else in the company. Distributing the reversible ones first builds capability without risking much of value.
Titles complicate the picture inside a smaller company. Roles overlap, one person may cover two functions, and authority follows tenure rather than job description. Writing decisions against roles that do not really exist produces a document nobody recognizes. Assigning against actual people, then revising as roles firm up, works considerably better.
The remedy does not require a large governance apparatus. Write down the several decisions that recur most often and name a decider for each one. Revisit that short list whenever the company changes shape, which happens far more often than most owners expect.
Communication problems are comfortable to discuss because nobody stands accused of anything. Decision rights problems require somebody to surrender an option they currently keep open. That trade is the entire difficulty, and it is also the entire solution. Teams described as unable to communicate are usually communicating perfectly well about a question nobody has been authorized to answer.
Frequently Asked Questions
How can you tell a communication problem from a decision rights problem?
Ask several people in the affected area who makes the final call on the contested question. Matching answers point toward a genuine information flow issue that better cadence can fix. Divergent answers point toward missing authority, which no amount of messaging will resolve. The test takes minutes and prevents months of misdirected effort.
Who should own a decision that spans two departments?
Ownership belongs to whoever carries the consequence of the outcome most directly. Splitting the decision between both leaders reproduces the deadlock in a more formal setting. The other department receives consultation rights, which means the decider must hear the input before choosing. Naming that arrangement openly matters more than which leader gets selected.
Do better tools reduce cross functional friction on their own?
Tools improve visibility into work that has already been assigned to somebody. They do not assign anything, and they can worsen the situation by generating more visible unresolved threads. Companies adopting a new platform to fix coordination usually rediscover the same disagreements in a new interface. The assignment has to happen in a conversation among people.
What is the fastest way to reduce recurring meetings?
Review every standing meeting and identify the decision each one exists to make. Any meeting without an identifiable decision becomes a written update instead. Any meeting with a decision gets a named decider and a closing date. Most calendars shrink noticeably after that single exercise.
Should decision rights be written down in a formal document?
Written rights survive turnover, absence, and disagreement in a way that verbal understandings do not. The document can be short, listing only the recurring decisions and the person accountable for each. Attempting to map every possible decision produces a document nobody maintains. Covering the contested ones captures nearly all of the benefit.
How does this change as a company grows?
Growth multiplies decisions faster than it multiplies people with authority to make them. What worked as informal founder judgment becomes a bottleneck without any single visible cause. The response is to distribute specific decisions rather than to add coordination meetings. Each round of growth deserves a fresh look at which decisions belong where.
No comments:
Post a Comment