THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
Date: Thu, 22 Aug 2002 17:15:43 -0700
02 06 01 61 02082202
Mr. Jack Park
jackpark@thinkalong.com
Street address
Palo Alto, CA Zip
..
Subject:
Weblogs, Grove and Groove
Dear Jack,
Jack,
Thanks for
your letter
today explaining the difference between Grove and Groove
technologies. I was confused. Your clarification cleared things up.
..
Are there examples where anyone has used Grove to provide addressability to
documents. Typically, documents are not terribly interesting; rather the
issues within documents and the accumulation of ideas that refine understanding
over time are of great benefit, as pointed out by
Mary Keeler on May 18, 2000, which is easily accomplished by adding
addressability to align information with original sources.
Recall that on April 5,
2000
Doug Engelbart called for addressability to strengthen
accuracy of knowledge; but, just two days ago on August 20, powerful social
barriers were revealed by Murray Altheim and Eric Armstrong
that resist
accurate communication.
Are there examples
of anyone using addressability created by Grove to grow the knowledge of an
enterprise,
as Ozzie talks about in his weblog? Doug Engelbart discusses
addressability
to improve the enterprise,
as well, in his 1992 paper. Does Doug know that Grove has solved the
problem; or, is there more to it?
..
On Groove, I looked further at some writings by Ozzie...
(note, Ozzie didn't seem to use Grove to apply uniform addressability,
but this is a few paragraphs down at....
"Second, for the line-of-business that generally creates custom Notes
applications, [Groove] enables the ability to rapidly assemble teams,
manage documents and projects, make decisions, and solve problems
across enterprise boundaries - all without having to fund IT to host
new Domino servers in the DMZ - a costly and time-consuming process,
or to fund their external hosting - unsecured and disconnected from
enterprise systems. LOB users can create new shared spaces as needed,
and developers can rapidly build applications using such powerful
products as VisualStudio.NET, to connect Groove shared space data to
extant Notes databases as well as to other products such as SharePoint
Portal Server."
.. Setting aside discussion about Domino servers in the DMZ and LOB
users, etc., Ozzie's explanation of using LN with Groove to
"...assemble teams, manage documents and projects, make decisions, and
solve problems across enterprise boundaries," sounds like the OHS/DKR.
..
Has anyone investigated to see how this is done? Sounds like a great
feature for Nexist.
Just wonder what is meant by "manage documents and projects"? For
example you have discussed implementing management rules through
Nexist. Does Groove do this? To illustrate, review on 950721 of PMBOK
and ISO standards showed a couple of rules they talk about are (1)
"continual learning," and (2) "traceability to original sources,"
although when you boil it down they mean largely the same thing, i.e.,
continually making connections that show and maintain cause and effect
over time. More recently, review of the Federal Acquisition
Regulations (FAR) showed similar rules because understanding causation
helps make decisions for managing projects.
.. How is this implemented by Groove? Is Groove the method in your letter
on October 25, 2000, discussing an
"engine"
with Paul Fernhout? Are Grove and
Groove complementary so that addressablity helps manage documents, projects and
making decisions? Just seems like all of the pieces are there for great things
to happen.
..
If John has time, maybe he can point out which of the KM solutions
listed in the proven template he submitted on 020610 accomplish
Ozzie's ideas for enterprise management with Grove, Groove and LN.
Would like to see some work product showing time and money saved, etc.
..
What seems most striking, however, is how all of this enterprise
management sits with the CEO who is worried about accountability?
..
People writing things down in weblogs and on "secure" intranet servers
creates an inherent audit trail because servers are backed up; people
download to notebooks in order to work at home and while traveling. It
is too difficult for participants on the ground to recognize gaps in
the record during the heat of battle that later cause mistakes, absent
proactive intelligence. For example discussing health care on July 29, 2000
Tom Munnecke
noted transformation issues arise from worry that an
enterprising engineer will design a "worm" or virus to mine electronic
records for actionable scenarios, giving new meaning to the phrase
"ambulance chasers"...
.. Has worry about accountability come up with Grove, Groove and Weblogs?