Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 20, Issue 2;   January 8, 2020: Disjoint Awareness: Analysis

Disjoint Awareness: Analysis


Breaking large problems into smaller parts can sometimes create a set of risks that make solving the problem in pieces more difficult than solving it as a whole. But we can still profit from breaking the problem into parts if we manage those risks.
Braided streams in Grewingk Glacier River

Braided streams in Grewingk Glacier River, Kachemak Bay, Cook Inlet, Alaska, in June 2009. Rivers emanating from retreating glaciers carry large volumes of sediment, producing braided river patterns with multiple channels. Braided channels are variable and dynamic. The Alaska ShoreZone exhibition guide states: "Although the threshold between meandering (sinuous, single channel river pattern) and braiding is not clearly understood, three factors are probably necessary for braiding to occur: 1) an abundant bedload supply (portion of a river's sediment load supported by the channel bed), 2) erodible banks, and 3) high stream power (the potential energy for a given river channel length)."

An analogy suggests that braiding of work streams is more likely when 1) there's much work to do and more work becomes evident as the collaboration progresses, 2) work can be readily transferred from one work stream to the next, and 3) a high level of urgency limits the ability of the teams to carefully resolve the issues that arise. As is often the case, the forces of Nature, by example and metaphor, provide insight into human behavior.

Photo courtesy U.S. National Oceanic and Atmospheric Administration. Photo credit: Alaska ShoreZone.

In my latest two posts, I've been exploring what I call disjoint awareness — a state of a collaboration in which its members labor under differing views of what each other is doing or intending to do. Their different understandings about each other's work and intentions can be problematic because it can lead to their interfering with each other's attempts to reach their joint or individual objectives. In last week's post, I noted three factors related to the work itself that tend to enhance the likelihood of disjoint awareness. They are the complexity of the work, the specialization of the collaborators, and the pace of change within the collaboration or the context in which it takes place.

