Tag Archives: collaboration

The Day From Hell: Why Does Anyone Care? 

05 Tuesday Jun 2018

Posted by in America, management, psychology, Uncategorized

≈ 15 Comments

Tags

, , , , , , , , , ,

The Day From Hell: Why Does Anyone Care? 

apple applications apps cell phone

Photo by Tracy Le Blanc on Pexels.com

I oversleep. The alarm did not go off and it feels late. I glance at my watch and sure enough, I’m late. I grab my iPhone to see whether I forgot to set it. Nothing works. I cannot even turn it on or reboot it. I’ll have to deal with it later. I will be late for my tennis match or have to skip breakfast. I decide to compromise and just grab a protein shake out of the fridge. Something’s wrong. It’s not cold. In fact, the refrigerator is not cold at all. Nor did the light go on when I opened the door. I try the kitchen lights. Nothing. Power is off throughout the house. I’m sure the bill was paid on time. I’ll deal after tennis. 

assorted trophies

Photo by Francesco Paggiaro on Pexels.com

I arrive at the court for my doubles match. The other three are already there. John says, “You’re late. We’ve decided we’re playing you.” 

“What? Very funny. Yeah, I’m good but not that good.” 

“No, it’s not a joke. We’re tired of losing. The three of us will stand you.” John’s face is deadpan. I look at the others and there is no sign of japery anywhere. 

“Well…that makes no sense whatever. Sorry I’m late. My phone alarm isn’t working. In fact, my phone isn’t working at all. But I’m sure this isn’t April First. How about if Tom and I take you two on?” 

“No. We’ve decided we’ll take you on.” 

I think that sounds crazy but whatever. I’ll call their bluff. At least I’ll get a lot of exercise! “Fine,” I say, “let’s just warm up for a few minutes.” 

“No. No warm-up. We’re already warmed up,” explains Tom.

“OK, fine. Just go ahead and serve.” 

“No, you have first serve,” says Larry. 

I quickly unsheathe my racquet and walk to the baseline, one ball in each pocket and one in my left hand. I position myself near the middle. It looks really weird to look across the net and see all three of them positioned there. “First in?” I query. 

“No,” they sing out in unison. “Serve it in.” 

“What is this joke, guys?” 

“No joke. Just serve.” 

“Fine.” I think to myself, I will play along till the joke gets old. Since I’m not warmed up, I just hit an easy serve into the middle of the box to start the point. 

“OUT!” shouts Tom, who generally makes fair calls. 

“WHAT?! That was in the middle of the box! It wasn’t even close to the line! Enough’s enough.” 

“Our call,” says Larry. 

“Yeah, it’s your call, but come on. You all know that was well in.” 

Our debate, if you can call it that, is interrupted by screaming tires and a loud crash coming from the nearby street. “What the hell was that?” 

No-one reacts or answers my question. Larry says, “Second serve.” 

I shake my head. “Guys. We should go up there and see if anyone needs to call 911. I mean, it would have to be one of you. My phone doesn’t work.”

Don, still with a bland, blank look on his face says, “None of the phones work. That was just a car crash. Probably intentional. Let’s just play.” 

I know I am not dreaming. But what is going on? “You seriously think someone crashed their car on purpose? What is with you guys this morning?” 

“Yeah,” says Larry. “It’s been going on all morning. Let’s just play. Second serve. Wait. Tom! Come over here. I want to play deuce court.” 

“No way,” says Tom. “I’m already here.” 

Larry wields his racquet above his head and charges at Tom. In seconds, they are both bleeding profusely and keep swinging at each other. Don joins in the fray. They are completely oblivious to my shouts so I pick up my stuff and head for the clubhouse to call for help. Maybe someone put some kind of drug in the water? Just then, another screech of breaks, squeal of tires and a loud crash. Another car crash? 

red and yellow hatchback axa crash tests

Photo by Pixabay on Pexels.com

By now, I am jogging through the parking lot toward the front desk at the tennis club. Something is terribly wrong. It all looks wrong. Then, I notice that virtually none of the cars are parked inside the white lines meant to indicate parking spaces. Some appear to have been left in the drive. Several are on the grass and one is in the flower bed near the gym. Many of the cars have smashed windshields.  

Collaboration? Cooperation? Teamwork? Who cares? 

I am very grateful for readers and commenters on my blog. Since the beginning of the year, I’ve been cataloging “best practices” in collaboration and teamwork in the form of Patterns. I think it may be time to “take stock” and make it clear why I am doing this, in case it isn’t obvious. 

I don’t “own” these Patterns. I don’t get any money from people using them. Why should I care whether people do a good job or a horrible job at collaborating? And, isn’t life all about competition anyway? 

IMG_9850

There was a time, not so long ago, that I really didn’t think it would be necessary to “explain” why it was important to cooperate. There was a time, not so long ago, when I thought most people knew that life was not all about competition. But lately, so-called “civil society” has been so rife with uncivil words and actions, at least in the “United” States, that I think it’s time to re-iterate why cooperation is vital. I also want to point out that, while there is certainly competition in life, there is also cooperation. 

Why all of life is not competition. 

In the natural life of animals and plants, there are, for some species, some specific times and places for competition. That is true. And, some of those competitions can be pretty fierce; e.g., antler-smashing bucks competing for mates. And, you could say that the rabbit eats a plant and that the coyote eats the rabbit. But there are far more ways that plants and animals cooperate. 

adult and cub tiger on snowfield near bare trees

Photo by Pixabay on Pexels.com

First, plants and animals participate in the recycling of material. Generally, plants gain energy from sunlight, and put some of that energy into compounds that are high energy and fit for consumption by some animals. In the process, plants also take carbon dioxide out of the air and replace it with oxygen. Animals breathe in oxygen and breathe out carbon dioxide. Animals eliminate “wastes” from their food and that “waste” replenishes nitrogen and minerals into the soil. Plants use the nitrogen and minerals. And, when animals and plants die, their bodies further enrich the soil for plants. 

Cooperation within the great tree of life doesn’t stop there, however. Flowering plants often cooperate with each other and with bees to flower so that there is a more or less a constant supply of pollen. Sucker fish take parasites off large fish. Butterflies collaborate with flowering plants. Rabbits collaborate with berry bushes. When there is danger, many animals and birds cry in such a way as to warn others. 

Let’s move on to consider what cooperation means for human beings. A single human being, however smart, will die soon after birth without the aid of more adult human beings. Apart from providing physical needs for the infant such as food and water, older humans immediately begin teaching the infant and then the child much of what he or she needs to know in order to survive. People have typically hunted, gathered, and prepared food in cooperative groups. People build shelters together. Cooperation among human beings has become more wide-spread and more complex over time. Most of the people in the so-called civilized world now rely on complex supply chains for food, water, clothing, electricity, security and learning. Dancing, playing music, playing sports, business, government — all of these activities depend on cooperation. 

photography of people stacking hands together

Photo by rawpixel.com on Pexels.com

Cooperation and competition in sports. 

Right now, the French Open tennis tournament is going on in Paris. The competitive spirit of the players is amazing! In some of the matches, shot after shot looks like a sure winner – only to be returned with another difficult-to-return shot. The players push themselves mentally and physically to the very limit and sometimes beyond. They are indeed fierce competitors.

But guess what? They follow the rules. And they show sportsmanship. No-one arranges to secretly injure another player or sabotage their racquet. The players cooperate to compete. After many of the most savage hard fought contests, the contestants often fall in each other’s arms. 

IMG_2818

In life, there is both competition and cooperation. In a world of 7 billion people, cooperation is more important than ever. In a world that relies on international supply chains and agreements and laws, cooperation is more important than ever before. In a world with nuclear, biological, and chemical weapons, cooperation trumps competition. The natural world has never been a zero-sum game; it has never been a fixed pie. Look around! Life has covered the planet largely through cooperation. To solve problems such as global climate change and the plastification of our oceans, we need widespread and effective cooperation more than ever. Of course, there is a role for competition as well. But competition is only fruitful within the bounds of cooperative frameworks. If we try to run this world under a non-cooperative and purely competitive framework, we will guarantee our own extinction. I had thought that was obvious to everyone, but apparently it isn’t. 

That’s why I’m trying to catalog best practices in collaboration and teamwork. 

————————-

Examples of cooperation: 

http://nectunt.bifi.es/to-learn-more-overview/cooperation-in-animals-ants-case/

https://listverse.com/2015/02/23/10-amazing-cooperations-between-different-animal-species/

http://vetsci.co.uk/2011/05/16/cooperation-between-species/#

https://epdf.tips/making-democracy-work-civic-traditions-in-modern-italy.html

Putnam, Robert D. (2000). Bowling Alone: The Collapse and Revival of American Community. New York: Simon & Schuster. ISBN 0-7432-0304-6.

—————————

Author Page on Amazon. 

Use Diversity as a Resource

31 Thursday May 2018

Posted by in management, psychology, Uncategorized

≈ 6 Comments

Tags

, , , , , , , , ,

Use Diversity as a Resource

IMG_9333

Prolog/Acknowledgement/History: 

On the one hand, I’ve always been fascinated with biology. If you learn or recall even a little about biology, you’ll know that diversity is a fundamental aspect of life. Life repeats patterns. But it balances that repetition with variation and diversity. 

At the same time, I’ve found it much more interesting in nearly every aspect of life to seek some substantial level of variety rather than constancy. That includes everything from flowers to fields of study to people to interact with. My “favorite color” is blue. But the last thing I want is to see only my favorite shade of blue. That is, after all, equivalent to being blind. While I love eating cashews, it would be hell to have only them for every meal. 

My first job after grad school was managing a project on the “Psychology of Aging” at Harvard Med School. We focused on such tasks as reaction time and memory but I also looked into adjacent fields; for example, it was clear that “ageism,” as well as sexism and racism, was alive and kicking. True enough, there are general trends of age-related slowing and memory issues, but there are several caveats. First of all, there is huge variability within an age group. In our studies of generally healthy veterans from their 20’s to 70’s, the differences within an age group were about 2.5 x as large (roughly speaking) as the overall age-related changes that we saw. The fastest individual in the whole study of several hundred people was not in their 20’s nor in their 30’s. In fact, it was a 55-year old school superintendent who raced motorcycles cross-country on the weekend. The effect of the way various tasks were constructed was far more important than individual differences. In over-simple but basically accurate terms, age is a weak variable when it comes to “mental performance,” individual differences are a moderate variable and the conditions of the tasks are strong variables. In my experience, having individuals with a diversity of ages produces better results. (Relevant studies of aging, not empirical proof of the immediately previous statement: 9, 10, 22, 28, 31, 37 in references below). 

portrait promenade la nature homme

Photo by hermaion on Pexels.com

When I started the Artificial Intelligence Lab at NYNEX, I learned something of the history of the phone company including the fact that the telephone was invented to try to help people with special needs (in this case, hearing loss). There are many other cases where inventions that are of great use to huge numbers of people were first inspired by trying to aid those with special needs. Already aware of the possible enrichment of the field of human-computer interaction by making it more accessible to people outside of Western Europe and North America, I helped organize and run workshops on “cross-cultural issues in HCI” and as I met people from different cultures, I became even more convinced that diversity offered a resource for innovation and excellence. (Reports on a few of these activities: 2, 8, 32, 33, 36).

OLYMPUS DIGITAL CAMERA

Working with people in other cultures or people with special needs, in my experience, provides a much greater wealth of possibilities than sticking with only one. (Some studies of relevance that I have been personally involved with: 11, 15, 16, 27, 30, 35, 38, 39, 40, 41).

Excellent arguments have been made by many as to why supporting diversity is the ethical thing to do and I quite agree with those arguments. Here, however, I am not making an argument on the basis of what is right; I am merely claiming that it is in everyone’s interest to support diversity and use it as a resource for creativity and innovation. 

Author, reviewer and revision dates: 

Created by John C. Thomas in May, 2018 

 

Related Patterns: 

Who Speaks for Wolf?, Build from Common Ground.

Abstract: 

Human societies have widely different customs about what is appropriate behavior. As people grow up in a culture, they generally learn one (or, more rarely two) ways to dress, eat, speak, walk, and so on. Diverse groups of people, regardless of how that diversity arises, will have a wider range of skills, experiences, perspectives, and attitudes to apply to solving a problem. This diversity is a resource that can help throughout problem solving to improve the chances of solving a problem, generating a good design, or resolving an issue. Therefore, when faced with a problematic situation, improve your chances of success by bringing to bear diversity on the problem. 

Context: 

Cultures developed separately in many places around the world. Partly to adapt to specific conditions and partly by accident, these cultures developed different cultural practices. In addition, humans, like every other living species, exhibits diversity on thousands of dimensions even at birth. Beyond that, people are further influenced to develop differently based on their families of origin and their peer groups. These differences are critical in having allowed us to develop a complex, highly interconnected society of many specialists. People can become incredibly skilled at tennis or playing the piano or writing poetry or programming in LISP or fixing plumbing problems or planting trees or hunting or cooking, to name a few of the thousands of specialities that now exist. Everyone doesn’t have to do every single task for themselves. If we did, we would all be moderately good at the same relatively small set of skills. Instead, we can mainly rely on others who are extremely good at doing what they do and trade the fruits of our labors at what we are expert at for the fruits of their labors. 

All these differences mean that it often takes slightly longer to find and work from common ground; to understand each other, than it might if everyone were born and raised identically. 

Many of us live in societies that push for the fastest possible answer, solution, design, or resolution. There is an absurd push toward speed at the expense of quality. This tends to make people impatient to “just get on with it” by which they actually mean, “just get on with it the way I want to do it.” 

IMG_2480

Problem: 

When people push to the fastest possible solution, it tends to compromise quality in every way. One of the most important ways it compromises quality is that it pushes people not to consider a large variety of ideas but instead to pick the first one or two that come to mind. Generally, the first few ideas that come to mind are not original in any significant way. The ideas will be largely deployed or implicit in the dominant culture already. There will be very few real innovations. 

There is another problem with such an approach. Whatever the “answer” is, it will typically not appeal to everyone or even be in everyone’s interest. As a result, a design will fail to gain the widest possible audience and may instigate a backlash among those whose needs are not being met or whose needs are actually being subverted. 

In a fairly homogeneous group, it is very likely that some vital aspects of the problem or situation will be overlooked. A solution will be derived based on limited data and then marketed based on limited appeal. This failure will be surprising to the homogeneous group because they are only looking at it from one perspective; viz., their own. 

