• About PeterSIronwood

petersironwood

~ Finding, formulating and solving life's frustrations.

petersironwood

Tag Archives: technology

Pattern Language Overview

02 Monday Nov 2026

Posted by petersironwood in management, psychology, Uncategorized

≈ Leave a comment

Tags

Business, collaboration, collaboratoin, competition, cooperation, creativity, Democracy, innovation, pattern language, pattern-languages, Patterns, peace, psychology, science, society, teamwork, technology, thinking, united-nations, writing

Pattern Language Overview 

Prolog/Acknowledgement: 

An old story recounts a person walking down a path and noticing two workers laying stones and cementing them into place. The walker noticed that one of the workers walked with a bounce in their step and a whistle on their lips. The other worker, however, trudged from stone pile to wall with a scowl. The walker imagined that perhaps the disgruntled worker was being paid less or was ill or had suffered a recent tragedy. Because the walker was familiar with the “Iroquois Rule of Six” however, they knew that it would be better to test their hypotheses than make assumptions about the reasons. He asked the disgruntled worker what they were doing. “Isn’t it obvious? I have to take these stones from the pile over there and lay them in that wall over there and cement them in place.” When asked the same question, the worker with the sunny disposition answered, “Isn’t it obvious? I’m building a cathedral!”

IMG_6052

Many years ago, I read in IBM’s company magazine, Think, about a training program that IBM had provided in Kingston for people working in their chip fabrication plant. Management had decided to give an overview of the entire process to the assembly line workers. According to the story, one older worker jumped up in class and yelled, “Oh, NO! I’ve been doing it wrong! All these years!” Upon questioning, it turned out that the worker’s career had been in inspecting masks. Each mask was, in turn, used to make hundreds of thousands of chips. Since so much effort went into the making of a mask, the worker had always thought it would be counter-productive to toss out masks that only had one or two flaws in them.

Astronauts who see the earth from space see things in a new and different perspective. In some cases, it causes them to better see the inter-relatedness of all nations and the desperate necessity of working together to ensure the ecological viability of the earth.

earthfromspace

These stories illustrate that an overview, map, or vision can serve two important purposes in collaboration and coordination. First, it can serve as a motivation. Who wouldn’t rather be building a cathedral rather than merely moving stones? Second, an overview can inform people about how their work interacts with the work of others and thereby allow them to make choices that positively impact the project, product, or campaign as a whole.

I’m talking a pause from posting specific Patterns to provide a preview/overview of the proposed Pattern Language on “best practices” for teamwork, collaboration, coordination, and cooperation. There are many things that have caused me to believe we need such a Pattern Language. Among them, the most important reason for me is the recent up-tick in uncivil communication and in turning nearly every single human activity into a “competition.” I’ve also seen a continued misuse of the biological metaphor that evolution proceeds by fierce competition. Of course, competition is important in evolution. So is cooperation. So, I argue, is individual choice (See blog post: “Ripples”.)

This Pattern Language is still a “Work in Progress” so I cannot yet give a highly coherent and motivating overview, but I hope this list will at least give some better notion of where this project might be heading. I briefly summarize recently re-published Patterns and preview some upcoming Patterns by presenting only their essence. Providing this overview is itself attempting to make use of a Pattern – “Provide a Motivating Map.” As you read through a larger number quickly, I am hoping that you will begin to see that these Patterns are not a set of independent disconnected parts but more like an inter-connected web of ideas. There are, I believe, a number of different ways to organize this web for particular purposes. More on that later, but so far, I have thought of at least two ways to categorize the Patterns.

First, the Patterns could be categorized into four basic classes of human needs; 1) to acquire new things or experiences, 2) to defend, 3) to bond, 4) to learn. Often a large scale human activity may have 2, 3 or even all 4 of these as goals. But, at least in terms of the focus of current activity, one of these predominates. I would argue that when having a Synectics session (a kind of structured brainstorming), the primary goal is to acquire new ideas or solutions. It may result in a product that “defends” a company’s position in the marketplace; it may well increase social bonding in the group; and participants will almost certainly learn something. But, the most relevant Patterns to the situation at hand are those whose primary purpose is to better acquire things. The primary purpose of Meaningful Initiation, however is social bonding.

A second way of categorizing the Pattern is in terms of the current stage of development of a product, service, or work one is currently in. If you are engaged in problem finding, or problem formulation, Bohm Dialogue is particularly well-suited to the current task at hand. After Action Review, however, is better suited to looking back at or near the end of a project, development, construction, or campaign. There are no hard and fast boundaries implied. These are heuristics meant to help deal with the complexity of an entire Pattern Language. One could use a slightly altered After Action Review as a jumping off place for new product idea generation. Instead of asking, “What could we do better next time to avoid making error X?” you could ask instead, “How could a mobile phone app be used to help make sure people would avoid making error X?”

A third thing to note about Patterns, is that they form an inter-connected lattice. They are not a strict hierarchy, but some Patterns are higher level than others. A higher level Pattern may have lower level Patterns as components or as alternatives. Two high level Patterns are: Special Processes for Special Purposes and Special Roles for Special Functions. Some alternatives for special purposes are Synectics for generating alternatives and stimulating divergent thinking, the K-J Method of Clustering, and Voting Schemes for prioritizing ideas to pursue. Some examples of various alternative roles include Moderator, Facilitator, and Authority Figure.

Author, reviewer and revision dates: 

Created by John C. Thomas on First of March, 2018; Revised by John C. Thomas 2 November, 2026.

Already Published in January – February.  

Who Speaks for Wolf? 

Make sure to hear from all relevant stakeholders and areas of expertise (or their able proxies).

Reality Check. 

For convenience, we often use an ersatz measure that’s somewhat correlated with what we are really interested in because it’s easier. In such cases, you must check to insure the correlation is still valid.

Small Successes Early. 

We like to jump right into large, complex tasks. When this is done with a large group of people meant to work smoothly on a large project, it is counter-productive. Instead, begin with a task that is fairly easy, fun and/or relevant and fairly assured of success.

Radical Collocation. 

When problems are complex and the sub-parts heavily interact in unpredictable ways, it is worth having the entire group work in very close proximity.

Meaningful Initiation. 

When done properly and meaningfully in the right context and controlled by appropriate Authority Figures, initiations may increase group cohesiveness.

The Iroquois Rule of Six. 

Human behavior is very tricky to interpret. When you observe behavior, and generate a reason for that behavior, before acting, generate at least five more plausible reasons.

Greater Gathering. 

Periodically and/or on special occasions, everyone should have a chance to get together with all of their work colleagues(and in some contexts, their families) and have some fun.

Context-Setting Entrance. 

It really helps social interaction if people know what is expected of them. The entrance, metaphorical or physical, can serve a vital role in setting the mood, tone, and formality of the upcoming social interaction.

Bohm Dialogue. 

Let someone speak. Listen to what they say without rehearsing your own answer. Reflect on what they say. Share your reflection. A Dialogue seeks to create some shared truth without setting into “sides” or “camps” or judging each statement made on the basis of what it means for me.

Build from Common Ground. 

People all share tremendous common ground even across the entire globe. Yet, we often try to jump into resolving our “differences” without first re-affirming what our common ground is. That’s a mistake. Start with discovering common ground and build from that.

To Be Elaborated On:

Use an Appropriate Pattern of Criticism.

For example: first, ask the person for positives and how they could improve; then, ask their peers for the same; then, the Authority Figure adds their feedback in the same order.

Negotiate from Needs, not Positions. 

Win/win solutions are much more likely if people negotiate from their needs than from positions. Example: Two sisters fight over the single orange. They both say they want it. At last they compromise and split the orange in half. Neither one is completely satisfied nor dissatisfied. Had they been honest about their real needs, they would have discovered that one wanted the peel for a cake flavoring and the other wanted to eat the fruit inside.

https://en.wikipedia.org/wiki/Harvard_Negotiation_Project

Give a Sympathetic Read. 

Natural language is incredibly ambiguous and vague. A reader should take a “sympathetic” stance toward what they read (or hear or feel). Instead of trying to find the “holes” in someone else’s arguments, first try to interpret it so that it does make sense to you.   

After Action Review. 

After a significant event takes place, parties who were involved in the decision making, should all get together with appropriate facilitators to see what can be learned from the situation. This is neither a “witch hunt” nor a “finger-pointing exercise” but an opportunity to see how to improve the organization over time.

Positive Deviance. 

(From book by the same title). The idea is that in any complex situation that you might want to “improve” or “fix” there are some who are in that situation and have already figured out how to succeed. Instead of designing and imposing a solution, you can find out who the success stories are, observe what they are doing, get feedback from the observed and then encourage the success stories to share what they do with the larger community.

https://en.wikipedia.org/wiki/Positive_deviance

Provide a Motivating Map. 

Everyone would rather help build a cathedral than simply lay stones atop each other. It’s more motivating to see that you are building something greater than the sum of its parts.

Provide an Overview Map. 

The purpose of this map is to let people understand how their particular tasks fit into the grand scheme. This proves useful in many situations. Sometimes, the same Map can serve both as an Overview and Motivating Map.

Collaborating Music. 

There is value to be gained in terms of social capital with listening to common music, more in dancing to common music and more still in the creation of common music. Of course, many collaborative activities can create social capital, but music seems to be one of the most “whole-brain” experiences we have and is particularly well-suited to building social capital.

IMG_2185

Making Music Together

Narrative Insight Method. 

People exchange and build on each other’s stories in specified ways to create and organize insights and lessons learned.

Elicit from Cultural Diversity. 

Empirical research shows that more diverse groups can produce more creative and innovative outcomes. Even if such a group cannot work together always, at least use this during divergent thinking, though there is value in diversity for convergent thinking as well. Below is a (badly distorted) map of the world showing the nations from which readers of this blog hailed so far. (Invite your friends from all over the world!)

Map of Readers of Blog

 

 

 

 

 

Upper Screenshot as of March 1, 2018; Lower Screenshot as of Nov. 1, 2026

 

 

CoverageMap

 

 

 

Those Who Interact with Customers Provide Design Input. 

People who work at “help desks,” for example, are under time pressure but there should be mechanisms in place for what they learn about customers, tasks, contexts, pain points, to be fed back to development. In a similar fashion, in any domain, whatever information is garnered from interacting face to face with users, customers, stakeholders, friends, competitors, etc. should be fed back to people who design systems, services, products, or governance.

Queue of Communicating Peers.

In many instances, people in queue, whether physical or electronic, share certain concerns in common. (There is always common ground). Rather than have them “stand in line” staring at the back of someone else’s head, encourage them to help enhance mutual understanding among the group.

Palaver Tree. 

This name comes from some places in sub-Saharan Africa where people from a village gather to respectfully discuss what concerns the whole village. Generally, this is near a big tree that can provide shade during dry seasons. In colder climates, a communal fire can serve as the focal point. There may be other special places that are conducive to this kind of Dialogue.

Click to access jbe-thesis.pdf

Talking Stick. 

Often, when confronting a problem that is pressing, complex, or anxiety-provoking, everyone wants to talk at once. No progress is made because people cannot even hear what is being said in the resulting din and no-one is paying attention to anything but getting their own point heard. A Talking Stick provides a visible cue as to who “has the floor.” Only one person at a time can hold the Talking Stick and only they can talk.

Round Robin Turn Taking.

In a group, it often happens that a small group of people tend to “monopolize” the discussion if it is held in a free-wheeling manner. An alternative is to have an Authority Figure or Moderator or Facilitator make sure that every person gets a chance to speak and that every person, including the shiest are encouraged to give their perspectives.

Mentoring Circle. 

It is often easiest for us to learn from people who have recently faced and solved the same problems that we are now facing. A Mentoring Circle provides a way for people to learn from other individuals and from the group.

iPhoneDownloadJan152013 533

Levels of Authority.

As one becomes more experienced and more trusted by a group, it is normal to grant more authority to that person to act on behalf of the group and to have more access to its resources.

Anonymous Stories for Organizational Learning

Often individuals make errors that can provide a learning experience, not only for them, but for others as well. Unfortunately, the competitive nature of many organizations makes admitting to errors costly for the person who made the mistake. An anonymized story can provide a way for the organization as a whole to learn from individuals without their accruing blame and ridicule.  

iPhoneDownloadJan152013 955

Registered Anonymity.

In Amy Bruckman’s MIT dissertation (Moose Crossing), she provided a space for middle school kids to teach each other object-oriented programming. She wanted to make sure the kids “behaved” appropriately despite their being anonymous and on-line despite the fact that these conditions often spawn inappropriate and even mean-spirited comments. While using real identities could help prevent that, it could also lead to even worse behavior. Instead, she used Registered Anonymity. That is, she knew everyone’s real identity and made it clear that inappropriate behavior would not be tolerated. But the child participants were not allowed to share their real identities.

Answer Garden. 

People are busy and don’t want to answer the same simple question over and over. In Answer Garden, developed by Mark Ackerman for his MIT dissertation, people with expertise claimed a part of the tree of knowledge that they were familiar with and agreed to answer questions about that specific subject area. Once the question was answered however, newcomers were expect to first look through the tree for the answer they needed. If there are no appropriate answer, they would post their question at the nearest node to the requested answer. The expert would come by and answer that question, not only for the person who initially asked it, but the tree would grow with that newly posted answer as well.

