CONTACTS 
0201 - Eugene Eric Kim                      650 326 0877
020101 - Mr. Eugene Eric Kim
020102 - eekim@eekim.com

SUBJECTS
Archive Too Hard to Find Anything, Eric Armstrong
Organizational Memory Who, What, When, Where, Why, How, How Much
Communication Biggest Risk of Enterprise Paradigm Shift of Millennium
Information Overload Entropy Not Enough Time to Think Cursory Analysi
Bac -link Data Base for Email Similar to DayPop Solves Information Ov
Recommendations Methods Tools For Evaluating Information on New Techn
DayPop Back-link Manager for Email, Eugene Kim

1809 -    ..
1810 - Summary/Objective
1811 -
181101 - Follow up ref SDS 18 0000, ref SDS 17 0000.
181102 -
181103 - Eugene explains a robust information stream provides opportunity for
181104 - people to participate.  Review, including following links and
181105 - responding, can be managed by being selective. He proposes a back-line
181106 - data base using DayPop to improve productivity, along with a system of
181107 - RFCs for organizing the way information is presented to provide a
181108 - formal structure and aids review.  No work product nor experience is
181109 - presented showing or indicating cost benefits.  Eugene suggests
181110 - appointing a work role, he calls a "librarian" to help manage the
181111 - submission of RFCs. ref SDS 0 JU5O  No estimates of cost and time
181112 - savings are provided.
181113 -
181114 -     [...in another record today, Henry van Eykan recognizes Eugene's
181115 -     ideas, and proposes using the EIC e-journal to further help
181116 -     organize the record. ref SDS 19 EC5N
181117 -
181118 -
181119 -
181120 -
181121 -
181122 -
181123 -  ..
1812 -
1813 -
1814 - Progress
1815 -
181501 - New Reality IT Diligence Hopeless Quagmire of Information Overload
181502 - Giving Up Weighed Down Communication Too Complex Analysis Paralyzed
181503 - Hopeless Quagmire Discourages Analysis Giving Up Disillusioned by IT
181504 -
181505 - Follow up ref SDS 18 EC5N, ref SDS 17 KA6H.
181506 -
181507 - Received ref DRT 1 0001 from Eugene Kim responding to Eric Armstrong's
181508 - letter yesterday, ref DRP 2 0001, reporting there is too much daily
181509 - information on the OHS/DKR project to understand and manage with tools
181510 - and methods he is using.
181511 -
181512 - Eugene responds....
181513 -
181514 -     I think it's great that people send out interesting links and
181515 -     articles; I agree with Eric that it's fairly overwhelming on this
181516 -     list, I think that's fine. If you have the time to follow the link
181517 -     and discover something useful in the process, more power to you.
181518 -     If you don't have time to follow the links, you're no worse off
181519 -     than you were before. ref DRT 1 1X6I
181520 - ..
181521 - This is a constructive perspective; but does not address the
181522 - issue of how to strengthen communication and collaboration.
181523 -
181524 -
181525 -  ..
181526 - Back-link Database for Email, Similar to DayPop
181527 -
181528 - Eugene suggests ideas for improving communication....
181529 -
181530 -     ....do a better job of organizing the links from archived e-mails
181531 -     in a useful way.  One solution, which has nice synergy with OHS
181532 -     development, is to create a localized back-link database from all
181533 -     of the e-mails posted to this list. The result would be something
181534 -     similar to the DayPop site that Alex brought to our attention
181535 -     (which, incidentally, I think is brilliant). ref DRT 1 617G
181536 -
181537 - Here is an example of the problem to be solved.
181538 -
181539 - Eric complains there are too many links.  In this case, Eugene
181540 - suggests a solution, but fails to provide a link demonstrating the
181541 - solution.  This failure eliminates ability to make an assessment of
181542 - work product.
181543 - ..
181544 - What experience does Eugene have using back-links for email, and
181545 - using DayPop for back-links that shows this will save time and money?
181546 - How does this idea fit criteria identified yesterday for evaluating
181547 - technologies to investigate? ref SDS 18 M16F
181548 -
181549 -
181550 -
181551 -
181552 -
181553 -
181554 -
181555 -
1816 -

SUBJECTS
Objectives Alignment with OHS/DKR Primary Criteria for Investigating
Application Criteria for Investigating New Criteria How Will It be Us
Decision Support Accurate Understandings Command Control Record Semio
RFC Formalism Present New Technologies for Review to Solve Informatio

2507 -
250701 -     ..
250702 -    Criteria to evaluate technology augmenting intelligence
250703 -    Formalize Correspondence on New Technologies for Review
250704 -
250705 -    Follow up ref SDS 18 M16F.
250706 -
250707 - Eugent continues with proposal for an system of RFCs to formalize
250708 - submissions of technology for review....
250709 -
250710 -     I'd propose a non-technical solution that, ironically enough, has
250711 -     its roots in Doug's lab 30 years ago: RFCs.  If you'd like to
250712 -     bring something to people's attentions, just post it to the list.
250713 -     If you'd really like people to pay attention to something, put
250714 -     together an RFC. ref DRT 1 O47O
250715 -     ..
250716 -     If you want to propose a feature, you write a TIP, and
250717 -     submit it. If accepted, the TIP gets assigned an ID, and is
250718 -     published under version control.  There is a format for writing
250719 -     TIPs, and a procedure for discussing and voting on TIPs.  TIPs are
250720 -     a wonderful mechanism for focusing attention and separating the
250721 -     wheat from the chaff.  It's a good example of using formalisms
250722 -     when you're ready to use them.
250723 -
250724 -           [On 011006 letter to John Deneen submits ideas for managing
250725 -           formalisms. ref SDS 20 MZ7N
250726 -
250727 -         This sounds like a new way of working called out by Doug
250728 -         Engelbart, reported on 991222. ref SDS 11 3696
250729 -
250730 -         Formalize information into an RFC aligns with planning
250731 -         yesterday to present evaluation criteria that helps people
250732 -         decide whether to investigate new ideas. ref SDS 18 4R5H
250733 -         ..
250734 -         How does anyone know when a TIP or RFC is accepted?
250735 -
250736 -         Who does the accepting, based on what criteria?
250737 -
250738 -         On 010315 Henry van Eykan wanted capability Eugene proposes
250739 -         today for separating "wheat from chaff." ref SDS 15 OM9L
250740 -
250741 -
250742 -
250743 -
250744 -
250745 -
250746 -
250747 -
2508 -

SUBJECTS
Librarian Assigned to Manage RFCs that Organize Information  n New Te
Com Manager Work Role Needed for Dialog Mapping Ontologist
Librarian Organizes Record Similar to Com Manager New Work Role
Knowledge Integrator Organizes Record Like Com Manager, Doug Engelbar
Work Role New Needed for Culture of Knowledge Co-evolve Education Alo
New Way of Thinking Working Doug's Mission Bootstrap Institute, 99122
Librarian Gets Information Quickly Dewey Decimal System Catagorize Or
New Way Working Good Management Consistent SDS Plan Perform Report Fa
Budget Overkill No Time No Budget Front-end Investment to Save Time C
Librarian Work Role Organize Record, Eugene Kim
Knowledge Integrator Com Manager Needed for Effective DKR, Doug Engel
Librarian Ontology Subjects Organic Structure Prepared and Applied by

8415 -
841501 -      ..
841502 -     Communication Manager Needed to Organize the Record
841503 -     Librarian Provides Com Manager Role to Organize the Record
841504 -
841505 -
841506 - Eugene suggests....
841507 -
841508 -     We could appoint a librarian and develop our own procedures for
841509 -     creating, submitting, and discussing RFCs, modeled closely after
841510 -     other communities' procedures.
841511 -
841512 -         Eugene seems to be calling for a new way of working proposed
841513 -         by Doug Engelbart, reported on 991222. ref SDS 11 3696  NWO
841514 -         calls for a work role to add intelligence to information,
841515 -         ref OF 3 6369, that expedites understanding and follow up on
841516 -         communication, explained on 890809. ref SDS 2 CJ9J
841517 -         ..
841518 -         On 960122 "librarian" is part of the support a
841519 -         Communication Manager role provides. ref SDS 6 6683  Some
841520 -         authorities suggest the librarian role is recognized by
841521 -         industry, reported on 940510. ref SDS 3 WJ4H  On 940603
841522 -         Stanford was developing mediators to assist expert librarians.
841523 -         ref SDS 4 8J6J
841524 -
841525 -         On 960626 article reports librarians are moving toward
841526 -         becoming knowledge navigators. ref SDS 7 R59H
841527 -
841528 -         On 001025 Doug suggested using a Knowledge Integrator.
841529 -         ref SDS 14 8094
841530 -
841531 -         On 010916 Eric Armstrong expected that Eugene's work using
841532 -         dialog maps could be supported by a new work role which he
841533 -         called an "ontologist." ref SDS 17 4J4J
841534 -         ..
841535 -         Who is the "we" that appoints the librarian?
841536 -
841537 -         Who pays for the librarian from whose budget?
841538 -
841539 -             Yesterday, on 011003 Eric Armstrong explained experience
841540 -             showing that organizing the record is hard work, which he
841541 -             is prepared to perform for payment. ref SDS 18 O73F
841542 -
841543 -             On 890324 executive who authorizes staff assignment says
841544 -             that adding "intelligence" to management is "overkill,"
841545 -             ref SDS 1 LZ5F, so nobody will pay for it. ref SDS 1 UB5F
841546 -
841547 -             On 970624 military commander who approves staffing feels
841548 -             intelligence is not cost effective. ref SDS 8 7388
841549 -         ..
841550 -         What is the work product that justifies payment, and how
841551 -         would work product be applied by people to improve
841552 -         productivity, earnings and stock prices?
841553 -         ..
841554 -         What tools and procedures help the librarian cope with
841555 -         the hopeless quagmire of complexity due to information
841556 -         overload that Eric reports on 011003? ref SDS 18 EC5N
841557 -
841558 -         Would scope of work and deliverables propoposed by the US Army
841559 -         Corps of Engineers for Communication Metrics be helpful for
841560 -         the librarian? ref DRP 1 4929
841561 -
841562 -         What skills, education, experience and temperment is needed
841563 -         for this work, in light of experience reported on 010725 that
841564 -         organizing an effective record is psychologically demanding?
841565 -         ref SDS 16 03M6
841566 -
841567 -         Would the "librarian" role reduce fear that prevents people
841568 -         from using intelligence because, in the beginning....
841569 -
841570 -  ..
841571 -           1.  People fear the light of knowledge, more than they fear
841572 -               the darkness of ignorance, as shown by....
841573 -
841574 -                  Hate accountability........980405, ref SDS 9 5065,
841575 -                  Ignorance is bliss.........991108, ref SDS 10 5368
841576 -                  Knowledge boggles mind.....000125, ref SDS 12 3867
841577 -
841578 -           2.  The effort for being an accountant of information
841579 -               appears beyond reach, like climbing mountains, reported
841580 -               on 950916, ref SDS 5 4930, and noted more recently by
841581 -               Henry van Eaykan on 000926. ref SDS 13 004M
841582 -
841583 -
841584 -
841585 -
841586 -
841587 -
841588 -
841589 -
841590 -
841591 -
841592 -
841593 -
841594 -
841595 -