Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 24, Issue 41;   December 18, 2024: Subgrouping and Conway's Law

Subgrouping and Conway's Law

by

When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks.
Tuckman's stages of group development

Tuckman's stages of small group development. Time spent in stages other than Performing is likely to defer accomplishing the group's task. That's why any factors that draw group members' attention away from the task or group development can be very costly indeed. This is the 1977 version of the development sequence, in which Tuckman and Jensen appended the Adjourning stage to the original four stages Tuckman hypothesized. Although this diagram seems to imply an endless loop of orderly passage through the five stages, and although that can happen, there are many possible paths through the stages of development. Image (cc) Attribution-ShareAlike 4.0 International license by DovileMi, courtesy Wikimedia.

Especially in larger task-oriented work groups working on the more complex tasks, subgrouping is the practice of forming a subgroup of the larger group in order to complete a subtask of the larger task. In task-oriented work groups, subgrouping is often driven by a combination of task demands and access to personnel. Some examples of factors influencing subgroup formation:

  • The subtask might require special knowledge that only a few people have
  • Completing the subtask might require special equipment or software that's available in only limited numbers
  • The subgroup might be a unit of an independent enterprise acting as a contractor or subcontractor to the organization hosting the larger group
  • The organization might designate the subgroup's members so as to avoid impractical combinations of time zones
  • The roster of the subgroup might be designed to ensure that the people who worked on an earlier version of the subtask would be well represented
  • A more dysfunctional example (of the many): Person A might be essential for completing the subtask, but Person A might be so difficult to work with that only a few members of the larger group can work with Person A in harmony

Communications technology reduces location constraints on subgroups

If the task demands that subgroup members work closely together and communicate often, then even as recently as 1990 or 2000, we would almost always assign people to the subgroup so that everyone was at the same site, or working in the same city or building. In terms of priority for assignment to subtask, someone's location might have rivaled their skill set.

Today's communications technologies can greatly diminish the impact of the location constraint. Access to videoconference technology is now so widespread that geography provides a much-reduced constraint on subgrouping. The demands of the task and personnel availability are now much more dominant than they once were.

Conway's Law

Conway's Law (the Law) Access to videoconference technology
is now so widespread that geography
now provides only a much-reduced
constraint on subgrouping
isn't actually a law in the legal sense. It's a pattern first described in 1968 by computer scientist Melvin Conway, and named "Conway's Law" by Fred Brooks in The Mythical Man-Month. [Conway 1968] [Brooks 1982] The Law says, "…organizations which design systems…are constrained to produce designs which are copies of the communication structures of these organizations." Conway 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.

As Conway puts it even more concisely, "Systems image their design groups." Specifically, for each pair of interacting system elements A and B, there is an interacting pair of groups of system designers, A' and B', respectively responsible for system elements A and B.

Conway's Law has implications that reach beyond system design. For example, it's likely a cause of the formation or persistence of technical debt in cases where reorganizations or organizational acquisitions have broken the homomorphism between the social architecture of the organization and the technical architectures of the systems that organization maintains. [Brenner 2019.4] [Brenner 2019.5]

The role of Conway's Law in subgrouping

Subgrouping might also provide an example of Conway's Law. But in a fascinating twist, in subgrouping, the Law can have influence in a direction opposite to the sense of the law as expressed by Conway. One can understand how the Law constrains an organization to produce system designs that, in Conway's words, "image their design groups." But suppose a task-oriented work group is performing maintenance on an existing system. When that work group forms subgroups, the demands of the task constrain how the subgroups form. In this way, the subgroups image the system.

If this is so, then when the task requires a period of intensive work on Subtask A, the work group would tend to form a subgroup (Subgroup A) to attend to Subtask A. Subgroup A might then develop along the lines of Tuckman/Jensen's Developmental Sequence for small groups, finally Adjourning when Subtask A is complete. [Tuckman & Jensen 1977]

Communications technology weakens the geographical constraint

Formerly, the geolocation of group members constrained communication patterns. That is, people who needed to work closely together had to be located conveniently to each other. Now, though, as noted above, geography plays a more limited role in determining communication convenience.

