CONTACTS 
0201 - Deneen Consulting                    925 229 1858
020101 - Mr. John Deneen
020102 - jjdeneen@ricochet.net

SUBJECTS
Tennenhouse, David VP Intel R&D Big Budget for Supporting Research at
Intel Has Budget under David Tennenhouse to Manage Project at UC Berk
CITRIS Project at UC Berkeley Managed by David Tennenhouse VP Intel R
Letter to Morris Requesting Support for Contacting Intel R&D Big Budg
Shipman Incremental Formalization Overcomes Objections to Capturing I
Jones, Morris Does Not Use SDS
Pictures PDF Not Efficient for Com Metrics KM Takes Too Much Time
Productivity Text Better for Management than Wordprocessing Need Flex
Pictures PDF Unproductive Waste Time Need Flexible Structure Addressa
Intelligence Uncommon Sense Counterintuitive Paradigm Shift Creativit
Culture Barrier to Intelligence in Business Work Practices Needed in
Writing Not Enough Time Paperwork Documentation Conversation Fast and
Incremental Intelligence Don't Write Record All at Once Get Help
Shipman, Frank Incremental Formalaization Overcomes Resistance to Cap
Context Analysis Story Associate Data Information with Objectives Req
Chompsky Grammer Innate Genetic Mental Capacity Reviewed with Landaue

