Sensemaking in Organizations Pt. 2

The Second Wave of Sensemaking

Bonnitta Roy
May 22, 2018 · 4 min read

This is a three-part story. In part one I presented a brief history of how organizations have changed in the past in order to make better sense of the environments they faced. In this article I discuss how agile adoption represents a second wave of sensemaking. In part three I discuss the future of work and the kinds of sensemaking technologies we can anticipate.

The 70’s and 80’s were times of competing ideas on organizational structure and group behavior. These were the intellectual grounds that produced open systems experimentation and a variety of hybrid structures. Organizational models moved away from the notion of an isolated organism, and metaphors based on the ideas of the new science of ecology, came to predominate. Yet the ideals put forth by open systems and ecological thinking were handicapped in practice, not because the models were faulty, but because information technology was inadequate to support the kinds of information flows that the models told them were necessary. Only until the mid 90’s was it possible to explore these models in actual practice — but the scene had already been set a decade before. Not surprisingly, then, organizations evolved at an unprecedented pace.

Open systems

The central insight emerging from open systems thinking is that all organizations are incomplete and depend on exchanges with other systems. The notion of “environment as threat” was replaced by the realization that environmental features are conditions for their survival. Open systems are characterized by 1) interdependent flows and 2) interdependent activities, performed by 3) shifting coalition of participants by way of 4) linking actors, resources and institutions, in order to 5) solve problems in 6) complex environments.

To make sense in open systems, the new information technologies were adopted to update the way information propagated through the system. But the two other sensemaking requirements also needed to change, namely, the ways people organize to sense and make sense together, and their thresholds for action.

Sure, organizations were quick to adopt ready-made information technologies that satisfied a decade-long demand, but they remain slow to examine their own structures and policies. On the structural front, sensemaking is thwarted by hierarchical systems, fixed power roles, functional silos, and vertically integrated companies. On the action side, change is stifled by centralized administration, bureaucratic inertia, policy-driven decision making, and an obstinate aversion to risk.

Agile as a social experiment

As soon as hackers could assemble comparable computing power in their own homes, or garages, a social experiment was underway. Was is possible for a small group of purpose-driven people to compete with companies whose employees had comparable skills, but whose financial coffers contained much larger resources? Of course, we now know that not only could the hackers compete — they completely out-performed the establishment.

The biggest take-away from this experiment was radical, and is often overlooked: As complexity of a task rises above a certain threshold, we will need to deconstruct the complexity in the organization in order to tackle it. Think of this as taming the problem situation.

As complexity of the task rises above a certain threshold, we need to deconstruct the complexity in the organization in order to tackle it. Think of this as taming the problem situation.

The Mathematics of Sensemaking

Just as good engineering secured the success of early manufacturing companies, and sophisticated systems design guaranteed survival for the natural system organization, sensemaking becomes a primary directive for the open organization. But sensemaking is very different from engineering and systems design. Let’s use a mathematical formulation to illustrate just how different.

At the level of rational systems, things get complicated and require better engineering. We can think of engineering as additive. As the assembly line or service route becomes more complicated, we need to add roles, tasks, quality control stations, safety precautions, and other kinds of redundancies. At the level of natural systems, things become more interdependent and complex, requiring more complex systems design. We can think of systems design as multiplicative (or even exponential), because it deals with amplifying forces.

When it comes to open systems, however, we need to work in reverse direction. We need to subtract from the existing complicated path dependencies, and divide out the interdependencies that make systems complex. We need to deconstruct the old assumptions and figure our way into a new way of thinking. Here, sensemaking begins from a fresh starting position where people can reason from first principles and find simple, but powerful protocols for action.

Read Pt 3 here

Agile Sensemaking

Sensemaking for agile teams

Bonnitta Roy

Written by

source code analyst .. APP AI

Agile Sensemaking

Sensemaking for agile teams

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade