Information access and flow LO11438
Sun, 15 Dec 1996 15:40:04 -0500

Replying to LO11433 --

Rol correctly wrote:

> A fast-moving organization will need information 'push' mechanisms for the
> critical, time-sensitive information. Perhaps these needs can also be met
> in a network environment, but I am uncertain how. Networks in general
> require someone at the end to get the info, and this is different than
> mechanisms in which info is given.

And that is why GroupWare/Messaging systems are so important. The
information is "pushed" out to those who can use it by those who either
discover it or have received it from another "pusher."

A networks are like the nerves in a nervous system. It's important that
the nerves are there and adequately connected. But for the nervous system
to create a desired action, messages must be sent and received throughout
the nervous system. Neurons are the messaging agents of the nervous
system; E-Mail is the messaging agent of an organization.

While E-mail allows information to be "pushed" there is no promise that it
will be received and interpreted the way the sender meant it. That's an
entirely different issue I don't want to get into in this message.

Here's a good example from where I work. Software Engineering writes the
software. The interface with two different support groups, one of which
focuses on future versions of the software, and the other focuses on
shipping software.

These two support groups are responsible for "sharing" the information
they get from engineering with the rest of technical support. Their
prefered delivery mechanism is to publish all new information on our
internal web (Intranet). That's fine, but insufficient, as most people
don't check their web-site everday. What I've asked for is an E-Mail that
at least says, "there's new stuff on the web, go read it." What I prefer
is both an E-Mail with the information, and permanent access to the
information on the web.

The current structure has created a couple of problems for us in the last
few weeks. We discovered a problem with the software and devoted a couple
of support engineers to solving it. They spent about 200 man hours in the
effort, only to find out that the solution had already been found and
fixed. . .but never communicated because it was on the Web. . .no E-Mail.
. .no voice-mail. . .no neurons. . .


Benjamin B. Compton

Learning-org -- An Internet Dialog on Learning Organizations For info: <> -or- <>