3518 -    ..
3519 - Summary/Objective
3520 -
352001 - Follow up ref SDS A0  0000, ref SDS 99 0000.
352002 -
352003 - John Deneen submitted a letter with references to excerpts from PDF
352004 - files intended to address resistance to supporting SDS.  A copy was
352005 - sent to Morris.  A two pronged arguement is presented that national
352006 - security currently requires increased attention to SDS intelligence,
352007 - and objections to not having enough time can be met in part by
352008 - creating the record incrementally, rather than all at one time.  There
352009 - seems to be an error in characterizing Morris as a user of SDS. Morris
352010 - does not use SDS. ref SDS 0 FF6H  "Formalization" is not defined, and
352011 - since PDF does not support links, John was unable to direct attention
352012 - to the defintion, which was located after considerable research.
352013 - ref SDS 0 TR5H  Formalization seems contemplate providing data base
352014 - structure for computer processing using an AI "engine" similar to
352015 - proposals offered the past two years for OHS/DKR.  SDS offers a design
352016 - that produces intelligence without computer processing. ref SDS 0 TR5H
352017 - It merely requires explaining what was used and where it is located.
352018 - ref SDS 0 FF5K  Incremental formalization proposed to overcome
352019 - resistance to SDS may be misplaced, since the difficulty that occurs
352020 - is conceptual, not time per se. ref SDS 0 9L5J  On the other hand,
352021 - "formalization" defined within the meaning "intelligence" set out in
352022 - POIMS, ref SDS 0 RU5K, is supported by incremental development of the
352023 - record, which aligns in some degree with Shipman et al.  Called and
352024 - discussed with Morris sending in a recommendation to Tennhouse at
352025 - Intel.  Morris was disappointed about getting SDS material with links.
352026 - One link seems to be okay, clicking on two links causes failure.
352027 - Morris requested Wayne Wetzel's report in printed format. ref SDS 0
352028 - U69M
352029 -
352030 -      [On 011015 sent printed copy of Wayne's report and ideas to help
352031 -      Morris prepare a recommendation to Tennenhouse. ref SDS A7  0001
352032 -
352033 -      [Sent John regular email linked to this record showing follow
352034 -      up.
352035 -
352036 -
352037 -
352038 -
352039 -
352040 -  ..
3521 -
3522 -
3523 - Progress
3524 -
352401 -  ..
352402 - Productivity Organizational Memory Requires Judicious Application
352403 - Organizational Memory Requires Effective Application for Productivity
352404 - Lack of Intelligence Delays Understanding of Intelligence Benefits
352405 - Incremental Formalization Overcomes Resistance to Intelligence
352406 -
352407 - Received ref DRT 1 0001 from John Deneen dated 011003, commenting on
352408 - the copy he received of the letter, ref DIP 5 0001 submitted to Morris
352409 - on 010928, ref SDS A0  0001, that confirmed telecon on 010924
352410 - discussing John's idea for Morris to propose to David Tennenhouse that
352411 - SDS be considered to support management of CITRIS, ref SDS 98 5F6N,
352412 - which came from a telecon with John earlier in the day. ref SDS 98
352413 - KD7M
352414 - ..
352415 - More attention is needed to providing context for links to new
352416 - information, so that people do not waste hours hunting for relevant
352417 - connections to objectives, requirements and commitments per Morris'
352418 - concern below. ref SDS 0 ID5I  Value of adding intelligence with
352419 - summary and context was explained by Gil Regev in a letter on 001019.
352420 - ref SDS 64 IM5F  Recently, on 011003 Eric Armstrong explained that new
352421 - realities of information overload increase benefits of intelligence to
352422 - improve productivity. ref SDS A1  EC5N
352423 -
352424 -      [On 011010 letter to Eric Armstrong proposes rather than give up
352425 -      on clicking links, provide context. ref SDS A6 M55G
352426 - ..
352427 - John explains in his letter today that.....
352428 -
352429 -      Review of SDS records linked in the letter to Morris Jones on
352430 -      010928, ref DIP 5 0001, suggests that objection to formalization
352431 -      in SDS records, that Mr. Jones and others seem to express were
352432 -      solved or mitigated using "incremental formalization" based on
352433 -      R&D experience with a software program called "Hyper-Object
352434 -      Substrate". ref DRT 1 0001
352435 -
352436 -          "Formalization" needs to be defined, and a link to something
352437 -          is needed that illustrates the definition in relation to SDS
352438 -          work product John cites, but does not link.
352439 -
352440 -          On 011004 Eugene Kim proposed using a "formalizm" of RFCs to
352441 -          better manage the work load for reviewing correspondence and
352442 -          links on new technologies that might advance the OHS/DKR
352443 -          project. ref SDS A2  M16F  Is this the reference for John's
352444 -          letter today?
352445 -
352446 -               ..
352447 -              PDF, Printed Media Inefficient for Intelligence
352448 -
352449 -              Below, John quotes recommendations from Shipman in a PDF
352450 -              file, but the quotes do not define "formalization,"
352451 -              merely cite resistance to it can be overcome in part by
352452 -              incremental, rather than all/or nothing application.
352453 -              ref SDS 0 L13F  Further in one of the pdf files there is
352454 -              a definition that sounds like an AI solution. ref SDS 0
352455 -              T17F
352456 -
352457 -
352458 -           ..
352459 -          Context Critical for Efficient Intelligence Capability
352460 -
352461 -          It helps to list which SDS records were examined, and what
352462 -          was reviewed in relation to objectives, requirements and
352463 -          commitments under consideration, as Doug Engelbart requested
352464 -          in his letter to the OHS/DKR team on 001025. ref SDS 65 00VU
352465 -          Organizational memory is only productive if care is used in
352466 -          providing context that enables timely, judicious review of
352467 -          links, explained on 990419. ref SDS 35 2601
352468 -
352469 -             [...below, Morris worries clicking on links wastes too
352470 -             much time. ref SDS 0 ID5I
352471 -
352472 -
352473 -           ..
352474 -          Intelligence New Method to Culture of Business Management
352475 -          Culture and Tradition Barriers to Learning New Methods
352476 -
352477 -          Morris is not a "user" of SDS, so this seems to be an error
352478 -          in John's letter, ref DRT 1 0001, that can be resolved by
352479 -          disclosing what was reviewed that left the impression Morris
352480 -          uses SDS.
352481 -
352482 -          On 010924 Morris discussed cultural pressures that make it
352483 -          difficult for people to create and use SDS, generally
352484 -          summarized as ignorance, fear and denial. ref SDS 98 XT5F
352485 -
352486 -          POIMS explains barriers to using "intelligence" in business.
352487 -          ref OF 1 5820
352488 -
352489 -          People do not understand benefits of intelligence, due to
352490 -          lack of experience, i.e., ignorance, and so fear investing
352491 -          time to learn something for which benefits are deferred. This
352492 -          leads to denial that intelligence is useful, under the
352493 -          pejorative of "overkill."  People don't understand the
352494 -          alphabet either, but they are put on a bus at an early age
352495 -          and taken to a place where they are encouraged to learn, and
352496 -          this brings a lifetime of benefits, despite lack of ever
352497 -          understanding the magic of alphabet technology.  Adults do
352498 -          not have this advantage, and so without encouragement, they
352499 -          will do what seems fast and easy at the time, as discussed on
352500 -          010924. ref SDS 98 W63J
352501 -
352502 -
352503 -           ..
352504 -          Experience Imparts Understanding Solves Innovation Loop
352505 -          Innovation Loop Prevents Discovering Benefits Intelligence
352506 -          Fools Gold Attracts Customers Looking for Easy Diggings
352507 -
352508 -          On 920215 Morris cited frustration learning to link records,
352509 -          as the reason for giving up using SDS, ref SDS 8 5820,
352510 -          stating software that is easy to learn is attractive to top
352511 -          executives, ref SDS 8 5774, despite not improving management,
352512 -          like fools gold, explained on 890809, ref SDS 2 MO5H, and
352513 -          reviewed recently on 001004. ref SDS 61 636N  However, the
352514 -          actual problem was an innovation loop of not understanding,
352515 -          and so not using SDS, which denied experience that imparts
352516 -          understanding of the SDS design supporting the intelligence
352517 -          process of plan, perform, report, ref SDS 8 QH3I, see POIMS.
352518 -          ref OF 1 1102  Earlier, analysis on 910529 shows that
352519 -          centuries of tradition forged by necessities of a manual
352520 -          world create cultural blinders that prevent most people from
352521 -          grasping the SDS design, without transition support.
352522 -          ref SDS 5 9989  Failure to obtain support, due to hubris, or
352523 -          cultural pressure, cited on 990527, ref SDS 37 1233, for
352524 -          example on 920402 "image" is major factor, ref SDS 9 0001,
352525 -          that makes it difficult for new users to gain skill quickly
352526 -          enough for benefits of "knowledge," which are inherently
352527 -          deferred, to outweigh feelings of inadequacy and loathing
352528 -          that occur when people, who are well paid, struggle to learn
352529 -          how to improve earnings, as noted by Andy Grove reported in
352530 -          the record on 980307. ref SDS 30 1660
352531 -
352532 -
352533 - John seems to quote, possibly from the R&D research initially
352534 - cited, that....
352535 -
352536 -      • premature structuring -- solved by not forcing users to
352537 -        initially enter formal information;, ref DRT 1 4Q6G;
352538 -
352539 -      • cognitive overhead -- mitigated due to lower overhead for
352540 -        initial entry and demand-driven effort required for later
352541 -        formalization;, ref DRT 1 NQ6J; and
352542 -
352543 -      • tacit knowledge -- mitigated by suggestion mechanisms which
352544 -        promote conscious understanding of previously tacit knowledge.
352545 -        ref DRT 1 ZQ6M
352546 -
352547 -
352548 -  ..
352549 - Intelligence National Security Increase Demand for SDS
352550 - National Security Focuses Attention on Benefits of Intelligence??
352551 - Benefits for Intelligence Encourage People to Improve the Work???
352552 -
352553 - John quoting from an article in the New York Times.....
352554 -
352555 -
352556 -         "Earlier Hijackings Offered Signals That Were Missed"
352557 -
352558 -
352559 - ....published on 011002 explaining weaknesses and lessons learned on
352560 - "intelligence" gathering, ref DRT 1 8M7F,
352561 -
352562 -       "[T]he failure to heed these signs is "an indication of failure
352563 -       to put the pieces together," said Gerald B. Kauvar, who was the
352564 -       staff director of the commission headed by Vice President Al
352565 -       Gore on aviation security and safety after the crash of T.W.A.
352566 -       Flight 800 off Long Island in July 1996. ref DRT 1 KO7M
352567 -
352568 - John further notes, perhaps continuing to quote from NYT article....
352569 -
352570 -    The authorities appeared to draw no lessons from the two attacks in
352571 -    1994.  But one of [the attacks] in hindsight, ref DRT 1 4Q8J, had
352572 -    striking similarities to [the terrorist attacks] of 010911....
352573 -
352574 -    ... But extrapolation may be a key lesson of Sept. 11. According to
352575 -    one executive at an aviation trade organization, "now we need to do
352576 -    that in very element of our life; that's how we fight this new
352577 -    war." ref DRT 1 AR8O
352578 -
352579 -         This is the "valley of death" issue Andy Grove's poses in his
352580 -         book, "Only the Paranoid Survive," reviewed on 980307.
352581 -         ref SDS 30 1660  On 001207 Reuters reported looming recession
352582 -         because too many people have too many problems. ref SDS 70
352583 -         V54M  On 000425 research showed SDS adds intelligence to daily
352584 -         work for "connecting the dots" of cause and effect" to see
352585 -         problems early so adjustments can be made before disaster
352586 -         strikes. ref SDS 51 0480  Since 001207 recession has struck
352587 -         with the most layoffs in 10 years, because people have too
352588 -         many problems.  Now, military intelligence failure has
352589 -         occurred, as forecast on 980815. ref SDS 32 1173
352590 -
352591 -         John does not say in his letter that DNRC, PG&E, USACE and SRI
352592 -         found that SDS provides useful intelligence to meet the demand
352593 -         created by the current national security crisis, and to work
352594 -         our way out of recession.  Neither does John say that no other
352595 -         technology is available for doing this, nor does he cite any
352596 -         other technology that can do this.
352597 -
352598 -         What then is the purpose of the letter?
352599 -
352600 -
352601 -
352602 - John continues....
352603 -
352604 -    Insightful analysis of these problems for SDS, OHS/DKR, Topic Map,
352605 -    etc., designers, including getting explicit formalization (e.g.,
352606 -    from aviation security and safety experts), ref DRT 1 959K
352607 -
352608 -         What does this mean?
352609 -         ..
352610 -         What is "formalization"?  What is explicit formalization
352611 -         in relation to other kinds?  Are there any examples?
352612 -
352613 -         SDS is a software program that strengthens use of alphabet
352614 -         technology for performing deliberative analysis that applies
352615 -         the intelligence process of plan, perform, report, explained
352616 -         in POIMS. ref OF 1 3742
352617 -
352618 -         OHS/DKR does not exist, there is no capability for using topic
352619 -         maps that accomplishes SDS capability; neither are there any
352620 -         designers working on OHS/DKR for supporting "intelligence"
352621 -         based on the report during the meetings at SRI on 000615,
352622 -         ref SDS 55 6271, and a year later on 010605. ref SDS 83 RU5O
352623 -
352624 -         After 2 years of research by SRI, there is no evidence of
352625 -         anyone ever saving time and money using a topic map for
352626 -         anything?  If so, provide a link.
352627 -
352628 -         What "analysis" is needed beyond using SDS for intelligence?
352629 -
352630 -  ..
352631 - John cites from two pdf files....
352632 -
352633 -    F Shipman and R. McCall, "Supporting Incremental Formalization with
352634 -    the Hyper-Object Substrate", ACM Transactions on Information
352635 -    Systems, 17, 2 (April 1999), pp. 199-227. ref DRT 1 YQ4F
352636 -
352637 -        http://www.csdl.tamu.edu/~shipman/tois-hos.pdf
352638 -
352639 -    This paper at para 5.1 says....
352640 -
352641 -       HOS [Shipman's et al, idea] was used for two semester projects
352642 -       in a graduate-level knowledge systems class. Each project was
352643 -       the work of a single student and took place over a period of two
352644 -       to three months. The goal of the class projects was to create a
352645 -       knowledge-based system for a domain and task of the student's
352646 -       choice.
352647 -
352648 -          Pilot testing knowledge management technology for 3 months by
352649 -          a few students in a college course, will not move any adults
352650 -          to improve the work.  SDS has been used for nearly 20 years,
352651 -          and found by PG&E, USACE, SRI, DNRC to save time and money.
352652 -          There is an extensive record demonstrating benefits of this
352653 -          method, as reported by DCMA on 010608. ref SDS 84 RS4J  But
352654 -          DCMA, also, reported on 010730 that ignorance, fear and
352655 -          denial prevents adults from improving the work to save time
352656 -          and money. ref SDS 93 P74N
352657 -
352658 - John lists a second pdf file....
352659 -
352660 -    F Shipman, C. Marshall, M. LeMere, "Beyond Location: Hypertext
352661 -    Workspaces and Non-Linear Views", ACM Hypertext '99 Proceedings,
352662 -    121-130. (won the Douglas Engelbart best paper award), ref DRT 1
352663 -    SR4O
352664 -
352665 -        http://www.csdl.tamu.edu/~shipman/ht99.pdf
352666 -
352667 -  ..
352668 -       Frank Shipman's work was reviewed previously on....
352669 -
352670 -          001220..............................., ref SDS 72 813M
352671 -
352672 -              Rigid formalization required by IBIS is not effective for
352673 -              knowledge work.
352674 -
352675 -
352676 -          001222..............................., ref SDS 73 K58L
352677 -
352678 -              Time key factor in knowledge.
352679 -
352680 -
352681 -  ..
352682 -
352683 - John's letter today, does not state from which document he quotes, but
352684 - opening and hunting through the pdf files cited above shows the
352685 - following is quoted from....
352686 -
352687 -        http://www.csdl.tamu.edu/~shipman/tois-hos.pdf
352688 -
352689 -    ... "The situation is ironic. On the one hand, users -- and
352690 -    software designers -- want proactive, high-functionality systems to
352691 -    support their daily work. On the other hand, users resist the
352692 -    formalization of information that is required for such higher-level
352693 -    functionality. ref DRT 1 NT6H
352694 -
352695 -
352696 -     ..
352697 -    SDS Supports Intelligence without Formalization, IBIS
352698 -    Formalization Uses Engine to Make Structure Semantics Explicit
352699 -
352700 -
352701 - Research in the pdf file shows in para 1 below the abstract....
352702 -
352703 -    ....developing proactive systems has been limited by fundamental
352704 -    difficulties in obtaining formalized information from users - i.e.,
352705 -    information whose structure and semantics are indicated explicitly.
352706 -    Current limitations of computers, especially the inability to
352707 -    process unrestricted natural language, mean that input generally
352708 -    must be formalized in order for significant computation to be done
352709 -    on the basis of it.
352710 - ..
352711 - Shipman, et al state further, beginning in para 1.1....
352712 -
352713 -    For the purposes of this paper we define formalization as the
352714 -    process of putting information in a symbolic form that can be
352715 -    processed by computer, or what Chomsky describes as a "formal
352716 -    language" [1956]. According to Chomsky's definition, computers can
352717 -    only process information that has been formalized, so some degree
352718 -    of formalization is required for computers to be of any use.
352719 -         ..
352720 -         This sounds like the "engine" proposed by Jack Park on
352721 -         000623, ref SDS 56 2915, to process text with computational
352722 -         linguistics, cited by NSF on 991213. ref SDS 45 3234
352723 -
352724 -         On 000425 Paul Fernhout pointed out no one has created the
352725 -         "engine" needed for Shipman's et al, idea. ref SDS 50 B8R4
352726 -         Same point was made on 001025. ref SDS 65 LR6N  On 010730 DOD
352727 -         understands KM to be an "engine" that processes email to make
352728 -         sense of something, ref SDS 93 WK9K, which sounds like a DARPA
352729 -         project that failed, leading to folks being discouraged, cited
352730 -         by Pat Lincoln on 010426. ref SDS 78 657O
352731 -
352732 -         Shipman, et al, do not cite work product showing their ideas
352733 -         can be implemented; they merely suggest another architecture,
352734 -         which has been investigated by OHS/DKR for 18 months, and
352735 -         found not susceptible for development.
352736 -
352737 -         SDS supports "intelligence" that enables proactive management,
352738 -         defined above, ref SDS 0 TZ4H, without an "engine" that
352739 -         creates explicit structure and semantics called out by Shipman
352740 -         et al. ref SDS 0 T17F  Or, stated another way, SDS provides an
352741 -         environment of flexible structure that has proven effective,
352742 -         as reported by USACE. ref DRP 6 6172
352743 -
352744 -  ..
352745 - Shipman, et al, continue in the same para....
352746 -
352747 -    More specifically, proactive systems require such formalization
352748 -    both to identify the tasks users are performing and to aid them in
352749 -    these tasks.
352750 -
352751 - Figure 1 in the paper indicates "argumentation" processing that may
352752 - imply IBIS, which has proven too rigid, reported on 000218.
352753 - ref SDS 48 7050
352754 -
352755 -         SDS does not require "formalization" both to identify the
352756 -         tasks users are performing and to aid them in these tasks.
352757 -
352758 -             [On 011213 Terry Winograd at Stanford seems to ask about
352759 -             this issue in relation to using SDS. ref SDS B0 UT4I
352760 -
352761 -         SDS provides capabilities for adding flexible structure, some
352762 -         automatic and some according to voluntary determinations that
352763 -         enable people to customize the record to meet evolving context
352764 -         of objectives, requirements and commitments. see POIMS,
352765 -
352766 -
352767 -  ..
352768 - Below figure 1, the authors state in part.....
352769 -
352770 -    ....moving information from a less formal to a more formal
352771 -    representation includes the delimiting of "chunks," as well as the
352772 -    determination of their types, properties (attributes and values)
352773 -    and relationships to other information "chunks."
352774 -
352775 -         This is a constructive idea that may be attributed to work by
352776 -         Chompsky, but cannot link into the paper to verify; it does
352777 -         seem to align with Miller's paper reviewed on 990303.
352778 -         ref SDS 34 LX6F
352779 -
352780 - Shipman, et al state in para 1.3.....
352781 -
352782 -    1.3 Problems in Getting Explicit Formalization from Users
352783 -
352784 -    ....it takes a great deal of extra time and effort.  Often this
352785 -    extra effort is not balanced by a payoff at the time the
352786 -    formalization is required and for the persons who must do the
352787 -    formalization. This discrepancy is noted by Grudin [1994] as a
352788 -    particular challenge for groupware.  Even relatively small amounts
352789 -    of this extra time and effort can disrupt the flow of work, causing
352790 -    attention to shift from the task to the system, as described in the
352791 -    case of design in [Fischer et al. 1991].
352792 -
352793 -          ..
352794 -
352795 -         Investing intellectual capital takes time, which by definition
352796 -         brings deferred rewards.  That is the critical difference
352797 -         between grazing on information and producing knowledge.  The
352798 -         authors fail to point out that, far from disrupting" the flow
352799 -         of work, investing time for adding intelligence to align work
352800 -         with objectives, requirements and commitments is critical in
352801 -         the new world order of a faster information to get things done
352802 -         correctly, on time and within budget, and failure to invest
352803 -         time for intelligence causes deferred costs, loss, delay,
352804 -         conflict, crisis and calamity, most often transferred to
352805 -         others, as Aristotle pointed out some time ago, see NWO.
352806 -         ref OF 2 YD6O see, also, POIMS, ref OF 1 VX7N, and analysis of
352807 -         high cost of medical mistakes on 990924. ref SDS 42 5576
352808 -
352809 - Authors continue....
352810 -
352811 -    The difficulties that users experience are not just interface
352812 -    problems.
352813 -
352814 -    Formalization requires many extra decisions to divide information
352815 -    into chunks, to type and label these appropriately, to link them
352816 -    with useful relationships and assign properties to them. If users
352817 -    end up focusing their energies on formalization rather than the
352818 -    domain task they are supposed to perform, the use of the computer
352819 -    could lead to the quality of their work actually being decreased
352820 -    rather than enhanced.
352821 -
352822 -         What evidence supports a proposition that adding intelligence
352823 -         to management decreases the quality of the work?
352824 -
352825 -         SDS provides inherent structure, and makes it fast and easy to
352826 -         produce useful intelligence, reported on 950204. ref SDS 15
352827 -         4995  USACE found adding intelligence improves the quality of
352828 -         everyone's work. ref DRP 6 6172
352829 -
352830 -         What slows SDS down is wading through a pdf file.
352831 -
352832 - Authors continue....
352833 -
352834 -    ....substantial time and effort are typically required to learn a
352835 -    formalism and to develop skill in representing ideas in it. This
352836 -    requires both talent and interest in formalization that users are
352837 -    unlikely to have.
352838 -
352839 -         Authors err in failing to note people require an interest in
352840 -         protecting national security, reported on 980815, ref SDS 32
352841 -         1173, and improving productivity, earnings and stock prices by
352842 -         avoiding continual bumbling, reported on 001207. ref SDS 70
352843 -         V54M
352844 -
352845 -
352846 - John's letter continues to quote....
352847 -
352848 -    At first glance it might seem that we are facing an intractable
352849 -    dilemma: users demand higher levels of functionality yet are
352850 -    unwilling to pay the inevitable price of increased formalization
352851 -    efforts.  But the appearance of dilemma here is illusory. It
352852 -    derives from the mistaken notions that formalization is an
352853 -    all-or-nothing and all-at-once proposition.  We argue here that an
352854 -    incremental approach to formalization is both acceptable to users
352855 -    and effective in getting far greater amount of formalized
352856 -    information into systems. ref DRT 1 C76O
352857 -
352858 -         What is a "user."  User of what?
352859 -
352860 -         Where is support for the proposition that "users" demand
352861 -         higher levels of formalization?  All of the evidence indicates
352862 -         people eschew formalization; there is overwhelming desire for
352863 -         empowerment to use bad management, because it seems fast and
352864 -         easy, as Grant Bowman noted on 001012. ref SDS 62 PT5M  On
352865 -         001101 an article cited this problem in technology sector.
352866 -         ref SDS 66 MX6H  Same problem in medical profession, reported
352867 -         on 990912. ref SDS 41 0960
352868 -         ..
352869 -         For example, if "formalization" referred to constructing
352870 -         a story from impressions conveyed by data and information
352871 -         connected to objectives, requirements and commitments, which
352872 -         are linked to chronologies of cause and effect that form a
352873 -         comprehensible pattern that conveys future consequences, as
352874 -         called out by Jeremy Campbell reviewed on 900303, ref SDS 4
352875 -         3016, this relates to organizational memory, intelligence,
352876 -         intellectual capital, perhaps a DKR or knowledge repository,
352877 -         as set out in POIMS. ref OF 1 1101
352878 -
352879 -         However, such is not Shipman's et al, referent, per above.
352880 -         ref SDS 0 TR5H
352881 -
352882 -         On 010420 Jeff Conklin argues there is strong demand for
352883 -         organizational memory, but offers no evidence. ref SDS 75 IE4M
352884 -         Experience on the OHS/DKR effort indicates there is no demand
352885 -         for knowledge, there is only demand for information, as
352886 -         related on 001126. ref SDS 68 QW8I
352887 -
352888 -         Therefore, apart from "arguing," where have these folks done
352889 -         any formalization or incremental formalization that provides
352890 -         experience showing resistance is "illusory."  Is there an
352891 -         example of work product and experience showing people can
352892 -         overcome resistance to such work product?
352893 -
352894 -
352895 -     ..
352896 -    SDS Implements Incremental Formalization
352897 -
352898 -    With this approach formalization need not be done at the time of
352899 -    information input and exclusively by the user; it can be done
352900 -    during system use and with substantial support from the computer.
352901 -    ref DRT 1 RD3M
352902 -
352903 -         Something done by the computer implies Jack's engine, per
352904 -         above. ref SDS 0 T17F
352905 -
352906 -         SDS implements this objective, explained on 001219.
352907 -         ref SDS 71 FO5M and specifically at ref SDS 71 OW6M
352908 -
352909 -
352910 - Continuing to quote from John's excerpt from F Shipman, C. Marshall,
352911 - M. LeMere...
352912 -
352913 -    In the following section we explain the approach we call
352914 -    incremental formalization.  We then propose a software architecture
352915 -    for supporting this approach -- an architecture instantiated in a
352916 -    prototype we call the Hyper-Object Substrate (HOS).  Following
352917 -    this, we describe experiences in using HOS for several types of
352918 -    applications that benefit from incremental formalization.  We
352919 -    conclude by summarizing the benefits of HOS and by identifying
352920 -    issues that arose from our experience with the system." ref DRT 1
352921 -    1F4G
352922 -
352923 -         How can any explanation of "intelligence" be delivered in a
352924 -         pdf file, since effective intelligence requires connection to
352925 -         links, and pdf files do not have this capability?  It is like
352926 -         delivering an automobile in a covered wagon.  As long as people
352927 -         are driving the covered wagon, they will never grasp the
352928 -         benefit of driving an automobile.
352929 -
352930 -
352931 - Following review of John's letter to Morris and I, per above,
352932 - ref SDS 0 HMTX, called and talked to Morris.
352933 -
352934 -
352935 -
352936 -
352937 -
352938 -
352939 -
3530 -

SUBJECTS
Video Conferences Cannot Capture Record of What is Said Voice Recogni

3604 - 0815
3605 -
360501 -  ..
360502 - Video Conferencing Not Supported by Voice Recognition Data Entry
360503 -
360504 - Morris will be listening to a broadcast on the computer this morning.
360505 -
360506 - I asked if Intel is using the video conferencing stuff that has been
360507 - promoted for selling computers the past few years?
360508 -
360509 - Morris advised this is used on rare occasions, because it has proven
360510 - to irrelevant, i.e., it does not contribute to productivity, earnings
360511 - and stock prices.
360512 -
360513 - I asked if Intel has come up with a reliable method for capturing what
360514 - is said in teleconferences?  So, for example, is he just going to
360515 - listen and observe the broadcast this morning, or make an effort to
360516 - capture the record?  Morris said I know the answer to that, so I guess
360517 - there has not been any progress on voice recognition.
360518 -
360519 -      [On 011008 received business lead on combining SDS and voice
360520 -      recognition software. ref SDS A5  0001
360521 -
360522 -
360523 -
360524 -
360525 -
3606 -

SUBJECTS
Cables, SCSI
Tape Backup, Exabyte 10 GB
Adaptec SCSI Card for Exabyte Mammoth LT Tape Drive
SCSI Adapters Controller Hard Disk Tape Drives Scanners

4207 -
420701 -  ..
420702 - Purchasing SCSI Adapter Bare Adequate, Use Existing Cable
420703 -
420704 - Reviewed issue about purchasing a SCSI adapter under consideration
420705 - from research yesterday afternoon. ref SDS A3  ZG6M  In particular, is
420706 - the existing ribbon cable adequate, so that the adapter can be
420707 - purchased "bare" for $156, rather than purchase the retail version
420708 - which includes a cable, as explained on 011005. ref SDS A3  I19O
420709 -
420710 - Morris feels the existing cable that came with the Mammoth LT Exabyte
420711 - tape drive should work with the Adaptec SCSI adapter 19160, so buying
420712 - the unit "bare" is likely adequate to accomplish installation.
420713 -
420714 -     [On 011008 followed up. ref SDS A4  0001
420715 -
420716 -
420717 -
420718 -
420719 -
420720 -
4208 -

SUBJECTS
SDS Endorse for Intelligence to Aid National Security Crisi
Fear Accountability Innovation Loop Knowledge Avoids Mistakes
Responsibility Notice Burden of Knowledge
Click Links Fear Responsibility Notice Burden of Knowledge
Object Click Links Fear Responsibility Notice Burden
Printed Report Requested Avoid Responsibility for Knowledge
Willfully Blind Object Click Links Fear Responsibility Notice Burden
Endorse SDS for Intelligence Initiative Based on Typical Day Scenario
SDS History Evaluating and Assessing Need for SDS
Print Preferred Fear Responsibility Notice Burden of Knowledge

6913 -
691301 -  ..
691302 - Responsibility for Knowledge Impossible to Avoid
691303 - Fear of Responsibility for Knowledge Request for Printed Media
691304 -
691305 - We reviewed two pending and related issues....
691306 -
691307 -     1.  On 010921 requested Morris to submit a letter endorsing SDS,
691308 -         ref SDS 97 0001, similar to the letter Wayne Wetzel submitted
691309 -         on 010725. ref SDS 90 0001
691310 -
691311 -     2.  On 010928 requested Morris notify David Tennenhouse, VP R&D at
691312 -         Intel, about using SDS for managing the CITRIS project.
691313 -         ref SDS A0  0001
691314 -
691315 -  ..
691316 - Morris advised this morning he has not read Wayne Wetzel's report on
691317 - using SDS, because he was disappointed that it takes two clicks
691318 - instead of one, i.e., click to the record and click on any link to get
691319 - Wayne's report.
691320 -
691321 - Morris cited his letter on 010921 giving notice that he clicked on the
691322 - link in the transmittal email, and this opened an SDS record, rather
691323 - than Wayne's letter on 010725. ref SDS 97 NE8G
691324 -
691325 - Morris recalled receiving a second letter on 010921 explaining he can
691326 - open Wayne's letter by clicking on any link in the SDS record that has
691327 - context for reviewing Wayne's letter. ref SDS 97 KN5M
691328 -
691329 -  ..
691330 - Morris advised this morning that he does not want context.
691331 -
691332 - Morris feels clicking on a second link is too much work.  He advised
691333 - that clicking on two links takes more time; and he seemed to relate an
691334 - Intel policy not to waste time opening a lot of links.
691335 -
691336 -     Morris' concern reflects in part Eric Armstrong's letter a few
691337 -     days ago on 011003 explaining information overload paralyzes
691338 -     productivity in a hopeless quagmire of complexity. ref SDS A1
691339 -     EC5N
691340 -
691341 -     Not wasting time opening unproductive links is important to
691342 -     productivity.  Using technology productively requires feedback
691343 -     explaining a link wasted time, and suggesting improvements, per
691344 -     above on the need for intelligence to provide summary and context
691345 -     that aids understanding. ref SDS 0 LY9O  Failure to provide
691346 -     feedback prevents improving work practices.  The problem of
691347 -     unproductive links is not solved by avoiding links altogether,
691348 -     which reflects fear of responsibility for knowledge, which cannot
691349 -     be accomplished in any case, as related on 991014. ref SDS 44 5304
691350 -
691351 -  ..
691352 -
691353 - Morris requested Wayne's report be re-submitted in a printed format,
691354 - so there is no burden to click on links for support and context.
691355 -
691356 -       [On 011015 sent printed copy of Wayne's report and ideas to help
691357 -       Morris prepare a recommendation to Tennenhouse. ref SDS A7  0001
691358 -
691359 -     On 991014 leadership must embrace knowledge, not shrink from it.
691360 -     ref SDS 43 3066  The same issue arose on 000504. ref SDS 53 5092
691361 -
691362 -     Advantages of using SDS records online rather than printing was
691363 -     reviewed with DCMA. ref SDS 93 EP3O
691364 -
691365 -     Using printed media is a related issue to destroying the record,
691366 -     to avoid the burden of improving management.
691367 -
691368 -     Clear, concise, complete communication is supported by SDS to
691369 -     balance the need for fast access to support information, and avoid
691370 -     getting lost in a lot of links, reviewed with Dave Buoncristiani
691371 -     on 990419. ref SDS 35 2601 and particularly at ref SDS 35 0896
691372 -
691373 -
691374 -  ..
691375 - Morris feels he does not know what to say for endorsing SDS.
691376 -
691377 -     The letter to Morris on 010921 provides context and background for
691378 -     preparing a constructive recommendation on SDS, based on Morris
691379 -     having contributed to SDS over the past 20 years, and interacting
691380 -     with SDS work product. ref SDS 97 NU7I
691381 -
691382 -         [On 011129 Morris objects to SDS on religious grounds; does
691383 -         not want to consider cognitive science. ref SDS A8 MG8N
691384 -
691385 -     On 010924 Morris offered favorable comments on SDS. ref SDS 98
691386 -     NK4J, noting rare agreement. ref SDS 98 X66J  On 010928 Morris was
691387 -     referred, ref SDS A0  G88L, to his favorable comments on 010425.
691388 -     ref SDS 76 EP7F  Accordingly, there is no shortage of analysis
691389 -     Morris has offered over the past 20 years on SDS, that can be used
691390 -     to craft an endorsement at this time.
691391 -
691392 -     Wayne's letter on 010725 has ideas to help Morris craft an
691393 -     endorsement. ref SDS 90 WJ7L
691394 -
691395 -     Bridge concepts from IT to Com Metrics are listed in the record on
691396 -     010730, which Morris can use to illustrate his explanation of SDS.
691397 -     ref SDS 93 2O6I
691398 -
691399 -     To save time, the letter on 010921 offered to assist Morris in
691400 -     preparing a letter on SDS. ref SDS 97 0001
691401 -
691402 -
691403 - Morris indicated that requesting a letter explaining experience
691404 - showing SDS strengthens management, as in the case of....
691405 -
691406 -  ..
691407 -
691408 -      DNRC.................................. 010725, ref SDS 90 0001
691409 -      USACE................................. 970418, ref SDS 25 3368
691410 -      PG&E.................................. 950110, ref SDS 14 0001
691411 -
691412 -
691413 - ....and which formalizes Morris' prior comments on SDS advantages....
691414 -
691415 -
691416 -      Likes SDS architecture................ 890809, ref SDS 3 8211
691417 -      Listening critical to communication... 890809, ref SDS 3 CJ9J
691418 -      Breakthrough design................... 910810, ref SDS 6 7793
691419 -      Unique management method.............. 911123, ref SDS 7 0477
691420 -      Small details cause major problems.... 921127, ref SDS 10 0674
691421 -      Organizational memory solves problems. 950228, ref SDS 17 1994
691422 -      Litigation needs critical details..... 950303, ref SDS 18 3333
691423 -      Com Manager intelligence aid.......... 980903, ref SDS 33 3300
691424 -      Memory critical details aided......... 990721, ref SDS 40 0001
691425 -      Enables good management practices..... 991014, ref SDS 43 2066
691426 -      Utopia compared to other methods...... 010425, ref SDS 76 EP7F
691427 -      Improves management................... 010924, ref SDS 98 NK4J
691428 -
691429 -
691430 - This record shows that Morris has thought a lot about Com Metrics for
691431 - helping executives, engineers, scientists, everybody... proactively
691432 - solve problems that worried Morris on 921127. ref SDS 10 0674  On
691433 - 001207 there is evidence that reducing problems in business avoids
691434 - recession. ref SDS 70 V54M  On 010911 need for SDS to "connect the
691435 - dots" to support timely intelligence greatly escalated.
691436 -
691437 - Today, Morris offered that a letter from him explaining this history
691438 - is an "excuse" for Rod's failure to offer information that convinces
691439 - customers to use SDS for improving management.  He feels that if Rod
691440 - cannot talk people into using SDS without endorsements from others,
691441 - then SDS is not worth using, similar to reasoning that, since Rod has
691442 - not accumulated a financial surplus, this shows SDS does not improve
691443 - management. ref SDS 89 J54K
691444 -
691445 - This analysis conflicts with the record of Morris' support for SDS,
691446 - beginning in 1984, what Andy Grove calls "strategic dissonance,"
691447 - reviewed on 980307. ref SDS 29 5517
691448 -
691449 -      [On 011202 Morris advised he believes cognitive science,
691450 -      psychology, philosophy and political scienced are not mature
691451 -      enough to be called science, and seemed to indicate that because
691452 -      mathematical predictions have a broader range of tolerance than
691453 -      electrical engineeing, these are not effective areas of study,
691454 -      which explains whey he cannot recommend SDS. ref SDS A9 0001
691455 -
691456 -
691457 -
691458 -
691459 -
691460 -
691461 -
691462 -
691463 -
691464 -
691465 -
691466 -
6915 -