Consequently, when subgroups form, geography likewise plays a more limited role than it did even 20 years ago. By employing modern communications technologies, we gain freedom to define subgroups that more closely produce a homomorphism between the work underway and the subgroup structure.

Last words

Meanwhile, while Subgroup A does its work, other subgroups might "form, develop, and adjourn in parallel with Subgroup A, though not necessarily in synchrony. In very large groups, a subgroup "foam" might develop, with each subgroup progressing through its own Tuckman/Jensen stages at its own rate. Potentially, at any given time, one subgroup or another might always be Storming. To an outside observer, the larger group might appear to be constantly Storming, and so chaotic as to provide a counterexample to Tuckman's model of group development, when actually Tuckman's model is being confirmed many times over, subgroup-by-subgroup. Go to top Top  Next issue: The Storming Puzzle: I  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
[Conway 1968]
Melvin E. Conway. "How do Committees Invent?", Datamation 14:5 (1968), pp. 28-31. Available here. Retrieved 11 January 2019. Back
[Brooks 1982]
Frederick P. Brooks, Jr. The Mythical Man-Month. Reading, Massachusetts: Addison-Wesley, 1982. Order from Amazon.com. Back
[Brenner 2019.4]
Richard Brenner. "Conway's Law and Technical Debt," Point Lookout blog, January 30, 2019. Available here. Back
[Brenner 2019.5]
Richard Brenner, "Balancing resources and load: Eleven nontechnical phenomena that contribute to formation or persistence of technical debt," 2019 IEEE/ACM International Conference on Technical Debt (TechDebt). IEEE, 2019. Back
[Tuckman & Jensen 1977]
Bruce W. Tuckman and Mary Ann C. Jensen. "Stages of small-group development revisited," Group and organization studies 2:4 (1977), pp. 419-427. Available here. Retrieved 22 November 2022. Back

Your comments are welcome

Would you like to see your comments posted here? rbrentSgXnAlNVWlhxNIJner@ChacAtZoEYrrmofzZnjPoCanyon.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 Project Management:

Finger PuzzlesFinger Puzzles and "Common Sense"
Working on complex projects, we often face a choice between "just do it" and "wait, let's think this through first." Choosing to just do it can seem to be the shortest path to the goal, but it rarely is. It's an example of a Finger Puzzle.
"Taking an observation at the pole."Risk Management Risk: II
Risk Management Risk is the risk that a particular risk management plan is deficient. Here are some guidelines for reducing risk management risk arising from risk interactions and change.
Edward Bernays, nephew of Sigmund Freud and an early pioneer in the field of Public RelationsCommunication Traps for Virtual Teams: I
Virtual teams encounter difficulties that rarely confront face-to-face teams. What special challenges do they face, and what can we do about them?
President Harry S. Truman, and Gen. Douglas MacArthur, meeting at Wake Island, 14 October 1950Ground Level Sources of Scope Creep
We usually think of scope creep as having been induced by managerial decisions. And most often, it probably is. But most project team members — and others as well — can contribute to the problem.
A switch in the tracks of a city tramwayThe Reactive Rescheduling Cycle
When the current schedule is no longer viable, we reschedule. But rescheduling is unlike devising a schedule before work has begun. People know that we're "behind" and taking time to reschedule only makes things worse. Political pressure doesn't help.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

A man in despair, as one might be following a layoffComing April 2: Mitigating the Trauma of Being Laid Off
Trauma is an emotional response to horrible events — accidents, crimes, disasters, physical abuse, emotional abuse, gross injustices — and layoffs. Layoff trauma is real. Employers know how to execute layoffs with compassion, but some act out of cruelty. Know how to defend yourself. Available here and by RSS on April 2.
A common image of bullying in actionAnd on April 9: Defining Workplace Bullying
When we set out to control the incidence of workplace bullying, problem number one is defining bullying behavior. We know much more about bullying in children than we do about adult bullying, and more about adult bullying than we know about workplace bullying. Available here and by RSS on April 9.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrentSgXnAlNVWlhxNIJner@ChacAtZoEYrrmofzZnjPoCanyon.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.