Also contributing to the formation and persistence of disjoint awareness is a widely used approach to problem solving known as analysis. Analysis is a standard way of attacking problems by which we break the problem into supposedly independent pieces (I'll call them work streams here). We than allocate responsibility for each work stream to an individual, team, department, division, subsidiary, or some other appropriate subunit of the entire collaboration. That is, in analysis, we reduce the problem to smaller, more manageable parts, and tackle the parts in parallel.

The method of analysis is very flexible, admitting of various ways of segmenting the work. For example, in a project, we decompose the total work into a set of tasks. The tasks have well-defined initiation criteria, objectives, initial inputs, deliverables, resources, schedules, budgets, and completion criteria. As a second example, in the operational context, we decompose the total work into (usually) functional units such as Administration, Development, Testing, Marketing, Sales, and so on. In some organizations, in the operational context, product, brand, customer, or channel define how we apply analysis to the entire operation.

To most people in modern organizations, analysis seems sensible and workable. And for many problems, it is. But there are difficulties. Typically, when these difficulties arise, we hold responsible the people who are doing the work. In this post, I argue that many difficulties arise not because of the behavior of the people doing the work, but instead because those difficulties are inherent in the choice to use the analytic approach to the work. It is analysis itself that leads to many of these difficulties. And often, analysis "accomplishes" this feat by creating conditions that lead to disjoint awareness.

At least four kinds of difficulties arise when we use analysis to address large, complex packages of work: boundary ambiguity, incomplete coverage, unanticipated work stream interactions, and what I'll call illusory factorability.

Boundary ambiguity
Boundary Problems arise not because of the
behavior of the people doing the
work, but instead because of the
choice to use the analytic approach
ambiguity arises when those responsible for different work streams disagree about who has responsibility for what. Using the concept of the Johari window, we can classify these boundary ambiguities in a way that's useful for resolving them.
Suppose two teams, A and B, harbor disagreements about which team is responsible for a given piece of the work I'll call W. From the perspective of Team A, and using the Johari Widow, the disagreement can be Open, Blind, Hidden, or Unknown. An Open ambiguity is one in which the teams both know that they're taking differing positions about which team is responsible for W. A Blind ambiguity is one in which Team A is unaware that Team B has a differing view of which team is responsible for W. A Hidden ambiguity is one in which Team A conceals the fact that Team A disagrees with Team B about which team is responsible. And an Unknown ambiguity is one in which neither Team A nor Team B realizes that they disagree about which team is responsible.
All four states exhibit disjoint awareness in that there is disagreement about responsibility allocation. But to complicate matters, Blind, Hidden, and Unknown ambiguities also exhibit disjoint awareness with respect to the disagreement itself.
Open ambiguities are subject to resolution politically. But the others cannot be resolved until they're converted to Open ambiguities. Either A or B or some other party must initiate a conversation that can lead to clarifying the situation.
Because toxic conflict is possible with Blind, Hidden, or Unknown ambiguities, working to bring them into the open offers the best hope for beneficial resolution.
Incomplete coverage
Incomplete coverage arises when a piece of necessary work is omitted from all defined work streams. When this happens inadvertently, resolution is relatively straightforward, although budget and schedule adjustments might be necessary.
But omissions are sometimes intentional or the result of a bias, especially when the omitted work is undesirable or risky. In these cases, omissions can be indicators of organizational dysfunction. Dealing with such omissions is likely to be ineffective until the dysfunction is addressed.
Unanticipated interactions
Unanticipated interactions between work streams can occur at the level of the actual work. They can also arise in other dimensions, such as resource contention or schedule conflicts. Political resolution of these interactions is usually straightforward when all parties are components of one political unit. More problematic are virtual collaborations that extend across multiple political units and work streams. Interactions in the virtual context must be resolved at the lowest level of the collaboration that's responsible for all contenders.
Unanticipated interactions can also appear in "lock up" configurations in which A depends on B, B on C, and C on A. Dependency loops of any length are possible, but the longer loops are more likely to be overlooked until they lock up. They're more difficult to detect in advance when the dependency loop spans multiple work streams, where disjoint awareness can play a more significant role in concealing the loops. Intentional search for such loops early in the effort of a project, or periodically in the case of operations, is a worthwhile endeavor.
Illusory factorability
An extreme form of difficulty arising from the analytic approach occurs when the collaboration tries to segment into smaller tasks a problem (or portion of a problem) that cannot be segmented. These problems are susceptible to solution only by teams that can work as one or nearly so.
One possible structure of such problems is what can be called braided work streams. Suppose we segment a problem into work streams, and assign a team to each stream. If the nature of the work of each stream is well understood by those performing the work, the teams can coordinate their plans and work so as to achieve their respective objectives as they would for any problem. But if the streams aren't understood well enough, disjoint awareness sets in, and the teams have, respectively, different understandings of each other's efforts. The respective stream plans will therefore need corrective action repeatedly and possibly frequently. Replanning might require nearly continuous coordination across multiple streams. The streams become, in effect, braided. In a very real sense, the problem wasn't actually factorable. Such problems might be better addressed as wholes.
In this example, factorability is compromised because of disjoint awareness of the work streams. But factorability can be compromised whenever the team's ability to coordinate is inadequate to the needs of the problem. For example, geographical dispersion of the team can reduce its ability to coordinate work across the team's various work sites. Other possible barriers to coordination include language, professional specialty, and in the case of strategic partnership, enterprise loyalty. Any barrier that contributes to disjoint awareness sufficiently to compromise the ability of the teams to adequately coordinate can compromise the factorability of the problem.

Analysis can work well when its risks are well managed. Examining the work streams for boundary clarity, coverage completeness, potential stream-stream interactions, and factorability can help in managing those risks. First in this series  Next in this series Go to top Top  Next issue: Disjoint Awareness: Systematics  Next Issue

Great Teams WorkshopOccasionally we have the experience of belonging to a great team. Thrilling as it is, the experience is rare. In part, it's rare because we usually strive only for adequacy, not for greatness. We do this because we don't fully appreciate the returns on greatness. Not only does it feel good to be part of great team — it pays off. Check out my Great Teams Workshop to lead your team onto the path toward greatness. More info

Your comments are welcome

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

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

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

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

A bear trapThe Mind Reading Trap
When we think, "Paul doesn't trust me," we could be fooling ourselves into believing that we can read his mind. Unless he has directly expressed his distrust, we're just guessing, and we can reach whatever conclusion we wish, unconstrained by reality. In project management, as anywhere else, that's a recipe for trouble.
A pattern that isn't a patternCoincidences Do Happen
When we notice similarities between events, or possible patterns of events, we often attribute meaning to them beyond what we can prove. Sometimes we guess right, and sometimes not. How can we improve our guesses?
A Rough-Legged Hawk surveys its domainTake Any Seat: II
In meetings, where you sit in the room influences your effectiveness, both in the formal part of the meeting and in the milling-abouts that occur around breaks. You can take any seat, but if you make your choice strategically, you can better maintain your autonomy and power.
Computer-generated image of the third stage ignition for Mars Climate OrbiterConfirmation Bias: Workplace Consequences Part II
We continue our exploration of confirmation bias. In this Part II, we explore its effects in management processes.
A view from the false summit of the Manitou incline in ColoradoFalse Summits: I
Mountaineers often experience "false summits," when just as they thought they were nearing the summit, it turns out that there is much more climbing to do. So it is in project work.

See also Personal, Team, and Organizational Effectiveness and Virtual and Global Teams for more related articles.

Forthcoming issues of Point Lookout

A blue peacock of IndiaComing October 4: Self-Importance and Conversational Narcissism at Work: I
Conversational narcissism is a set of behaviors that participants use to focus the exchange on their own self-interest rather than the shared objective. This post emphasizes the role of these behaviors in advancing a narcissist's sense of self-importance. Available here and by RSS on October 4.
Men in conversation at an eventAnd on October 11: Self-Importance and Conversational Narcissism at Work: II
Self-importance is one of four major themes of conversational narcissism. Knowing how to recognize the patterns of conversational narcissism is a fundamental skill needed for controlling it. Here are eight examples that emphasize self-importance. Available here and by RSS on October 11.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenogMhuqCxAnbfLvzbner@ChacigAthhhYwzZDgxshoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.