Forces:

  • Diversity of background leads to diversity of experiences.
  • The expectations of any one person are primarily based on their own past experiences.
  • The behavior of any other person is largely based on that person’s past experiences. 
  • People in fairly homogeneous groups tend to focus on their similarities rather than their differences; in some cases, they may even denigrate or make fun of other groups. 
  • Fairly homogeneous groups who focus on their similarities will further reduce the space of possible ideas to ones that are shared by the entire group. In other words, the group will work within the constraints of the intersection of their experiences rather than the union of their experiences. 
  • Ideas and approaches that appeal to those in a fairly homogeneous group will engender a false sense of universality of the appeal. It is easy to believe that the idea will be liked by everyone as much as it is by this particular group.  
  • The same unconscious close-mindedness that prevents the fairly homogenous group from generating very innovative ideas will also make it very difficult to accurately diagnose the real source of the failure.  
  • People in a diverse group will provide that group with an initial set of ideas that is far larger than the set of ideas generated by a homogeneous group. 
  • Moreover, people in a diverse group, if they see diversity as a resource, will tend to more often work from the union of their ideas than limiting themselves only to the intersection of their ideas and experiences.   
  • Ideas can play off against each other and produce still other new ideas. Thus, the diverse group who views their diversity as a strength will start off with a larger pool of ideas; will produce still more “recombinant” new ideas; and will more likely allow a look at the large space formed by the union of ideas rather than being limited by the intersection. 
  • Moreover, people in a diverse group will not only be more likely to produce an innovative service, product, or solution; they will also be more able to see how to market the idea, or specialize it, or localize it to any population represented within the group.    

Solution: 

When facing any particularly challenging situation, try to construct a highly diverse group of people to face that challenge. Respect and learn from each other’s differences. Focus on your diversity as a resource to be capitalized on rather than a handicap to be overcome. 

IMG_9325

 

Examples: 

  1. Artists as diverse as Frank Lloyd Wright, Vincent Van Gogh, and The Beatles intentionally allowed themselves to be exposed to Asian versions of their art in order to enhance and extend their own styles.

2. High level chefs who specialize in a particular type of cuisine may also become conversant in other types of cuisine to expand the palette of tastes from which to select. 

3. In problem solving, it often happens that the representation a person uses can have a huge impact on how easy a problem is to solve. Similarly, different things are often better said in different languages.  Even when it comes to advances in an entire field, they often follow new ways of representing things. For example, understanding human speech began making much more progress once the sonogram (which shows time on the X-axis, frequency on the Y-axis and amplitude as darkness) came into use as a representation (rather than the earlier representation of a speech waveform with time on the X-axis and amplitude on the Y-axis). Modern medicine today relies on many kinds of “scans” – not just X-rays, though X-rays certainly allowed a big advance over guesswork. (Studies indicating the importance of representation: 1, 3, 4, 5, 6, 13, 18, 19, 20, 23, 24, 25, 26).  

Resulting Context:

Generally speaking, when diverse groups work together and view their diversity as a resource, the result is a better product, service, solution, or resolution. In addition, it typically happens as a kind of side-effect, that the roads to marketing in diverse markets are also opened up. Finally, everyone within the group learns from the others in the group. Inclusion and diversity have another very powerful positive impact. Everyone sees that what one does is the basis for reward rather than what one is or who they know. (Studies on the impact of diversity on team performance: 7, 12, 17, 42). 

This is a huge win for teams, groups, companies, and nations. If people feel that they will be rewarded based on what they do, then people are incentivized to do the best they can. If people feel that they are rewarded based on their age, race, sex, national origin etc. — that is, things over which they have no control, then no-one is motivated to do their best. Those in the out-group feel it is fairly pointless and those in the in-group feel it is unnecessary. 

Of course, there are many other factors besides diversity that impact creativity and innovation. The latter depend on leadership, organizational context, process, support, incentives, etc. In the short term, if people are under time pressure, some may perceive that they haven’t been as productive even if they have if there more ideas and more varied ideas are discussed. Arranging the context so that people are motivated to do well rather than do quickly will be critical to success. 

IMG_6566

References: 

[1] Bellamy, R., Erickson, T., Fuller,B., Kellogg, W.,  Rosenbaum, R., Thomas, J. and Vetting Wolf, T (2007) Seeing is believing: Design visualization for managing risk and compliance. IBM Systems Journal 46:2, 207-218.

[2] Best, M., Deardon, A., Dray, S., Light, A., Thomas, J.C., Buckhalter, C., Greenblatt, D., Krishnan, S., Sambasivan, N. (2007). Sharing perspectives on community centered design and international development.  Human-Computer Interaction, INTERACT 2007. New York: Springer.

[3] 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. 

[4] Carroll, J. Thomas, J. Miller, L. & Friedman, H.  (1980). Aspects of solution structure in design problem solving. American Journal of Psychology, 93 (2), 269-284.

[5] 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. 

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

[7]Chow, I. (2018) “Cognitive diversity and creativity in teams: the mediating roles of team learning and inclusion”, Chinese Management Studies, 12 (2), 369-383, https://doi.org/10.1108/CMS-09-2017-0262

[8] Dearden, A., Dunckley, L, Best, M., Dray, S., Light, A. & Thomas, J.C. (2007).  Socially responsible design in the context of international development. Panel presented at INTERACT 2007, Rio de Janiero, BZ,

[9] Fozard, J. L., Thomas, J. C., and Waugh, N. C. (1976). Effects of age and frequency of stimulus repetitions on two-choice reaction time. Journal of Gerontology, 31, (5), pp. 556-563. 

[10] Fozard, J. and Thomas, J. (1975). Psychology of aging: Basic findings and some psychiatric implications.  In J. Howells (Ed). Modern Perspectives in the psychiatry of old age. NY: Brunner/Mazel.

[11] Friedman, B., Brok, E., Roth. S. K., Thomas, J. C. (1996). Minimizing bias in computer systems. SIGCHI Bulletin, 28(1), pp. 48-51. 

[12] Kurtzberg, T. (2005). Feeling creative, being creative: An empirical study of diversity and creativity in teams. Creativity Research Journal, 17(1), 51-65.

[13] Malhotra, A., Thomas, J.C., Carroll, J. & Miller, L. (1980). Cognitive processes in design. International Journal of Man-Machine Studies, 20 , 119-140.

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

[15] Srivastava, S., Dhanesh, K., Basson, S., Rajput, N., Thomas, J., Srivastava, K. (2012). Voice user interface and growth markets. India HCI conference.

[16] Srivastava, S., Rajput, N, Dhanesha, K., Basson, S., and Thomas, J. (2013). Community-oriented spoken web browser for low literate users. CSCW, San Antonio, TX, 2013.

[17] Stahl, G., Maznevski, M., Voigt, A., and Jonsen, K. (2009). Unraveling the effects of cultural diversity in teams: A meta-analysis of research on multi-cultural work groups. Journal of International Business Studies, 1-20. 

[18] Thomas, J.C. (1991). The human factors of voice interfaces. Journal of the Washington Academy of Sciences 80 (3), 138-151. 

[19] Thomas, J.C. and Schneider, M. (1982). A rose by any other alphanumeric designator would smell as sweet. Behavior and Information Technology, 1 (4), 323-325. 

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

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

[22] Thomas, J. C., Fozard, J. L. and Waugh, N. C. (1977). Age-related differences in naming latency. American Journal of Psychology, 90(3), pp. 499-509. 

[23] Thomas, J.C. (1974). An analysis of behavior in the hobbits-orcs problem. Cognitive Psychology 6 , pp. 257-269. 

[24] Thomas, J. (2015). Chaos, Culture, Conflict and Creativity: Toward a Maturity Model for HCI4D. Invited keynote @ASEAN Symposium, Seoul, South Korea, April 19, 2015.

[25] Thomas, J. (2014). Mobile Systems for Computational Social Science: A Perfect Storm. Invited keynote address at UbiComp workshop, Sept. 13, 2014, Seattle, WA.

[26] Thomas, J., Diament,J., Martino, J. and Bellamy, R., (2012). Using “Physics” of Notations to Analyze a Visual Representation of Business Decision Modeling. Presented at VL/HCC 2012 conference in Salzburg, Austria.

[27] Thomas, J. C. , Basson, Sara H., and Gardner-Bonneau, D.  (2008 & 1999) Universal access and assistive technology. In D. Gardner-Bonneau (Ed.), Human factors and voice interactive systems. Norwell, MA: Kluwer. 

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

[29] 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. 

[30] Thomas, J.C. (1997). Steps toward universal access in a telecommunications company. In B. Friedman (Ed.), Human values and the design of computer technology. Stanford, CA: CSLI. 

[31] 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. 

[32] Thomas, J.C. (2007). Panelist, Meta-design and social creativity: Making all voices heard. INTERACT 2007, Rio de Janeiro, BZ, Nov., 2007.

[33] Thomas, J.C. (2007).  E-learning: An opportunity to meld modern technology and ancient wisdom? Panelist, E-learning.  INTERACT 2007, Rio de Janeiro, BZ, Nov. 2007.

[34] Thomas, J.C. (2005). Patterns to promote individual and collective creativity.  Presented at the Human Computer Interaction International, Las Vegas, NV, July 27, 2005.

[35] Thomas, J.C. (1996). Invited panel presenter at the National Research Council’s workshop: Toward an every-citizen interface to the national information infrastructure, Washington, DC., August 23, 1996.

[36] Thomas, J.C. & Kellogg, W. (1993). Cross-cultural perspectives on human-computer interaction: report on the CHI ’92 workshop. SIGCHI Bulletin, 25 (2), 40-45.

[37] Trewin, S., Richards, J., Hanson, V., Sloan, D., John, B., Swart, C., Thomas, J. (2012). Understanding the role of age and fluid intelligence in information search. Presented at the ASSETS Conference, Boulder CO.

[38] Trewin, S., Bellamy, R., Thomas, J., Brezin, J., Richards, J., Swart, C., and John, B.E., (2010). Designing for Auditory Web Access: Accessibility and Cellphone Users.  The 7th International Cross-Disciplinary Conference on Web Accessibility, W4A.

[39] Trewin, S, Richards, J.,Bellamy, R, John, B.E.,Thomas, J.C., Swart, C.Brezin, J. (2010). Toward Modeling Auditory Information Seeking Strategies on the Web. CHI Work In Progress. 

[40] Trewin, S., Bellamy, R., Thomas, J., Brezin, J., Richards, J., Swart, C., and John, B.E., (2010). Designing for Auditory Web Access: Accessibility and Cellphone Users.  The 7th International Cross-Disciplinary Conference on Web Accessibility, W4A.

[41] Trewin, S, Richards,J.,Bellamy, R, John, B.E.,Thomas, J.C., Swart, C.,Brezin,J. (2010). Toward Modeling Auditory Information Seeking Strategies on the Web. CHI Work In Progress. 

[42] Yap, C., Chai, K. & Lemaire, P. (2005). An empirical study on functional diversity and innovation in SMEs. Creativity and Innovation Management, 14 (2), 176-190. 

Support Both Flow & Breakdown

21 Monday May 2018

Posted by in America, management, psychology, Uncategorized

≈ 3 Comments

Tags

, , , , , , , , , , ,

Support Both Flow & Breakdown

IMG_4663

Prolog/Acknowledgement/History: 

Only a few days after moving into our San Diego home (with a beautiful drip-irrigated garden), I glanced outside to see a geyser sprouting about ten feet into the air. San Diego can only survive long term if people conserve water! Yet, here we were — wasting water. I rushed outside to turn off the sprinkler system. As I ran to the controller, I noted in passing that the nearby yard lay soaked with pools of water. I turned off the sprinklers — except for the geyser which continued its impersonation of “Old Faithful.” I tried turning the valve on that particular sprinkler and did manage in that way to completely soak myself but the water waste continued unabated. We called the gardener who knew and explained the location of the shutoff valve for the entire house and garden. Later, he came and replaced the valve with a newer type. The old type, which had failed, failed by being stuck in the fully ON position!

Often in the course of my life, I have been frustrated by interacting with systems — whether human or computer — that were clearly designed with a different set of circumstances than the one I found myself in at the time. In a sense, the Pattern here is a specific instance of a broader design Pattern: Design for Broad Range of Contexts. The specific example that I want to focus on in this Pattern is that design should support the “normal” flow of things when they are working well, but also be designed to support likely modes of breakdown.

During the late 1970’s, I worked with Ashok Malhotra and John Carroll at IBM Research on a project we called “The Psychology of Design.” We used a variety of methods, but one was observing and talking with a variety of designers in various domains. One of the things we discovered about good designers was a common process that at first seemed puzzling. Roughly speaking, designers would abstract from a concrete situation, a set of requirements. They would then create a design that logically met all the requirements. Since we were only studying design and not the entire development process (which might include design, implementation, debugging, etc.) it might seem that the design process would end at that point. After all, the designer had just come up with a design that fulfilled the requirements.

What good designers actually did however, at least on many occasions, was to take their abstract design and imagine it operating back in the original concrete situation. When they imagined their design working in this concrete reality they often “discovered” additional requirements or interactions among design elements or requirements that were overlooked in the initial design. While unanticipated effects can occur in purely physical systems, (e.g., bridges flying apart from the bridge surface acting like a wing; O-rings cracking at sufficiently cold temperatures), it seems that human social systems are particularly prone to disastrous designs that “fulfill” the requirements as given.

woman in white wedding gown near orange car

Photo by Slobodan Jošić on Pexels.com

 

The Pattern here specifically focuses on one very common oversight. Systems are often designed under the assumption that everything in the environment of the system is working as it “should” or as intended. This particular type of breakdown was featured in an important theoretical paper authored by Harris and Henderson and presented at CHI 99. That paper claimed systems should be “pliant” rather than rigid. A common example most readers have had with a non-pliant system is to call an organization and be put into an automated call-answering system that does not have the appropriate category anywhere for the current situation but still does not have a way to get through to a human operator.

A telling example from their CHI Proceedings article is that of a paper-based form that was replaced with a computerized system with fixed fields. So, for example, there were only so many characters for various address fields. When someone needed to make an exception to the address syntax with a paper form, it was easy. They could write: “When it’s time to ship the package, please call this number to find out which port the Captain will be in next and ship it there: 606-555-1212.” In the computerized form, this was impossible. In fact, there were so many such glitches that the workers who actually needed to get their work done used the “required” “productivity-enhancing” computer system and also duplicated everything in the old paper system so that they could actually accomplish their tasks.