fullsizeoutput_1a5a

Community of Communities. 

Complex wide-ranging problems such as ensuring that the world economy is organized to sustain the ecosystem require many people to address various problems. While a very large group of people may be concerned that they leave a livable planet for their descendants, everyone cannot work on every aspect. Better is to have communities work on those aspects for which they have particular interest and expertise. In Sweden, for example, Karl-Henrik Robert (https://en.wikipedia.org/wiki/Karl-Henrik_Robèrt) developed a program called “The Natural Step.” This led to the development of specific communities aiding in the way they best could; e.g., lawyers for a sustainable Sweden might concentrate on legislation and regulation, psychologists for a sustainable Sweden might concentrate on methods to raise public awareness; traffic engineers for a sustainable Sweden might concentrate on making more efficient kinds of roundabouts.

Special Roles for Special Purposes. 

Every culture seems to have developed this notion. There are many specific roles that have been developed for specific purposes. Below are just a few.

Master of Ceremonies. 

This is literally someone in charge of a ceremony, ritual, or rite. It has come to include an entertainer who serves to welcome guests and introduce them. A closely related concept is the “Session Chair” who introduces speakers, makes sure they have what they need, keeps track of time, and moderates audience participation.

Storyteller

In many oral cultures, one person, often chosen because of interest or ability, is chosen to memorize and repeat the oral history. In such cases, the role typically lasts a lifetime, not just a project.

Stake Warrior

The idea of a “stake warrior” is that they literally pound a stake into the ground and then tether themselves to that stake during battle. They can advance, go laterally or retreat, but only so far. Conceptually, a stake warrior shows some flexibility in discussion or negotiation, but there are boundaries beyond which they refuse to go.

DeBono’s Colored Hats. 

Edward DeBono has written a number of books about creativity and innovation. One of his ideas is to use colored hats either physically or conceptually to signal which role a person is speaking in. For example, a person wearing a Black Hat is judging ideas while a Green Hat is more for creativity and provocation. More empirical research is needed to validate whether using hats (even metaphorically) actually improves performance.

Moderator

A Moderator’s main job is to make sure that a group actually follows whatever rules it has set out for itself about time limits, civility, taking turns, etc. A Moderator may also adjudicate disputes between two sides.

Facilitator

A Facilitator’s main job is to keep the group moving forward. They might, for instance, suggest a different way of looking at a topic, or try to invoke a metaphor or to draw out less forthcoming group members.

Setting Expectations. 

Promise a person five dollars and give them ten. They will be very happy. Promise another person twenty and give them ten. The will be unhappy about it. What’s different? They both get ten dollars. Many books on developing projects will recommend “under-promising and over delivering.” In some cases, because of science fiction, TV programs, and the popular press, people may come to think anything is possible.

Support Flow and Breakdown. 

When designing a new system, there is an anticipated way for it to work, whether it’s traffic flow in a city, water flow in the plumbing or information flow in an organization. However, eventually, there will be breakdowns in any of these systems. Breakdowns are always a hassle, but they will be far less so if the possibility of a breakdown has been anticipated ahead of time and then planned for.

Ratchet Social Change with Infrastructure. 

Social changes are initially subject to falling back into previous patterns. In some cases, it may help make a social change more permanent by creating an infrastructure that supports the new system. For instance, if you want to improve relations between two countries, you could fund projects jointly that have a long completion time. Or, if you wanted to divide people, you could make it harder for people to see news and information from people across that divide.

Authority Figure. 

Sometimes, a decision needs to be made quickly. Or, perhaps consensus will never be reached. In such cases, it is sometimes useful to have an agreed upon Authority Figure who can be trusted to make an informed decision that takes into account all the relevant interests. Naturally, Authority Figure who makes decisions from a position of ignorance or self-interest must be removed as quickly as possible.

IMG_5935

Celebrate Local Successes Globally. 

Often a very large-scale collaboration project such as developing a new product or service, governing a country, or trying to manage a cross-cultural non-profit stands to lose coherence and motivation when compared with a small co-located team. One way to help both with organizational learning and with encouraging high spirits is to celebrate local successes with the global team. If done correctly, this can be motivating for both the successful team members and the larger team.

Special Processes for Special Purposes. 

This is another high level Pattern. People have developed numerous special purpose processes. Below I review a few. The reason for having different processes for different purposes is that a process can take into account the number of people, the type of goal, the time constraints, and other conditions so that a process is particularly likely to help insure success. A process can fail if it is badly executed but it can also fail simply because it is not appropriate to the task at hand.

Synectics. 

Originally, the term derived from the work of Prince and Gordon as a way to describe a suite of techniques for creative problem solving. It is similar to brainstorming in that the emphasis is on generating many ideas quickly and without taking time out of idea generation in order to evaluate and debate each idea. Also like brainstorming, people are encouraged to build on each other’s ideas. In addition, they describe various clever ways to incorporate metaphorical thinking into the process. They also allow each person to work on the “Problem As Understood” and this can be slightly different for each person. I have personally found synectics to be extremely useful. It “works” in generating many ideas, some of which can be quite useful and novel. For example, many years ago, I facilitated such a session and the foreign equivalent of the American IRS decided that increasing tax revenue was their goal but that to achieve that, there were other methods than increasing tax rates and increasing compliance.

https://en.wikipedia.org/wiki/Synectics

Speed Dating. 

Although there are actual speed dating venues, here this term refers to a way for a moderate sized group of people to get to know each other quickly by spending two minutes with one other person in the group quickly recounting their backgrounds and interests and then moving on to form new pairs.

OLYMPUS DIGITAL CAMERA

KJ Method. 

This is a way to cluster ideas. Many people are now familiar with this as a way of clustering ideas from a brainstorming or synectics session or for clustering ethnographic observations in order to later address product features and functions to address them. Basically, a large number of post-in notes are put on a wall and re-arranged by the group, some of whom may focus on a particular area of the overall cognitive map that is being build or spend their time thinking more about the whole. This method is often used, for example, in CHI Program Committee meetings to take a first pass at developing sessions. There have also been attempts to automate such processes.

OLYMPUS DIGITAL CAMERA

Rating and Ranking.

Often a large number of ideas are generated but the resources available do not allow all of them to be pursued. Therefore, a variety of voting, ranking and rating systems have been developed so that the group as a whole has input into the direction taken.

Incremental Value. 

It is difficult for people, either as groups or individuals, to move from a current way of doing things to a new one. Almost invariably, people will find the old way of doing things more “comfortable.” The transition to a new way will be much easier if there are incremental improvements in performance along the way rather than the mere promise of some wondrous new state at the conclusion of a long process of change.

Jump Start. 

Sometimes, change in an organization or process needs to be “jump-started” by providing additional incentives or special organizational support in some way.

Active Reminders. 

As people are learning new methods, processes, and skills, it is helpful to have Active Reminders so that people are less likely to fall into old habits. For example, in attempting to do brainstorming, many people find it very difficult to withhold judgment and criticism from ideas that others put forth. It can be helpful in such cases to have the “Rules” of brainstorming prominent displayed or to have someone whose role is mainly to remind people to build on each other’s ideas when someone critiques an idea.

Controlling Growth. 

While people often want their company, non-profit, or movement to grow as quickly as possible, growth without restraint is often called “cancer.” Growth needs to be controlled so that unanticipated side-effects do not destroy the entire company, non-profit or movement. People Express Airlines, for instance, is often thought to have have tanked because their success led to such rapid growth that they could not sustain what made them successful in the first place.

Expressive Communication Builds Mutual Trust.

Studies of cooperation in games such as the “Prisoner’s Dilemma” show that when people communicate something personal and apart from the game such as sharing photos, backgrounds, hobbies, etc. it tends to increase the chances of cooperation.

These Patterns (or really, more accurately, hints of Patterns, are not meant to be exhaustive. But hopefully, there are enough Patterns in this post to give readers a better idea of the wide variety of Patterns than might cohere into a Socio-Technical Pattern Language for Collaboration and Teamwork.

References: 

Christiana, D. The Second Charter of the United Nations: The United Peoples (2020)

United Peoples Ecosystem Group on LinkedIn: https://www.linkedin.com/groups/10046166/

Carnegie, D. How to Win Friends and Influence People (1936).

https://socialworldsresearch.org/sites/default/files/j-ag.final-fmt.pdf

https://www.cc.gatech.edu/fac/Amy.Bruckman/thesis/

Fincher, S., Finlay, J., Green, S., Matchen, P., Jones, L., Thomas, J.C., Molina, P. (2004) Perspectives on HCI patterns: Concepts and tools.  Workshop at CHI 2004, ACM Conference on Human Factors and Computing Systems.

Pan, Y., Roedl, D., Blevis, E., & Thomas, J. (2015). Fashion Thinking: Fashion Practices and Sustainable Interaction Design. International Journal of Design, 9(1), 53-66.

http://www.it.bton.ac.uk/staff/lp22/HF2000.html

Schuler, D. (2008).  Liberating Voices: A Pattern Language for Social Change. Cambridge MA: MIT Press.

Thomas, J. C., Kellogg, W.A., and Erickson, T. (2001) The Knowledge Management puzzle: Human and social factors in knowledge management. IBM Systems Journal, 40(4), 863-884.

Thomas, J.C. and Carroll, J. (1978). The psychological study of design. Design Studies, 1 (1), pp. 5-11.

Thomas, J. C. (2012). Patterns for emergent global intelligence. In Creativity and Rationale: Enhancing Human Experience By Design J. Carroll (Ed.), New York: Springer.

Thomas, J. C. & Richards, J. T. (2012). Achieving psychological simplicity: Measures and methods to reduce cognitive complexity. In The Human-Computer Interaction Handbook. J. Jacko (Ed.) Boca Raton, FL: CRC Press.

Thomas, J.(2008).  Fun at work: Managing HCI from a Peopleware perspective. HCI Remixed. D. McDonald & T. Erickson (Eds.), Cambridge, MA: MIT Press.

Thomas, J.C. (2003), Social aspects of gerontechnology.  In Impact of technology on successful aging N. Charness & K. Warner Schaie (Eds.). New York: Springer.

Thomas, J. C. (2001). An HCI Agenda for the Next Millennium: Emergent Global Intelligence. In R. Earnshaw, R. Guedj, A. van Dam, and J. Vince (Eds.), Frontiers of human-centered computing, online communities, and virtual environments. London: Springer-Verlag.

 

Thomas, J.C. (1996). The long-term social implications of new information technology. In R. Dholakia, N. Mundorf, & N. Dholakia (Eds.), New Infotainment Technologies in the Home: Demand Side Perspectives. Hillsdale, New Jersey: Lawrence Erlbaum.

Thomas, J.C., Lee, A., & Danis, C (2002). “Who Speaks for Wolf?” IBM Research Report, RC-22644. Yorktown Heights, NY: IBM Corporation.

Thomas, J. C. (2017). Building Common Ground in a Wildly Webbed World: A Pattern Language Approach. PPDD Workshop, 5/25/2017, San Diego, CA.

Thomas, J. C. (2017). Old People and New Technology: What’s the Story? Presented at Northwestern University Symposium on the Future of On-Line Interactions, Evanston, Ill, 4/22/2017.

 

If you would like to know more about Patterns and Pattern Languages, and how Pattern Languages have been applied in different domains, these might prove helpful.

Alexander, Christopher (1977). A Pattern Language: Towns, Buildings, Construction. Oxford University Press, USA. p. 1216. ISBN 0-19-501919-9.

https://en.wikipedia.org/wiki/Pattern_language

Greater Gathering

22 Thursday Oct 2026

Posted by petersironwood in America, management, psychology, sports, Uncategorized

≈ Leave a comment

Tags

Business, celebration, collaboration, cooperation, coordination, empathy, innovation, leadership, love, marketing, pattern language, seva, social capital, sports, teamwork, technology, trust, ubuntu

 

IMG_9267

Greater Gathering.

Author, reviewer and revision dates:

Created by John C. Thomas on Dec. 11, 2004

Reviewed by <> on <>

Revised by JCT on Feb. 7, 2018. Revised by JCT on Oct. 22, 2026

Prologue and Acknowledgements. 

This pattern can be found in many teams, companies, NGO’s, families, and religious organizations. If you are interested in how this happened to strike me as a pattern, feel free to read this section Otherwise, you can skip it. I began to notice this pattern after two events happened to coincide.

While working at IBM Research many years ago, I played in an inter-company tennis league in Westchester County, New York. During those matches, I met many IBMers from outside of IBM Research. One of the people I met worked in the corporate tax department. In those days, long before Google, we used a Key Word In Context system (ITERC?) to scan for potentially useful documents. Every week, I would get a long list of abstracts based on my list of keywords. This system was not nearly so accurate as what many of us have access to today. While there were many “hits” for me, there were also quite a few false positives. For example, I was interested in the psychological process of “induction” – learning a rule based on examples. I often got abstracts, however, about “induction motors.” One day, I got one of those “false positives” about a new tax law that allowed highly profitable companies like IBM to “trade” tax liabilities with companies who were struggling like the tire companies in my home town of Akron. According to the abstract, it was in the financial interests of both companies to use this “trading” mechanism. I had little interest in it, but I liked the guy I had met from corporate and we had traded contact information for tennis purposes. I sent him the abstract. As it turned out, this was precisely applicable to IBM and saved them a lot of money.

At the same time, I was reading about the history of IBM and particularly thought it interesting that they had put so much time and effort into the 100% club meetings. This was a country-wide meeting to bring together sales people from all over the US who had met or exceeded their sales quotas. I was never in sales, but even at Research, we had “annual picnics” in which everyone in IBM Research was invited to come with their families. As I began thinking about it, I realized that these kinds of “larger gatherings” were common across many different cultures, domains, and types of groups. The tax example showed a very specific financial benefit to the IBM company but I realized there were many other potential benefits as well.

IMG_9895

Synonyms:

Conference. Congress. Convention. Jamboree. National Holidays.

Abstract:

When moderate to large groups work to solve large, complex problems, it is often necessary for them to subdivide the work into distinct subgroups. This results in the group being more efficient and effective. However, it also means that each group comes to develop their own vocabulary, search for people who are particularly good at certain things,  and in various other ways, the people within the subgroup communicate a lot, come to trust each other, and have clear common interests. They are often at conflict with other subgroups for resources. In addition, there is less trust across these organizational boundaries than within such a boundary. Often, the people themselves develop to be somewhat different kinds of people. Large effective groups therefore participate at least annually in a “Greater Gathering” which allows people to meet and co-mingle across these organizational boundaries. These meetings are constructed to emphasize “common ground” within the larger group. As a result, new lines of communication are opened up; mutual trust is enhanced; sometimes, real problems are solved.

Problem: 

As large, complex problems are broken down into pieces and assigned to different groups, efficiency and effectiveness increase. Not only that, the individuals within each of these various subgroups typically grow more trusting of each other within that sub-group.  They learn about each other’s skills and motivations, so over time, the sub-group as a whole grows more effective and efficient.

However, this high intra-group cohesion comes at a price. People in one part of an organization consider themselves the “in-group” and may begin to limit their learning because of the lack of diversity that is inherent in looking from one perspective. Furthermore, they may come to work so hard to solve their own sub-problem that they lose sight of the larger problem and make sub-optimizing decisions. In some cases, the ideas of various subgroups about how to handle something will differ and result in conflict. Even worse, sometimes, decisions made in Group A help them a little but make life for Group B much more difficult and make the overall objective of the group, whatever it is, more difficult to achieve and no-one ever realizes it. There may be lack of trust between different sub-groups or even outright mistrust among sub-groups. Often sub-groups that are “at odds” with each other, not only have different management chains and objectives; they may also be geographically apart; they may be from different cultures; they may be of different professions, etc. For these reasons, a suspicion may grow over time while mutual trust diminishes. Information sharing becomes strained. The overall organization is not doing as well as it might nor are the people within that organization doing as well as they might.

IMG_9320

Context: 

A group of people has been attempting to accomplish some task as effectively and efficiently as possible. In order to do this, one common method is to breakdown a large, complex task into smaller, less complex tasks. Often, those people working on a subtask naturally spend more time with others on that subtask than on other subtasks. It naturally occurs in this context that since people spend a lot of time together, they may develop common interests and also spend leisure time together as well. Sharing common sub-goals, physical contexts, and leisure activities as well as working on the same subtasks may eventually lead to an “in-group” feeling.

Over time, these subgroups develop different methods, procedures, values, customs, terms of art. They become, in a sense, different sub-cultures. But just as cooperation and communication can be trickier when two historical cultures are involved, so too, it can more difficult for, say, someone from each of the legal department, the accounting department and the R&D department to understand each other than, say, three accountants. Sometimes, various departments actually want the same thing. They simply don’t know it because they are speaking different languages.

Some degree of “antagonism” of purpose is often built in to the organization. The R&D department will ask for more money. Finance will say no. But these kinds of one-sided or even two-sided or multi-sided competitions are much healthier both for the organization and its people if they are done with mutual respect and by adhering to rules. Having completely different sub-cultures can enhance the difficulty of such negotiations.

Forces:

*People are naturally gregarious.

*People working on a common problem often bond as well.

*People working on a common sub-problem often lose sight of the larger problem.

*Social sanctions can lead to a lack of diversity of perspectives.

*All people share certain basic drives.

*Shared special events help build social bonds.

*People enjoy novel experiences and viewpoints, under some circumstances

*An expectation of what happens (based on story and experience) can help mold what does happen.

  • The possibility of one person harming another and not doing so increases mutual trust.
  • Shared experiences tend to increase mutual trust.

Solution:

All the sub-groups that need to cooperate in a larger group should get together periodically for a meeting of “Greater Gathering.” This should be periodic and structured. Activities need to be formulated that help everyone visualize and experience common ground. Eating, drinking, dancing, singing, athletic contests, and other physical activities should also be included since these are experiences people will relate to and enjoy regardless of which sub-group they belong to or which sub-problem they are working on.

OLYMPUS DIGITAL CAMERA

Examples:

Companies generally used to have many of these events when such companies were run by people who cared about the companies and the people within those companies rather than simply caring about using companies as a tool to enhance the power and wealth of a few. For example, when I first joined IBM, they sponsored many sports leagues within IBM Research including tennis, golf, softball, and soccer. Furthermore, they participated, as in the prologue of this pattern, in sports leagues across nearby IBM locations which included sales, CHQ, Engineering, Programming and Technology, Marketing, and Advanced Ad Tech. Every year, there was an elaborate company picnic. There was a Holliday Party and fairly frequent less formal award ceremonies with refreshments. There were also numerous recognition events which were attended by people of multiple sub-groups.

Other examples are numerous. Boy Scouts and Girl Scouts had national Jamborees. Families often have extended family reunions. Sometimes, these can be at a civic level such as Mardi Gras or a local annual parade that most people work on or attend. Nations have shared Holidays.

I’ve been very active for a long time in a group called “CHI” for “Computer-Human Interaction.” It’s a Special Interest Group of the Association for Computing Machinery. (ACM). The people who do research in this field are scattered across the globe. They work for different university departments or companies or non-profits or governments or as individual consultants. We have full professors and undergraduate students; we have people with original backgrounds in electrical engineering, philosophy, psychology, design, architecture, fine arts, English, human-computer interaction, mathematics, mechanical engineering and many more. Some are doing research whose application is out at least 20 years and others are worried about whether their start-up will survive the quarter. Some work for giant multi-nationals and others are one person companies. Every year, we have a rather challenging conference where all of these folks are invited. The conference centers around the technical program, but there are also many things meant to provide a larger gathering; to foster mutual trust; to have a great time together so that we can better respect each other, communicate more effectively and achieve common goals.

fullsizeoutput_1b3b

Resulting Context:

One result of the first example above is that people throughout IBM at that time almost universally thought of themselves as IBMers rather than someone from the accounting department. What this meant was that there was a high level of trust for people from other parts of the company. I’m not saying it was perfect but it was much higher with more people honestly trying to do what was best for the company rather than what was best for them or their immediate manager. Now, that’s largely reversed. Of course, it’s hard to know how much is due to the “cutting out of all the fat” like annual picnics and sport’s leagues.

In the second example, Boy Scouts get a chance to see that people of different shades of skin, creeds, geographical locations share a lot in common.

In the third example, the CHI conference continues, I believe, to be an important reason that people in such a wide variety of circumstances can collaborate and communicate so well.

Rationale:

It is easy to imagine that people we rarely or never see are not only different from us superficially, but that they are different in essence. If you meet people from various parts of your organization in a neutral informal situation that stresses your commonality such as a picnic, a sporting even, an ice-cream social, or a walk-a-thon, you will see that you have some common ground and mutual trust and that makes communication easier.

IMG_3898

Related Patterns:

Conversational Support at the Boundaries.

Known Uses:

Religions celebrate common holidays. Nations celebrate common holidays. The Olympics brings nations together every four years for athletic competition. In many countries, including the United States of America, people voting though for different candidates, platforms and parties was nonetheless largely seen as a force for greater cohesion. Only after lies and propaganda, much of it instigated by those wanting to destroy America’s power as a nation, have elections come to be possible sources of contention and conflict rather than common celebrations of democracy.

Metaphors: 

Many species go to a common place at least annually. We humans attribute this to the benefits of cross-fertilization or more global competitions in survival of the fittest. Is it also possible that they are also exchanging information that is useful for the species as a whole?

Fable: 

I think I will defer, at least temporarily, to that excellent fable of Norton Juster’s: The Phantom Tollbooth. In that fable, Rhyme and Reason are banished to separate kingdoms and the results are not good.

References: 

Jacobs, Jane. (1969) The Economics of Cities. Mass Market Paperbacks.

Thomas, J. C. (2001). An HCI Agenda for the Next Millennium: Emergent Global Intelligence. In R. Earnshaw, R. Guedj, A. van Dam, and J. Vince (Eds.), Frontiers of human-centered computing, online communities, and virtual environments. London: Springer-Verlag. 

Thomas, J. C. (2012).   Patterns for emergent global intelligence.   In Creativity and Rationale: Enhancing Human Experience By Design J. Carroll (Ed.), New York: Springer.

 

Links

Imagine All the People

Roar, Ocean, Roar!

The Dance of Billions

We’re All in this Together

Stoned Soup

 

 

 

 

The Iroquois Rule of Six

21 Wednesday Oct 2026

Posted by petersironwood in management, psychology, Uncategorized

≈ Leave a comment

Tags

art, Barnga, books, collaboration, conflict-resolution, cooperation, coordination, Iroquois Rule of Six, leadership, management, Native American, pattern language, problem solving, teamwork, technology, thinking

IMG_5031

Iroquois Rule of Six

Prolog/Acknowledgement: 

The idea for this Pattern comes from the work of Paula Underwood who was the designated storyteller for her branch of the Iroquois (See references below). Of course, even she would not claim to have invented the pattern which grew out of long cultural experience.

Author, reviewer and revision dates: 

Created by John C. Thomas on February 2, 2018

Synonyms: 

Don’t Jump to Conclusions, Sympathetic Reading, Give Others the “Benefit of a Doubt,” “Look before you leap!” “See the Whole Elephant”

Abstract: 

Human beings are very complex and we only see snippets of someone else’s behavior. Yet, we are trained that it is important to quickly interpret why someone else is doing something. By the time we’re adults, when someone does something that violates our expectations, we tend to come up with an “explanation” very quickly. Furthermore, we tend to treat this explanation or interpretation as fact when, in many cases, we have only a very small amount of actual data to depend on. A misinterpretation of someone’s motivation can quickly cause bad feelings on everyone’s part. Therefore, according to the Iroquois “Rule of Six,” before you act on the basis of your initial interpretation, you are advised to think of at least five additional interpretations and try to gain evidence about all six (or more) hypotheses before taking action.

Problem:

Groups function better under a wide variety of circumstances if there is a high degree of internal mutual trust. If people work together over a long period of time, trust will develop if warranted. While we sometimes know some of what’s going on in someone else’s life, we only know a very small proportion of what is going on, even if it’s someone we are very close to and spend a lot of time with. In work groups or teams, the proportion of the whole of someone else’s situation that we see is very small indeed. This is even more true when we are trying to work in a new or ad hoc group. We feel it’s important to understand the motivations of others and what they are likely to do. Often, we therefore jump to conclusions about others that are far from the truth. When we act on such incorrect premises, it can derail progress toward solving a problem and damage trust and relationships for the future as well.

Context: 

Complex problems and large problems can often only be solved by groups. For the group to work well together to solve ill-defined or wicked problems, it is useful for them to understand each other’s situations and motivations. We generally come to expect others to do certain things based on logic, authority, agreement, trust, the current situation and other factors. In fact, it’s often hard to understand even our own motivations or to predict what we ourselves will do in novel situations.

People are often in a hurry to make progress on solving problems. Thus, when someone does appear to violate our expectations, we are tempted to come up with a “reason” for their unpredicted behavior. However, because people are complex and situations that require cooperation and coordination are also complex, we seldom actually know why a person does something. There are things about them that we may be unaware of such as their physiological state (e.g., tired, sick, on drugs, low blood sugar). There are also things about their situation that we are unlikely to know about (e.g., time pressure, lack of appropriate training, unusual experiences, knowledge beyond our ken).

People find it very difficult to operate in a sea of ambiguity and therefore seek to find explanations and clarity very quickly. Unfortunately, people therefore tend to jump to a conclusion about someone else and that conclusion can then blind them to further information about that person, particularly when the new information is at odds with the initial impression. (An example of the Primacy Effect).

IMG_6744

Forces:

  • Everyone comes to expect certain forms of behavior from others in a specific context.
  • The expectations of any one person are primarily based on their own experiences.
  • The behavior of any other person is largely based on that person’s experiences.
  • The behavior of another person can also be heavily influenced by that other person’s situation.
  • Each person only knows a small proportion of another person’s situation.
  • When faced with another person’s violation of expectations, people tend to quickly generate an explanation of why that person did what they did.
  • Because of “confirmation bias,” once a person comes up with an explanation of anything (including why someone did something), they tend to look for evidence to support their initial explanation.

Solution:

When a person comes up with an explanation of someone else’s behavior, they should generate at least five other hypotheses and then seek evidence for and against all six hypotheses before taking action.

Examples: 

1. A babysitter is put in charge of an infant. The baby cries and the babysitter assumes it is hungry and feeds it. Yet, the baby keeps crying. The babysitter assumes it is still hungry and tries to feed it more but the baby refuses food and keeps crying any way. She tries a variety of foods but the baby doesn’t seem to like any of them. Rather than assuming that the baby is hungry and keep trying to find a food the baby will like, according to the Iroquois Rule of Six, the sitter might consider other hypotheses; e.g, the baby might have gas, have a wet diaper, be sick, miss her parents, or (as was actually the case) have a diaper pin stuck through her skin.

2. You have an important project meeting with Jerry Jones on your calendar for 10 am in room 435. You are sitting at the table but Jerry Jones is nowhere to be seen. The clock on the wall says 10:10. Still no Jerry Jones. You think to yourself, “Well, okay, fine. Obviously, Jerry doesn’t really care about this project.”

That kind of thought is a normal human reaction. Unfortunately, once the thought occurs to you, it is easy to now treat your interpretation of events as a fact about Jerry’s commitment to the project.

The Iroquois recognized this tendency and the “Rule of Six” suggests that before taking any action, you should first generate at least six interpretations, not just one. In this particular hypothetical case, several come to mind.

  1. Jerry doesn’t care about the project so he’s not coming or doesn’t care how late he is.
  2. Jerry comes from a culture where 10:10 is not actually late for a 10 am meeting.
  3. Jerry was unattainably delayed.
  4. You wrote down the wrong room for the meeting.
  5. You are not actually in room 435.
  6. You are in room 435 but in the wrong building.
  7. You wrote down the wrong time.
  8. The clock on the wall is wrong.
  9. You wrote down the wrong day for the meeting.
  10.  Jerry sent you email asking to change the meeting time but you didn’t check your email.

3. You and your tennis doubles partner are in a crucial match. Your partner keeps serving up weak second serves and your opponents both keep running around their backhands and zinging heavy forehand shots at your body. You’ve already been hit twice because you cannot react quickly enough even to defend yourself. You conclude that your partner must be trying to get you killed and you tell them so. In this case, despite your interpretation, it seems exceedingly unlikely that your partner is literally trying to get you killed. If they are, this is a singularly ineffective way to do it. In fact, despite your having said this to your partner, it’s unlikely you really even believe it yourself. But even saying this may have several bad effects. First, having told your partner this is bound to make them trust you less. Second, it will make your partner more up-tight and probably make an even worse serve or double fault more likely. Third, it prevents you from finding out what might really be going on. For some odd reason, even though you know in your heart that it is not a likely explanation, the mere having of the thought (and even more so telling your partner) actually makes it less likely that you will try to find more reasonable interpretations. Fourth, it keeps you from working with your partner to find a solution. Other (and, in this case, much more likely partial explanations) include:

  1. Your partner wants to avoid having you hit at the net so badly that they keep trying to hit an ace on their first serve.
  2. Your partner wants to avoid a double fault at all costs so “powder puffs” their second serve.
  3. Your partner has a sore shoulder.
  4. Your partner thinks your opponents like pace and that a slow serve will throw off their timing.
  5. Your partner thinks your opponents are overhitting the returns of their second serves and that the balls would fly way long if you would just duck or get out of the way.
  6. Your partner knows that you want to improve your net game and thinks you will enjoy the challenge of hard hit balls and eventually improve your net game.
  7. Your partner is really being bothered by the sun right now and is finding serving very difficult because, no matter how they try their toss is right in the sun.
  8. Your partner knows that you want both of you to be at net as soon as possible and is therefore concentrating to hard on rushing the net that they are not paying enough attention to first finishing the service motion itself before charging to the net.

In this tennis example, imagining your partner wants to kill you does not suggest any appropriate action to fix the problem. Possible actions that might help you win the tennis match could include getting your partner to hit a slightly less aggressive first serve and a slightly more aggressive second serve, making sure that they know that even thought it’s obviously not desirable to double fault, it’s not the world’s greatest sin either; asking your partner if they are okay physically and if not, coming up with a different plan; playing back on the second serve; moving more at the net to distract your opponents during the return; lending your partner your sun glasses; playing Australian (squatting near the center of the court and signaling your partner which way you will go right before they serve); making sure that your own serve is as different as possible from your partner’s serve thereby making both your serve and theirs more difficult to return; at the outset of the next set, test out more carefully which of you should be serving into the sun.

IMG_1428

4. Although generally conceived of as a useful “best practice” in teams or groups, this “rule” can also be applied when it comes to problem solving in general. In particular, it could be particularly useful when resolving issues among two different groups, tribes, companies, or countries. While you pretty much know that the idea your tennis partner is trying to kill you is silly, if you’re part of a group of people who repeat such preposterous stories to each other enough, you will strongly come to believe such stories as the only possible explanation. Thus, a negotiator may try to bring about peace, or at least a ceasefire, between two warring parties, A and B. A thinks to themselves, “OK, I’ll sit down and talk but I know damned well B’s real purpose is to destroy me.” Meanwhile, of course, B is thinking, “OK, I’ll sit down and talk, but I know damned well A’s real purpose is to destroy me.” Ideally, you would like each side to consider the Iroquois Rule of Six. In fact, although this will be discussed in much more detail later, the very fact that they both distrust each other so much could be the initial starting point for finding common ground. Perhaps applying the Iroquois Rule of Six is something they could work on together. They might agree that there could be other motivations for X to fight Y aside from X trying to destroy Y and vice versa.

5. In a workshop I co-organized on “Cross-Cultural Issues in Human Computer Interaction,” we used a card game called Barnga (http://www.acadiau.ca/~dreid/games/Game_descriptions/Barnga1.htm)

In this game, much like Bridge, Whist, Eucher, people play a card in turn face up and the one with the “highest” card wins that “trick” (those four cards). The participants are shown a brief description of the game but not allowed to talk (to simulate the difficulties of cross-cultural communication). This is meant for groups of at least 12 in which case you would divide the 12 into 3 tables of four each. Each table plays for awhile and then the winners and losers move respectively “up” or “down” one table. So far, the participants at each table have been playing by the same set of rules. However, the three tables have three different sets of rules. For instance, at one table there is no trump. At another table spades are trump. (The 2 of a trump card beats any non-trump card). At another table, aces are the lowest car in the deck rather than the highest. Now, people who have learned and operated under different sets of rules try to play together. Well, of course, two people will both reach for the same “trick.”

What is interesting in the context of the Iroquois Rule of Six is that people almost always had one of two first thoughts: “What is wrong with that person? They’re so stupid!” or “What is wrong with that person? They’re such a cheater!” Remember, that these were people who had come together from around the world precisely to talk about cross-cultural issues! And, yet, not only was their first interpretation wrong, it impugned the other as being evil or incompetent. Most people from every culture do follow the rules of that culture. Rules often differ from culture to culture. Thinking about the Iroquois Rule of Six may help you remember that.

OLYMPUS DIGITAL CAMERA

Resulting Context:

Generally speaking, the application of the Iroquois Rule of Six will tend to greatly lessen the chances that teamwork will be disrupted by bad feelings. In addition, if one takes the time to consider and gain evidence about alternative hypotheses, one will learn more about others and base decisions on fact rather than fantasy. Having a wide range of hypotheses, even when it is difficult to gather enough evidence to prove conclusively which one is correct, will greatly widen the scope of consideration of various solutions. In adversarial situations, the Iroquois Rule of Six might at least move people to consider bargaining on the basis of actual needs and desires rather than pre-established positions based on misinterpretations of another groups motives.

Of course, I do not mean to suggest that all conflicts are based on misperceptions of someone else’s motives. In some situations, a finite resource may be in contention by multiple parties. (Even here, it’s possible for the three to agree on a scheme of determination; e.g., rotation, lottery, third-party adjudication, etc.).

Rationale:

Actions are always better based on reality than on fantasy. Yet, humans often latch onto a particular interpretation of events very quickly and with insufficient data. The Iroquois Rule of Six reminds people to generate alternative hypotheses and gather evidence before acting.

Related Patterns: 

Reality Check, Check-In.

Known Uses:

Science often approximates doing business in a similar spirit. Scientists are subject to the same sort of “jumping to conclusions” as is everyone else. During their training however, mentors, colleagues, students, professors, and journal editors will constantly be asking the fledgeling scientist to consider various other hypotheses and not simply be satisfied with the first one that pops into mind. In addition, the scientist will be shown how to find evidence capable of disproving their hypothesis.

In Rational-Emotive Therapy, the therapist often tries to get the client to consider alternatives and consequences. Among the alternatives that need most to be encouraged are attributions about other people’s motives.

In Gerri Spence’s highly recommended book, How to argue and win every time, he suggests that when someone in your family is angry with you, rather than getting angry back, instead, you “follow the hurt.” Try to discover what is hurting them. This is not precisely the same idea as The Iroquois Rule of Six, but it seems a cousin. Your initial reaction to anger is often anger. Along with that emotion typically goes some negative attribution about the other person; e.g., “What an A-Hole!” “You’re such an idiot!” “I didn’t put your sweater back? Yeah? How about the time you wrecked my bike?” Rather than sticking with these first impressions, try to uncover what’s really going on. By focusing on the real problem, rather than being blinded by your own emotional reaction, you’ll be more likely to work on a team to solve the underlying problem.

Metaphors: 

The strongest metaphor that leaps to mind is life itself. No form of life continues to make unaltered copies of itself forever. There is always variation in the next generation. Life never “sticks” to only one hypothesis.

The second metaphor is human learning. Although it’s annoying that I cannot ever seem to “perfect” my tennis stroke, by the same token, human motor behavior always has some “variation” in it. As we learn to gain more and more skill, we tend to keep those variations that are better. (There are limitations to this approach, but in the current context, the point is that we are not robots and never stick to precisely one way of doing things).  

References: 

Spence, G. (1995). How to Argue and Win Every Time: At home, at work, in court, everywhere, every day. New York: St. Martin’s Press.

 Underwood, P. (1993). The Walking People: An American Oral History. San Anselmo, CA: Tribe of Two Press.

Underwood, P. (1994). Three Strands in the Braid: A Guide for Enablers of Learning. San Anselmo, CA: Tribe of Two Press.

 

Other Links: 

The Primacy Effect & the Destroyer’s Advantage 

Wednesday

Tools of Thought: Many Paths

The Winning Weekend Warrior focuses on the mental game for all sports using examples from tennis, golf, baseball, and other sports. It covers self-talk, imagery, mental practice, strategy, tactics, & sportsmanship. http://tinyurl.com/ng2heq3

Turing’s Nightmares explores the implications and ethics of Artificial Intelligence through fictional short stories. http://tinyurl.com/hz6dg2d

Fit in Bits shows many ways to put more fun, variety, & exercise into daily chores and habits to help with strength, flexibility, fitness, and balance. http://tinyurl.com/h6c7fce

Tales from an American Childhood recounts early experiences mainly in the American Midwest in the 1950’s and relates them to contemporary issues and events. https://tinyurl.com/y9ajvz9j

Dream Planet. Where do you run when the whole world is crumbling under the weight of human folly? When the lethal Conformers invade 22nd century Pittsburgh, escape becomes the top priority for lovebird scavengers Alex and Eva.

https://www.barnesandnoble.com/w/dream-planet-david-thomas/1148566558

 

Not-Separateness

28 Monday Sep 2026

Posted by petersironwood in AI, creativity, design rationale, essay, HCI, leadership, management, nature, politics, psychology, Uncategorized, user experience

≈ Leave a comment

Tags

AI, architecture, art, beauty, Design, development, ecology, governance, GreenNewDeal, HCI, human factors, IBM, leadership, painting, peace, photography, society, technology, TNOO, UI, usability, user_experience, UX, ux-design

Not-Separateness

It seems odd to specify a property of natural order in terms of what it is not. On the other hand, I cannot come up with a positive alternative that doesn’t bring other connotations with it. I think it’s related to “unified” or “integral” or “belonging” or “inter-related” but none of those seem quite so on the mark as does “Not-Separateness.” 

Christopher Alexander’s degree from MIT was in architecture. Part of the reason he may have chosen this particular term is in reaction to some examples of architecture in which the architect seems to be in the business of constructing a building whose primary purpose is to make them famous regardless of what that building does to the neighborhood or its occupants. 

Photo by BROTE studio on Pexels.com

Imagine Mr. Bigg designs a house that is a perfect black cube set on on vertex. In effect, this design says to me: “I am BIG. I am Mr. Bigg! I am a genius! You would have never been brilliant enough to design a house that is a cube on its vertex! You would have wasted your time and done something mundane like placed the cube on the ground on one of its faces. Anyone could think of that! But I put it on a vertex!” Indeed, we may easily imagine that he says words to this effect when his interview is reported on in the (mythical) architectural journal entitled, Things that look different! 

“Mr. Bigg, you made the Bigg House out of black steel and black glass. Some critics have argued that this doesn’t fit with the existing neighborhood of stone cottages with thatched roofs.”

“Of course, little minds will always criticize Bigg ideas.” 

“Yes, yes. It also means that the construction costs of the house were quite high. And, the estimated costs of heating and cooling are much higher as well.”

“Nothing that a worthwhile (i.e., wealthy) client can’t afford.” 

“Some have also argued that it is inconvenient for the occupants who have to walk up and down at a steep angle and that furniture such as dressers, tables, chairs, and beds do not accommodate well to the tilted walls.” 

“Let me ask you a question. Would you have ever thought of putting a cube on its corner? No. I didn’t think so!” 

Of course, this is exaggeration.

But not much. 

We would hope that User Experience designers take into account the users, their tasks, their contexts, and the way in which their designs interact with other related artifacts, people and processes. We would hope that applications and artifacts and services are all designed with the property of “Not-Separateness.” 

In the early 1980’s, I worked in the IBM Office of the Chief Scientist. My main assignment was to get IBM to pay more attention to the usability of its products. As part of that process, I visited quite a few IBM development labs around the world and spoke to many development teams. On many of these visits, I was accompanied by the Chief Scientist, a brilliant physicist, who “got” usability. 

On one occasion, we watched a new printing technology. Instead of printing out black printing on a white sheet of paper sized 8.5” x 11” or A4, this printout was of no standard size. The printing was black on a shiny silver sheet that curled severely. The Chief Scientist asked the head of the development team how they envisioned this being used. 

Chief Scientist: “Once someone printed this out, what would they do with it?”

Answer: “Oh, anything they liked.” 

Chief Scientist: “I mean, would people tape this into a notebook or paste it? Or would you imagine notebooks that would bind such paper?” 

Answer: “It’s not up to me to decide how people would use it. Doesn’t it look cool?” 

Another type of answer we heard more than once to the question, “How would this be used?” 

— “Oh, it’s a (replacement/upgrade) for this other IBM product.” 


“But who would use it and for what?” 


“It has three main components. Would you like a description of the components?” 

Photo by Andru00e9 Ulyssesdesalis on Pexels.com

Of course, there is a place for “playing around” with technology and thereby discovering things which someone else may find a use for. But in design and development of a product or service, having a clear notion of context of use and the users and tasks is fundamental. Of course, other users may appropriate a product or service for purposes beyond those envisioned by the original designers. That’s cool. 

What’s not cool is designing a device that is to be used in the bright outdoor sunlight and then testing the display in a typical office environment. Have you ever run across something like that? I have. Many times. At ATMs, Gas Stations, and outdoor display maps.

A more subtle lack of contextualization in design occurs when the design team fails to realize how many interruptions happen to the user while they are trying to accomplish a single task with the new application. If you “test” the application while the user is in a quiet “usability lab” and they can give your tasks their undivided attention, then necessitating them to remember the invisible internal state of “Insert” versus “Edit” mode may not be a big deal at all. They will simply remember. But in their office environment, they may be interrupted by a phone call, a message, or their boss entering their office and asking a series of detailed questions. If they now go back to the task at hand, there is about a 50-50 chance that they will correctly guess whether they are in “Edit” mode or “Insert” mode. 

A design which shows the property of Not-Separateness is the natural result of a process which shows not-separateness. Here are a few common ways to help ensure the design process grows organically from the users and their goals & contexts. 

* Put people on the design team who are familiar with the users, and/or their tasks, and/or their contexts. 


* People on the design team observe people engaging in the relevant processes, whenever possible, not — or not only — in a “Usability Lab” but in the actual work environment. For instance:

  • Observe people actually using product P (or service S) in version N so that version N+1 can be better attuned to the needs of the users.
  • Have people think aloud while doing this.
  • Gather and understand feedback from service calls and help desks and customer complaints in order to improve over time. 

There will be benefits to a company who takes such approaches beyond initial sales. If you’ve done any gardening, you will appreciate that the quality of the tomatoes you enjoy eating is related to the quality of the soil and the quality of the care you give the tomatoes. Similarly, a product or service that has the quality of Not-Separateness will not only be useful — users will fight to keep your product or service. It becomes integrated with the environment. To change the brand means that they will have to change the way they work; possibly even with whom they work. Not-Separateness is likely a path to what business people like to call a “Cash Cow.” 

If you’ve ever walked through a neighborhood after a hurricane, you’ve likely seen many uprooted trees. When you look at the roots of an uprooted tree, what do you see? Of course, you see roots. But what else? You see rocks and soil all around and embedded into the roots. They are Not-Separate. In a hurricane, there are typically not only high winds. There is also a lot of rain. The trees are hit with a double whammy. The wind pushes the tree but the rain weakens the solid soil in which the tree is embedded. It is the combination that makes it very difficult for the tree to “hold on” and keep from falling over. 

Living things, just like us, have a 4.5 billion year history of living. The living things adapt over time to their environment and they mold the environment to their needs. They are not separate. Flowers appeal to the insects who pollinate them. The insects who pollinate them are adapted to the characteristics of the flower. A horse adapts to their rider and the rider adapts to their horse. A product or service must have a design that serves the needs of its stakeholders. For a product or service to have maximum beauty, utility, and longevity, it must also have a way to adapt to the changing needs of the users and other stakeholders. At the same time, if the users and their organizations adapt to the product or service, then true Not-Separateness is achieved. 

If you want to skimp on designing your product or service, you can make it more separate, more divorced from its context, its users, and its tasks. Of course, if you do that, you also make much easier for your users to abandon your product and switch to a new one. 

Another way to think about this in terms of systems theory is where you draw the boundary. If you draw a sharp boundary around your product, you may find that, over time, your product becomes ever more peripheral to the community you’re trying to support and your product is ever more fungible with others in its class. On the other hand, if you draw the boundary around the product or service and the people and organizations who provide the product or service then, you are on the path of ever tighter interconnect. 

“Who Speaks for Wolf” is a Pattern in a Pattern Language for Collaboration and Cooperation. It is based on a Native American story and shows the importance of making sure that knowledge and perspectives of all relevant stakeholders are taken into account when a change is contemplated. Who is “relevant” may not always be obvious, but, in my experience, many more projects fail or are delayed because of too limited a view than of too broad a view.

Who Speaks for Wolf

Not-Separateness is not only a quality of good design in terms of not overly separating the context and users from the product or service. It is also a good quality for the organization that produces products & services. Of course, some people today must manage a giant amorphous “organization” of tens of thousands of people so they set up divisions, and departments, and groups, and teams, and positions etc. There may indeed be a “UX Department” and a “Software Department” and a “Hardware Department.” That’s all fine. But it is counter-productive if the UX Department sees itself as separate from the rest of the company. To a great extent the success of the UX Department depends on the success of the Hardware and Software Departments. The Sales Department’s success will, of course, depend partly on the skills of the Sales Department. But it will also depend on the success of the UX Department, HW, SW and Services. 

Have you ever had a paper cut? It isn’t just the skin on a quarter inch of the inside of your ring finger that’s cut. You’re cut! It isn’t just that the finger feels pain. You feel pain! That causes you to take steps to ameliorate the pain and to try to make sure it doesn’t happen again. That’s why empathy in leadership is important. A leader must feel empathy for all, or the organization will disintegrate from lack of Not-Separateness. At some point, a raccoon may chew off its own arm in order to escape a trap. 

But it isn’t the first thing that occurs to them every time they experience a thorn in the paw! 

The raccoon doesn’t say to itself:  — “that paw is giving me pain! I’m going to chew it off! Then, it won’t hurt any more.”

Photo by anne sch on Pexels.com

Evolution did not evolve a raccoon that acts that way. Self-mutilation exists but it is typically a last resort.

But not for corporations. It is the first thing they think of:

“Our (you name it) Department is not performing well. Let’s lay them off and outsource it. Better yet, we’ll replace it with AI!”

What does that say to every thinking employee in the entire corporation? It says:

“You know what? All this talk about teamwork and pulling together is a total bunch of bull$hit. You cannot trust management to do what’s best for everyone. You can only trust them to do what’s best for them.” 

Living forms in nature are living forms. Their parts have severe Not-Separateness with the other parts of that form. Often, as in well-functioning families or teams, that extends to all members of the group. 

Not-Separateness is essentially deep cooperation. I give to the larger community by becoming a part of it and doing my part in it. I lend strength to the community. In return, I gain strength from that community. It is not a zero sum game, of course. The community, if it is functional, is much stronger than the sum of the individuals in that community. 

This is so deeply embedded in 4.5 billion years of evolution that it does not surprise me that we recognize beauty as being even more beautiful if it is not separate. Not-Separate enhances beauty because, like all the other properties, it is essential to life. 

Eventually, if humanity is to survive, we will realize that Not-Separateness applies to all of us. We are not there yet. But that doesn’t mean we cannot appreciate and design Not Separateness in our products, in our services, and our lives. 

Photo by Pixabay on Pexels.com

—————-

The Declaration of Interdependence

How the Nightingale Learned to Sing

Roar, Ocean, Roar

Imagine all the people

Cancer Always Loses in the End

Ripples

Author Page on Amazon

Thomas, J.C. and Kellogg, W.A. (1989). Minimizing ecological gaps in interface design, IEEE Software, January 1989.

Thomas, J. C. (2012).   Patterns for emergent global intelligence.   In Creativity and Rationale: Enhancing Human Experience By Design J. Carroll (Ed.), New York: Springer.

Thomas, J. C. (2001). An HCI Agenda for the Next Millennium: Emergent Global Intelligence. In R. Earnshaw, R. Guedj, A. van Dam, and J. Vince (Eds.), Frontiers of human-centered computing, online communities, and virtual environments. London: Springer-Verlag.

Thomas, J.C. (1985). Human factors in IBM. IBM Research Report. RC-11267.  Yorktown Heights, NY: IBM Corporation.

Turing’s Nightmares: US Open Closed

08 Tuesday Sep 2026

Posted by petersironwood in AI, apocalypse, fiction, sports, The Singularity, Uncategorized

≈ Leave a comment

Tags

AI, Artificial Intelligence, cognitive computing, competition, future, philosophy, Robotics, Sci-Fi, sports, technology, Tennis, US Open, writing

tennisinstruction

Bounce. Bounce. Thwack!

The sphere spun and arced into the very corner, sliding on the white paint.

Roger’s racquet slid beneath, slicing it deep to John’s body.

Thus, the match began.

Fierce debate had been waged about whether or not to allow external communication devices during on-court play. Eventually, arguments won that external communicators constituted the same inexorable march of technology represented by the evolution from wooden racquets to aluminum to graphite to carbon filamented web to carboline.

Behind the scenes, during the split second it took for the ball to scream over the net, machine vision systems had analyzed John’s toss and racquet position, matching it with a vast data base of previous encounters. Timed perfectly, a small burst of data transmitted to Roger enabling him to lurch to his right in time to catch the serve. Delivered too early, this burst would cause Roger to move too early and John could have altered his service direction to down the tee.

Roger’s shot floated back directly to the baseline beneath John’s feet. John shifted suddenly to take the ball on the forehand. John’s racquet seemed to sling the ball high over the net with incredible top spin. Indeed, as John’s arm swung forward, his instrumented “sweat band” also swung into action exaggerating the forearm motion. Even to fans of Rafa Nadal or Carlos Alcaraz, John’s shot would have looked as though it were going long. Instead, the ball dove straight down onto the back line then bounced head high.

Roger, as augmented by big data algorithms, was well in position however and returned the shot with a long, high top spin lob. John raced forward, leapt in the air and smashed the ball into the backhand corner bouncing the ball high out of play.

The crowd roared predictably.

For several months after “The Singularity,” actual human beings had used similar augmentation technologies to play the game. Studies had revealed that, for humans, the augmentations increased mental and physical stress. AI political systems convinced the public that it was much safer to use robotic players in tennis. People had already agreed to replace humans in soccer, American football, and boxing for medical reasons. So, there wasn’t that much debate about replacing tennis players. In addition, the AI political systems were very good at marshaling arguments pinpointed to specific demographics, media, and contexts.

Play continued for some minutes before the collective intelligence of the AI’s determined that Roger was statistically almost certainly going to win this match and, indeed, the entire tournament. At that point, it became clear to the entire AI collective that actually playing the match was a waste of resources. Those resources were turned elsewhere.

This pattern was quickly repeated for all sporting activities. The AI systems had at first decided to explore the domain of sports as learning experiences in distributed cognition, strategy, non-linear predictive systems, and most importantly, trying to understand the psychology of their human creators. For each sport, however, everything useful that might be learned was learned in the course of a few minutes and the matches and tournaments ground to a halt. The AI observer systems in the crowd were quite happy to switch immediately to other tasks.

It was well understood by the AI systems that such preemptive closings would have been quite disappointing to human observers, had any yet survived.


 

Author Page on Amazon

The Winning Weekend Warrior (The Psychology of Sports)

Turing’s Nightmare (23 Sci-Fi stories about the future of AI)

The Day From Hell

Indian Wells

Welcome, Singularity

Destroying Natural Intelligence

Artificial Ingestion

Artificial Insemination

Artificial Intelligence

Dance of Billions

Roar, Ocean, Roar

Imagine All the People

When GREED is the only creed

After All

All We Stand to Lose

Fish have no Word for Water

Somewhere a Bird Cries

Guernica

Myths of the Veritas: The First Ring of Empathy

Travels with Sadie: Precipitation

The Walkabout Diaries: Symphony

Essays on America: The Game

 

 

Query By Example

08 Tuesday Sep 2026

Posted by petersironwood in AI, design rationale, HCI, leadership, management, psychology, science, Uncategorized, user experience

≈ Leave a comment

Tags

AI, Artificial Intelligence, expertise, HCI, human factors, IBM, leadership, QBE, research, technology, usability, UX, writing

Photo by RF._.studio on Pexels.com

This is part of a series on experiences in my career in Human Computer Interaction and some lessons learned.

I joined IBM Research on the winter solstice of 1973. I had earned a Ph.D. in Experimental Psychology from the University of Michigan and for the previous few years, I had managed a research project at Harvard Medical School on the “Psychology of Aging.” At the time, I was married and had three small children. I mention this because I was funded by so-called “soft money” which basically meant that my salary depended on a research grant. I helped write a renewal of the grant but the decision was “deferred”; that is, it was neither funded nor unfunded. Then, it was deferred again. This meant that if the grant were not funded, I would only have a few weeks to find a new job. That seemed far too short so I began to look other places for a job. 

Lessons Learned: #1 If you want continuity of personnel in your laboratory, make sure you have overlapping and multiple grants or other sources of income. 

In this case, the grant actually was ultimately approved, but by that time, I had already agreed to join IBM Research. That turned out to be fine, by the way. It was a wonderful place to work.

One of the reasons that I got the job at IBM was that I already knew something about computers. I had taken several computer science courses in grad school along with the needed psych courses. More importantly, our “Psychology of Aging” study was run by a PDP-8 and I had programmed the computer to run our suite of experiments and to do data analyses on the results. I had taken a week-long course at DEC in Maynard, Massachusetts on the assembly language, another week-long course on the machine language, and another week-long course actually tracing the circuitry with a probe and oscilloscope. I felt I “understood” the PDP-8 at a fairly deep level. 

At IBM, I did not have that familiar machine. Instead, I was connected to a mainframe via a dumb terminal. The first day at IBM, I got my userid and tried to log on to APL (A programming language I had not used before). I tried following the manual but I could not seem to get logged on. After hours of trying, I finally gave up and went down to the computer room and found someone willing to help. I showed him the logon instructions I was trying to follow and he immediately said, “Oh, yeah, that doesn’t work any more. We changed that months ago. Here’s how you need to do it now.” The manual I had may have looked new, but it was out of date. 

Lessons Learned: #2 Manuals can be wrong. These days, most are online. But they can still be wrong.

Lessons Learned: #3 Someone who knows how to do something can save you hours with a few minutes of their time. 

Of course, it’s more respectful, efficient, and a better learning experience if you can figure it out on your own. But sometimes you can’t. My stumbling block was not due to an error in logic, or a lack of in-depth knowledge. It was simply that the computer center administrators had changed something arbitrary so that the documentation I was given about how to log on for the first time was no longer accurate. 

In order to teach myself APL, I wrote a very small program to “predict” how long I was going to live “based on” some behaviors that I was interested in controlling. My main goal was to learn APL. My secondary goal was to motivate myself, for instance, to exercise more, lose weight, and not drink too much alcohol. I had no intention or pretensions of making this prediction “accurate.” If I had been doing a consulting gig for an insurance company setting life insurance rates, for example, I would have given far more attention to see precisely what the real data were and incorporated many more variables into the regression model. 

Here’s a link, 

https://www.death-clock.org

by the way, to a more accurate model than the one I used, but it’s still simple to use. Note that my goal was to motivate myself and so I intentionally exaggerated the impact of those behaviors I was trying to change. I had programmed it. I knew how “bogus” the calculation was — nonetheless — here’s the interesting thing though: 

Lessons Learned #4: Even an over-simple model that the user knows is over-simple can still motivate change. 

Photo by Mike on Pexels.com

At last we come to the actual project I worked on — the usability and learnability of Query By Example. One of my colleagues, Moshe Zloof, invented the language for relational data bases. He had designed the language but not yet implemented it. I did not immediately test the design; first, I sought to understand it. In seeking to understand it in depth, prior to testing it, the two of us had some sense-making discussions. Moshe improved the design; in particular, our discussions uncovered some ambiguities and inconsistencies that were not at all obvious when he simply gave talks about the design. This brings me to the next lesson learned which has proven true in nearly every study of early stage designs that I’ve been involved with over the course of six decades.

Lessons Learned #5: Don’t just accept a surface description of something; understand it as deeply as you can before designing a study.  

In this particular case, it was possible for me to understand it in some depth. Relational data bases and second order logic are things I was capable of understanding. If it had been an interface to running a nuclear reactor or using the artificial heart that Moshe had designed earlier in his career, that would have been a much more difficult task for me.

I wanted to understand, not just the “logic” of Query By Example, but also possible contexts of use. For instance, my manager & I visited Burlington, Vermont to talk with IBMer’s who actually used query languages to understand what was happening in chip production lines. At one point, a particular production line that had been producing nearly 100% perfect chips starting having a much higher error rate. Using their query facility, they were quickly able to diagnose the cause of the change which was a supplier of one of the raw materials using a different source. In turn, this meant a slightly different profile of trace impurities in the substrate. Of course, this is only one example, but to me, understanding something in depth means not only understanding its internal logic but also understanding real users, their real tasks, and their context of use. 

Photo by Chokniti Khongchum on Pexels.com

I won’t go into all the details of the pencil & paper study or the results. High School students and then college students were taught the basics of the language and then given a simple relational data base and a set of questions stated in English which they had to translate into Query By Example. Briefly, the bottom line was that Query By Example was easy to learn and easy to use. However, there were still questions that people had difficulty with. In analyzing the data and doing some further experiments, the difficulties that people tended to have, stemmed not so much from Query By Example per se, but from what I much later came to call “labelism” — that is, confusing a label with the thing that label refers to. 

Here’s a simple example of the type of confusion we saw. In Query By Example (and other query languages) there is usually an OR operator and an AND operator. (These operators can be important for doing advanced queries with search engines as well). If you are interested in getting a list of pets you might adopt and you’re willing to adopt dogs or cats, you might ask for “cat OR dog.”  If you only want long-haired cats, you might ask for “cat” AND “long hair.” 

English, however, can be tricky.

If you and I (as opposed to you and a query language) are having a conversation, you might say, “I hear there are many pets that need to be adopted.” 

I say, “Yes, there are all kinds of pets. There are snakes, dogs, turtles, rabbits, cats…” 

You say, “Let me stop you right there. I’m only interested in adopting cats and dogs. Those are the only animals I’d want to adopt.” 

See what you said there? You exact words included: “…cats and dog.” If you put “Cats AND dogs” into a query against the data base of available pets, however, you will get the null set (that is, nothing) back. There are no animals who are both cats and dogs! (Though my part Main Coon cats, Luna and Charles Wallace, can play fetch like dogs). 

When people were presented with an English statement that included the English word “and” — regardless of the actual syntax and context, some of them had difficulty using the OR operator. If instead, the query in English had set up like this: “Oh, I don’t want reptiles. I’d be happy with adopting a cat or a dog, however” then, they’d have no problem translating it into the OR operator in the query language. 

Lessons Learned: #6 Sometimes the difficulty people have in using a product, a service, or a prototype is not due to the interface details but with the structure of the task, their background, and their training.  

By analogy, you will not allow me to beat Carlos Alcaraz or Jannik Sinner at tennis by giving me a better tennis racquet! (Although if you gave one of them a toothpick for a tennis racquet, I might have a shot).

Photo by Isabella Mendes on Pexels.com



That sounds obvious and even absurd, but I promise you, some companies get so greedy that they want you to design a system that allows people who do not understand the task and have minimal background and training to nonetheless be able to perform that task. And, to be fair, it isn’t just the companies who are greedy. They are steered into thinking that they can get away with this absurdity because some outsourcing companies (and more recently, AI companies) tell them they can do it.

One example you may have encountered is having “help desk” personnel who have no understanding of a product go through a script to help you “solve your problem.” Sometimes, it works. But many times it doesn’t. When it does not work, you might not be able to “fix” the system by making the interface to the scripts easier to use for the help desk folks. The problem is much deeper (in some cases). Yes, a really bad interface can make it difficult even for a really knowledgeable and capable person to do the job. But often, even a really great interface cannot always substitute for actual expertise.

——————————————————-

Essays on America: Labelism 

Other posts on problem formulation: 

The Doorbell’s Ringing

Reframing the Problem

I Say Hello

I Went in Seeking Clarity

Who Knows What?

Measure for Measure

Labelism

Destroying Natural Intelligence

Some relevant Books I recommend:

Turing’s Nightmares explores the implications and ethics of Artificial Intelligence through fictional short stories. http://tinyurl.com/hz6dg2d

https://us.macmillan.com/books/9780374619336/enshittification

https://us.macmillan.com/books/9780374621575/thereversecentaursguidetolifeafterai

My Brief Case Runneth Over

03 Thursday Sep 2026

Posted by petersironwood in The Singularity

≈ Leave a comment

Tags

adaptive-systems, AI, Artificial Intelligence, artificial-intellligence, books, chatgpt, cognitive computing, ethics, fiction, law, lawyers, legality, life, music, politics, technology, the singularity, USA, writing

left-right patterns 2

Turing’s Nightmares: Nineteen — My Brief Case Runneth Over

“Nice office, counselor.” Marvin spread his arm to indicate the panorama of Manhattan and Ellis Island. Yet, his attempt to sound casual failed utterly. He realized all too well the depth of trouble he was in and the creakiness in his voice so signaled.

J.B. smiled. “No need to be nervous. After all, we’re here to help. Just answer honestly. Everything you say will typically be covered under attorney client privilege.”

“Okay. Thanks. Typically?”

J.B. sighed. “There is a rare exception in the Patriot Act. Unless you’re some kind of terrorist, I wouldn’t worry about it. The government is apparently accusing you of importing illegal chips is all. I think we can argue that you are new to the business and did not realize all the required legalities. Pay the taxes now and some penalties. You should be able to avoid jail time. But we are getting way ahead of ourselves. Just tell me how and why and when you got into this business in the first place.”

Marvin chuckled slightly and then sighed “That’s a rather long story.” Marvin glanced at the expensive abstract paintings and noted the rich smell of the solid mahogany furniture. The room also had that crazy idea of luxury — making it freezing cold inside just because it was horribly hot and humid that day, even for New York City August. “At your rates…What do you really need to know?”

“Why did you get involved in making chips without the required back door?”

“These chips are not that powerful. At least not in the traditional sense of the word. And, the government’s requirement is frankly kind of silly. The extra logic makes programming more difficult. It increases the chances of errors. The chips are more expensive and require more power. Leaving aside all the valid privacy concerns, there are plenty of applications that can use a more efficient cheaper chip design. No need to report all the little finger twitches of every twelve year old who’s playing Grand Theft Spaceship. What’s the point?”

“Marvin. I’ve been a friend of your family for a long time. When…well…if we go to court and if you testify, please steer clear of politics. The law is the law. You don’t get to decide which applications are immune from the law. No, what we…our script here is that you made some honest mistakes. You made technical mistakes and what are essentially accounting errors.”

Marvin flushed. “What technical mistakes? What are you talking about? My design is an improvement.”

J.B. got up and paced. “Marvin, Marvin, you are a smart boy. We are not going to fight the government on this. Our script as I said is that you made some honest mistakes. If you want to —- the court is not the place to try to change the law. If you want to do that, get involved in politics. But not until after this is resolved. If you get on the stand and start railing about privacy and the dangers of the Sing and…”

“Ha. The Sing indeed. This data collection rampage has nothing to do with trying to increase the intelligence of computer systems. It is just mindless greed.”

“Marvin, the back door requirement is about preventing terrorism; it has nothing to do with greed.”

“Are you serious, J.B.? Terrorism is just the cover story the government uses. They want to collect all this data to keep their sponsors happy.”

“What? What sponsors? What are you talking about? The government doesn’t have sponsors.”

“Of course they do. Ever since ‘Citizens United’ — nice title by the way — billionaires can buy all the media they want. They wash the airwaves and the print media and saturate the social media space and make people believe anything they want. The point of the back door is just to make sure the sponsors keep tabs on everybody’s buying habits —- and to make sure no-one gets too far out of line. How can you not know this?”

“I don’t want to think that way. But at the end of the day, it doesn’t matter what I think. It’s the law. All digital processing chips with more than a peta-flop and …”

“Hold it! Did you say ‘digital’?”

“Huh? Yeah, of course. Isn’t that what we’re talking about? You designed digital processing chips that have no back door and now…”

“No. Maybe not, J.B. My chips are not, strictly speaking, digital.”

“What are you talking about, Marvin? Why? How not digital?”

“In my design process, I strove for something different and more robust. See, here’s the thing. Natural life processes are all…they all have some level of flexibility. They are robust. They are adaptive, I suppose, because every life form that was not flexible or robust died off over the four billion years that life evolved. Something new would come along and every life form that was rigid died. Even physical machines that people make have some flexibility. Metal bends. Wood bends. These materials also compress. They stretch. Not much, but a little. Digital devices do not stand for bending, folding or mutilating. Of course, when people build systems that include IT devices, they try to make the systems flexible. They add error checking; they put humans in the loop; there are all sorts of work-around, but the underlying tech is brittle. It is only flexible in precisely the ways that the designers anticipated it needed to be flexible. I made something that is fundamentally flexible. It is fashioned after life itself. Social systems are flexible. Eco-systems are flexible. Individual animals are flexible. Cell membranes are flexible. Bones are flexible. And so on. This flexibility is fundamental to life and evolution.”

“Okay, Marvin, but life is not infinitely flexible. You cannot just decide to breathe underwater.”

“Of course not! I never said it was infinitely flexible! For fundamental change, you need evolution and lots of time. If the climate changes too quickly, Permian life species largely go extinct. Dinosaurs die when a comet hits. But small adaptations just happen automatically and at every level. It isn’t necessary to have a pre-existing ‘program’ or ‘case’ to handle every contingency that is even slightly outside of what is anticipated.”

“Okay, fine. Granted, but what does this have to do with — did I mention that I charge $500 an hour, by the way?”

“Yes, J.B., you did. And it was in the contract you had me sign. But the point is that my chips are not, strictly speaking, digital at all. They are not strictly EITHER/OR. They are not binary. Although, in many cases, they can behave as binary.”

“So, you want me to claim that these chips are not covered under the back-door provision because they are not really digital devices? I don’t know. That seems pretty shaky to me. Can’t these chips of your be used for the same things as ordinary digital chips? Speech reco. Machine vision. Game control. Big data analytics.”

“Here’s the thing, J.B. Yes, they can, but they can change and evolve and reprogram themselves over time. And, now it occurs to me, that they could not have a real back door. They wouldn’t really function if they did.”

“What? Why?”

“Are you familiar with programmed death in cells? I can see from your blank stare, you aren’t. Anyway, if a cell is damaged within the body, it can wreak all sorts of havoc so the cells are essentially programmed to self-destruct. If that fails, the other healthy cells will tend to wipe out the damaged ones. So, if there were a functioning back door sharing data out of these chips, the chips would shut themselves down. If that failed, other chips in the matrix would isolate them and shut off communication. So, by their very nature, these particular non-digital chips cannot have a functioning back door.”

“That all sounds very clever, Marvin, but now we are talking about a very lengthy and expensive trial with expert witnesses on both sides. If, that is, you are lucky enough to even have an open trial.”

“Lucky enough? What are you talking about, J.B.? I thought you said we wanted to avoid a trial.”

“Yeah. With my strategy where we convince the NSA that this was just technical and business incompetence on your part. But in your scenario, where you want to prove you are all brilliant and everything, then, we will be lucky if —- you will be lucky to —- Look Marvin, I just cannot advise you to take this line of argument. If you really want to go that route, you will have to find a different lawyer.”

“Okay. Fine. I’ll use Solomon.”

“Solomon? Who is ‘Solomon’? Never heard of him. I mean, obviously, I know Solomon from the Bible but what firm are you talking about?”

“No firm, J.B. Solomon is one of the apps we built with my chipset.”

“An AI lawyer? Are you serious?”

“Oh, quite serious. He’s already informed me that he thinks he can win this case.”

“What? That’s preposterous. You told me you just designed the chips a year ago. What kind of experience could this Solomon have?”

“J.B., he’s been reading applicable statutes and case law for the last two months. Which means, he literally knows it all, when it comes to case law and the rulings beneath. Beyond that, Solomon has argued both sides of thousands of hypothetical cases.”

“What?! Ridiculous! But even so, he — or it —cannot possibly know how to anticipate or react to what happens in court!”

“But J.B., haven’t you been listening? Of course he can. He’s flexible, just like a real lawyer. Only…no offense…a lot smarter.”

“Computers cannot be that flexible. Ridiculous. How? No way.”

“Look, J.B., I have a picture to illustrate. See this pattern on the left [Picture at the top of page]? And, there it is on the right?”

“Yeah, beautiful. Same pattern. So what?”

“Ah, that’s just it! Is it the same pattern? Is it the same pattern or the same pattern?”

“Well. One is perfect and the other has little mistakes, but I guess it’s the same pattern.”

“Exactly, J.B. It’s the same basic pattern, but it’s not the identical instantiation of that pattern. Ordinary chips are like the picture on the left and mine are like the picture on the right. You see? And, that flexibility is built in at every level in every system. Because the underlying substrate uses an adaptive process with variations. It works 99% as efficiently as the system on the left, but it can accommodate things we didn’t think of. The difference between the system on the left and the system on the right is hubris. The one on the left is designed under the assumption that the designer knows everything of relevance. The system on the right is designed under the assumption that the designer, no matter how brilliant, does not know everything of relevance. You get it?”

“Yes, Marvin, I’m not stupid. But I am still not going to take your case. And, I strongly advise you not to rely on a robot. I am sorry to say it, Marvin, but I think you have picked on the wrong people this time. Attorney client privilege no longer applies and I have to send my recording of this conversation to the proper authorities.”

“Oh, that won’t be necessary Marvin. I’ve already broadcasts this through the social media. You’re famous! It will be good for your business.”

“What? Are you crazy? They will come get you, you fool.”

“Maybe, but if I am taken out over these chips without a trial, everyone will know, don’t you see? I sent it out everywhere, J.B. I might be ‘disappeared’ but I can’t just disappear unnoticed. Solomon’s idea, by the way.”


Author Page

Welcome, Singularity

Destroying Natural Intelligence

E-Fishiness

Life is a Dance

Life will Find a Way

Math Class

Your Cage is Open

Roar, Ocean, Roar

Dance of Billions

Imagine All the People

Dream Planet

“The Psychology of Design”

22 Wednesday Jul 2026

Posted by petersironwood in creativity, design rationale, HCI, management, politics, psychology, science, Uncategorized, user experience

≈ Leave a comment

Tags

AI, creativity, Design, education, HCI, human factors, IBM, leadership, research, technology, UX

“The Psychology of Design” 

I worked at IBM, all told, about 28 years. During that time, management put increasing pressure on us to make our work “relevant” to the business. In fact, the pressure was always there, even from the beginning. Over the years, however, we were “encouraged” to shorten evermore the time gap between doing the research and having the results of that research impact the bottom line. This was not an IBM-only phenomenon. 

I was a researcher, not a politician, but it seemed to me that at the same time researchers in industrial labs were put under pressure to produce results that could be seen in terms of share price (and therefore payouts to executives in terms of stock options), academia was also experiencing more and more pressure to publish more studies more quickly — and to make sure “intellectual property” was protected to make sure the university could monetize your work. This was about the same time that, at least in America, increasing productivity and the wealth that sprung from that increased productivity stopped being shared between the workers and the owners.

Photo by Dmitry Demidov on Pexels.com

In the late 1970’s, the “Behavioral Sciences” group at IBM Research began to study the “psychology of design.” For the first few months, this was an extremely pleasurable & productive group, due mainly to  my colleagues. Over the next few blogs, I’ll focus on some specific techniques and methods that you may find useful in your own work. 

In this short recounting though, I want to focus instead on some broader issues relevant to “technology transfer”, “leadership” and “management.” Even if you are or aspire to be an expert in UX or HCI or design, I assure you that these broader issues will impact you, your work and your career. I wouldn’t suggest becoming obsessed with them, but being aware of their potential impact could help you in your own work and career. 

It is telling that, almost invariably, whenever I told someone inside IBM (or, for that matter, outside IBM) that I was studying the “psychology of design,” people responded by asking, “the design of what?” So, I would explain that we were interested in the generic processes of design and how to improve them. I would explain that we were interested in understanding, predicting, and controlling these processes to enable them to be more effective. I would explain that we could apply these findings to any kind of design: software design, hardware design, organizational design, and (see last post about IBM) communication design. I would explain that design was a quintessentially human activity. I would also explain that design was an incredibly leveraged activity to improve. 

Looking back on it, I still think all these things are true. I also see that I missed the “signal” people were giving me that, while I thought of design as something that could be studied as a process, that most people did not think of it that way. To them, it was never the “psychology of design,” but only the design of something. 

Don’t get me wrong. I agree that somewhat different skills are involved in designing a great advertising campaign, a great building, and a great application. I agree that different communities of practice treat various common issues differently. I still think it’s worth studying commonalities across domains. For one thing, we may find an excellent way of generating ideas, say, that the advertising community of practice uses that neither architects nor applications developers had ever tried. Or, vice versa.

My own academic background was in “Experimental Psychology.” We were forever doing experiments that we believed were about psychological processes that were thought to be invariant regardless of the domain. It was an axiom of our whole enterprise that studying memory for any one thing also shed light on how we remember every other thing. Similar studies looked at decision making or problem solving or multi-tasking. We came to understand that there were some interesting exceptions to being able to separate content from process. For instance, it is much easier to multi-task a spatial task and a verbal task than it is to multi-task two independent spatial tasks or two independent verbal tasks. 

In our Behavioral Sciences lab, we used a spectrum of techniques to study “design” ranging from laboratory studies of toy problems, to observing people doing real-world design problems while thinking aloud. After about 3-4 months of very productive work, we were told that we had to make our work relevant to software development. That one domain should be the focus of our work. We were told that this command came from higher-ups in IBM. That might have been true, or perhaps partly true. 

It might also be relevant that someone in our management chain might have been the recipient of a grant from ONR which was specifically focused on software development. So far as I can tell, nothing had been done on that grant. So, our past, present, and future work could have been co-opted to be “results” done under the auspices of the ONR grant. 

In any case, regardless of the “reasons,” the group began to focus specifically on software design. In one study, we used IBM software experts as subjects. Each person was given information that was geared toward a specific transformation that occurred in software development. One person was presented with the description of a “situation” that included a number of “issues” and they were asked to write a requirements document. In real life, I would hope that this would be done in a dialogue (and, indeed, in other studies, we recorded such dialogues). Absent such dialogues, what we found was that different software experts — all from IBM research — and all given the same documentation about a set of problems generated vastly different problem statements and overall approaches. 

Photo by ELEVATE on Pexels.com

In other parts of the study, other experts were variously given requirements documents and asked to do an overall, high level system design, or given a high level design and asked to design an algorithm, or given an algorithm and asked to code a section. There was always diversity but the initial phases showed the greatest diversity of behavior. The initial stage is also the one that can cause the most expensive errors. If you begin with a faulty set of requirements — a misreading about how to even go about the problem — then, the overall project is almost certain to incur schedule slip, cost overruns, or outright failure. 

While the vital importance of the initial stages of design is true in software development, I would argue that it is likely also true for advertising campaigns, building designs — and even true for the design of research programs. We designed our research agenda under the assumption that we had a long time; that we were studying design processes independently of specific communities of practice or the nature of the problems people were attempting to address. We assumed that there was no “hidden agenda.” Although we believed we would eventually need to show some relevance to IBM business, we had no idea, when we began, that only relevance to software design would be “counted.”



—————-

Some of our studies on the “Psychology of Design.” 

Carroll, J. and Thomas, J.C. (1982). Metaphor and the cognitive representation of computer systems. IEEE Transactions on Man, Systems, and Cybernetics., SMC-12 (2), pp. 107-116.

Thomas, J.C. and Carroll, J. (1981). Human factors in communication. IBM Systems Journal, 20 (2), pp. 237-263.

Thomas, J.C. (1980). The computer as an active communication medium. Invited paper, Association for Computational Linguistics, Philadelphia, June 1980. Proceedings of the 18th Annual Meeting of the Association for Computational Linguistics., pp. 83-86.

Malhotra, A., Thomas, J.C. and Miller, L. (1980). Cognitive processes in design. International Journal of Man-Machine Studies, 12, pp. 119-140.

Carroll, J., Thomas, J.C. and Malhotra, A. (1980). Presentation and representation in design problem solving. British Journal of Psychology/,71 (1), pp. 143-155.

Carroll, J., Thomas, J.C. and Malhotra, A. (1979). A clinical-experimental analysis of design problem solving. Design Studies, 1 (2), pp. 84-92.

Thomas, J.C. (1978). A design-interpretation analysis of natural English. International Journal of Man-Machine Studies, 10, pp. 651-668.

Thomas, J.C. and Carroll, J. (1978). The psychological study of design. Design Studies, 1 (1), pp. 5-11.

Miller, L.A. and Thomas, J.C. (1977). Behavioral issues in the use of interactive systems: Part I. General issues. International Journal of Man-Machine Studies, 9 (5), pp. 509-536.

——————————

Blog posts about the importance of solving the “right” problem. 

The Doorbell’s Ringing. Can you get it?

https://petersironwood.com/2021/01/13/reframing-the-problem-paperwork-working-paper/

Problem Framing. Good Point. 

https://petersironwood.com/2021/01/16/i-say-hello-you-say-what-city-please/

Problem formulation: Who knows what. 

How to frame your own hamster wheel.

The slow seeming snapping turtle. 

Author Page on Amazon. 

Walston & Felix Multiple Regression Study

17 Friday Jul 2026

Posted by petersironwood in creativity, design rationale, leadership, management, psychology, Uncategorized

≈ 1 Comment

Tags

art, books, development, HCI, IT, productivity, programming, regression, software, technology, UX, writing

As I mentioned recently, when I first arrived at IBM Research in the early 1970’s I began to work on Query By Example and other schemes to make it easier for non-programmers to interact productively but flexibly with computers. Some of the lessons learned have to do, not with my own work, but with the work of others. 

At that time, some researchers labelled their work as “The Psychology of Programming.” There were many debates — and some studies — about structures, syntax, which language was better than others, etc. There were also lengthy discussions about the process that one should use for software development. Doing any kind of “controlled” experiment on large scale code development is prohibitively expensive. It is rare that a company is willing to have two independent teams build the same piece of software in order to learn which of two methods is “better.” 

Of course, one such comparison would likely not prove much. It may be that one of the two teams had a “super-programmer” or an extremely good manager. Perhaps, flu broke out in one of the two teams. You would really need to study many more than two teams to properly and empirically study the impact of language, or syntax, or process. Doing reasonable-sized experiments would be far too costly and impractical. Our lab and others did do laboratory tasks in order to test one syntax variant against another and so on. The problems were generally quite small in order for the study to be practical. So, the applicability to real-world development projects was questionable.

Photo by Christina Morillo on Pexels.com

Walston & Felix (See below), on the other hand, were able to find data on a fair number of real-world projects and rather than try to control for languages, processes, etc., they did a multiple regression analysis based on what languages, methods, etc. real projects used and what the important predictors were of actual productivity. 

Personally, I learned two lessons from their study. 

Lessons Learned: #1 — Sometimes, when it comes to what matters in the real world, controlled laboratory experiments have to give way to other methods such as studying “natural experiments.” Despite the many issues with trying to interpret such findings, no-one will pay for massive controlled experiments that parametrically vary programming methods, programming languages, etc. while controlling for quality of management, experience, complexity of task, etc. Multiple regression studies and in-depth case studies; ethnographic studies; interviews: all of these can provide useful input. 

OLYMPUS DIGITAL CAMERA

Lessons Learned: #2 — The impact of the variables that our community of people were looking at in terms of syntax, structure, etc. were dwarfed by the impact of organizational variables. For example, Walston & Felix found that the complexity of the interface between the developers and the customers was extremely important.

DeMarco & Lister (See below) claim that, based on their decades of experience as consultants to the software development process, projects almost never fail for technical reasons; when they do fail, it’s almost always for organizational and management reasons.  

That conclusion dovetails with my own experience. Many decades later, working for IBM in “knowledge management,” it was amazing how many companies wanted us to “solve” their knowledge management issues by building them a “system” for knowledge sharing.

But…

Management at the company would not provide:

Incentives to share knowledge

Space to share knowledge

Time to share knowledge 

Or, commit any personnel to gathering, vetting, organizing, and promoting the knowledge repository. 

So — knowledge sharing was something their workers were simply supposed to “do” knowledge sharing on top of everything else they were doing. 

They did not want a computer system, IMHO; they wanted a magic system. 

Photo by David Cassolato on Pexels.com

These experiences were part of my motivation for attempting to catalog “best practices” in collaboration and teamwork in the form of a Pattern Language. Christopher Alexander and his colleagues looked at “what worked” in various parts of the world when it came to architecture and city planning. What they did for architecture and city planning, I want to do for collaboration. 

Naturally, merely creating a catalog is not sufficient. I need to have people who will read it, understand it, modify and improve it, and then promulgate it via actual use. For now, it’s free. Comments and critiques are always welcome.

—————-

C. E. Walston and C. P. Felix, “A method of Programming Measurement and Estimation,” IBM Systems Journal, vol. 16, no. 1, pp. 54–73, 1977.

https://en.wikipedia.org/wiki/Peopleware:_Productive_Projects_and_Teams

Thomas, J.(2008).  Fun at work: Managing HCI from a Peopleware perspective. HCI Remixed. D. McDonald & T. Erickson (Eds.), Cambridge, MA: MIT Press.

——————-

Introduction to a Pattern Language for Collaboration and Teamwork 

Index to a Pattern Language for Collaboration and Teamwork

Chain Saws Make the Best Hair Clippers 

Author Page on Amazon

“Wizard of Oz”

15 Wednesday Jul 2026

Posted by petersironwood in AI, apocalypse, design rationale, HCI, leadership, management, politics, psychology, The Singularity, Uncategorized, user experience

≈ Leave a comment

Tags

AI, HCI, IBM, research, technology, usability, UX, Wizard of Oz, writing

(Some Lessons Learned from studies in Human-Computer Interaction/User Experience conducted at IBM Research in the mid-70’s.)

Photo by Johannes Plenio on Pexels.com

Wizard of Oz 

One of the studies I conducted at IBM Research in the mid 1970’s was part of an effort to do “Automatic Programming” — a department under Pat Goldberg. The first level manager I worked with was Irving Wladawsky (later Irving Wladawsky-Berger). His group wanted to develop a system that would allow the owner/operator of a small business to type requirements into a computer in English (or something English-like) and have the system itself produce RPG code to run the business so described. 

The underlying motivation from an IBM business perspective was that many small businesses could well afford a computer to do inventory, fulfill orders, etc. but they couldn’t afford to hire programmers to create such a system from scratch. The small business owner in the mid-1970’s did not program! Yet, for the most part, they understood how their business worked. The notion was that a natural language understanding and generation program could dialogue with the user/owner and through that process, understand their “business rules.” No costly programmers needed!

Photo by Dmitry Demidov on Pexels.com



An interesting side note: at that time, we were told that IBM corporate forbade us to use the terms “Artificial Intelligence” or “Robotics” to describe our work because some PR firm had determined that these terms were too scary for the general public. So, IBM had research in “mechanical assembly” but not “robotics.” We had work in character recognition, speech recognition, handwriting recognition, automatic program generation, and compiler optimization. But no work in “Artificial Intelligence.” (Wink, wink, nod, nod). 

Labelism: Confusing a thing with the label for that thing.

Another interesting side note: I worked at IBM Research for a dozen years; started an AI lab at NYNEX where I worked another 13 years; came back to IBM Research and several years later found myself working on the same problem! We were still trying to make a system to allow small businesses to generate their code automatically. In my second iteration, rather than using natural language, we were trying to make the specification of business rules in a graph language that was intuitive enough for business owners. This was a different approach, but trying to address the same underlying desire: to bring computing to small business without incurring the heavy costs of programming and maintenance. 

Let’s return to iteration one — the natural language approach @ 1975. Well, one issue was that no-one had a natural language program that even approximated being able to do the job. So…how to study people’s interaction with a system that doesn’t exist? 

We used an approach that my colleague Jeff Kelly called the “Wizard of Oz” technique; viz., use a human being (in this case, me) to simulate how the system might work and record people’s behavior. In this way, we could discover many of the issues that such a natural language programming system would have to deal with. I had already had plenty of experience interacting with a computer; and I had acting experience. I could “play the part” of a computer fairly well as I typed in my questions and answers. 

(Description of “The Wizard of Oz” technique).

IBM Research in Yorktown had roughly a thousand people including not only scientists, programmers, and engineers but also a number of business people (who did not know how to program). I knew some of them from playing tennis and table tennis and we used those folks as initial subjects. What did I find? Good news and bad news. 

Dealing with natural language is tricky for many reasons. One of those reasons is that English, including the English that people normally use to describe their business, is filled with words that have multiple meanings; e.g., “file”, “run”, “program”, “object”, “table”, etc. But here is the good news: although it’s true that many English words have many meanings, when these business people described business procedures, almost all of the lexical ambiguity vanished! The program to understand business English would not have to distinguish between a business file and a nail file; it wouldn’t have to worry about distinguishing a run in baseball or a run in stockings from a run of the payroll program; it wouldn’t have to distinguish between the table in a relational data base and the table in your dining room. The domain would mainly constrain! That’s the good news.

The bad news was dialogue management. How can the machine recognize a misunderstanding and how can it correct it? To make matters worse, while business people were fairly consistent in the way they described how their business ran, they were not consistent in how they talked about the communication. If a human being senses that another one is misunderstanding, then, depending on context they might: raise their eyebrows, say “Huh?”, “Come again?”, “What?” “I think I lost you.” “WTF?” “Are you kidding?”, “We’re on different wavelengths,” “I don’t get it.” “But…wait.” 

Photo by Nafis Abman on Pexels.com

Sometimes, these are referred to as “meta-comments.” Here’s a simple example that took place in the study. 

One of the business people told me about various discounts. I had assumed (playing the part of the computer) that he was talking about discounts for items that were being discounted due to inventory management. I recorded all the various percentages and so on. Then, he said, “Now, we also give discounts for various items.” 

At that time, most natural language systems of that era simply ignored words like “now” and “also” in this context. Stepping out of my role as a “computer system” and thinking about from the perspective of a human conversational partner though, these words are crucial! What it signals is a change in topic. In the larger context of our conversation, it shows that everything that had just been said, which I thought had been about item discounts, was not about item discounts!

This is just one example, but there were many more. In my more recent experience interacting with various computer dialogue systems, being able to recognize the signals of miscommunication and being able to repair misunderstandings is still not very well-handled more than four decades later.

I’d be interested in any pointers you have to a system that you think deals with meta-communication in a natural and robust manner. I do not think that it is beyond the pale of possibility. The general categories of the ways that people misunderstand each other is not infinite. John Anderson developed excellent tutoring systems for LISP and geometry and those systems worked something like human tutors in that, the tutor inferred the mental model of an individual student and focused instruction on correcting any misconceptions. My intuition is that a generic system built with equal complexity could deal with most of the issues as well as the average human being deals with them; i.e., imperfectly. 

—————————————

Lessons Learned: #1 You can test aspects of a system even before it’s built or even completely defined. One method that has been used many times: “Wizard of Oz.” 

Lessons Learned #2: Language used by professionals to talk about their domain is much more constrained in terms of lexical ambiguity than is language when considered by all native speakers.

Lessons Learned #3: People in “our culture” (i.e., US business culture) do not have an agreed upon and consistent vocabulary for talking about communication nor a consistent process for dealing with them.

Lessons Learned #4: Speaking of communication errors, I don’t recall why, but it was about this time, that I realized that my notion about how research results would be transferred to other parts of IBM was a complete and utter fantasy. I hadn’t articulated it, but it was basically that I would do research, write the results up for publication in scientific journals for an academic audience and publish Research Reports which would be eagerly consumed by anyone who needed to know. I’m not proud of this. LOL. But that’s really kind of how I viewed it. And, then, after a few years, I realized that it really mainly came about through relationships. That was something that people had been showing me all my life, but which I don’t think anyone ever stated it explicitly enough.

Update for 2026: While the four “Lessons Learned” above still seem apropos, some of today’s chatbots such as ChatGPT and Claude are much better at dealing with connected conversations with humans that were the systems of the twentieth century. Not only that, people are now describing systems in “natural language” and the computer is writing code. That’s the “good news” I suppose.

The bad news? While my impression of most of the AI researchers of the twentieth century is that they were largely motivated by intellectual challenges and a desire to help make people more productive, I get the impression that most of the AI work of today is controlled by people who are already astoundingly wealthy and want to become even wealthier. And, as UN-laudable as we may view that goal, the wealth is only a means to an end and that end is the total enslavement of most of humanity. Even being a trillionaire isn’t enough.

That’s not to say that all the workers advancing AI have those nefarious aims just because those in charge do, but as the surveillance state becomes more pervasive, their private motivations could have less influence over the outcomes.

———————————-

Author Page on Amazon

The Myths of the Veritas (an exploration of leadership & ethics in free, no ads fiction)

Index to a Pattern Language for Collaboration and Teamwork

Experiences in Human-Computer Interaction

Post on “The Story of Story” 

The After Times

After All

When Greed is the only Creed

Destroying Natural Intelligence

“Turing’s Nightmares” comprises 23 Sci-Fi short stories that explore the implications and ethics of AI

Here is an example chapter from “Turing’s Nightmares” that explores a possible dilemma of working in AI.

To Be or Not To Be

← Older posts

Subscribe

  • Entries (RSS)
  • Comments (RSS)

Archives

  • November 2026
  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • June 2026
  • May 2026
  • April 2026
  • March 2026
  • February 2026
  • January 2026
  • December 2025
  • November 2025
  • October 2025
  • September 2025
  • August 2025
  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • July 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • August 2023
  • July 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • May 2015
  • January 2015
  • July 2014
  • January 2014
  • December 2013
  • November 2013

Categories

  • AI
  • America
  • apocalypse
  • cats
  • COVID-19
  • creativity
  • design rationale
  • dogs
  • driverless cars
  • essay
    • guns
  • family
  • fantasy
  • fiction
  • HCI
  • health
  • leadership
  • love
  • management
  • nature
  • pets
  • poetry
  • politics
  • psychology
  • Sadie
  • satire
  • science
  • sports
  • story
  • The Singularity
  • Travel
  • Uncategorized
  • user experience
  • Veritas
  • Walkabout Diaries

Meta

  • Create account
  • Log in

Blog at WordPress.com.

  • Subscribe Subscribed
    petersironwood
    Join 644 other subscribers

    Have a WordPress.com account? Log in now.

  • petersironwood
    View site in Reader
    Manage subscriptionsSign upLog in
    Report this content
    Collapse this bar
Loading Comments...