Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 12, Issue 17;   April 25, 2012: Communication Refactoring in Organizations

Communication Refactoring in Organizations

by

Last updated: August 8, 2018

Inadequate communication between units of large organizations is one factor that maintains the dysfunction of "silo" structures in large organizations, limiting their ability to act coherently. Communication refactoring can help large organizations to see themselves as wholes.
Then-Capt. Elwood R. Quesada who became commanding general of the 9th Fighter Command in operation Overlord

Then-Capt. Elwood R. Quesada, assigned to intelligence in the Office of the Chief of Air Corps in October 1940. He became commanding general of the 9th Fighter Command, where he established advanced Headquarters on the Normandy beachhead on D-Day plus one, and directed his planes in aerial cover and air support for the Allied invasion of the continent. As LTC Michael Chandler argues in his Air University thesis (2007), Gen. Quesada identified weaknesses in German air doctrine that limited their ability to prevail in the war. Specifically, German doctrine viewed air power as a tool of ground units. In effect, the German air elements were divided into silos controlled by ground unit commanders. They were therefore limited in their ability to act as a coherent force. This placed certain kinds of missions outside their ability to accomplish — specifically, missions on the scale of the theater, such as air dominance.

Something similar happens in the enterprise when its elements — here called "silos" — are unable to act in a coordinated fashion. Communication refactoring removes one obstacle to coherent action.

For more, see Chandler, Michael J., Lieutenant Colonel, USAF. "Gen Otto P. Weyland USAF: Close Air Support in the Korean War." A thesis presented to the School of Advanced Air and Space Studies, U.S. Air University, 2007. Photo courtesy U.S. Air Force.

When we discover misunderstandings, and work them out, we tend to focus on the misunderstanding at hand. Afterwards — not often enough — we ask ourselves, "Is it possible that there are some similar misunderstandings elsewhere?" If we look upon misunderstandings as potential indicators of broader difficulties, we often find opportunities to search around for other examples of that same difficulty.

For example, suppose you discover that one of the Advance Marketing (AM) teams began meeting weekly to make plans for a new product introduction. And suppose you find that they've been meeting without a representative from Customer Support (CS). This isn't good, because AM does need input from CS, and CS needs to be fully aware of what AM is planning. After investigating, you manage to correct this communication defect.

But you don't stop there. It occurs to you that other AM product introduction planning teams might be doing the same thing — that is, excluding CS. Not by intention, perhaps, but it doesn't matter why. Upon investigation you discover two AM teams that are including CS and one that isn't. So you fix the one that isn't, too. Finally, you address the problem generally between AM and CS, and that kind of omission won't be happening again. Success.

But what about the relationship between CS and the Product Development teams? Are they keeping each other as informed as they need to? Since you don't know, you investigate that, too, and you fix what you find there. More success. You keep doing this until all the connections with CS are working right.

Then you take it further. You look at all the silos, top to bottom, to determine whether all the people that need to connect with each other are actually connecting. It becomes an enterprise-wide initiative.

I call Communication refactoring is a
disciplined process of improving
communication between the
parts of an organization
this process communication refactoring. It's a method for generalizing one situational repair of organizational communications to all possible instances where it might be beneficial, throughout the organization. In this way, by improving organizational communication gradually, we help to transform the organization from a series of weakly interacting silos into a coherent whole. I say "help" because there's a lot more to do to achieve coherence, but communication refactoring is a good start.

The term refactoring is borrowed from Software Engineering, where it refers to a disciplined practice of gradually transforming a program's code, usually by a series of seemingly tiny changes, that, over time, make the code more readable, maintainable, and extensible without directly affecting its intended functionality. By analogy, communication refactoring is a disciplined process of improving communication between the parts of an organization.

You might ask, "Where else can we apply the refactoring approach to improve the effectiveness of the day-to-day interactions of organizational life?" My guess: everywhere. You can start today. Go to top Top  Next issue: On Noticing  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrenlQQKrsKkwGvTJrqgner@ChacuwofWzVdibuUpEOdoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

A cheeseburger with friesMy Boss Is Driving Me Nuts
When things go badly, many of us experience stress, and we might indulge various appetites in harmful ways. Some of us say things like "My boss is driving me nuts," or "She made me so angry." These explanations are rarely legitimate.
Benjamin FranklinProblem-Solving Ambassadors
In dispersed teams, we often hold meetings to which we send delegations to work out issues of mutual interest. These working sessions are a mix of problem solving and negotiation. People who are masters of both are problem-solving ambassadors, and they're especially valuable to dispersed or global teams.
The Marx brothers: Chico, Harpo, Groucho and ZeppoTINOs: Teams in Name Only
Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.
World global temperature departuresConfirmation Bias: Workplace Consequences Part I
We continue our exploration of confirmation bias, paying special attention to the consequences it causes in the workplace. In this part, we explore its effects on our thinking.
FlamesHow to Get Out of Firefighting Mode: II
We know we're in firefighting mode when a new urgent problem disrupts our work on another urgent problem, and the new problem makes it impossible to use the solution we thought we had for some third problem we were also working on. Here's Part II of a set of suggestions for getting out of firefighting mode.

See also Personal, Team, and Organizational Effectiveness and Effective Communication at Work for more related articles.

Forthcoming issues of Point Lookout

A pair discussion in a speedstormComing February 27: Brainstorming and Speedstorming: II
Recent research into the effectiveness of brainstorming has raised some questions. Motivated to examine alternatives, I ran into speedstorming. Here's Part II of an exploration of the properties of speedstorming. Available here and by RSS on February 27.
A meeting that's probably a bit too largeAnd on March 6: A Pain Scale for Meetings
Most meetings could be shorter, less frequent, and more productive than they are. Part of the problem is that we don't realize how much we do to get in our own way. If we track the incidents of dysfunctional activity, we can use the data to spot trends and take corrective action. Available here and by RSS on March 6.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenrybaGOHNXkfDaYvoner@ChackRDlQzwnyFPAHFVMoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.