THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
S U M M A R Y
DIARY: October 31, 2000 02:36 PM Tuesday;
Price of growing a customer for KM.
2...Listening to Doug
3...Hyperscope, Hyperlens Used by Others
4...SDS Proof of Concept Knowledge Management Possible and Practicle
5...Study What Works to Learn Enough Knowledge about Knowledge Management
6...Not Enough Knowledge to Develop Knowledge Management
7...Discovering Secrets of KM Requires Experience Performing KM
8...Open Source Does Not Require Open Source Development
9...Paul advises he is starting a new assignment tomorrow, and so
Click here to comment!
Contributors Use Links in Launch Plan to Comment on Plan
Listening to Doug, 000424
OHS Launch Plan Submitted
Hyperscope Hyperlens Used by Others
Hyperscope Name of Translate/Transcode Program for OHS, Doug Engelbar
Hyperlens Name of Translate/Transcode Program for OHS, Doug Engelbart
Tscope Name of Translate/Transcode Program for OHS, Doug Engelbart
Hyperscope Intermediary Processor Operates Between Browser and Files
Learn KM Pilot Test Use KM to Discover How to Create KM Tools
2911 - ..
2912 - Summary/Objective
291301 - Follow up ref SDS 49 0000, ref SDS 45 0000.
291303 - Jack Park points out that initial names selected for OHS translater
291304 - tools have been adopted by others. Tscope is another possibility,
291305 - which Doug proposed recently. ref SDS 0 ADK1 Jack urges listening to
291306 - Doug. This entails submitting analysis of OHS architecture with links
291307 - to the Launch Plan Doug's requested on 001025. ref SDS 0 I67L Jack
291308 - proposes getting knowledge on KM from sources "out there," even though
291309 - 10 months of research have not disclosed it. ref SDS 0 ADK2 Knowledge
291310 - can, also, be acquired from experience using KM for daily work.
291311 - ref SDS 0 HG7D This can be accomplished as research, or to reduce
291312 - costs by improving management. ref SDS 0 X56K Jack explains KM
291313 - development can be accomplished using conventional project management
291314 - methods, where people are paid to perform work according to objectives
291315 - and planning set by management; the result can then be published as
291316 - open source. ref SDS 0 TX7J Paul Fernhout prefers volunteer work, and
291317 - indicates progress is impaired because solutions are tied up by
291318 - development in proprietary dot coms. He does not explain work product
291319 - that evidences knowledge management. ref SDS 0 L36H Paul is starting
291320 - a new assignment that will reduce his availability to contribute on
291321 - the DKR project. ref SDS 0 NU83
291325 - ..
2916 - Progress
291701 - Listening to Doug
291702 - Hyperscope, Hyperlens Used by Others
291704 - Follow up ref SDS 49 F35Y, ref SDS 46 A5U6.
291706 - Jack submitted a letter the other day reporting research that shows
291707 - another organization is using the term hyperscope, which Doug proposed
291708 - for the transcoding program set out in the OHS launch plan submitted
291709 - on 001025. ref SDS 46 A5U6
291711 - ..
291712 - Jack's letter today, ref DRT 1 0001, reports that further research
291713 - also shows that an alternate name Doug proposed on 001008, Hyperlens,
291714 - is also being used by someone else.
291716 - ..
291717 - On 001008 Doug was also considering Tscope. ref SDS 38 5RW6
291719 - ..
291720 - Another popular naming scheme is "cyber..." as in cyberspace,
291721 - cybernetics, and so on (see SRI plans to improve internal management
291722 - on 000829. ref SDS 30 MJ6F) Possibly Cyberhyp might be available.
291724 - ..
291725 - Jack says in his second letter addressed to Welch, ref DRT 2 0001, and
291726 - copied to the OHS/DKR team says...
291728 - What is happening here is that we are, IMHO, ignoring the
291729 - teachings of the one individual who might just know more about the
291730 - topic than we do, Doug. ref DRT 2 4G8I
291732 - ..
291733 - It helps to list a few teachings that illustrate benefits derived from
291734 - by learning from Doug's "teachings." For example...
291736 - 1. Doug's 1962 proposal for SRI that led to development of
291737 - Augment NLS cited Vannevar Bush, reviewed on 991222,
291738 - ref SDS 8 XS6N, who taught efficiencies of electronic
291739 - records management require complementary tools for
291740 - linking and organizing the record to create trails of
291741 - association for precision access, reviewed on 960304.
291742 - ref SDS 4 GX59
291744 - ..
291745 - 2. Doug Engelbart proposed in a letter on 000405 that the
291746 - OHS/DKR team add links in email for constructing trails
291747 - of associations in the archive. ref SDS 14 2484
291749 - ..
291750 - 3. Libraries, electronic records management, today and for
291751 - the moment called a "knowledge repository" require
291752 - granular indexing to efficiently construct case studies
291753 - that improve productivity with lessons learned,
291754 - reviewed on 960304. ref SDS 4 368K
291756 - ..
291757 - 4. Information from daily meetings, calls, and documents
291758 - requires a historian, analyst, or similar professional
291759 - role who "delights" organizing the record to construct
291760 - useful trails that expedite daily work so that people
291761 - can optimize collective IQ to get things done correctly
291762 - with less diligence and discipline, reported on 960304.
291763 - ref SDS 4 364J Doug's "collective IQ" ideas were
291764 - reviewed on 991222. ref SDS 8 KI49
291766 - ..
291767 - This record applies teaching Jack Park offered in a letter to the
291768 - OHS/DKR team on 000630 about separating analysis from original
291769 - manuscripts (i.e., documents). ref SDS 27 MD3O
Knowledge Management Discouraged Not Enough Knowledge Give Up Don't
780401 - ..
780402 - SDS Proof of Concept Knowledge Management Possible and Practicle
780403 - Study What Works to Learn Enough Knowledge about Knowledge Management
780405 - Jack's letter continues...
780407 - Case in point: I suspect that the SRI meetings seduced us into
780408 - believing that *we* would just start out and design and build an
780409 - OHS all by ourselves. That effort culminated in the meeting at
780410 - which folks began to conjecture that there isn't enough knowledge
780411 - to do KM even when [Welch was] sitting in the same meeting and...
780412 - had been doing it for umpteen years. Gads. ref DRT 2 0S8L
780414 - ..
780415 - Jack seems to follow up today on discusison a month ago on 000922,
780416 - ref SDS 33 EF49; at that time, he explained reluctance to be the only
780417 - person discussing SDS and POIMS. ref SDS 33 U23L
780419 - [On 020726 systems and technology development begins with
780420 - investing time to "study what works," and then adding
780421 - innovation to synthesize various capabilities into a new
780422 - capability that improves productivity. ref SDS 62 E63H
780424 - ..
780425 - [On 071220 case study shows Jack's work helping OHS/DKR team
780426 - consider SDS. ref SDS 63 M53N
780428 - ..
780429 - [On 080422 Gary Johnson describes SDS design applies a theory
780430 - of knowledge and work product demonstrates unique ability to
780431 - perform. ref SDS 64 054Y
780433 - ..
780434 - [On 081224 Jack Rakove, history professor at Stanford,
780435 - discussed Madison's contribution to the Constitution explained
780436 - Articles of Confederation failed because of "free rider"
780437 - problem that makes everybody afraid to go first. ref SDS 65
780438 - VR7N
780440 - ..
780441 - Jack's letter today refers to a meeting at SRI on 000615. Eugene Kim
780442 - reported concensus had formed that there isn't enough "knowledge" to
780443 - develop "Knowledge Management." ref SDS 25 6271 This reflected Lee
780444 - Iverson's earlier report on 000324, ref SDS 12 4877, saying many
780445 - organizations have tried to devleop Knowledge Management tools, and
780446 - all have failed. Jack clarifies today, that SDS may have succeeded,
780447 - at least in providing a path for progress.
780449 - ..
780450 - Case study on 001017 listing SDS records created for Doug's group at
780451 - SRI supports Jack's point that people can learn Knowledge Management
780452 - by learning to use SDS. ref SDS 42 1575 On 000504 Jack reported
780453 - people ignored experience performing Knowledge Management, and noted
780454 - this must be pondered in order to advance the work of developing
780455 - OHS/DKR capability. ref SDS 19 XD5M
780457 - ..
780458 - In fact, people are immersed in the solution but technology that
780459 - feeds a culture of "grazing" on endless information in meetings,
780460 - calls, and email, explained in NWO, ref OF 3 156O, obscures the path
780461 - for discoverying how to assemble ingredients that augment
780462 - "intelligence," discussed with Doug on 000327. ref SDS 13 4420
780464 - ..
780465 - The dilemma Jack presents today occurs often when major advance arises
780466 - on the landscape. Similar hypothetical scenario is presented in NWO
780467 - on resistance Tesla encountered to his breakthrough design for
780468 - alternating current technology in the 1890s. ref OF 4 RE5F
780470 - [On 001116 Jack Park letter to OHS/DKR team meeting at SRI
780471 - reports SDS records on the Internet demonstrate amazing
780472 - ability to accomplish Knowledge Management that validates
780473 - claims in POIMS. ref SDS 51 953G
780475 - ..
780476 - [On 001126 OHS/DKR team decides to continue using popular
780477 - information management tools rather than use SDS in order to
780478 - learn Knowledge Management. ref SDS 53 T63N
780480 - ..
780481 - [On 001130 Jack submits article reporting IBM did not have
780482 - enough knowledge to create Knowledge Management tool; IBM
780483 - failed to convert Lotus Notes into KM. ref SDS 55 F26K
780485 - ..
780486 - [On 011003 Jack reports having no clues for creating
780487 - Knowledge Management, ref SDS 60 O74L, which Eric Armstrong
780488 - requested to avoid quagmire of information overload that
780489 - paralizes productivity. ref SDS 60 EC5N
780491 - ..
780492 - [On 011208 Jack Park cannot cite other technologies that
780493 - have the SDS design for "intelligence" support. ref SDS 61
780494 - FV5H
780496 - ..
780497 - SDS was started in 1983, reported in history of SDS on 000723.
780498 - ref SDS 28 0008
780500 - ..
780501 - Jack makes a good point about "learning by doing," described in POIMS
780502 - as synergy between thinking and doing. ref OF 1 2049
780504 - ..
780505 - What is the process by which "teachings" are actually "learned"? One
780506 - criteria seems to be applying what is taught into the stream of daily
780507 - work experience. This requires a record showing what was "taught,"
780508 - and where it is applied, illustrated above. ref SDS 0 HN3L Where, for
780509 - example, has effort been invested to review Doug's teachings in the
780510 - OHS/DKR launch plan, requested by Doug on 001025? ref SDS 46 00VU
780512 - ..
780513 - When people are being supported by KM, as with the DKR team for the
780514 - past 10 months, and do not recognize support is occurring, (see the
780515 - meeting on 001017, ref SDS 42 3995), leadership is needed to show the
780516 - way.
780518 - ..
780519 - This requires spending money to pay people for acquiring experience
780520 - doing KM, rather than chasing around the Internet looking for
780521 - information "out there." KM must be endemic to daily work practice,
780522 - in order to discover the secrets of desiging effective technology.
780524 - ..
780525 - [On 001116 Jack Park reported to OHS/DKR team SDS records on
780526 - the Internet are amazing "existence proof" validating claims
780527 - of POIMS for supporting Knowledge Management. ref SDS 51
780528 - 953G
780530 - ..
780531 - [On 010916 Eric Armstrong reported SDS enables amazing
780532 - memory with mechanisms that obviously work. ref SDS 59 0001
780534 - ..
780535 - Making sense of persistent difficulties developing Knowledge
780536 - Management, noted in Jack's letter today, ref SDS 0 0S8L,
780537 - indicates...
780539 - 1. Knowledge Management seems to be a secret of SDS that is
780540 - hidden in plain sight, shown by SDS records on the
780541 - Internet, cited by Jack, and illustrated by this record,
780542 - and further supporting prior analysis on 000425.
780543 - ref SDS 17 0480
780545 - ..
780546 - 2. People need experience performing Knowledge Management in
780547 - order to learn enough to develop software tools that aid
780548 - the process.
780550 - ..
780551 - People understand information management from learning and using
780552 - alphabet technology beginning in grammar school. People experience
780553 - information technology every day attending meetings, making calls,
780554 - writing and reading, sending, receiving, storing, and retrieving
780555 - documents. Energy expended performing these physical tasks are
780556 - experienced consciously in the moment through sensory perception.
780557 - Knowledge occurs differently. Mental energy connects memory of
780558 - related events into rule-based assumptions that link cause and effect.
780559 - This occurs entirely subconsciously on automatic pilot, explained in
780560 - POIMS. ref OF 1 L66K People have no awareness of an intelligence
780561 - process that transforms information into the power of knowledge to
780562 - control the future. Since assumptions are mind numbingly fast and
780563 - easy, explained in NWO, ref OF 4 FU6J, people rarely experience the
780564 - steps of creating a connected record.
780566 - ..
780567 - [On 001126 Eugene Kim proposes OHS/DKR team learn Knowledge
780568 - Management by doing information technology using email with
780569 - greater diligence, rather than use SDS. ref SDS 53 QW8I
780571 - ..
780572 - People have very limited experience doing Knowledge Mangement, because
780573 - checking the record and "connecting the dots" to verify accuracy is a
780574 - lot of hard work using popular information technology for email,
780575 - wordprocessing, etc, shown by research for the OHS/DKR project at SRI,
780576 - reported on 000307. ref SDS 11 767G An example is frustrations trying
780577 - to find documents in a typical law firm, reported on 960406,
780578 - ref SDS 6 5922, which is an essential step for constructing links,
780580 - ..
780581 - [...below, Jack says not enough is known to create KM.
780582 - ref SDS 0 ADK2
780584 - ..
780585 - [On 010420 Jeff Conklin reported people have very limited
780586 - ability to capture and manage organizational memory.
780587 - ref SDS 58 IE4M
780589 - ..
780590 - [On 001127 Eric Armstrong reports discovering that moving
780591 - beyond IT to produce KM capability is complex and so very
780592 - difficult to accomplish. ref SDS 54 TN4J
780594 - ..
780595 - [On 001130 Jack reports SDS has the right structure for
780596 - knowledge and the interface that makes the structure useful
780597 - for people. ref SDS 56 H17O
780599 - ..
780600 - [On 001105 Henry van Eykan is working on developing an
780601 - archive to preserve Doug's legacy. ref SDS 50 8621
780603 - ..
780604 - On 001028 the opportunity for leadership to develop experience was
780605 - explained. ref SDS 49 G4EJ
780607 - ..
780608 - People don't want to do Knowledge Management using traditional manual
780609 - methods with email, wordprocessing, Palm Pilots and filing cabinets,
780610 - because it is a lot of hard work and is not fun; so, like mining coal,
780611 - sweeping the floor, accounting and other tasks people won't do unless
780612 - paid, some money has to be put up to pay people to use good management
780613 - practice instead of feel good managment, for a long enough time to
780614 - understand how to perform knowledge management. The money for this
780615 - comes from research, development and marketing budgets, because people
780616 - don't believe prospectively that adding intelligence to management
780617 - improves earnings. None-the-less, if money can be found to pay people
780618 - for doing Knowledge Management, this invstment will not only show how
780619 - to develop tools, it will save a lot of money. Knowledge Management
780620 - doesn't cost anything; like advertising, it pays for itself.
780622 - ..
780623 - People grasp intuitively that "intelligence" should be helpful,
780624 - otherwise there is no point in Knowledge Management projects; however,
780625 - when the "leather hits the road," everybody bails out and jumps on the
780626 - Internet for another quick fix, because advancing beyond information
780627 - practices of writing a letter, report, or arcticle, people don't
780628 - understand what technology can do to enhance human cognition.
780630 - ..
780631 - It costs money, either proactively through research, or through long,
780632 - hard won experience, to gain that knowledge, as proposed to SRI on
780633 - 001011. ref SDS 39 0001
780635 - ..
780636 - [On 001121 letter to OHS/DKR proposes selling SDS to people
780637 - for gaining experience doing KM to learn how to develop OHS
780638 - capability. ref SDS 52 XU8I
780640 - ..
780641 - [On 001126 Eugene Kim proposes OHS/DKR team learn KM by
780642 - doing IT with greater diligence, rather than use SDS.
780643 - ref SDS 53 QW8I
How Soon Can I Get This in an SDS Record
Open Source Project
Open Source Evaluation
Study Needed Demonstrate Open Source Best Strategy, 000601
80% Solution Typical Open Source Result
Not Enough Knowledge about Knowledge to Design Knowledge Management
Termite Production Uses Invisible Hand Rather than Directed Design
Augment Code Should be Released
SDS Record Use Shows KM Can Succeed
Open Source Develop with Conventional Management then Release to Open
KM Architecture Too Difficult OHS Failed, Jack Park
A11401 - ..
A11402 - Not Enough Knowledge to Develop Knowledge Management
A11403 - Discovering Secrets of KM Requires Experience Performing KM
A11405 - Follow up ref SDS 49 ADK2, ref SDS 46 ADK1.
A11407 - Received ref DRT 2 0001 from Jack responding to the record on 001028
A11408 - that shows there is not enough knowledge to develop KM under open
A11409 - source methods. KM. ref SDS 49 PE6M,
A11411 - ..
A11412 - Jack says today
A11414 - I do not believe that I know enough about KM, but I do not
A11415 - consider myself one who believes that there isn't enough knowledge
A11416 - *out there* on which to begin a learning exercise. In fact, there
A11417 - may be far too much knowledge out there. Sorting through it all is
A11418 - the tough part. ref DRT 2 PE7G
A11420 - [On 001121 offer to sell SDS so the team dan do KM to learn how
A11421 - to create an OHS. ref SDS 52 XU8I
A11423 - ..
A11424 - [On 001127 Eric Armstrong says kernel of KM design too complex,
A11425 - progress slow. ref SDS 54 0001
A11427 - ..
A11428 - [On 011003 Jack reports there are no clues for creating an
A11429 - OHS/DKR capability to improve IT, ref SDS 60 O74L, which Eric
A11430 - Armstrong needs to avoid quagmire of information overload that
A11431 - paralizes productivity. ref SDS 60 EC5N
A11433 - ..
A11434 - Paul Fernhout's letter today, also, says KM is a new field, and
A11435 - noting...
A11437 - ... it is harder to get people together to make such solutions
A11438 - because less people are aware of the issues (especially given all
A11439 - the "hot" proprietary work happening in dot-coms). ref DRT 3 8J3I
A11441 - If useful, "hot" proprietary work is being accomplished in
A11442 - knowledge management, someone on the planet would know about
A11443 - the generl character. At a minimium, work product would be
A11444 - evident by showing up in earnings and solutions to world
A11445 - problems. But information overload remains a chronic problem
A11446 - that impacts dot coms, as it does others. Several weeks ago,
A11447 - while waiting for BART at the Embarcadero station, a woman
A11448 - mentioned she works for a dot com that is developing
A11449 - communications infrastructure. She was taking the 2000 train
A11450 - instead of 1700, because she needed 3 extra hours to answer
A11451 - email. She was frustrated by not having enough time for
A11452 - communication, and mentioned a recent meeting where colleagues
A11453 - complained they were falling behind because of continual
A11454 - mistakes. This person had never heard of knowledge management.
A11455 - An anecdote is not dispositive, but neither is it encouraging.
A11457 - ..
A11458 - Jack continues...
A11460 - We have choices. We can appeal to the philosophers in search of
A11461 - some *roots* on which to layer our efforts. We can follow other,
A11462 - so called *failed* efforts (Notes, according to your records), or
A11463 - we can just go off and invent our own and see if that *fails* as
A11464 - well. I, speaking personally, am inclined to learn as much about
A11465 - pragmatic thinking by way of C.S. Peirce as I can, with the
A11466 - thought that this might provide sufficient roots to get started.
A11467 - ref DRT 2 6F7L
A11469 - ..
A11470 - The call to rely on philosophy, and Peirce in particulare might focus
A11471 - on the correlation he makes between knowledge and experience, reviewed
A11472 - on 000515. ref SDS 21 5026
Open Source Can be Developed with Adequate Management Operations
Open Source Can Occur After Core Capability Developed
Release Open Source After Development, 001031, Jack Park
Release to Open Source After Development by Proprietary Methods
A70701 - ..
A70702 - Open Source Does Not Require Open Source Development
A70704 - Jack makes a strong point...
A70706 - We continue to confuse the notion of *Open Source Software* with
A70707 - the notion of homebrew software. ...a professionally managed
A70708 - project in which contributors receive compensation for software
A70709 - development is a greatly different project than one managed and
A70710 - built by volunteers. ref DRT 2 VE9G
A70712 - ..
A70713 - Paul Fernhout submits thoughtful analysis, ref DRT 3 1W6O, confirming
A70714 - support on 000831 for volunteer development, ref SDS 31 0001, that
A70715 - conflicts with plans announced during the meeting at SRI on 001017,
A70716 - ref SDS 42 01EY, to select a core development team.
A70718 - ..
A70719 - Paul relates experience where tensions arise between paid staff and
A70720 - volunteer. ref DRT 3 V94L
A70722 - See Drucker: theory x and theory y, on 931130. ref SDS 3 9677
A70724 - Development, professional, or otherwise, needs experience using KM
A70725 - in order to discover what to develop. When there is not enough
A70726 - knowledge, the discipline of audits may overcome the allure of
A70727 - feel good management, per analysis on 001017. ref SDS 42 AE7F
A70729 - ..
A70730 - On 000503 a project was proposed for open source to develop
A70731 - implementation support. ref SDS 18 6903
A70733 - ..
A70734 - Open Source after product development, could be a tool for
A70735 - spurrring sales by getting others to spend money to advertise and
A70736 - spread the word about KM
A70738 - [On 010201 Jack submits marketing ideas for Open Source.
A70739 - ref SDS 57 0001
A70742 - ..
A70743 - Paul feels release of existing Augment code would encourage open
A70744 - source participation. ref DRT 3 U66J
New Assignment Starting Less Active on DKR Project
A80401 - ..
A80402 - Paul advises he is starting a new assignment tomorrow, and so
A80403 - will be less active in the project for the period ahead. ref DRT 3
A80404 - EH9H