CONTACTS 
0201 - Blueoxen                                                                                                                                                           O-00000756 0101
020101 - Mr. Eugene Eric Kim                                                                                                                                              O-00000756 0101

SUBJECTS
Summary Context Increase Understanding of Meetings Intelligence Adds
Organize Subjects Manage Information Documents Categories Memory Who,

1804 -
1804 -    ..
1805 - Summary/Objective
1806 -
180601 - Follow up
180602 -
180603 - Eugene Kim notified the group collaborating on developing OHS/DKR-like
180604 - technologies, following up work with Doug Engelbart in 2000, that four
180605 - (4) people have volunteered to summarize the archive record of email,
180606 - saying....
180607 -
180608 -    1.  yak
180610 -         ..
180611 -    2.  Date: Mon, 2 Feb 2004 20:57:32 -0800
180612 -        From: Eugene Eric Kim
180613 -        To: yak
180615 -         ..
180616 -    3.  Subject:  yak@collab] summary volunteers needed
180617 -
180618 -           http://collab.blueoxen.net/forums/yak/2004-02/msg00031.html
180619 -
180621 -         ..
180622 -        Work Role Proposed for Analysis to Summarize the Record
180623 -        Summary Critical Part Adding Intelligence to Information
180624 -        Volunteers to Work Intelligently Shows Transformation Occurring
180625 -
180626 -        One of the questions on the survey sent last November asked if
180627 -        people would be willing to contribute to weekly summaries of
180628 -        the discussion on this group.  A surprising number (4)
180629 -        responded yes. That number was surprising to me, because I
180630 -        expected it to be zero. :-) To me, that indicated the great
180631 -        value that people gained from the summaries, and the
180632 -        recognition that collective effort spent doing the summaries
180633 -        would result in greater returns for all.
180635 -  ..
180636 - What is the basis for summarizing weekly?  Is there experience showing
180637 - weekly summary has greater utility than summarizing by event
180638 - day-to-day, as occurs using SDS?  Why not summarize every two weeks,
180639 - by month or every two months?  How is summary connected to details for
180640 - maintaining alignment with original sources in organizational memory
180641 - called out by management standards, reviewed on 950721, ref SDS 3
180642 - 1740, and required by government regulations to ensure good management
180643 - practice, reviewed on 020504? ref SDS 14 XV7L
180645 -  ..
180646 - Eugene offers no links to any support for asserting there is a need to
180647 - summarize the record.  Other than four people have volunteered, which
180648 - may mean they are looking for something to do, what is the evidence of
180649 - value from saving lives, time and money that people care enough about
180650 - to invest time for this work?
180651 -
180652 -      [...there is new evidence today from another record showing
180653 -      demand for a work role to write up the record, after people have
180654 -      received a record without charge for a year. ref SDS 16 0001
180656 -  ..
180657 - Calling for contributors to volunteer time for summarizing the record
180658 - supports recent ideas Tom Munnecke submitted on having someone or a
180659 - group add value to information in daily correspondence, so that
180660 - progress is expedited on objectives.  This generally supports Com
180661 - Metrics scope for a new professional role defined in the report issued
180662 - by USACE on 970328, ref DRP 3 JM7O, and further called out in NWO,
180663 - noting that in addition to a new role, special tools and leadership
180664 - are essential ingredients for transformation from information to a
180665 - culture of knowledge. ref OF 13 6369
180667 -  ..
180668 - Besides summarizing, in the past, people working on OHS/DKR efforts
180669 - have listed "ontology" and "refactoring" as part of the tasks
180670 - performed by a new work role, e.g., on 001222, ref SDS 9 I53M, and
180671 - later on 010916. ref SDS 11 8M6K
180673 -  ..
180674 - Summary is a key part of "intelligence" defined in POIMS,
180675 - explaining technology for converting information into knowledge.
180676 - ref OF 3 0367  The importance of summary, emphasized in Eugene's
180677 - letter today, was reviewed on 040102, also, calling for organization,
180678 - analysis, alignment, summary, and feedback next year using SDS on
180679 - Gary's project, ref SDS 15 H55F, to implement the eight (8) steps of
180680 - Communication Metrics listed on 001219. ref SDS 8 4W4L
180681 -
180682 -
180684 -  ..
180685 - Summary Supports Collaboration to Cross-fertilize Ideas
180686 -
180687 - Eugene continues...
180688 -
180689 -    4.  Given the scope and depth of recent discussions, we need
180690 -        summaries more than ever.  Additionally, Blue Oxen now hosts
180691 -        several collaboratories -- not just this one -- and there is
180692 -        some very interesting and important discussion there as well.
180693 -        One of the goals of the collaboratories is to facilitate the
180694 -        cross-fertilization of ideas.  Summaries will go a long way in
180695 -        achieving this.
180697 -  ..
180698 - Eugene's rationale for summarizing the record supports the explanation
180699 - in POIMS, ref OF 4 TJ6I, which calls for a process of "summary
180700 - connected to the details of daily work. ref OF 4 6011  Eugene does not
180701 - address the loss of value of summary, and consequent loss of time and
180702 - money, when time is invested to summarize in isolation without also
180703 - performing the critical mass of tasks required for adding intelligence
180704 - to convert information into knowledge.
180706 -  ..
180707 - Would be helpful to get an explanation of how summary cross-fertilizes
180708 - ideas posed in Eugene's letter?  POIMS diagrams the "intelligence"
180709 - cycle of plan, perform, report that leverages human cognition for
180710 - continual learning that generates knowledge and ideas. People are an
180711 - important part of the process through communication that enables
180712 - collaboration.
180713 -
180714 -
180715 -
180717 -  ..
180718 - Hard Work Typically Reduces Performance Even with Payment
180719 - Knowledge Management a Lot of Hard Work Using Information Technology
180720 -
180721 - Eugene continues...
180722 -
180723 -    5.  Having done the summaries the old way, I have a good idea of
180724 -        the time it takes to do them right, and also ways that we can
180725 -        distribute the load.  I'd like to discuss those ideas here, and
180726 -        also hear other people's ideas.  More importantly, I want to
180727 -        collect on those affirmative responses. :-) If you're willing
180728 -        to contribute some time to the summaries in some shape or form,
180729 -        please join the discussion here.  Let's use this forum to hash
180730 -        out the best way to do the summaries.
180731 -
180732 -        -Eugene
180734 -  ..
180735 - Previously, on 001126 Eugene explained the need for summary to improve
180736 - progress on the OHS/DKR project. ref SDS 7 PK4N  At that time, a
180737 - volunteer, Grant Bowman, explained that doing knowledge work is a lot
180738 - of hard work using information tools everybody likes. ref SDS 7 B15I
180739 - Grant asked if people should change their tools? ref SDS 7 X8PW
180740 - Grant's point was supported by prior research reported on 000307.  The
180741 - OHS/DKR team found reports saying that doing knowledge work with
180742 - conventional tools everybody likes is a lot of hard work. ref SDS 4
180743 - 5362  This research is supported by the record over a span of several
180744 - years on the OHS/DKR effort where, other than SDS work product listed
180745 - on 001017, ref SDS 5 1575, and cited by Doug Engelbart on 001027,
180746 - ref SDS 6 OH9N, nobody did any of the steps Eugene listed for helpful
180747 - knowledge practices using popular tools people like.  At that time on
180748 - 001126, Henry van Eykan reported experience showing SDS is effective,
180749 - and faster and easier for knowledge tasks than using popular tools.
180750 - ref SDS 7 K16L  Eugene recommended sticking with popular information
180751 - technology everybody likes. ref SDS 7 QW8I
180753 -  ..
180754 - Eugene's report today that prior efforts he made to summarize show
180755 - that distributing the work will make the new assignment being proposed
180756 - easier for people to support by reducing the amount of hard work any
180757 - one person has to perform. ref SDS 0 VU45  Eugene's planning seems to
180758 - recognize that, without tools to make good management fast and easy,
180759 - cited by Henry van Eykan on 001126, per above, nobody will do it.
180761 -  ..
180762 - On 010916 Eric Armstrong reported observing Eugene work on organizing
180763 - the record of email.  Eric's report that information technology Eugene
180764 - used for dialog mapping made the work slow and difficult, which aligns
180765 - with the picture Eugene describes for the current volunteer task.
180766 - ref SDS 11 4J4J  The next day, on 010917 Eugene seemed to confirm
180767 - Eric's assessment that using information technology for knowledge
180768 - management takes along time. ref SDS 12 MB9H
180770 -  ..
180771 - Under this record, there is no reason to believe volunteers will
180772 - provide summaries of the email archive proposed in Eugene's letter,
180773 - per above. ref SDS 0 TV8H  Besides issues of time and effort, most
180774 - people feel good management is unncessary overkill, reported on
180775 - 890324. ref SDS 1 WR9K  If this is done at all, it may last for a few
180776 - weeks, and will prove to be of marginal utility, since summary
180777 - requires a more robust set of complementary tasks for adding
180778 - intelligence to convert information into useful knowledge.  Eric
180779 - Armstrong reported on 011006 that good management practices are so
180780 - hard and disagreeable to perform, using popular technology everybody
180781 - likes, that people have to be paid to do the work, ref SDS 13 O73F,
180782 - similar to paying coal miners, ditch diggers, lawyers, doctors,
180783 - software engineering and other difficult, sometimes disagreeable
180784 - tasks.
180786 -  ..
180787 - On 010908 Jack Park explained why even well paid engineers, CEOs,
180788 - indeed everybody using popular information technology everybody likes
180789 - has an overwhelming tendency to use bad management, rather than invest
180790 - time to summarize the work and perform the other tasks required for
180791 - working intelligently. ref SDS 10 YF5O  The problem seems most acute
180792 - in organizations where people are well paid, e.g., IBM, Microsoft,
180793 - Bechtal, PG&E, Aerospace company, Lochkeed, et al, where managemet is an Alice in
180794 - Wonderland of continual bumbling, noted by Kissinger reviewed on
180795 - 940609. ref SDS 2 4238
180797 -  ..
180798 - Since volunteers are not paid, the prospects for this initiative seem
180799 - comparable to the prior initiative on 001126, per above. ref SDS 0
180800 - GF6F
180801 -
180802 -
180803 -
180804 -
180805 -
180806 -
180807 -
180808 -
180809 -
180810 -
180811 -
180812 -
180813 -
180814 -
180815 -
180816 -
180817 -
180818 -
180819 -
180820 -
180821 -
180822 -
1809 -