![]()
|
||||
Build
a good-enough vision Provide minimum specifications, rather than trying to plan every little detail. |
||||
Bibliography |
Since the behavior
of a CAS emerges from the interaction among the agents, and since the
detailed behavior of the system is fundamentally unpredictable, it does
little good to spend all the time that most organizations spend in detailed
planning. Most organizational leaders have participated in very detailed
planning, only to find that assumptions and inputs must be changed almost
immediately after the plan is finalized. Complexity science suggests that
we would be better off with minimum specifications and general senses
of direction, and then allow appropriate autonomy for individuals to self-organize
and adapt as time goes by. The science behind this principle traces it
roots back to a computer simulation called Boids, developed
in 1987 by Craig
Reynolds. The simulation consists of a collection of autonomous agents
the boids in a environment with obstacles. In addition to
the basic laws of physics, each agent follows three simple rules: (1)
try to maintain a minimum distance from all other boids and objects; (2)
try to match speed with neighboring boids; and, (3) try to move toward
the center of mass of the boids in your neighborhood. Remarkably, when
the simulation is run, the boids exhibit the very lifelike behavior of
flying in flocks around the objects on the screen. They flock, a complex
behavior pattern, even though there is no rule explicitly telling them
to do so. While this does not prove that birds actually use these simple
rules, it does show that simple rules minimum specifications
can lead to complex behaviors. These complex behaviors emerge from the
interactions among agents, rather than being imposed upon the CAS by an
outside agent or an explicit, detailed description.
Most of the time, however,
organizations are not machine-like; they are complex adaptive systems. The key learning
from the simulations is that in the case of a CAS, minimum specifications and purposeful
variation are the way to go. This principle would suggest,
for example, that intricate strategic plans be replaced by simple documents that describe
the general direction the organization is pursuing and a few basic principles for how the
organization should get there. The rest is left to the flexibility, adaptability and
creativity of the system as the context continually changes. This, of course, is a
frightening thought for leaders classically trained in the machine and military metaphors.
But the key questions are: Are these traditional metaphors working for us today? Are we
able to lay out detailed plans and then just do it with a guaranteed outcome? If not, do
we really think that planning harder will be any better?
|
|||
Next | Previous | Return to Contents List All Components of Edgeware
Principles Copyright © 2001, Curt |