As part of the effort (described in the last blog post) to get IBM to pay more attention to the usability of its products, we pushed to make sure every development lab had a usability lab that was adequately equipped and staffed. This was certainly a vital component. However, usability in the lab did not necessarily ensure usability in the field. There are many reasons for that and I collaborated with Wendy Kellogg in the late 1980’s to catalog some of those. This effort was partly inspired by a conversation with John Whiteside, who headed the usability lab for Digital Equipment Corporation. They brought people who used a word processor into their usability lab and made numerous improvements in the interface. One day he took some of the usability group out to observe people using the text editor in situ in a manuscript center. They discovered that the typists spent 7 hours every day typing and 1 hour every day counting up, by hand, the number of lines that they had typed that day (which determined their pay). Of course, it was now immediately obvious how to improve productivity by 14%. The work of this group seems to have been inspirational for Beyer & Holtzblatt’s  Contextual Design as well as the Carroll & Kellogg (1989) paper on “Artifact as Theory Nexus.”

fire portrait helmet firefighter

Photo by Pixabay on Pexels.com

 

Author, reviewer and revision dates: 

Created by John C. Thomas in May, 2018

fullsizeoutput_17

Related Patterns: 

Reality Check, Who Speaks for Wolf?

Abstract: 

When designing a new system, it is easy to imagine a context in which all the existing systems that might interact with the new system will operate “normally” or “properly.” In order to avoid catastrophe, it is important to understand what reasonably likely failure modes might be and to design for those as well.

Context: 

For people to design systems, it is necessary to make some assumptions that separate the context of the design from what is being designed. There is a delicate balance. If you define the problem too broadly, you run the risk of addressing a problem that is too intractable, intellectually, logistically or financially. On the other hand, if you define the problem too narrowly, you run the risk of solving a problem that is too special, temporary, or fragile to do anyone much good.

In the honest pursuit of trying to separate out the problem from the context, it happens that one particular form of simplification is particularly popular. People assume that all the systems that will touch the one they are designing will not fail. That often includes human beings who will interact with the system. Such a design process may also presume that electrical power will never be interrupted or that internet access will be continuous.

Systems so designed may have a secondary and more insidious effect. By virtue of having been designed with no consideration to breakdowns, the system will tend to subtly influence the people and organizations that it touches not to prepare for such breakdowns either.

Problem:

When the systems that touch a given system do fail, which can always happen, if no consideration has been given to failure modes, the impact can be disastrous. Most typically, when the system has not been designed to deal with breakdowns, the personnel selection, training, and documentation also fail to deal with breakdowns. As a result, not only are the mechanisms of the systems unsuited to breakdowns; the human organization surrounding the breakdown is also unprepared. Not only is there a possibility of immediate catastrophe; the organization is unprepared to learn. As a result, mutual trust within and of the organizations around the system are also severely damaged.

architecture building fire exit ladders ladder

Photo by Photo Collections on Pexels.com

Forces:

  • Design is a difficult and complex activity and the more contingencies and factors that are taken into account, the more difficult and complex the design activity becomes.
  • Not every single possibility can be designed for.
  • People working on a design have a natural tendency to “look on the bright side” and think about the upside benefits of the system.
  • People who try to “sell” a new system stress its benefits and tend to avoid talking about its possible failures.
  • It is uncomfortable to think about possible breakdowns.
  • When anticipated breakdowns occur, the people in relevant organizations tend to think about how to fix the situation and reduce the probability or impact of breakdowns for the future.
  • When unanticipated breakdowns occur, the people in relevant organizations tend to try to find the individual or individuals responsible and blame them. This action leaves the probability and impact of future breakdowns unimproved.
  • When people within an organization are blamed for unanticipated system failure, it decreases trust of the entire organization as well as mutual trust within the organization.

* Even when consideration of support for breakdown modes is planned for, it is often planned for late in an ambitious schedule. The slightest slippage will often result in breakdowns being ignored.

Solution:

When designing a system, make sure the design process deals adequately with breakdown conditions as well as the “normal” flows of events. The organizations and systems that depend on a system also need to be designed to deal with breakdowns. For example, people should be trained to recognize and deal with breakdowns. Organizations should have a process in place (such as the After Action Review) to learn from breakdowns. Having a highly diverse design team may well improve the chances of designing for likely breakdowns. 

Resulting Context:

Generally speaking, a system designed with attention to supporting both the “normal” flow of events and likely breakdown modes will result in a more robust and resilient system. Because the system design takes these possibilities into account, it also makes it likely that documentation and training will also help people prepare for breakdowns. Furthermore, if breakdowns are anticipated, it also makes it easier for the organization to learn about how to help prevent breakdowns and to learn, over time, to improve responses to breakdowns. There is a further benefit; viz., that mutual trust and cooperation will be less damaged in a breakdown. The premise that breakdowns will happen, puts everyone more in the frame of mind to learn and improve rather than simply blame and point fingers.

fullsizeoutput_12e0

Examples: 

1. Social Networking sites were originally designed to support friends sharing news, information, pictures, and so on. “Flow” is when this is what is actually going on. Unfortunately, as we now know, social media sites can also not work as intended, not because there are “errors” in the code or UX of the social media systems but because the social and political systems that form the context for these systems have broken down. The intentional misappropriation of an application or system is just one of many types of breakdowns that can occur.

2. When I ran the AI lab at NYNEX in the 1990’s, one of the manufacturers of telephone equipment developed a system for telephone operators that was based on much more modern displays and keyboards. In order to optimize performance of the system, the manufacturer brought in representative users; in this case, telephone operators. They redesigned the workflow to reduce the number of keystrokes required to perform various common tasks. At that time, operators were measured in terms of their “Average Work Time” to handle calls.

In this particular case, the manufacturer had separated the domain into what they were designing for (namely, the human-machine interface between the telephone operator and their terminal) from the context (which included what the customer did). While this seemed seemed like a reasonable approach, it turned out when the HCI group at NYNEX studied the problem with the help of Bonnie John, the customer’s behavior was actually a primary determiner of the overall efficiency of the call. While it was true that the new process required fewer keystrokes on the part of the telephone operator, these “saved” keystrokes occurred when the customer, not the telephone operator, was on the critical path. In other words, the operator had to wait for the customer any way, so one or two fewer keystrokes did not impact the overall average work time. However, the suggested workflow involved an extra keystroke that occurred when the operator’s behavior was on the critical path. As it turned out, the “system” that needed to be redesigned was not actually the machine-user system but the machine-user-customer system. In fact, the biggest improvement in average work time came from changing the operator’s greeting from “New York Telephone. How can I help you?” to “What City Please?” The latter greeting tended to produce much more focused conversation on the part of the customer.

Just to be clear, this is an example of the broader point that some of the most crucial design decisions are not about your solution to the problem you are trying to solve but your decision about what the problem is versus what part of the situation you decide is off-limits; something to ignore rather than plan for. A very common oversight is to ignore breakdowns, but it’s not the only one.

black rotary telephone beside beige manekin

Photo by Reynaldo Brigantty on Pexels.com

3. In a retrospective analysis of the Three-Mile Island Nuclear Meltdown, many issues in bad human factors came to light. Many of them had to do with an insufficient preparation for dealing with breakdowns. I recall three instances. First, the proper functioning of many components was shown by a red indicator light being on. When one of the components failed, it was indicated by one of a whole bank of indicator lights not being on. This is not the most salient of signals! To me, it clearly indicates a design mentality steering away from thinking seriously about failure modes. This is not surprising because of the fear and controversy surrounding nuclear power. Those who operate and run such plants do not want the public, at least, to think about failure modes.

Second, there was some conceptual training for the operators about how the overall system worked. But that training was not sufficient for real time problem solving about what to do. In addition, there were manuals describing what to do. But the manuals were also not sufficiently detailed to describe precisely what to do.

Third, at one critical juncture, one of the plant operators closed a valve and “knew” that he had closed it because of the indicator light next to the valve closure switch. He then based further actions on the knowledge that the valve had been closed. Guess what? The indicator light showing “value closure” was not based on feedback from a sensor at the site of the valve. No. The indicator light next to the switch was lit by a collateral current from the switch itself.  All it really showed was that the operator had changed the switch position! Under “normal” circumstances, there is a perfect correlation between the position of the switch and the position of the valve. However, under failure mode, this was no longer true.

accident action danger emergency

Photo by Pixabay on Pexels.com

4. The US Constitution is a flexible document that takes into account a variety of failure modes. It specifies what to do, e.g., if the President dies in office and has been amended to specify what to do if the President is incapacitated. (This contingency was not really specified in the original document). The Constitution presumes a balance of power and specifies that a President may be impeached by Congress for treasonous activity. It seems the US Constitution, at least as amended, has anticipated various breakdowns and what to do about them.

There is one kind of breakdown, however, that the U.S. Constitution does not seem to have anticipated. What if society becomes so divided, and the majority of members in Congress so beholden to special interests, that they refuse to impeach a clearly treasonous President or a President clearly incapacitated or even under the obvious influence of one or more foreign powers? Unethical behavior on the part of individuals in power is a breakdown mode clearly anticipated in the Constitution. But it was not anticipated that a large number of individuals would simultaneously be unethical enough to put party over the general welfare of the nation.  Whether this is a recoverable oversight remains to be seen. If democracy survives the current crisis, the Constitution might be further amended to deal with this new breakdown mode.

5. In IT systems, the error messages that are shown to end users are most often messages that were originally designed to help developers debug the system. Despite the development of guidelines about error messages that were developed over a half century ago, these guidelines are typically not followed. From the user’s perspective, it appears as though the developers know that something “nasty” has just happened and they want to run away from it as quickly as possible before anyone can get blamed. They remind me of a puppy who just chewed up their master’s slippers and knows damned well they are in trouble. Instead of “owning up” to their misbehavior, they hide under the couch.

Despite the many decades of pointing out how useless it is to get an error message such as “Tweet not sent” or “Invalid Syntax” or “IOPS44” such messages still abound in today’s applications. Fifty years ago, when most computers had extremely limited storage, there may have been an excuse to print out succinct error messages that could be looked up in a paper manual. But today? Error messages should minimally make it clear that there is an error and how to recover from it. In most cases, something should be said as well as to why the error state occurred. For instance, instead of “Tweet not sent” a message might indicate, “Tweet not sent because an included image is no longer linkable; retry with new image or link” or “Tweet not sent because it contains a potentially dangerous link; change to allow preview” or “Tweet not sent because the system timed out; try again. If the problem persists, see FAQs on tweet time-out failures.” I haven’t tested these so I am not claiming they are the “right” messages, but they have some information.

Today’s approach to error messages also has an unintended side-effect. Most computer system providers now presume that most errors will be debugged and explained on the web by someone else. This saves money for the vendor, of course. It also gives a huge advantage to very large companies. You are likely to find what an error message means and how to fix the underlying issue on the web, but only if it is a system that already has a huge number of users. Leaving error message clarification to the general public advantages the very companies who have the resources to provide good error messages themselves and keeps entrenched vendors entrenched.

slippery foot dangerous fall

Photo by Pixabay on Pexels.com

References: 

Alexander, C., Ishikawa, S., Silverstein, M., Jacobsen, M., Fiksdahl-King, I. and Angel, S. (1977), A Pattern Language: Towns, Buildings, Construction. New York: Oxford University Press.

Beyer, Hugh and Holtzblatt, Karen (1998): Contextual design: defining customer-centered systems. San Francisco: Elsevier.

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.

Carroll, J. and Kellogg, W. (1989), Artifact as Theory-Nexus: Hermeneutics Meets System Design. Proceedings of the ACM Conference on Human Factors in Computing Systems. New York: ACM, 1989.

Casey, S.M. (1998), Set Phasers on Stun: And Other True Tales of Design, Technology, and Human Error. Santa Barbara, CA: Aegean Publishing.

Gray, W. D., John, B. E., & Atwood, M. E. (1993). Project Ernestine: Validating GOMS for predicting and explaining real-world task performance. Human Computer Interaction, 8(3), 237-309.

Harris, J. & Henderson, A. (1999), A Better Mythology for System Design. Proceedings of ACM’s Conference on Human Factors in Computing Systems. New York: ACM.

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

Thomas, J. (2016). Turing’s Nightmares: Scenarios and Speculations about “The Singularity.” CreateSpace/Amazon.

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.

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

Thomas, J. (2015). Chaos, Culture, Conflict and Creativity: Toward a Maturity Model for HCI4D. Invited keynote @ASEAN Symposium, Seoul, South Korea, April 19, 2015.

Author Page on Amazon

Find and Cultivate Allies

14 Monday May 2018

Posted by in America, management, psychology, Uncategorized

≈ 4 Comments

Tags

, , , , , , , , , ,

Find and Cultivate Allies

IMG_2818

Prolog/Acknowledgement: 

The idea for this Pattern comes from personal experience although I am sure there must be many other writers who make a similar point.

Author, reviewer and revision dates: 

Created by John C. Thomas in May, 2018.

IMG_9320

Abstract: 

Human beings are highly social beings by nature. We work more effectively in groups (for many tasks) and it’s also more pleasurable. In a group of any size and complexity, people will have a large variety of goals and values. To achieve a goal, including but not limited to change within the group itself, it is useful to make common cause with others within the larger group. Whenever it becomes useful to promote social change of any kind, it is important to seek out and then cultivate allies. You will achieve greater success, enjoy the process, and learn much.

Context: 

Complex problems and large problems can often only be solved by groups. Within a large group, there will be many sub-groups and individuals whose motivations, expertise, and values are partially different from those in other sub-groups or from those of other individuals. In order to achieve any kind of goal including but not limited to changes within the group itself, a great deal of knowledge must be brought to bear and a large number of actions will be required. Generally, an individual or a small group will not have the knowledge, power, or resources to take all of these actions.

The variety of goals, values, experiences, and scope of power of various individuals and subgroups within a larger group can be viewed as a resource. The interactions among such individuals be a source of creativity. In addition, in order to accomplish some goal, you may seek and find among these individuals and groups those whose goals are compatible with yours and whose power and resources allows them to do things you cannot do yourself.

Individuals are subject to a variety of perceptual and cognitive illusions and these may be exaggerated by being in a large group. Changing a group, team, organization, corporation, NGO may be even more difficult than changing an individual even if the change would benefit the group, team, organization, corporation or NGO. Within any organization, there come to be entrenched interests that are orthogonal to, or even antithetical to, the espoused purposes of the group.

iPhoneDownloadJan152013 527

Problem:

Over time, organizations eventually begin to behave in ways that are ineffective, inefficient, or even antithetical to their purpose. Whatever the cause, an individual who recognizes these infelicities in the organization will typically not, by acting alone, have the power to change them. Force of habit, custom, the culture, and the entrenched power of others will tend to make change by an individual extremely difficult or impossible despite their pointing out that the current way of doing things is counter-productive.

Forces:

  • People who wield local power in an organization are often afraid that any change will weaken their power.
  • Changing one part of the organization generally means that other parts must also change, at least slightly.
  • What works best for an organization must necessarily change over time because of changes in personnel, society, technology, competition, the environment, and so on.
  • Organizations typically codify the way they currently work by documenting procedures, providing training, incorporating current processes into software systems, floor layouts, and so on.
  • Each person in an organization is typically rewarded according to the performance of a small area of the organization that centers on or near them.

* People within an organization of any size will exhibit large variations in knowledge, skill, values, goals, and the resources available to them.

* In many organizations, a valid reason for continuing to do X is simply to say, “That’s the way we’ve always done it.”

* It is not considered a valid reason for change from doing X to doing Y to simply say, “We’ve never done it this way before.”

* Organizations are therefore prone to continuing along a path long after it is a fruitful, ethical, or lawful path.

Solution:

If a person wishes to change how a large organization does things, they need to find and cultivate potential allies within the organization. Allies may be people who can be convinced that the change is best for something that is best for that individual, their department, the organization as a whole, for society or for life on earth. These allies will have crucial information, power, friends, or resources to help make the change possible.

IMG_1183

Example: 

For two years, in the early 1980’s, I worked in the IBM Office of the Chief Scientist. My main mission was to get IBM as a whole to pay more attention to the usability of its products. No-one worked for me. I had no budget. I did, however, have the backing of the Chief Scientist, Lewis Branscomb. Among his powers, at the time, was the ability to “Non-Concur” with the proposed plans of other parts of IBM. This meant that if other IBM divisions did not have usability labs or adequate staff, the Chief Scientist could block the approval of those plans. Lewis himself was a great ally because he had a lot of personal credibility due to his brilliance. Having the power to block the plans of other divisions was also critical.

IBM at this time already had some Human Factors Labs who had done excellent work for years. However, there were large areas such as software that were mainly untested. In addition, most of IBM’s users were technical people and many of the usability tests had been done on other technical people. This had been appropriate but with the extension of computing into other areas of life, many of IBM’s “end users” were now people with little technical computer background. This included administrative assistants and clerks; even chemists, physicists, MD’s, lawyers and other people with advanced education found IBM products hard to use. None of these fairly new groups of users had typically used computers much or had been taught their use in their schooling.

I needed to find allies because the changes that were necessary to IBM were widespread. One important ally was already provided: Tom Wheeler had a similar position to mine within another corporate staff organization called “Engineering, Products, and Technology.” Tom could also get his boss to non-concur with the plans of divisions who were unwilling to “get on board” with the changes. But I needed more allies.

One obvious source of allies were the existing Human Factors Groups. Where they existed, they were typically staffed and managed by excellent people; however, they were often understaffed and often brought in near the end of the development cycle. In many cases, only their advice on “surface features” or documentation could be incorporated into the product. This was frustrating to them. They knew they could be more effective if they were brought in earlier. Often, this did happen, but typically because they had developed personal reputations and friendships (allies) within their organization. It was not mandated by the development process.

Who else would benefit from more usable IBM products? There’s a long list! A lot of “power” within IBM came from Sales and Marketing. The founder, Thomas J. Watson was himself primarily a sales and marketer. Most of the CEO’s had been from this function of the organization. Many in Sales and Marketing were beginning to see for themselves that IBM products were frustrating customers. Finding people within such organizations who were willing to stand up and “be counted” was critical. It was especially useful to find some allies in Europe who were on board with suggested changes. In many countries in Europe, there were various social and legal constraints that gave even more weight to having products that did not cause mental stress, repetitive motion injuries, eyestrain, hearing loss and so on.

In many parts of IBM, there were also “Product Assurance” organizations that required products to be tested before final release. In this case, two simple but crucial and fundamental changes needed to be made. Again, people who worked in Product Assurance wanted these changes to be made. First, we needed to convince development to work with Product Assurance earlier rather than later so that any problems would not be the cause of product announcement slippages (or ignored). Second, we needed to convince Product Assurance to test the procedures and documentation with people outside the development teams. Current practice was often for the Product Assurance people to watch people on the development team “follow” the documented process to ensure that it actually worked. The problem with this process is that language is ambiguous. The people on the development team already knew how to make the product work, so they would interpret every ambiguity in instructions in the “proper” way. IBM customers and users, however, would have no way of knowing how to resolve these ambiguities. Instead of making sure that the documentation was consistent with a successful set-up, the process was changed to see whether documentation actually resulted in a successful set-up when attempted by someone technically appropriate but outside the development team.

fullsizeoutput_1164

People within IBM product divisions did care about budgets. Adding human factors professionals to existing labs or, in some cases, actually setting up new labs, would obviously cost money. We needed to show that they would save money, net. Some of the human factors labs had collected convincing data indicating that many service calls done at IBM’s expense were not due to anything actually being wrong with the product but instead were because the usability of the product was so bad that customers assumed it must not be working correctly. In most cases, fixing the usability of products would save far more money than the additional cost of improving the products.

In some cases, developing allies was a fairly simple business. For example, IBM had a process for awarding faculty grants for academic research relevant to its technologies and products. These were awarded in various categories. Adding a category to deal with human-computer interaction required a single conversation with the person in charge of that program. Similarly, IBM awarded fellowships to promising graduate students in various categories of research. Again, adding the category of human-computer interaction resulted from a single conversation. It should be noted that the ease of doing that resulted much more from the fact that it was known throughout the company that usability was now deemed important and the fact that I worked for the well-respected Chief Scientist than from any particular cleverness on my part.

In at least one case, an ally “fell in my lap.” Part of how I operated was to visit IBM locations around the world and give a talk about the importance of usability for IBM’s success. Generally, these talks were well-received although that did not guarantee any success in getting people to change their behavior. When I gave the talk to the part of IBM that made displays, however, I got a completely hostile reaction. It was clear that the head of the division had somehow made up his mind before I started that it was complete nonsense. I had no success whatever. Only a few months later, the head of this division got an IBM display of his own. He couldn’t get it to work! He did a complete 180 and became an important supporter, through no fault of my own. (Of course, there may have been additional arm-twisting beyond my ken).

iPhoneDownloadJan152013 499

There were also two important, instructive, and inter-related failures in lining up my allies. First, it was very difficult to line up development managers. An IBM developer’s career depended on getting their product “out the door.” Not every product development effort that began resulted in a product being shipped. Once the product was shipped, the development manager was promoted and often went to another division. So, from the development manager’s perspective, the important thing was to get their product shipped. If it “bombed” after shipment, it wasn’t their problem. In order for the product to be shipped, it had to be forecast to make significant net revenue for IBM. No big surprise there! However, these predictions did not take into account actual sales, or the actual cost of sales, or the actual service costs, or even the actual production costs. The only thing that was really known were the development costs. So, for every additional dollar the development manager spent during development, there was one dollar added to the development costs, but also an additional dollar added to predicted service costs and predicted manufacturing costs. Moreover, there were an additional five dollars added to the predicted sales and marketing costs. If they spent an extra dollar doing usability tests, for example, it added not just one but eight dollars to estimated overall costs. Moreover, since IBM was in business to make a profit, an increase of 8 dollars in costs, meant an increase of nearly 20 dollars in projected price. This meant fewer predicted products sold.

In actuality, spending an additional dollar to improve usability of products should reduce service costs and sales and marketing costs. But that is not the formula that was used. The logic of the formula, corroborated by correlational data, was that bigger, more complex products had higher development costs and also had higher service, manufacturing and sales costs. When one compared a mainframe and a PC, this formula made sense. But when used as a decision tool by the development manager, it did not make sense. (By analogy, there is a strong correlation between the size of various species of mammals and their longevity. This, however, does not mean that you will live twice as long if you double your own body weight!).

Recall however, that the development manager’s career did not much depend on how successful the product was after release; it mainly depended on showing that they could get their product shipped. Development managers proved to be difficult to get “on board.” In some cases, despite the organizational pressures, some development managers did care about how the product did; were interested in making their products usable; did spent additional money to improve their product. Making such allies, however, relied on appealing to their personal pride of ownership or convincing them it was best for the company.

Some development managers suggested that perhaps I could get the Forecasters to change their formula so that they would be given credit for higher sales to balance the projected increase in price (and attendant reduction in sales volume forecasts). It would have been an excellent leverage point to have gotten the Forecasting function as an ally. I was not, however, sufficiently wise to accomplish this.

The organizational payoff matrix for the forecaster was quite skewed toward being conservative. If they used the existing formula and ended up thereby “killing” a product by reducing the sales forecast because of the money spent improving usability, no-one would ever find out that the forecaster might have erred. On the other hand, if I had convinced them by giving them evidence (which would necessarily be quite indirect) that the product, by virtue of its being more usable, would therefore sell many more units, there were at least two logical possibilities. First, I might be right and the product would be a success. The forecaster would have done the right thing and would keep their job (but not be likely to receive any special recognition, promotion, or raise). Second, I might be wrong (for a variety of reasons having nothing to do with usability such as unexpected competition or unexpected costs) and the product might tank. In that case, the company would lose a lot of money and the forecaster might well lose their job. While I occasionally found development managers I could convince to be allies because I could get them to value making the most excellent product over their own career, I never was able to gain any allies in the Forecasting function. In retrospect, I think I didn’t take sufficient time to discover the common ground that it would have taken to get them on board.

IMG_3121

Resulting Context:

Finding allies will often enable the organization to change in ways that will benefit the organization as a whole and most of the individuals and sub-groups within it. If done with the best interests of the organization in mind, it should also increase internal mutual trust.

There is a related Anti-Pattern which is finding allies, not to change the organization in a positive way, but to subvert the organization. If, instead of trying to make IBM be more effective by making its products more usable, I had tried to ruin it by finding allies who, in the process of ruining IBM would also profit personally, that would have been highly unethical. Such a process, even if it ultimately failed, would decrease internal mutual trust and decrease the effectiveness of the organization. Of course, one could imagine that some competitor of IBM (or of a government or team) might try to destroy it from the inside out by favoring the promotion of those who would put their own interests ahead of the company or its customers. Finding allies is likely to be ethical when it is for the best interests of the overall organization and all its stakeholders and if is a known initiative (as was the case for improving the usability of IBM products).

References: 

https://gps.ucsd.edu/faculty-directory/lewis-branscomb.html

Branscomb, L. and Thomas, J. (1984). Ease of use: A system design challenge. IBM Systems Journal, 23 (3), pp. 224-235.

Thomas, J. (1984) Organizing for human factors. In Y. Vassilou (Ed.) Human factors and interactive computing systems. Norwood, NJ: Ablex.

Thomas, J.C. (1985). Human factors in IBM. Proceedings of the Human Factors Society 29th Annual Meeting.  Santa Monica, CA: Human Factors Society. 611-615. 

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

Author Page on Amazon: https://www.amazon.com/author/truthtable

Speak Truth to Power

10 Thursday May 2018

Posted by in America, management, psychology, Uncategorized

≈ 1 Comment

Tags

, , , , , , ,

Speak Truth to Power

IMG_9266

Prolog/Acknowledgement: 

This is a well-known phrase and also served as the subtitle to an on-line course I took recently on political consulting. I thought it would be useful as a follow-up to the last blog post which comprised the Anti-Pattern: Power Trumps Good. It is all well and good to say that one should speak truth to power. But how exactly does one go about that? Most people realize that exercise is good for them and eating lots of refined sugar is not; but knowing that is not enough to make those lifestyle changes happen. It is easy to forgo exercise; it is easy to get hooked on sugar; it is easy to “go along” with whoever is in power and accept or acquiesce in whatever they say. Hopefully, the pattern Speak Truth to Power can help motivate people but also provide some guidance in how to go about it. The result will be organizations that are more effective and efficient as well as being more life-promoting to interact with or belong to. That said, if you are like most people, it will be uncomfortable initially to speak truth to power just as it will be uncomfortable to start an exercise program or stop your sugar addiction. But that doesn’t mean it’s impossible.

A committed individual can accomplish a lot. In many cases, however, an organization can accomplish a lot more. Most organizations have some kind of power structure. In order to collaborate and cooperate most effectively, it is important to understand, not only how to be an outstanding individual contributor to the goals of that organization; it is also important to know how to help the organization as a whole meet its goals. The next few Patterns should help with being effective in your work for and with organizations: Speak Truth to Power; Find Allies; Seek Forgiveness, not Permission; Servant Leadership; Prioritize; Seek to Work Down, not Up the Chain of Command.  

Author, reviewer and revision dates: 

Created by John C. Thomas in May, 2018

IMG_9136

Synonyms: 

Be Yourself. Be Honest.

Abstract: 

Human beings often need to form large groups in order to accomplish great things. In order to coordinate the actions of a large group, the most commonly used mechanism is to form a hierarchy of power and control. In the best of circumstances, information flows up such a chain of command only so far as it needs to; decisions are made; these decisions are carried out through the chain of command. Such “command and control” structures can be efficient, but they are subject to the difficulty that people in positions of power may use their power, not to achieve the goals of the organization but instead use the organization only for their own ends. People in power may concoct a rationalization or story or outright lie that makes it seem as though they are doing things for the common good when they are only doing things to consolidate their own power or to make themselves comfortable. People in power may discourage subordinates from giving them honest feedback about the effects of their decisions. As an antidote, it is important for everyone in the organization to speak truth to power. That is, you must find a way to insure that important information, including “bad news,” is made available to the organization.

Context: 

Complex problems and large problems can often only be solved by groups. In many cases, these groups have considerable structure including, importantly, a hierarchical control structure which gives some people the power to make decisions. Often, these decisions are not just about the appropriate course of action for the group as a whole; they also include decisions about the other people in the group; e.g., who to promote, give a raise to, fire, okay a transfer, write a recommendation and so on. Hopefully, the person “in charge” of a group or team within a larger organization knows or makes sure to learn a good deal about the domain as well as the people he or she works with. Ideally, people use their power to gather information, facilitate fruitful discussion, and make decisions that people within the group understand even if they don’t always agree. However, as point out in the Anti-Pattern: Power Trumps Good, it is also possible that the person “in charge” uses power primarily for their own benefit; in extreme cases, they will use it for sexual exploitation, to blame others for their bad decisions, to take credit for things they didn’t do and so on. Such bosses often only want to hear about the good that comes from their decisions. They only want to hear data and arguments that support their positions.

