![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.](../images/edinburgh-forth-bridge-composite.png)
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 © 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 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 Lawmay 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. Top
Next Issue
Are 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
Your comments are welcome
Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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.
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:
Managing Pressure: Milestones and Deliveries
- Pressed repeatedly for "status" reports, you might guess that they don't want status —
they want progress. Things can get so nutty that responding to the status requests gets in the way of
doing the job. How does this happen and what can you do about it? Here's Part III of a set of tactics
and strategies for dealing with pressure.
Things We Believe That Maybe Aren't So True
- Maxims and rules make life simpler by eliminating decisions. And they have a price: they sometimes foreclose
options that would have worked better than anything else. Here are some things we believe in maybe a
little too much.
Not Really Part of the Team: II
- When some team members hang back, declining to show initiative, we tend to overlook the possibility
that their behavior is a response to something happening within or around the team. Too often we hold
responsible the person who's hanging back. What other explanations are possible?
Narcissistic Behavior at Work: I
- Briefly, when people exhibit narcissistic behavior they're engaging in activity that systematically
places their own interests and welfare ahead of the interests and welfare of anyone or anything else.
It's behavior that threatens the welfare of the organization and everyone employed there.
Implicit Interrogation Tactics
- When one person tries surreptitiously to extract information from another at work, an implicit interrogation
is taking place. Here are seven tactics that people use to interrogate others without revealing what
they're doing.
See also Workplace Politics and Problem Solving and Creativity for more related articles.
Forthcoming issues of Point Lookout
Coming July 3: Additive bias…or Not: II
- Additive bias is a cognitive bias that many believe contributes to bloat of commercial products. When we change products to make them more capable, additive bias might not play a role, because economic considerations sometimes favor additive approaches. Available here and by RSS on July 3.
And on July 10: On Delegating Accountability: I
- As the saying goes, "You can't delegate your own accountability." Despite wide knowledge of this aphorism, people try it from time to time, especially when overcome by the temptation of a high-risk decision. What can you delegate, and how can you do it? Available here and by RSS on July 10.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
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](../images/social-icons/email-32.png)
![Follow me at LinkedIn](../images/social-icons/linkedin-reg-32.png)
![Follow me at X, or share a post](../images/social-icons/x-32.png)
![Subscribe to RSS feeds](../images/social-icons/feed-icon-32.png)
![Subscribe to RSS feeds](../images/social-icons/facebook-icon-32.png)
Recommend this issue to a friend
Send an email message to a friend
rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
![Technical Debt for Policymakers Blog](../images/logos/techdebtpolicy-logo-sm-1.png)