Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 19, Issue 5;   January 30, 2019: Conway's Law and Technical Debt

Conway's Law and Technical Debt

by

Conway's Law is an observation that the structures of systems we design tend to replicate our communication patterns. This tendency might also contribute to their tendency to accumulate what we now call technical debt.
Bottom: Aerial view of the Forth Bridge, Edinburgh, Scotland. Top: Inside the Forth Rail Bridge, from a ScotRail 158 on August 22, 1999.

Bottom: Aerial view of the Forth Bridge, Edinburgh, Scotland. Top: Inside the Forth Rail Bridge, from a ScotRail 158 on August 22, 1999. A very early steel structure, the Forth Bridge was constructed from 1882 to 1890 using the methods of the day. As described by Erlend Clouston, "Around 4.8m sq ft of metal was sliced by the bridge's engineers into strips of varying slenderness, clamped together by about 7m of the tomato-sized rivets." [Clouston 2009]

To protect it against corrosion, a problem that afflicts all steel bridges, it must be covered with paint. But because the bridge is constructed of so many small parts, scraping and repainting it is a gargantuan task. Indeed, the Forth bridge had become famous for the fact that repainting it has been continuous. By the time the painters complete the job, it has been time to start again. This latest repainting, though, has been done with epoxy, which is expected to last for 25 to 40 years. So we need a new metaphor for never-ending jobs.

Technical debt might meet that daunting challenge. Controlling technical debt in large systems is a never-ending job, possibly because of Conway's Law and the ceaseless change that afflicts organizations.

Aerial view Copyright &copy, Andrew Shiva. Inside view (cc) Lexcie.

In a 1968 article in Datamation, computer scientist Melvin Conway describes a connection between system designs and the social communication patterns of the organizations that create those system designs. [Conway 1968] He says, "…organizations which design systems…are constrained to produce designs which are copies of the communication structures of these organizations." He also observes:

This kind of a structure-preserving relationship between two sets of things is called a homomorphism. Speaking as a mathematician might, we would say that there is a homomorphism from the linear graph of a system to the linear graph of its design organization.

Specifically, for each pair of system elements A and B that interact, there is a pair of groups of people, A' and B', respectively responsible for system elements A and B, which also interact.

According to Conway [Conway 2019], and conferred on Conway's insight the name "Conway's Law." It was widely consistent with the state of engineering in the late 20th century, and remains so today, more or less, under the name mirroring. [Querbes & Frenken 2018]

The paradox of Conway's Law and technical debt

Systems large and small, but especially the large ones, tend to accumulate technical debt [Cunningham 1992], which is a collection of unwelcome technical elements that contribute to lower engineering productivity or to a higher probability of defects during development, maintenance, or enhancement efforts, and which we would therefore like to revise, repair, replace, rewrite, create, or re-engineer for sound engineering reasons. [Brenner 2017.1] And technical debt accumulates in systems even though the organizations that design and maintain those systems have communication structures that are clearly defined. That would seem to contradict Conway's Law. If communication is so well structured, then why do the systems these organizations work on become so chaotic over time?

Resolving the paradox

The chaos that evolves in systems over time might be, in part, a result of Conway's Law. Technical debt has many causes, but surely one of them is the apparently endless stream of reorganizations, early retirements, promotions, terminations, offshoring, onshoring, outsourcing, insourcing, layoffs, mergers, spinoffs, and acquisitions that repeatedly disrupt the communication structures and social relationship networks of the engineers employed in large enterprises.

Following each disruption is a period of adaptation in which these communication structures become orderly again. But when they do, they rarely match the structure of the systems those organizations are charged with maintaining and enhancing. Conway's homomorphism is therefore disrupted. The social communication patterns of an organization that formerly matched the structures of the systems it works on might match them no longer. That mismatch makes for difficulties in sustaining coherence of the design of those systems.

Over time, as a natural consequence of Conway's Law, the system evolves toward creating a new homomorphism — that is, toward matching the new social communication structure. Sometimes it catches up. But then the cycle repeats. Unless the system design is thoroughly updated to restore the homomorphism between the system and the social communication structure, traces of the old remain, and those traces can accumulate to form what appears to be a degraded, chaotic system structure: technical debt.

Generalizing Conway's Law

Conway's Law The chaos that evolves in
systems over time might
be, in part, a result of
Conway's Law
may be only a special case of a more general principle. Conway's Law asserts that there is a homomorphism between the modular structure of a system and the communication structure of the organization that designed the system. But the correspondence might be more than merely geometrical. For example, organizations whose cultures value elegance, or consistency, or quality are more likely to produce systems that exhibit those same attributes. And similarly, if the culture doesn't value elegance, or consistency, or quality, we can expect that culture to create systems that lack those attributes.

And when the organizational culture changes, the systems "try" to match it. If they can't quite keep up, the result is technical debt.

Last words

It's reasonable to suppose that further investigation into the interplay between Conway's Law — or a more general form of it — and the technical debt concept may yield further insights. In the meantime, managers would do well to consider carefully how to preserve Conway's homomorphism when making changes to organizational structures. Go to top Top  Next issue: Grace Under Fire: III  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!

Footnotes

Comprehensive list of all citations from all editions of Point Lookout
[Clouston 2009]
Erlend Clouston. "A working life: The Forth bridge painter," The Guardian, July 24, 2009. Available here. Back
[Conway 1968]
Melvin E. Conway. "How do Committees Invent?", Datamation 14:5 (1968), 28-31. Available here. Retrieved 11 January 2019. Back
[Conway 2019]
Melvin E. Conway. See MelConway.com. Fred Brooks cited Conway's article in his classic, The Mythical Man-Month. Back
[Querbes & Frenken 2018]
Adrien Querbes and Koen Frenken. "Grounding the 'mirroring hypothesis': Towards a general theory of organization design in New Product Development," Journal of Engineering and Technology Management 47 (2018), 81-95. Back
[Cunningham 1992]
Ward Cunningham. "The WyCash Portfolio Management System." Addendum to the Proceedings of OOPSLA 1992. ACM, 1992. Back
[Brenner 2017.1]
Richard Brenner. "A policymaker's definition of technical debt," TechDebtPolicy Blog, November 10, 2017. Back

Your comments are welcome

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

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

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 Workplace Politics:

Former U.S. Secretary of State Colin PowellDevious Political Tactics: A Field Manual
Some practitioners of workplace politics use an assortment of devious tactics to accomplish their ends. Since most of us operate in a fairly straightforward manner, the devious among us gain unfair advantage. Here are some of their techniques, and some suggestions for effective responses.
Jeffrey Skilling, in a mug shot taken in 2004 by the United States Marshals ServiceKinds of Organizational Authority: the Informal
Understanding Power, Authority, and Influence depends on familiarity with the kinds of authority found in organizations. Here's Part II of a little catalog of authority, emphasizing informal authority.
President George W. Bush of the United States and Crown Prince Abdullah of Saudi ArabiaSocial Transactions: We're Doing It My Way
We have choices about how we conduct social transactions — greetings, partings, opening doors, and so on. Some transactions require that we collaborate with others. In social transactions, how do we decide whose preferences rule?
The city walls of Dubrovnik, CroatiaProblem Displacement by Intention
When solving problems creates new problems, or creates problems elsewhere, we say that problem displacement has occurred. Sometimes it's intentional.
U.S. President Franklin D. Roosevelt signs the Social Security Act, 13 August 1935Bad Trouble: Coping strategies
When Bad Trouble develops at work people make choices about coping. If they cope constructively, they have choices about how to do that. Even those who don't cope constructively have choices. Here's a survey of the wide range of choices people make.

See also Workplace Politics and Workplace Politics for more related articles.

Forthcoming issues of Point Lookout

A diagram of the cross section of a boat with a single water ballast tank at the bottomComing January 22: Storming: Obstacle or Pathway?
The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.
The Eisenhower Matrix of Urgency by ImportanceAnd on January 29: A Framework for Safe Storming
The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post 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.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.