fullsizeoutput_17ed

Problem:

Groups function better if decisions are based on facts. Yet, sometimes the person in charge does not want to hear facts that argue for a different course of action from the one they want or if the facts show that a previous decision turned out to be a bad one. People who work for such a boss may well know these “uncomfortable facts” but the boss has the power to promote them, fire them, give them a raise, and so on. This puts pressure on those who work for such a boss to tell the boss what he or she wants to hear so as to stay in their good graces. If a bad decision is made it is generally bad for the overall organization, the team, and at least some of the individuals on the team.

Forces:

  • Having power tempts many people to abuse that power.
  • A person in power can bestow positive and negative sanctions based on obedience and compliance rather than competence.
  • People in an organization know they are supposed to be working for the best interests of the organization as a whole.
  • If a person in power signals (implicitly or explicitly) that they will use that power to put everyone under them in compliance with their wishes rather than what is best for the organization, it is tempting to be compliant.
  • When faced with an ethical dilemma, if people do what is expedient rather than what is right, they can generally find a way to “rationalize” their unethical decision.
  • An organization that runs on personal power as the driver for decision making will make inept decisions that are often at cross-purposes.
  • An organization that runs on personal power will tend to attract and keep the kind of person who will fail ethical tests.
  • If some people in an organization are willing to forgo the facts in order to please the boss, it will tend to encourage others to do the same.
  • If some people in an organization are willing to speak truth to power, it will encourage others to do the same.

 

fullsizeoutput_1987

Solution:

Speak truth to power. There are many ways to do this. Depending on circumstances and the character (or lack of character) of the person in power, it may help to be bombastic, quiet, rational, emotional, respectful, or find a way to demonstrate that taking facts into account is in their interests as well. In many traditional and highly hierarchical Japanese companies, the workers always defer during working hours and publicly. After hours, a junior person may “unfortunately” get drunk and “accidentally” let the truth out to his superiors. Later, after sobering up, they apologize. In the Middle Ages, the Court Jester might tell the King truth. However you do it, speak truth to power. And, if you are in power, encourage everyone to speak the truth to you.

Examples: 

  1. To understand this example, it takes a while to set the stage. You need that background in order to understand how necessary it was to speak truth to power. For a time, I was the Executive Director for an AI lab. The company that I worked for was having a problem with their credibility. Fewer than 15% of the union people trusted top management. The figure for people in management like me, was even lower. The CEO called in a top consultant who told them about what Sam Walton did (who, at that time, enjoyed high trust among his employees). Every week, he had an hour long conference call. Each of his 700 store managers were on the call. Each manager had a chance to describe in one minute, a problem that he or she had encountered and how they had solved it. Part of the reason this process worked for Sam Walton was that he already had a lot of credibility. He would spend fully half his time traveling the country in jeans and a pick-up truck with two dogs in the back. He knew each of his store managers personally. Beyond that, while clearly some problems are local, any given store manager might very well have a solution to a problem that the other 699 could use.

By contrast, in the company I worked for, at this time, there were 70,000 “managers” in the company. The range of jobs among these 70,000 was tremendous. Some, like me, were in R&D. Others were telecom engineers or personnel counselors or accountants or software engineers. Our CEO at that time was definitely not someone wear jeans nor to ride around in a pickup truck with dogs in the back. He definitely was someone who “stood on ceremony” and expected others to do the same.

Management realized that 70,000 was far too many for everyone to speak about problems and solutions, but they still thought it important to make this weekly experience interactive. So, they decided that each week, the CEO would talk at the 70,000 managers for an hour about something important such as that they had a clear understanding of their precise role and duties. After the talk, each of the 70,000 managers would be asked to react with the touch-tone keypad. In this example, they were supposed to indicate on a 10-point scale how much they had a clear understanding of their precise role and duties. The basic structure of this had been decided. They came to me, because I was an “expert” in human-computer interaction. They wanted to know whether the “0” key should be used to indicate a “ten” or whether it was better to use “9” as the top of the scale and “0” as the bottom of the scale.

cuts

Wow.

I made it very clear that this plan was a disaster waiting to happen and would do nothing to improve trust between people in the company and top management. After explaining this as clearly, yet politely as I could, the person from Corporate who presented the plan said, in essence:

“Well, when my boss asks me what the best way to do something is, it isn’t my job to tell him that it’s a bad idea. It’s my job to figure out the best way to do it.”

I said, in essence:

“Well, if my boss asks me what sort of chain saw he should use to trim his  hair, I think it is definitely my job to tell him that trimming his hair with a chain saw is a really bad idea.”

The guy from Corporate was not pleased. Eventually, however, before implementing this plan, they did run some focus groups and I am happy to report that this plan was never implemented.

Of course, it’s uncomfortable to be a nay-sayer, particularly when the CEO of the company has already been involved in choosing (what I saw as) a disastrous course of action. But the alternative would have been to dishonest. The alternative would ultimately done a disservice to myself, my work colleagues, the stockholders of the company and, indeed, to the CEO himself.

In my opinion, you should always be mentally prepared to lose your job even before you accept the job offer. You should be prepared to be fired for insubordination, laid off for no reason, or suffer at the hands of someone in power who is not really doing what is best for the organization. Then, when you are surprised by someone making an absurd request, you already know where you stand.

fullsizeoutput_11a6

2. In the 1990’s, I became intrigued with the idea of a “Learning Organization.” The idea is simple in essence but non-trivial to implement. Just as individual animals (including humans) learn, so too can an organization be set up so that lessons learned by a few can be shared by the many. (Some of the Story Patterns just posted are meant to encourage just that). Working with consultants, my colleague Bart Burns and I made the outline of a plan to help turn our company into one that was a “Learning Organization.” In order to modify this plan appropriately and ensure its acceptance, it would be necessary to get the CEO’s backing. (FYI, this was a different CEO than in example 1). I decided that I wanted to present this to our CEO directly. This is, of course, not how things are typically done. Good manners would be to convince my boss. If I convinced him it was a good idea, I would still have to convince him to try to convince his boss. And, not only would I have to convince my boss to convince his boss; I would have to convince him to convince his boss to convince his boss. And so on. I knew the company. I knew it would never happen. The further up the management chain you went, the more conservative the people were about “shaking the boat.”

Instead, I set up an appointment with the CEO directly, went to the meeting, made the pitch. I immediately told my boss what I had done and why. It was a gamble, but my boss was a smart man. He realized I was right that it would never go up the hierarchy to the CEO. Furthermore, even if I had convinced my boss, he might still appear foolish to his boss, or his boss’s boss. Basically, by not telling my boss, I had actually saved him some potential embarrassment and hassle. This is not a method I would try many times in a career and you’d better be ready for consequences. In this case, I felt that the transformation that it might have made to the organization was worth the risk. The “truth” here was not something that could be proven with the kind of certainty we have about, say, global climate change. I could not “prove” that being a Learning Organizations was a good idea. So, it was speaking my truth to power, not an objectively provable truth.

fullsizeoutput_1991

3. In The Shawshank Redemption, a crucial turning point in the movie occurs when the main character, Andy, overhears one of the prison guards talking about some tax problems. He asks the guard whether he trusts his wife. The guard is ready to kill him, but Andy persists. If the guard can really trust his wife, Andy can show him how to avoid the taxes by putting everything in the name of the guard’s wife. This allows Andy to begin working for all he guards and indeed making lots of money for the prison officials. He eventually uses the information to his great benefit. In this plot, Andy was taking a chance. It would have been easier just to keep his head down and say nothing.

Resulting Context:

Speaking truth to power tends to help an organization be effective. It tends to prevent people in power from trying to dictate truth to suit their private agenda. In addition, when people speak the truth, it makes for a more creative, more peaceful workplace. People can concentrate on finding out what’s what and doing what’s correct, not dwell on what the likes and dislikes of the next person in the hierarchy are or how to curry favor with them. “The truth shall make you free.”

Related Patterns: 

Reality Check.

References: 

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

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

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

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

https://www.amazon.com/author/truthtable

 

Fostering Group Cohesion through Common Narratives

28 Saturday Apr 2018

Posted by in family, management, psychology, Uncategorized

≈ 1 Comment

Tags

, , , , , , , ,

Fostering Group Cohesion through Common Narratives

IMG_3611

Prolog/Acknowledgement: 

The idea for this Pattern emerged from work done around 2000 with colleagues at IBM Research (including Cynthia Kurtz, Carl Tait, Frank Elio, Debbie Lawrence, Neil Keller, Andrew Gordon), Lotus (including Dan Gruen, Paul Moody, Michael Muller), and at the IBM Knowledge Institute(including Dave Snowden, Larry Prusak, Sharon Darwent & Fiona Incledon) on the business uses of stories and storytelling. Of course, stories have long been used by leaders to motivate groups and to help foster group cohesion.

Author, reviewer and revision dates: 

Created by John C. Thomas April, 2018.

fullsizeoutput_176c

Abstract: 

Stories that we tell ourselves help define who we are and frame our experience, both individually and collectively. In relatively stable cultures, a number of common stories are usually shared by everyone. What makes storytelling challenging in modern life is that group boundaries are continually shifting and changing. It often happens that groups which used to be separate must learn to work together; e.g., because of a peace treaty, corporate merger or acquisition, or even a marriage involving extended families. In these cases, it helps to find within the stories of these groups, common values among the previously disparate groups and then make compelling versions of stories that express these values and tell them back to the entire newly formed team, family, group, company, or nation.

Context: 

Groups across many contemporary cultures and throughout history have tended to tell, learn, and repeat stories as a way of codifying what is desirable and acceptable behavior, understanding the world, and communicating important lessons learned across generations. Such stories often include “creation myths” but also include stories about the “hero’s journey.”

In most cultures, these stories are transmitted orally regardless of whether such “cultures” are based on geography, company, religions, or even families. It’s true that some important stories have been put into written form. For example, many company founders have their own stories of founding the company put into written form. Religions often have sacred texts. However, both corporate cultures and religious sects and even congregations transmit the “proper interpretation” of these written documents orally. The written texts are modified very slowly while the oral interpretations can possibly change much more quickly. Nonetheless, the stories often persistently encode modes of behavior over centuries and even millennia.

When groups are stable over a long period of time and have minimal interaction, the fact that diverse groups have quite different stories seldom causes difficulties. As these diverse groups began to interact more frequently, it often happened that one group (typically the one with superior weapons) used violence to impose their stories on the other group. More recently, the world has become highly interconnected through inventions and developments in communications such as telegraphy, telephony, and the internet. Physical travel is also faster via rail, cars, and airplanes. People with different stories now come in contact of one sort or another very frequently indeed. Many of the most pressing problems that the world now faces including overpopulation, pandemics, and the destruction of the ecosystem require global cooperation.

Problem:

The very different stories of different groups are not simply just a matter of preference or taste. They are much more crucial and central than that. The stories portray how people should act; they specify good and bad values. When cultures collide, the fact that their very different stories encapsulate very different preferred modes of behavior often fosters suspicion, fear, hatred and disgust. People do not simply observe that others behave differently in terms of speech, dress, food, rituals, and so on. They perceive that the others are doing things, not just differently, but wrongly. The stories of the “in-group” can be used to rationalize exploitation, enslavement, or even genocide.

fullsizeoutput_1351

Forces:

  • Life is too complex, changing, and chaotic to describe completely in empirically falsifiable scientific statements.
  • Learning from others who have relevant experience can shorten learning time.
  • Humans are social creatures who can feel empathy for others.
  • Cultures use stories as memorable and succinct ways to encapsulate lessons learned and inculcate the proper values in the young.
  • Because stories encapsulate much of a culture’s knowledge, members of the culture habitually do what is prescribed by stories and avoid what the stories proscribe. In this way, they can focus decision making among a much smaller set of possibilities and not be perpetually at a loss as to what to do.
  • Because stories are valuable guides for the individual, they are reluctant to change those stories. If learned early, contradictory evidence is then particularly ineffective at altering or discarding stories.
  • When people in the “in-group” perceive those in the “out-group” as behaving “badly” (not doing what the stories say they should), trust is ruined and cooperative action is nearly impossible.

Solution:

Whenever two or more groups with different stories must work cooperatively for mutual benefit, create and promulgate new stories that stress the commonalities among the groups rather than stressing differences. In more detail, one way to do this is to collect important, value-laden stories from each group; find the common values expressed; generate stories that stress these common values; and then re-introduce these common values in the form of compelling, memorable common stories.

pexels-photo-874207.jpeg

Examples: 

  1. Two people from very different cultures fall in love. Individually, they find that their love supersedes any feelings of disrespect for the way the other eats, dresses, speaks, etc. In fact, the difference may even be part of the attraction. However, the two families each experience discomfort when confronted with someone who is so different from what they are used to. In some cases, the couple may simply convince their families to accept their choice of mate. In other cases, as in Romeo and Juliet or West Side Story, love ends in tragedy. In other cases, they would work together by each learning more of the stories of their partner’s culture and find, among those stories, common values. They may find or create stories that stress these common values and relate those back to their families. A nice illustration of this is in the movie, The Hundred-Foot Journey in which two families from very different cultures come together over their skills and love of fine cooking.

2. In a corporate reorganization, both the Marketing and the R&D Departments are put under one executive whose job is to speed to market a stream of innovative new products. Among the factors that make this a difficult task is the fact that Marketing and R&D have different values, culture, and success stories. Of course, it will help if they are rewarded only for mutual success. But even this may not be enough. It will help to find and promulgate common stories that stress common, rather than different, values. Marketing people may typically dress more sharply than R&D people and put more emphasis on flash and dazzle. But stressing that will hardly encourage better cooperation. Instead, it will work better to stress, for example, persistence, originality and being willing to change based on feedback. These are values that are important for success in R&D and for success in Marketing. The story of Thomas Edison (light bulb; lead storage battery) and Ray Kroc (McDonald’s franchise) for instance, both show that success comes with persistence in the face of repeated failure.

