Managing The 21st Century Organization: April 2007
Managing The 21st Century Organization: April 2007
Managing The 21st Century Organization: April 2007
net/publication/264325369
CITATIONS READS
32 4,799
1 author:
Valdis E Krebs
Orgnet, LLC
46 PUBLICATIONS 1,419 CITATIONS
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Valdis E Krebs on 30 July 2014.
ORGANIZATIONS: OLD VERSUS NEW In hierarchies, everyone is linked to a boss above them.
When change was slow, a tall hierarchy with segmented Groups are not connected to each other except through
knowledge was the organizational structure of choice. This a common boss. Going outside the formal lines of com-
model was developed in the mid-1800s to run the railroads munication and authority is usually frowned upon in rigid
and worked very well to get the trains on time with minimum hierarchies.
accidents. This model worked well for 100 years until the In the knowledge economy, the organization structure
economy saw the influx of computers, copious amounts of has changed. The hierarchy is not gone. It still represents the
data, and rapid information flows. Figure 1 shows the hier- authority structure and the division of functional responsi-
archy of an IT department. The CIO is at the top, the direc- bility. The hierachy of old now shares the organization stru-
tors are at the next level down and report to the CIO, and cure with emergent networks that respond to dynamic
finally the managers are the bottom rows reporting to the environments. A new structure – representing information
directors. No one beneath the level of manager is shown on flow and knowledge sharing – reveals how things really get
the chart. For privacy reasons, the actual names of the done in the information age. This new structure is based on
employees are hidden and replaced by numbers. data gathered from employees via a survey.
Another simple solution was to allow direct interactions solution is to attempt to mine knowledge from employees,
between the various technical employees, without going codify it, and store it in a large database. Many large con-
through the various assistant project managers, who ended sulting firms tried this approach in the 1990s with usually
up being bottlenecks early in the project. These interven- sub-par results. They found that people were not always
tions, along with others, improved the information flow, and willing to make public their best knowledge and that codify-
reduced the communication load on the hubs, whose per- ing tacit knowledge was like trying to nail jelly to the wall. It
formance improved later in the project. did not work, and just left a mess.
Why not use the power of the network itself to create a
INSIDE THE ORGANIZATION: COMMUNITIES AND solution? Improve the organizational network and then use
CLUSTERS technology to help people communicate across wide spans
Network ties are distributed unevenly in organizations. of the human network. At first blush, improving an organiza-
People that work together form networks together – clusters tion-wide network may seem an overwhelming task. Where
emerge around established work relationships. Engineers do we start? First, look at the networks and communities of
working on Project X form a cluster, those working on Project practice/interest/knowledge that have organized around a
Y form a cluster, and those working on Project Z form a specific topic, product, service or customer. Usually, the
cluster. Everyone knows everyone else within the local whole organization does not have to be included in the
cluster, and yet only a few individuals have boundary span- problem space. Second, map out the network nodes and
ning ties to other clusters. Strong, frequent ties are usually their connections (who goes to whom for expertise/knowl-
found within clusters, while weaker, less frequent ties are edge/advice on X?). From this network map, you can see the
found between clusters. various clusters and how they are connected.
Clusters of concentrated connections appear throughout Figure 8 shows an emergent community of practice at
an organization and throughout industries. Some clusters IBM. This was not a prescribed community – it was not
have many ties outside the group, while other clusters have formed under direction of management. This community
only a few. Poor connections between clusters result in very formed over time, and survived over time, based on common
long path lengths throughout the organization. In such a interests, knowledge and goals.
network it is easy to access those in your cluster but not
those in other clusters. This often results in distant clusters
not knowing what information and knowledge is available
elsewhere in the organization.
Often, the knowledge you need is in clusters other than
your own. Networks have a horizon beyond which it is diffi-
cult to see what is happening. Research by Noah Friedkin, at
the University of California at Santa Barbara, has shown that
this network is approximately two steps in a human network
– your direct contacts and their direct contacts. Around
three steps out, things are real fuzzy – you do not have a
good idea of what is happening in that part of the network.
Beyond three steps, you are blind to what is happening in
the rest of the network – except for obvious ”public” infor-
mation known by everyone. So the popular idea of it being a
”small world” because we are all separated by an average of
six degrees is misleading. Six degrees is actually a very large
world – one, two and three degrees is a small world! It is
usually those separated by two degrees where the ”small Figure 8. Emergent Community of Practice at IBM.
world” discoveries happen – it is here where you discover the
person next to you on the plane is related to a friend from We were looking for the emergent organization – how
your university days. work was really done – what the real structure of the organi-
In a network of very long path lengths between clusters, zation was. Figure 8 shows us how work was really accom-
your ability to find the knowledge or information you need is plished in the organization. Two nodes/people are linked if
very constrained. If the knowledge that you seek is not they both confirm that they exchange information and
within your network horizon (one or two steps), then you resources to get their jobs done. Each work group involved
assume it is not available in your organization and you rein- in the study received a different color node.
vent it, or pay for it on the outside. Exasperated with the The network visualization immediately revealed that
network horizon in his organization, a former CEO of HP there was an emergent cluster of specific professionals in
once lamented, “If HP only knew what HP knows.” the organization. It appeared to be the key to getting things
The natural response in many organizations is to throw done. The central members of the community in Figure 8 are
technology at the problem. A very poor, yet quite common, connected by the darker links.