3. Two companies merge. Let’s say one (a sports-focused media company) has a corporate culture that stresses work hard/play hard while the other (a sports-focused engineering company) culture stresses work hard/family time. If it’s really important for the two cultures to merge and then work together, promoting stories about the outrageous parties and wild orgies that the first company participates in will not be helpful. Instead, it will be good to find stories from both companies that stress the “work hard” part. Since both companies are concerned with sports, the settings and characters from stories can both utilize sports. But the values that are stressed should relate to working hard and the resultant rewards.

pexels-photo-139681.jpeg

4. Many nations in an entire region of the world; e.g., Europe, are sick of centuries of war and counter-productive bickering and the inefficiency that comes of contradictory rules and regulations on transportation, environmental protections and so on. Despite different cuisines, traditional dress, and languages, they wish to be able to cooperate more effectively. In furtherance of that goal, they form a “European Union” which promotes the freer interchange of products, ideas, and people. Together, they constitute a formidable trading block and military force. It is important in such an effort to find stories that stress commonalities and then make sure these are prominently communicated among all the members. By contrast, an agent who wants to weaken or divide such a union would promulgate stories, even false stories, that stress differences.

Resulting Context:

Once a newly merged group shares a common story or set of stories stressing common values, they are much more likely to experience a higher degree of trust. This will make interactions more pleasant in terms of the on-going experiences but will also result in more effective action in meeting common or overlapping goals.

Related Patterns: 

Build from Common Ground.

References: 

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

Darwent, S., Incledon, F., Keller, N., Kurtz, C., Snowden, D., Thomas, J.(2002) YOR920000749US2 Story-based organizational assessment and effect system (granted).

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. (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. (1999) Narrative technology and the new millennium. Knowledge Management Journal, 2(9), 14-17.

Author Page on Amazon:

Author Page

Narrative Insight Method

16 Monday Apr 2018

Posted by in management, psychology, story, Uncategorized

≈ 1 Comment

Tags

, , , , , , , ,

Narrative Insight Method

fullsizeoutput_1335

Prolog/Acknowledgement: 

Since my dad worked mainly as an electrical engineer and my mother as an English/Drama teacher, I’ve always felt pulled in two directions: toward science, mathematics, systemization, practical solutions, and formalism and simultaneously toward the arts, particularly various types of storytelling. I finally had a chance to synthesize these two areas while managing a project for several years at IBM Research on the business uses of stories and storytelling. Though this project provided value in various ways to many within IBM, there was no single part of IBM whose main business was stories. For this reason, finding funding was a continual challenge. Our closest allies, apart from my senior manager, Colin Harrison, were The IBM Knowledge Management Institute, researchers at LOTUS, and a part of IBM internal education located in Atlanta. My group at IBM Research included Carl Tait, Andrew Gordon, Cynthia Kurtz, Debbie Lawrence, and Frank Elio. Larry Prusak and David Snowden from the IBM Knowledge Management Institute were particularly interested in stories as were Michael Muller, Dan Gruen, and Larry Moody at LOTUS. The method described here was mainly developed by Cynthia Kurtz, Dave Snowden, and Neal Keller of IBM Research Education though writing the method as a “Pattern” is my own responsibility.

Author, reviewer and revision dates: 

Created originally by John C. Thomas in January of 2002, and revised substantially during April, 2018.

MikeandStatue

Synonyms: 

Story Circles.

Abstract: 

Experts learn valuable lessons from their experiences. Such lessons can guide less experienced people. In small trusted groups, a natural, effective, and traditional way for experts to share their knowledge is to trade stories (See, e.g., Orr, 1990, Talking about Machines). A challenge for large organizations is to extend this process to larger groups and non-co-located personnel. Writing stories is a possibility; however, in many cases experts are too busy to write stories and find the process of writing stories difficult and unnatural as compared with telling stories. The method describes here minimizes the time of the expert, allows them to tell stories in a natural setting and organizes the knowledge in a useful manner.

Basically, about 12-24 people who are all interested in a topic but have various levels of experience are brought together for an hour. After a short introduction, the large group is subdivided into smaller groups of 3-5 people each, making sure that each group includes at least one experienced person and at least one less expert. For about 35 minutes, the group tells stories about their experiences and these are recorded for later transcription and analysis. The small group decides which story would be best to share with the larger group. The “best” story from each subgroup is shared with the larger group and this is followed by a short discussion. This plenary session is also recorded. People are thanked for their participation and given some sort of very nominal gift or memento.

OLYMPUS DIGITAL CAMERA

Context: 

Within societies and organizations, people generally differentiate into specialties. Many of these specialties require years of training and experience before people reach maximum effectiveness. In most societies, mechanisms have been set up so that those with more experience can help those with less experience learn more effectively and efficiently than if every generation had to learn completely on their own. People tell stories for many reasons, but one major use of stories is to help create and share knowledge across levels of expertise and across generations.

Less expert people in a large organization or community of practice typically want to learn from more experienced people. This is beneficial for the individuals as well as for the larger organization or community of practice. In modern societies, many of the people who have relevant knowledge are physically distant from the people who need the knowledge. In many cases, much of the most valuable knowledge of experts is tacit knowledge.

An organization typically has people available who may not be expert in the subject matter but have relatively more expertise in writing stories and organizing educational materials. The experts in a given subject matter are typically very busy and in most cases, may lack both the skills and the time to produce good written stories.

IMG_1289

Problem:

Experts have valuable knowledge based on their experience. However, experts in organizations are typically very busy people. They are willing to share stories informally and orally but do not necessarily have the skill or patience to write stories. Moreover, it can be difficult to find stories relevant to a specific situation. In addition, stories often reveal lessons learned through the sharing of mistakes that were made by the experts. In fact, experienced people have generally made many mistakes through the course of their careers. They do not typically want to have all of these mistakes made public inside and outside of an organization.

If one is telling a story face to face, there are many cues about how the story is being received. The teller can sense whether the audience is understanding, interested, bored, or shocked for example. The teller can then adjust the story to suit the audience and the situation as they continue to tell the story. The writer of a story lacks this type of information to mold the story while it is being created.

iPhoneDownloadJan152013 526

Forces:

· The time of experts is valuable.

· Subject matter experts are typically not experts in producing educational materials.

· People expert in producing education materials need to gain access to high quality content.

· In many fields, much of the most important knowledge that experts gain through their experience is in the form of tacit knowledge.

· Tacit knowledge is not well communicated by formal methods but can often be well communicated by stories*.

· Experts telling stories of their relevant experiences orally to small groups that contain other experts as well as some novices comprises a natural way for experts to share experience.

· Storytelling occurs only when the social situation is right.

· Telling a story about one’s experiences increases the probability that someone else in a group will also share a story about their experiences.

· Producing written stories requires special skills.

· Experts who have experience relevant to novices may be remotely located from them.

· Different learners learn best at different rates, by different media, and in different styles.

· Since stories often reveal errors on the part of the storyteller, it can be important in competitive organizations to hide the identity of the storyteller while retaining the lessons learned.

IMG_4100

Solution:

Provide an informal setting conducive to storytelling; this is encouraged by several factors. 1. Provide non-standard seating arrangements with easily movable chairs. 2. Conduct in a room with an informal atmosphere. 3. The structure and content of the invitation should be friendly but make clear the importance of the activity. 4. Gather a commitment to participate, making sure people know their time commitment is for one hour only. 5. Provide friendly but clear reminders near the time of the session with an additional check on the commitment to participate. 6. Provide refreshments at the beginning of the meeting. 7. Limit participation to a group of 8 to 20. 8. Groups should include experts as well as people knowledgeable in the topic but less expert. 9. Set expectations both prior to and during the session that people will be sharing stories, (E.g., “We find that when a group of experts get together like this, they generally end up telling stories about their experiences.”). 10. Make the recording clear but not obtrusive, and modeling storytelling at the outset.

During the session itself: 1. Greet people warmly and thank them for coming. 2. Break people into 3-4 smaller groups. 3. Each group should include a facilitator/recorder. 4. Digitally record the sessions with separate high quality tape recorders for each subgroup. 5. Tell the subgroups that they will be sharing stories based on their experiences and that then the group will choose one story from each subgroup to share with the larger group. 6. Implement this plan. 7. Facilitate to gently guide people back to telling stories of concrete instances (as opposed, for instance, to making general statements or pronouncements). 8. After each subgroup shares its story with the whole group, allow discussion to continue, encouraging but not insisting on storytelling.

Examples:

  1. We used this methodology to provide learning materials in the form of stories for NOTES 5. Such stories were not focused on how to invoke specific functions but rather on how to use NOTES to enhance your work practices or enhance team coordination and communication.
  2. We used this methodology to develop stories about “boundary spanning skills.” This was used for R&D personnel from a number of diverse organizations interested in organizational learning.
  3. Finally, we also used this method to develop learning materials for the IBM Patent Process based on multiple sessions.

Resulting Context:

After such sessions, it is necessary for the tapes to be transcribed and for analysts to find the lessons learned. The stories leading to the lessons learned were also included in shortened and anonymized format. In the case of the learning materials for the IBM Patent Process, the learning materials were in the form of Guided Exploration Cards. This form of documentation was originally developed by John Carroll and colleagues for product documentation. (See The Nurnberg Funnel, John Carroll, in references).  In other situations, stories and their lessons could be arranged in other ways.

While the intended “product” of using this method with respect to materials for “how to” produce patents were the Guided Exploration Cards, it also happened that master inventors and more novice inventors who were initially brought together for this exercise subsequently began additional fruitful collaborations and consultations. Indeed, sharing stories may typically have the effect of increasing group cohesion in the longer term as well as providing lessons learned.

IMG_4945

References: 

Carroll, J. M. (1990), The Nurnberg Funnel: designing minimalist instruction for practical computer skill. Cambridge, MA: MIT Press.

Orr, J. (1996), Talking about machines: an ethnography of a modern job. Ithaca, NY: ILR Press. (Available on Amazon).

https://www.amazon.com/Talking-about-Machines-Ethnography-Collection/dp/0801483905

*Thomas, J., Kellogg, W., & Erickson, T. (2001), The Knowledge Management Puzzle: Human and Social Factors in Knowledge Management. IBM Systems Journal, 40(4):863 – 884.

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

Author Page on Amazon:

https://www.amazon.com/author/truthtable

Indian Wells Tennis Tournament

19 Monday Mar 2018

Posted by in management, sports, Uncategorized

≈ 6 Comments

Tags

, , , , , , , , ,

IMG_2778

This blog post is a short break from my attempts to build a “Pattern Language” of best practices for teamwork, collaboration, coordination, and cooperation. I wish to re-iterate why I feel the enterprise is important. I have been attending the  Indian Wells tennis tournament and watched some amazing matches. While it’s tempting to write about the matches, I will leave that aside. What struck me about the tournament, aside from the athleticism and grit of the players, was the widespread and effective teamwork, collaboration, coordination, and cooperation that the tournament represents. This is obviously related to the Pattern Language because it gives an example of what can result from excellent teamwork and cooperation. In other words, this tennis tournament is just one illustration of why it matters.

IMG_2764

It’s nicer in some ways to sit in your living room and watch sporting events on TV. You don’t have to deal with glaring hot sun at noon or chilly winds in the evening. You can get up to hit the bathroom any time you want and snacks are right there in the kitchen. However, you do not get a feel for just how incredible is the athletic ability of the players nor the velocity and precision of the shots when you watch on TV. More important in the context of cooperation is that when you watch on TV, every time there is a break in the action, you are treated to commercials. When you are at the actual venue, however, there is also ample opportunity for observing a little bit of the incredible collaboration and teamwork that an event like this requires. Even at the venue, all you see is the snow that dusts the surface of that tenth of the iceberg that rises above the ocean. With a little imagination, you can get an inkling of how much more collaboration must be required that you do not see.

IMG_2773

The reason I want to dwell on this for just a little is that collaboration and cooperation permeate a healthy society. Indeed, widespread collaboration and cooperation are critical for society’s existence. Yet, it is easy to take cooperation for granted like the air we breathe. People like me, who have lived almost their lives in peaceful and kind circumstances, may easily forget that it need not be so. People have lived in circumstances of war, oppression, and slavery. We should never take cooperation for granted. Even in a very peaceful circumstances, there are many screw-ups in collaboration and while we notice the screw-ups when they affect us directly, we tend not to realize the vast interconnected threads of collaboration and cooperation that we rely on every day.

IMG_2823

Let’s return then to the Indian Wells tennis tournament and examine just a few of the many collaborative aspects. First, there are the professional athletes, of course. Let’s return to this later, to understand a little of the massive cooperation required for there to be professional athletes in general and what’s required in cooperation to make any particular athlete operate at their amazing level of skill. What other roles are there? Possibly coaches, trainers, officials, and the ball boys and ball girls come to mind. It’s quite likely that if you watch tennis (or any other sport) on TV, one of the most salient roles is that of the TV announcers. They are a major part of most people’s experience of pro sports. Yet, when you are actually at the venue, they are relatively invisible. If we watch TV, we are cooperating in making the TV announcer a major part of our sports experience.

IMG_2810

At the venue itself, there are many other obvious roles. There are police assigned to the area. There are hundreds of volunteers who help people park, answer questions, check bags and check tickets. There are vendors selling various wares as well as offering up a variety of food items. This is all much more obvious when you attend a sports event in person. But the cooperation doesn’t stop there. How do the clothing and food get to the venue? How are we able to eat food that is grown far away and sometimes packaged? Where did the recipes come from? Why do people share recipes? At this point in our cultural evolution, you can attend an event in Southern California and enjoy some excellent Japanese food at Nobu. Japanese speak Japanese. And Japan is more than 5000 miles away. So, somehow, through a giant network of collaborative and cooperative relationships, people in Southern California are able to produce delicious meals that reflect a cuisine developed in a different culture with a different language. Of course, Japanese is not the only cuisine represented at the venue. There are hundreds of options that originated elsewhere.

There is also clothing on offer, much of it designed in one place, manufactured in another place, and shipped via complex supply chains. You can buy it with a credit card. But how does that work? You guessed it. It works because of other giant networks of cooperation and trust. Yes, it’s true that some people steal credit cards and there are elaborate systems to minimize losses but even those elaborate systems work on trust.

IMG_2791

The venue comprises parking, stadiums, parks, practice courts, with running water and electricity, working toilets, wheelchair access, and gates for crowd control. Again, the existence of the venue requires widespread cooperation among various levels of government, financial institutions, tennis organizations, volunteer organizations, and fans. But it isn’t even just contemporary cooperation that’s involved. These kinds of large scale venues go back in our history thousands of years. We’ve been collaboratively building best practices in city planning, architecture, crowd control, with many idea exchanges across cultures. We must remember that, by and large, the fans also cooperate. They don’t simply mob the gates to crash in without paying. The vast majority of fans are quiet during actual play, sit in their assigned seats, get up to allow others to pass and so on. This kind of cooperation also depends, in part, on widespread public education in how to be civil.

IMG_2811

Let’s return for a moment now to consider that our society has professional athletes. Some people make a career out of playing a sport extremely well. But playing the game extremely well does not, in and of itself, enable professional athletics to exist. There have to be fans both at the venue and watching TV who pay, either with dollars or with taxes or with their attention to commercials. There are organizations who administer the sport. There are, in this example, thousands of coaches and tennis venues to develop the sport and spot prodigies early who then receive additional coaching and training. There are ranking systems and systems to seed players in tournaments. There are manufacturers who make tennis balls and tennis racquets which have evolved over time to allow more elegant play which pushes the game toward more extremes of human performance. This kind of evolution of artifacts does not happen “automatically.” It too requires communication and cooperation.

IMG_2787

Indian Wells is just one event in one sport. If you dig beneath the surface just a little, you will see that nearly everything on the planet is the result of thousands of years of mainly cooperative enterprise. Of course, the players compete. They try their hardest to win. But they try to win within an agreed upon set of rules and regulations. If no-one followed the rules, there would be nothing very interesting to watch. If you’ve seen one bar fight, you’ve seen them all. There is no elegance and no beauty in watching thugs slug it out and waste time and resources. I dwell on this because it is critical to keep in mind that having a decent society that helps people thrive depends on having cooperation, teamwork, collaboration, and coordination. The individual human brain may be relatively large compared to an ape’s. But what really sets us apart is not our individual intelligence. Abandon a baby with a perfectly good brain into a forest by themselves and, if they survive at all, they will not behave much differently from an ape or a raccoon. They may scrabble for food and water, but they will not end up building a tennis court or constructing a tennis racquet.

IMG_2816

It’s not turtles all the way down. It’s trust. It’s cooperation. That’s what makes us human. If we just grab everything for ourselves and lie about it, it subverts the very foundation of human life. Our human nature is to control our competition to acting within agreed upon boundaries for the good of all. If we forget that, we are not “lowering ourselves” to the level of wild animals. We are way below that. We are like a wild cat who refuses to use its hearing and fast reflexes to hunt. We are like a redwood tree who refuses to use the sun’s rays. We are like a deer in the forest who refuses to forage but instead expects other deer to bring them food. Willfully ignoring that we are a social species; intentionally lying in order to gain advantage to ourselves will never help create a bigger pie. In the short term, it can get you a bigger piece. But the cost is that you despoil what it means to be human. Grabbing all you can for yourself subverts the very essence of what makes humanity such a successful species. This has always been true throughout human history. Now, however, cooperation is more vital than ever both because we are on the brink of destroying the ecosystem we depend on for life itself and because we have even more brutally destructive weapons than ever before. We have cooperated through much of our human history. Now, we need to do it even more intelligently and more consistently — or face extinction. The earth doesn’t need us. But we need the earth. And, each other.

IMG_2818———————————————————

Author Page on Amazon: https://www.amazon.com/author/truthtable

Build from Common Ground

25 Sunday Feb 2018

Posted by in America, psychology, sports, Uncategorized

≈ 6 Comments

Tags

, , , , , , , , ,

OLYMPUS DIGITAL CAMERA

CHI Workshop Activity: Working Together to Create World Map (Florence, 2008)

Build From Common Ground

Prolog/Acknowledgement: 

The idea for this Pattern comes from long personal experience trying in many contexts to get to solutions quickly without first bothering to try to find common ground. In addition, I am working on a project to provide a platform to support civil discussion, debate, Dialogue, and deliberations. One of the other founders has a long history with The Interactivity Foundation which also uses various methods to build from common ground.

Author, reviewer and revision dates: 

Created by John C. Thomas on February 20-25, 2018

IMG_2979

Synonyms: 

Abstract: 

Human beings share a large majority of their genes. Life on earth began 4.75 billion years ago. Only around 100,000 years ago people began migrating out of Africa, going to different places and evolving different cultures, religions, and languages. In addition to our long common history, people across the globe want many of the same things: freedom, food, water, safety, love, friendship, a space to be themselves, a life with some pleasure and a sense of meaning or higher purpose.

In the so-called developed world, there is an emphasis on doing things as quickly and efficiently as possible. To accomplish that, many people are extremely specialized in their education and profession in addition to whatever differences they have in culture and family background. Often, in a highly populated, highly interconnected world, people must collaborate and cooperate at a very large scale. Since some of the problems we face (e.g., preventing atomic war; preventing plagues; reducing global climate change) are vital, people are passionate about getting to solutions. They want to do this quickly. There is often a natural tendency to focus immediately on the problem as initially defined, and then to focus on differences and to resolve those differences as quickly and efficiently as possible. This does not generally work. People are invested in their own solutions which depend on their own background and experiences in their various cultures, families, education and training. Focusing from the onset on differences sets up a competitive mindset which then has everyone thinking how to “win” against their competitors. Unlike athletic competitions, people are unlikely even to agree initially on the “rules” for deliberations and debate, and often have pre-existing “positions” to sell to everyone else or force on everyone else.

Therefore, for any group trying to solve a problem collaboratively, it works better to first identify and build on common ground. Later, after some degree of trust is established, people may (or may not) find it useful to examine as well their differences as a source of ideas for how to solve the larger problem.  They may choose from a variety of methods to make progress. Starting with common ground can help everyone involved to see that they are all part of one big and quite similar “in-group” with a problem to solve rather than focusing on everyone else as being in an “out-group” that needs to be defended against.

IMG_3240

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 usually develop if warranted. This is what happens in most (but not all) work groups, teams, standing committees, etc. However, it often happens that other problems need to be understood and solved by groups that span pre-existing organizations. For example, a town needs to collectively decide whether to sell a beautiful community park to a mall developer who promises tax revenue and convenient shopping for the town. A state needs to decide whether to legalize marijuana or to ban assault weapons. A nation needs to decide whether or not to work with other nations to reduce air and water pollution. People addressing such issues will often have to address them in combination with others that they do not already know well and may not trust.

Often such decisions as those mentioned above must be made under some time pressure. Some people will have vested interests in a “solution” that is particularly favorable to them regardless of how much it hurts others. When people begin by stating their own position and trying to “sell it” to others, an adversarial atmosphere is created so that “winning” rather than “solving” becomes the dominant tone of subsequent conversations and actions. This almost always results in sub-optimal solutions and, in addition, almost always results in reducing trust and social capital among the people deciding.

Even under the best of circumstances, with everyone committed to finding a “good” solution for all, people will tend to misunderstand each other simply because language is ambiguous and vague. People have different assumptions based on their experiences, culture, and training what process to follow as well as what constitutes acceptable rules and boundaries. If we add to these inherent difficulties the further (and avoidable) difficulty that people are focused on the ways people are different, it will tend to prevent mutual trust and prevent the emergence of new ways to find, formulate and solve the problems at hand.

IMG_5159

Context: 

Complex problems can often only be solved by groups. Even when the nature of the problem is simple enough for one person to solve, people want to feel that they or their representatives are engaged in the process if the outcome will impact them. For the group to work well together to solve problems, it is useful for them to understand each other’s situations and motivations. When in a hurry or under stress, people often perceive others and their motivations, not on the basis of inquiry into what those are but on group membership and the way that group differentiates itself from other groups.

Our nervous systems (and those of other animals) are constructed to be particularly sensitive to differences and changes. Our education and society teach us to differentiate as much as possible. We celebrate the wine connoisseur who can tell you the year and vineyard and scoff at the person who simply says, “I like all wine.” Sometimes, of course, fine differentiation is critical, particularly for an omnivore. We need, for instance, to be able to differentiate the three leaves of a wild strawberry from the three leaves of poison ivy. In biology class, we get high grades for correctly labeling 100 different parts of the earthworm and get no credit for simply saying, “Look! These are all parts of an earthworm! How cool! I had no idea it was that complex inside or that it has so many of the same parts we do!” In many contexts, being able to further differentiate things is a good thing. Even in group problem solving, there are situations where this is true. However, we typically do not ask ourselves whether this is one of those situations. We tend to dive unthinkingly into exploring differences.

Forces:

  • Our brains are not infinite but finite. We, along with other animals, generally focus on foreground while ignoring or presuming the background. Our nervous system is especially tuned to differences and changes, not to similarities and constancies.
  • Our educational systems typically focuses on teaching people to make even finer and further differentiations beyond what our senses immediately show.
  • Societies typically celebrate finding additional differences rather than finding additional similarities. Experts are typically defined by their ability to detect differences rather than their ability to see similarities.
  • People are quintessentially social animals. Therefore we tend to join groups. Each group coheres around a group identity which tends to define itself in terms of differences from other groups and seldom mentions similarities.
  • Each person only knows a small proportion of another person’s situation and individuality. Often, we treat each person according to their differentiating group membership(s) rather than their similarities to ourselves or according to the complexity of their individual selves.

Solution:

When a group begins to address a situation that impacts many people in various ways, and especially if people already have opinions and positions on the situation, begin by stressing, creating, or fostering their common ground before even starting any other problem solving activity.

OLYMPUS DIGITAL CAMERA

Sharing a Meal at CHI 2008 Workshop

Examples: 

1. At IBM Research, for several years, I managed a research project on the “business uses of stories and storytelling.” I worked with a small team of researchers & consultants to develop tools and techniques. One patent (Story-based organizational assessment and effect system) was originally inspired by trying to help companies involved in mergers and acquisitions deal with cultural differences between companies. The suggested technique essentially involved collecting stories from the two original companies, analyzing them for the underlying values that were expressed in the stories, finding common values in the stories from both original companies, creating new stories using the values and situations from the originals but making sure the new stories were constructed to be memorable and motivating; and finally re-introducing these stories to the people from both companies. The reason for this whole process was to stress common ground so that people from two companies could work better together.

StoryPatent

2. At a workshop at the 1992 ACM Conference on Human Factors in Computing Systems (CHI ’92), I co-organized and co-led a workshop on “Cross-cultural issues in HCI.” At the beginning of the workshop, the participants entered the assigned workshop room to find that it had been set up in a “classroom style” with one small table and two chairs at the front of the room and all the other chairs and desks set up for the “listeners.” We wanted the room set up as a large circle. Everyone pitched in to re-arrange the room into this large circle. This physical activity provided additional common ground for the team. One outcome of the Pattern “Small Successes Early” is to provide common ground. Having people work together to perform a physical task is one way to establish common ground.

We also played a game called “Barnga.” In my introduction to the game, I explained that it was much like Bridge, Whist, or Euchre. To my surprise, none of the participants attending from Asia had any idea how to play such games or what I meant by “tricks” or “following suit.” That experience illustrates how easy it is (at least for me!) to over-estimate how much common ground exists in a group.  (http://www.acadiau.ca/~dreid/games/Game_descriptions/Barnga1.htm)

In a later workshop (2008) on “Human Computer Interaction for International Development,” at the suggestion of Andy Dearden, we began by cooperatively building a map of the world from materials at hand (illustrated above) before delving into the details of the workshop. Starting with this as “common ground” we then explored some of our differences by standing on the representation of where we were from, a favorite place we had visited, a place we wanted to visit, etc.

3. Religions regularly practice rites and rituals. For practitioners of the religion, this provides common ground regardless of a host of differences among the adherents. Of course, it is a double-edged sword because differences among these rites and rituals can also separate people. One of the more brilliant scenes from West Wing cuts among scenes of people attending religions services that are variously Jewish, Muslim, and Christian while the viewer knows that there is an unsuccessful peace effort underway. In this case, the uncommented footage helps to illustrate the common ground among these three religions.

earthfromspace

4. The Family of Man was both an ambitious photography exhibit and a book (definitely worth buying) that portrays people across the world to illustrate precisely that we do have common ground.

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

5. In an earlier blog post, I showed with back of the envelope calculations just how “related” humanity is in terms of genetics, experience, ideas, and matter. In fact, all of life on earth is highly inter-related and it has been for its entire 4.75 billion years.

https://petersironwood.wordpress.com/2017/03/09/math-class-who-are-you/

6. In a recent episode of the TV series, Madam Secretary, the Secretary of State is trying to resolve a conflict between two nations A and B. The diplomats from A say they cannot trust B and the diplomats from B say that they cannot trust A. She suggests that they start from their mutual distrust as part of common ground. In other words, rather than treating the mistrust of A and B as two separate issues, she begins by suggesting that A and B both share two things in common: not only a desire for peace but also a difficulty in trusting the other side. Even mutual distrust can be framed as a basis for common ground. This is more than a linguistic trick. It is an important reframing. It may well turn out that a single event such as a soccer game with teams that have members from both nations may help reduce mistrust on both sides at the same time.

7. Holiday celebrations, the preparation and consumption of food, listening to music, or appreciating the beauty of nature may all provide additional ways of beginning with common ground. Of course, there are cultural differences in all of these as well so one must take some care to provide something that actually is common ground and not something that tends to emphasize the differences among people in these activities.

8. One of the plenary speakers at CHI 1989 in Austin Texas was an astronaut who had been in space. I spoke with him after and during our conversation, he claimed that all astronauts, whatever country they were from, shared the same experience of seeing earth from space; viz., that the national boundaries we typically think so much about were only political; most are not physical. He said all the astronauts were struck by how thin and fragile our atmosphere is and that the earth is the only place around that is capable of sustain the breadth and depth of life. Many of them found this realization of “common ground” the most transformative of all their experiences in the space program.

Resulting Context:

Once people experience common ground, they may still disagree, debate, discuss, or hopefully dialogue in order to identify issues and problems. Experiencing common ground makes it harder to “dehumanize” the other side. It decreases the chances that people will engage in counter-productive actions such as “name calling” or using propaganda techniques to “prove” that they are right and their “opponents” are wrong.

Rationale:

Actions are always better based on reality than on fantasy. Reality is that people share much in common. Reality is that there are also many remaining differences. The entire problem solving process (including problem finding, problem formulation all the way through to finding issues with solutions and re-solving, re-negotiating, re-designing, or re-developing a solution) is enhanced when it is based on a balanced view that includes both real similarities and real differences. We already have a culture and an educational system that focuses on differences. Focusing on common ground is a critical factor in balancing our view so that we do not try to solve problems based on the partial truth that we are all different.

Related Patterns: 

Reality Check, Check-In, Small Successes Early.

Metaphors: 

It is a windy day in San Diego as I write this. We have a set of wind chimes outside the bedroom. Whichever direction the wind blows; however windy it gets (within bounds); and even if the wind is quite chaotic, the sound that emerges is always harmonic and tuneful. This is because of the structure and relationships of the chimes. It would be nice if we could have a platform that encouraged and promoted civility. I think that could work because of the nature of the platform. One of the “chimes” could be Bohm Dialogue; another could be “Building from Common Ground.”

Another musical example is Jazz Improvisation. If a group of musicians who know each other get together, they can improvise some very nice music. If they’ve never met, they will almost certainly agree on a few boundaries before beginning such as style, time signature, key signature. They may well start by having the percussion set up a “beat” that everyone relates to.

Now, imagine instead that seven random people are thrown together from seven different cultures. Each has an instrument that none of the others has ever seen. They have completely different musical experiences and expectations. Does it not make sense that they will take more time to converge on anything good? Doesn’t it seem as though they first need to discover some kind of common ground in terms of scales, rhythms, degree of repetition before achieving a good result? Or, do you think they should argue about which kind of music is best first? Do you think any of the seven will be able to convince the other six that “their” kind of music is superior? Suppose instead of having as one mutual goal making good music, instead, they are in a contest and only one of them will “win” and go on to the next round. Surely, this will only further confound any possible teamwork. Add to this, that they only have two minutes. What kind of performance would you expect now? And, yet, we seem to expect people from very different backgrounds to get on-line and instantly “make good music together.” Whether it’s 140 characters, 280 characters or a whole paragraph, it seems unlikely you will be able to sway anyone to move from “their position” to “your position.”

IMG_3524

International sports competitions such as the Olympics provide a setting where people from around the world get together and compete. These are not random people; they are all immensely talented and skilled; however, they are also all highly competitive. Yet, the venue provides a framework for competition that provides a structure for competing within common ground. Despite being from different cultures and using different languages, the athletes push each other to amazing performances with a minimum of rancor. Every athlete realizes as well that every other athlete has also gone through a rigorous selection and training process involving many sacrifices to get where they are — more common ground. The Olympics might be thought of as a particularly interesting example of finding common ground despite people having different backgrounds, language, and goals. Sports may also be thought of as a compelling metaphor. When politics are reported in the media, they are most often treated as a sporting event. But it is a strange kind of sporting event in that such reporting seldom stresses common ground and instead focuses on strategy, polls, winning, losing, and differences. It almost never reports on common ground in politics. In reporting on actual sporting events, however, the reporting focus often does cover the common ground that athletes face; e.g., the training, the dedication, the sacrifices that families must make, the importance of coaching, etc.

References: 

https://www.goodreads.com/book/show/197193.The_Family_of_Man

https://www.johngraham.org/coach/17-finding-common-ground-negotiating-and-resolving-conflicts-part-i

http://www.tandfonline.com/doi/full/10.1080/03057267.2016.1206351

http://journals.sagepub.com/doi/abs/10.1177/1049732306289705

https://www.researchgate.net/publication/221517384_Video_Helps_Remote_Work_Speakers_Who_Need_to_Negotiate_Common_Ground_Benefit_from_Seeing_Each_Other

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. & Kellogg, W. (1993). Cross-cultural perspectives on human-computer interaction: report on the CHI ’92 workshop. SIGCHI Bulletin, 25 (2), 40-45.

 

Context-Setting Entrance

13 Tuesday Feb 2018

Posted by in management, psychology, Uncategorized

≈ 8 Comments

Tags

, , , , , , ,

IMG_2566

 

Context Setting Entrance

Prolog/Acknowledgement/History: 

It occurs to me that some readers would like to know more about Pattern Languages; the pros and cons; pointers to the research; perhaps, how to write (or find) Patterns. I will do that soon on the basis of my current understanding. I’d like to put out a few more examples first though. I find that concepts such as “Pattern” and “Pattern Language” are much better defined by example than by rule. In the meantime, here below are some pointers to give a better flavor of what this odd creature, A Pattern Language, actually looks like and whether it can be housebroken or used for hunting. As you can tell by the list below, I have tried this creature in many different circumstances. To me, it seems quite happy and affectionate. I think that when it comes to trying to work with Pattern Languages, it is necessary to treat it something like a puppy. Your attitude will be an even more important a predictor of your success than your cleverness or knowledge of the Patterns.

Let every Pattern be “frisky” and let each Pattern explore and check out odd corners of the domain (and each other). There are cases where a Pattern doesn’t apply and there are cases where no Pattern applies just as your puppy can’t do anything they want. And, there are a few places where Pattern Languages are not at all appropriate just as there are places where no pets are allowed. For example, some situations are well enough understood that they can be characterized by a mathematical formula. No need for a Pattern (or a puppy) there, though it could still be fun.

https://www.slideshare.net/John_C_Thomas/toward-a-sociotechnical-pattern-language

https://www.slideshare.net/John_C_Thomas/ppdd-copy?qid=2852eb5e-9639-44e0-b648-eb46defc0721&v=&b=&from_search=1

https://www.slideshare.net/John_C_Thomas/chi2006-workshop-paper-on-trust

https://www.slideshare.net/John_C_Thomas/chi2006-workshop-paper-on-trust

https://www.slideshare.net/John_C_Thomas/sigchi-extended-abstractsjct

http://www.cs.cmu.edu/~yangwan1/cscw2011/papers/cscw2011extendedabstractW7positionpaper-JCT.pdf

https://www.slideshare.net/John_C_Thomas/handover-jct

There are several “sources” of inspiration for this Pattern. First, I was struck by one of Christopher Alexander’s architectural Patterns because it resonated with one of my own pet peeves — modern buildings often give no clue as to where the blasted entrance is! Part of Pattern 110 – Main Entrance says the following:

“The entrance must be placed in such a way that people who approach the building see the entrance or some hint of where the entrance is, as soon as they see the building itself.” 

To this, I say, “Amen!”

Being able to know where the entrance is, of course, is somewhat different from saying the entrance should give a clue as to what sort of behavior is appropriate once inside. In terms of my own experience however, this Pattern of Alexander’s set me to thinking about the importance of entrances.

IMG_4127

At about the time I became aware of that Pattern, I was working at IBM Research and used a system that my wife and other friends at IBM developed called “Babble.” This was a mixed synchronous/asynchronous messaging system with wonderful functionality but a rather “unprofessional” look to it. Later, when she managed the group, she hired an extremely talented architect/designer and Babble was replaced with a much more beautiful system called Loops (as in “keeping people in the loop”). The functionality was quite similar but the second design was much more beautiful. Oddly, it never got quite so much use as the first system. I began to wonder whether it was so beautiful that people felt as though what they needed to be more formal, respectful, and serious when they wrote there.

At about the same time, I built a website with some nice graphics. This was a wiki meant for everyone in a community to use. Instead, what I got was email from people suggesting things I could add to the website. “No, it’s a wiki, I explained. You don’t need my permission. Just add what you want!” Very few takers. Later, I made it more “rough-looking” and people began adding material to it.

IMG_2884

While traditions in a culture condition us to expect certain kinds of behavior when we go to a dry cleaners, a pub, or a cathedral, it seems that when it came to electronic media, cues were often missing or misleading. In a later project to improve search on www.ibm.com, I noted and then explained to management that although IBM was trying to be the high price, high quality provider, their website looked, at that time (@2000) a lot more like K-Mart’s website than it did that of Harrods or Neiman Marcus. All of these specific situations led me to believe that context-setting entrances (e.g., splash screens and portals) were not being sufficiently accounted for in the design of electronic media.

Author, reviewer and revision dates: 

Created by John C. Thomas on February 13, 2018

Synonyms: 

Set Appropriate Expectations

Abstract: 

Human societies have widely different customs about what is appropriate behavior in different contexts. As people grow up in a culture, they learn when and where various actions and styles of behaving and talking are appropriate. When someone enters an unfamiliar setting, it is generally to everyone’s advantage that the new person has some idea about what is appropriate. Therefore, before the person even enters it is nice to provide the right emotional tone and mood appropriate to the current situation. In some cases, this can be done architecturally or musically. In other cases, people may be given a “program” which through typography, word choice, or images may set the tone for a gathering. By setting the context at the entrance, people understand better what is expected of them; it prevents their embarrassment and enhances the ritualistic aspects of the event as well as making the practical outcomes achieved more effectively.

Problem:

Groups function better when the people in the group behave within a set of norms. For example, at a golf match, there are specific roles for contestants, caddies, audience members, officials, vendors, and the press. Each of them is expected to play a particular role with respect to the tournament. In addition to that however, there are expectations about the appropriate style. In golf, as in tennis, it is expected that the audience be quiet during actual play. Baseball and football players as well as professional fighters talk trash to each other but tennis players and golfers typically do not. If people use the “wrong” norms for the occasion, they may be embarrassed as well as upsetting the rest of the group. In some cases, such as a church service, prom, funeral, wedding, or legal proceedings, failing to follow the norms may even tend to thwart the social binding purpose of the event. For example, many things that would be “appropriate” at the bachelor or bachelorette party right before a wedding would not be appropriate as part of the post-wedding toasts. Because there are “rules” even if just one person follows those rules, it diminishes the feeling of group cohesion for everyone. In some cases, violating the norms could also have considerable practical consequences. For example, if a small town has a barn-raising event and there are assigned roles and responsibilities, someone simply “winging it” or following some completely different process of home building could be frustrating, counter-productive, or dangerous.

Context: 

Cultures developed separately in many places around the world. Partly to adapt to specific conditions and partly by accident, these cultures developed different cultural practices. There are many cultures around the entire world who celebrate e.g., successes, conceptions, births, deaths, marriages, divorces, graduations, birthdays, coming of age, etc. Aside from rituals and special events, there are also particular places where one is expected to behave in a certain way or certain people such as royalty who are supposed to be addressed in certain ways. There are also particular holidays that precipitate particular behaviors, moods, rituals, etc.

To insure that everyone in the group or community knows what is expected of them, more experienced members of the group or community might conduct training, provide written materials,  to the less experience or perhaps even put some information on a “cheat sheet” of some kind.

Yet, there may always be the possibility of those without the training or instructions to become involved in a social situation with demanding rules. In such cases, it helps to set the context by the words, shapes, colors, music, architecture and thereby let people know what the proper tone should be for the occasion .

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. So, when someone behaves “badly” — too informally or too formally, for instance, many immediately think badly of them. And, they, in turn, through being embarrassed, think less of the group, event, ritual, etc. than they would have if they had simply been “clued in” as to what was expected.

OLYMPUS DIGITAL CAMERA

OLYMPUS DIGITAL CAMERA

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 past experiences.
  • The behavior of any other person is largely based on that person’s past experiences. 
  • People are particularly influenced in their perception of something new by their first experience.
  • Because modern cultures are often quite fluid, it often happens in the real world that people enter a Holiday, special event, ritual, building, or website that they are unfamiliar with.
  • When a person seems to be too uptight or too loose for the situation, we tend to make (and stick with) negative attributions about them.
  • When someone attempts to “fit in” to a new group or situation and fails because they couldn’t tell how they were supposed to act, they will tend to reject the group, event, or medium.
  • There are numerous clues that can be used to set a mood or predispose people to behave in certain ways.

Solution:

When designing a website, application, building, party, or basically anything at all, use cues at your disposal to let people know what sorts of behavior and what styles of behavior are appropriate.

IMG_5153

Examples: 

1. Motion picture use both imagery and music at the beginning to let the audience know what this movie is about and even presage how it will turn out. Consider for a moment the difference between the beginning of The Sound of Music and Jaws. In both cases, the imagery and the music are quite appropriate to the overall dramatic arc.

2. You enter a restaurant. Even before you are seated or look at a menu, based on the noise level, background music, architecture, how crowded it is, and how the people are dressed, you generally have a fairly good idea of what is appropriate and inappropriate conversation and behavior as well as what the price range is likely to be.

3. You see a book at the bookstore or on-line. Before buying the book, or indeed, even reading a few pages, you already have an impression based on the cover, the size and age of the book, the blurb, and the author’s profile what type of book this is to be. For example, and hopefully, the cover art of Turing’s Nightmares says: “This is science fiction” and “The world is going to be quite different.” The tone will be somewhat surprising and unpredictable On the other hand, the cover of The Winning Weekend Warrior” is going to be about victory and is set in the real world. The tone will be fun and happy. The dust jacket of Christopher Alexander’s A Pattern Language, looks to me quite formal and serious. It seems rather tome-like because of the sparseness of cover imagery, the typography and the presence of so many authors on the cover.

4. When it comes to social media, of course, a large part of what people “see” in the “entrance” are the posts, blogs, tweets, comments of other participants. If one wanted, for instance, to increase the chances that users were respectful, polite, or rude, one could alter the first few posts, blogs, tweets or comments that a new user saw and that could serve as a model for what was deemed most appropriate.

Resulting Context:

Generally speaking, a context setting entrance will help people behave more appropriately. This will result in less friction, fewer outcasts, greater group cohesion, and greater social capital. It may also help people choose more appropriately among various possible churches, movies, restaurants, movies and on-line venues.

Rationale:

Most people most of the time wish to act appropriately. Letting them know what that is increases the chances that they will be able to.

Related Patterns: 

Special Events. Greater Gathering.

Known Uses:

Metaphors: 

The strongest metaphor that leaps to mind are various “warnings” in the plant and animal kingdom; e.g., brightly colored poisonous snakes and tree frogs as well as “attractors” such as flowers use to attract bees and birds and fish use to attract potential mates.

IMG_9886 

References: 

Alexander, C., Ishikawa, S., Silverstein, M., Jacobsen, M., Fiksdahl-King, I. and Angel, S. (1977), A Pattern Language: Towns, Buildings, Construction. New York: Oxford University Press.

Thomas, J. (2015). The Winning Weekend Warrior: How to succeed at golf, tennis, baseball, football, basketball, hockey, volleyball, business, life, etc.  CreateSpace/Amazon.

Thomas, J. (2016). Turing’s Nightmares: Scenarios and Speculations about “The Singularity.” CreateSpace/Amazon.

IMG_0218

IMG_9850