CONTACTS 
0201 - Intel Corporation                    408 765 8080
020101 - Mr. Morris E. Jones; Business Unit Manager =408 545 9521
020102 - morris.jones@intel.com
020103 - Cable Network Operation

SUBJECTS
Where to Take SDS from Here, Dave Vannier, 990422
Utopia Competence Handle Complexity Cost Savings Avoid Mistakes Rewor
500 People Doing Same Thing
Directories A Problem
500 People Working on Same Document SDS Causes Harm
Feedback Shows Attractiveness of SDS Record on Web
Scale Many Com Managers Producing SDS Records Complex Overwhelming
Objection Not Enough Time to Learn SDS Intuitively Reverting to Conve
Document Management Log Writing Managment Correspondence
Doc Log Tracks Accountability Version Control Communication
Version Control Multiple People Working on Same Document File, Morris
Groupware Version Control Change History MS Word

5114 -    ..
5115 - Summary/Objective
5116 -
511601 - Follow up ref SDS 91 0000, ref SDS 85 0000.
511602 -
511603 - Morris raised a new objection to using SDS.  He feels check in and
511604 - check out for document management present a risk that prevents many
511605 - people from using SDS to work on a contract.  No experience using SDS
511606 - was cited, except to note that so far, several people working the same
511607 - document have not been using SDS, so we cannot be 100% sure that
511608 - problems would not arise, and that, if problems did arise, these would
511609 - not be more harmful than the benefits from adding intelligence to
511610 - management.
511611 -
511612 -      [On 010618 letter to Morris on Nexist that may solve check in and
511613 -      check out. ref SDS 93 0001
511614 -
511615 -      [On 010619 telecon with DCMA indicates management problems fixed
511616 -      by SDS, check in and out not cited. ref SDS 94 KWSQ
511617 -
511618 -
511619 -
511620 -
511621 -  ..
5117 -
5118 -
5119 - Progress
5120 -
512001 - Scale of Many People Using SDS Diminishes Benefits of Intelligence
512002 - Multiple Users Presents Challenge Editing Common Docs - Contracts
512003 -
512004 - Received ref DRT 1 0001 from Morris answering to the letter yesterday,
512005 - ref DIP 7 0001 that responded to his letter, ref DRP 3 0001, on 010426
512006 - asking what's the next step?  If you had the windows version, are
512007 - people ready for it, ref SDS 85 0001, based on Morris' letter previous
512008 - day reporting that use cases show SDS is a "utopia" compared to the
512009 - way people work using other technologies and methods.
512010 -
512011 - The letter to Morris on 010613 cited inquiry by DCMA about using SDS,
512012 - ref SDS 91 NG8O  The letter further pointed out reluctance to change a
512013 - successful design for SDS, except to add the ability for changing the
512014 - size of the window, and to have ample memory. ref SDS 91 EV4G  The
512015 - letter, also, asked Morris about trying SDS again, now that it appears
512016 - to be easier to learn than when he tried SDS in 1991. ref SDS 91 IT4L
512017 -
512018 -  ..
512019 - Morris says today.....
512020 -
512021 -    Nice to have some responses to your system.
512022 -
512023 -        This appears to notice DCMA inquiry on 010608, ref SDS 90 0001,
512024 -        mentioned in the letter to Morris, ref DIP 7 SK9F, on 010613.
512025 -        ref SDS 91 NG8O
512026 -
512027 -    The windows question does not solve the issues of 500 people
512028 -    working on the same thing. You need to comprehend that also.  Yes,
512029 -    you use directories, but they are not constantly changing, and if
512030 -    you delete something, it is only your problem.
512031 -
512032 -        This sounds like reasoning to avoid responsibility for adding
512033 -        intelligence to management.  On 990713 there was concern that
512034 -        "intelligence" was funny and alien. ref SDS 41 1767  On 990525
512035 -        management could not be improved because engineers don't like
512036 -        to write. ref SDS 37 0966  On 950204 SDS was overkill; now it
512037 -        is underkill.  On 931117 Morris wanted a way to distribute SDS
512038 -        records to help a lot of people. ref SDS 13 2Q61
512039 -        ..
512040 -        On 911121 Chips had an AI program that was better than
512041 -        SDS for engineering management, but it turned out that nobody
512042 -        used it. ref SDS 7 5609
512043 -
512044 -           [On 010622 confirmed SDS is not a groupware program.
512045 -           ref SDS 96 VO4H
512046 -
512047 -
512048 -
512049 -
512050 -
5121 -
5122 -
5123 - 2118
5124 -   ..
512401 - Submitted a letter to Morris asking for clarification of his
512402 - concern, however, it bounced back.
512403 -
512404 - Called Morris.
512405 -
512406 - We initially checked his email address, and it turned out that somehow
512407 - an "i" got inserted in his email address, so it read "@ihome" instead
512408 - of "@home."
512409 -
512410 -
512411 -  ..
512412 - Version Control Supports Document Management for Check In and Out
512413 - Contracts Need Careful Management of Changes Input by Many People
512414 -
512415 - Morris clarified concern in his letter, per above, about using SDS. He
512416 - explained work in his group on writing contracts is accomplished by a
512417 - number of people, rather than just one.
512418 -
512419 - This reflects civilization that leverages individual efforts using
512420 - synergy of interdependent activity through communication, discussed in
512421 - POIMS. ref OF 2 O87L  SDS supports Communication Metrics explained on
512422 - 950327 to strengthen collaboration.
512423 -
512424 - Today, Morris cited accountability issues for....
512425 -
512426 -                •  check in and
512427 -                •  check out
512428 -
512429 - ....control used at Intel to manage the record of document changes.
512430 - He called these capabilities....
512431 -
512432 -
512433 -                      groupware
512434 -
512435 -
512436 -  ..
512437 - Morris seemed to indicate that because SDS does not have specific
512438 - "check in" and "check out" features, this prevents using SDS to
512439 - improve daily management, and specifically to help prepare a better
512440 - contract.
512441 -
512442 -      [On 010618 letter to Morris on Nexist that may solve check in and
512443 -      check out. ref SDS 93 0001
512444 -
512445 -      [On 010619 telecon with DCMA indicates management problems fixed
512446 -      by SDS, check in and out not cited. ref SDS 94 KWSQ
512447 -
512448 -      [On 010619 Lee Iversion at SRI submits specs for NODAL and
512449 -      Collaborative Document Repository to improve document management
512450 -      for version control. ref SDS 95 0157
512451 -
512452 -      [On 010623 Morris called this capability groupware. ref SDS 97
512453 -      VO4H
512454 -
512455 -      [On 020110 Morris demonstrated that Microsoft Word and Outlook
512456 -      have good version control and enable collaboration by entering
512457 -      comments to a document. ref SDS 98 5HYX
512458 -
512459 -  ..
512460 - Accountability for check in and check out control is a documnet
512461 - management issue that has been reviewed in the record under the
512462 - description of "version control" and "versioning."  Doc Logs are used
512463 - when the scale of activity creating and revising documents, like
512464 - contract provisions, plans and specifications, increases complexity,
512465 - causing a morass of mistakes and delay, commonly called bumbling.
512466 -
512467 -  ..
512468 - On 890809 Morris noted that telling people to listen is faster and
512469 - cheaper than using SDS, but people won't listen.  On 990524 he
512470 - maintained there are better programs for engineering management than
512471 - SDS, but people won't use them. ref SDS 36 6892
512472 -
512473 -  ..
512474 - This evening, Morris observed during our call that SDS improves
512475 - management to avoid bumbling, once a contract is prepared, but does
512476 - not have adequate accountability to "check out" and "check in"
512477 - documents by many people preparing a contract, or other document, for
512478 - example, a specification and design for a computer chip, a boat, a
512479 - bridge, etc.  Morris seemed to indicate SDS strengthens understanding
512480 - and follow up for one person using SDS, but, if more than one person
512481 - uses SDS to prepare a contract, this would cause problems of version
512482 - control in document management.
512483 -
512484 -  ..
512485 - Document Management and Versioning are important.....
512486 -
512487 -     On 911116 engineering management failed, causing $millions of
512488 -     dollars in extra expense and delay on Broadwater Dam, when doc log
512489 -     requirements for submittal review were ignored. ref SDS 6 0001
512490 -
512491 -     On 991217 a conference on Knowledge Management reported version
512492 -     control is important to lawyers, for the reasons Morris cites
512493 -     today. ref SDS 47 0196
512494 -
512495 -      ..
512496 -     On 000210 version control is a major concern to engineers in
512497 -     developing an OHS/DKR. ref SDS 49 2993
512498 -
512499 -     On 000305 Ted Nelson is attributed with developing transclusion to
512500 -     improve versioning. ref SDS 51 4725
512501 -
512502 -      ..
512503 -     On 000504 Eugene Kim proposed OHS/DKR provide version control
512504 -     available in manual systems. ref SDS 60 4966  Jack Park supported
512505 -     Eugene's ideas. ref SDS 60 6082
512506 -
512507 -     On 001018 Eric Armstrong reported slow progress developing his
512508 -     OHS/DKR program, which seemingly was caused by difficulties in
512509 -     developing version control for document management, that Morris
512510 -     cites this evening as critical to productivity. ref SDS 73 M4W7
512511 -
512512 -  ..
512513 - SDS methods strengthen document management by maintaining a detailed
512514 - history of work on everything, including documents.  This enables a
512515 - stronger paradigm that integrates documents with human thought derived
512516 - from daily experience, as reported by USACE on 970418, ref DRP 4 6172,
512517 - as set out in the proposal to SRI on researching KM. A Doc Log system
512518 - integrated with other features under the POIMS design, ref OF 2 2688,
512519 - where everything is organized by date and time, and linked to
512520 - chronologies of cause and effect.  On 000709 Bill DeHart explained in
512521 - a conference call with Morris that experience using SDS at PG&E shows
512522 - SDS ability to manage time makes SDS a much strong solution than is
512523 - available from conventional methods and tools. ref SDS 69 1029  SDS
512524 - has additional ways of organizing information into a web of connected
512525 - "intelligence."  On 970116 Morris observed SDS solves a problem Morris
512526 - described as "fractionalized subjects" using the SDS design of organic
512527 - subject structures, ref SDS 29 1732, which is explained in the record
512528 - on 980523, ref SDS 2 SQ5L, and later on 910221. ref SDS 5 RR5I
512529 - ..
512530 - Experience has shown SDS is a stronger solution for maintaining
512531 - accountability through alignment to avoid the risk of bumbling that
512532 - otherwise arises in perofrming complex work, as previously discussed
512533 - on 991014. ref SDS 42 5600
512534 -
512535 - Morris disagreed.  He noted that SDS methods are different from
512536 - industry efforts for developing enterprise management.  This aligns
512537 - with Morris' analysis on 911123 that SDS works differently from the
512538 - way other people manage. ref SDS 8 4930  More recently on 010223, a
512539 - colleague at Intel commented on frustrations trying to predict what
512540 - buyers of personal computer technology want. ref SDS 78 W56J
512541 -
512542 - Earlier, on 001207 Reuters reported productivity, earnings and stock
512543 - prices are down because too many people are having too many problems.
512544 - ref SDS 74 V54M  Wordprocessing, email, endless meetings, cell phones,
512545 - palm devices and other information management tools make communication
512546 - the biggest risk in enterprise due to meaning drift. see POIMS.
512547 - ref OF 2 8774  One might therefore conclude the best course to sell
512548 - something that adds lasting value.
512549 - ..
512550 - SDS improves current practice by adding "intelligence" to
512551 - management, as reported by USACE, ref DRP 4 6172, which enables a
512552 - transitioning from IT to a culture of knowledge. see POIMS.
512553 - ref OF 2 2049
512554 -
512555 - A related objection to using SDS was raised on 951103 when Morris
512556 - asked.....
512557 -
512558 -     ....what happens when there is more than one Scribe producing SDS
512559 -     records in a management setting, and the records conflict?
512560 -     ref SDS 24 9066
512561 -
512562 - Changes in scale impact performance, as Engelbart points out in his
512563 - 1992 paper on Groupware, reviewed on 991222. ref SDS 48 1596  Impacts
512564 - of scaling up "listening" to widen the range of understanding and
512565 - follow up requires experience to assess.
512566 - ..
512567 - This evening, we reviewed the record showing worry that
512568 - "versioning" diminishes the value of SDS is not based on experience
512569 - using SDS.  On 010425 Morris described use cases in the Typical Day
512570 - Scenario as "utopia" compared to the way people work with existing
512571 - technologies and systems. ref SDS 84 EP7F  On 950204 he related
512572 - attending a seminar on management that described SDS methodology,
512573 - which Morris said was "overkill," ref SDS 17 5932, which supported a
512574 - prior report on 890324 that SDS is a "gold plated" system that is
512575 - overkill, ref SDS 1 6894, because it maintains accountability.
512576 - ref SDS 1 4488  More recently on 991021 SDS was criticized again for
512577 - maintaining accountability, which some prefer to avoid. ref SDS 43
512578 - 2695  Moving from "utopia" and "overkill" for one person using SDS
512579 - supporting a team or project, to fatal defect for 2, 3 or 100 using
512580 - SDS is a dramatic change in performance that is not supported by the
512581 - record. What calculation supports this proposition?  Assuming it were
512582 - true, under the rule announced on 911021, SDS should be embraded as
512583 - the best method for causing confusion that avoids accountability.
512584 - ..
512585 - On 911123 Morris noted that SDS enables using good management
512586 - practice consistently. ref SDS 8 0477  He said other executives don't
512587 - work this way.  Earlier on 890809 Morris cited need for better
512588 - "listening," which is supported by SDS. ref SDS 4 CJ9J  On 970603 Dave
512589 - Vannier at Intel noted SDS supports good management practice.
512590 - ref SDS 30 4528  On 000706 Bill DeHart explained SDS works better than
512591 - other technologies because it provides better organization.
512592 - ref SDS 69 0784
512593 -
512594 - At that time, on 000709 concern about too many people using better
512595 - management was not cited.  The worry was that it takes too long for
512596 - people to grasp the benefits of better management. ref SDS 69 Z28N
512597 -
512598 - For example, Stephen Covey says a good management habit is to first
512599 - understand, then decide on action, and recommends keeping a journal to
512600 - maintain mental acuity, because that sharpens understanding, reviewed
512601 - on 921205. ref SDS 12 2231  Understanding enables follow up so things
512602 - get done correctly, on time and within budget.  That is what SDS does
512603 - -- it keeps a journal to sharpen understanding, and we use that to
512604 - follow up.  If we scale up to enable more people understanding and
512605 - follow up there should be fewer problems.
512606 - ..
512607 - Drucker makes a similar point, that paramount responsibility of
512608 - management is analysis, reviewed on 931130. ref SDS 14 7911  SDS
512609 - enables analysis that is not presently getting done.
512610 -
512611 -      Can it really be true that Com Metrics improves management for
512612 -      one person, but, if we try to improve understanding and follow up
512613 -      for 2 or 3 or 100, then the law of diminishing returns reduces
512614 -      the value of getting things done accurately and on time by
512615 -      everyone?
512616 -
512617 - Does this proposition withstand scrutiny?
512618 -
512619 -      On 990525 Morris pointed out that engineers don't like to write,
512620 -      ref SDS 37 0966, and Andy Grove pointed out on 990527 that
512621 -      engineers don't like read. ref SDS 38 5110   How can check in and
512622 -      check out be a material factor in productivity, where literacy is
512623 -      at issue?
512624 -      ..
512625 -      SDS improves alphabet technology by arranging information
512626 -      into chronologies of cause and effect that maintain alignment to
512627 -      avoid meaning drift, see POIMS. ref OF 2 1299  The alphabet is
512628 -      used by a lot of people to prepare contracts.  Why can't the
512629 -      methods that help people avoid problems using alphabet technology
512630 -      to prepare a contract without SDS, be used to do the same thing
512631 -      with SDS so that work practices are strengthened all the way
512632 -      around?
512633 -
512634 - Ordinarily, if people are having too many problems, some effort would
512635 - be made to address those problems by improving the work.  Adding
512636 - support for using good management consistently is the most direct way
512637 - to improve productivity, earnings and stock prices.  If there is
512638 - evidence that SDS is helpful for one person, then it might be helpful
512639 - for many, as seen from the example of alphabet technology.  In other
512640 - words, if we improve something that a lot of people are using, it
512641 - would seem to more likely than not to raise everyone's productivity.
512642 - If there is concern about "check in" and "check out" controls on
512643 - writing a contract, then this work can be monitored more carefully, so
512644 - if harm materializes from large scale use of SDS, then use would for
512645 - that function would be performed on a smaller scale.
512646 -
512647 -
512648 -  ..
512649 - Improvement Comes from Experience
512650 -
512651 - Experience using SDS on a larger scale will doubtless yield refinement
512652 - and improvement, as has occurred the past 20 years.
512653 -
512654 - Document management is an important, but small part of SDS support,
512655 - Concerns, real or imaginary, in this area, should not stand in the way
512656 - of strengthening organizational memory, listening, understanding and
512657 - follow up at a time when productivity, earnings and stock prices are
512658 - in decline under the current regimen of Information Technology (IT).
512659 -
512660 - Moving from IT to a culture of knowledge requires a transition, that
512661 - evolves practices over time to work with stronger capability, set out
512662 - in the letter, ref DIP 7 TI7M, on 010613.
512663 - ..
512664 - Implementation of SDS typically begins with one person, then 2,
512665 - then 3 over a several year period.  This provides ample opportunity to
512666 - assess impacts of scale and design accommodations.  Waiting until
512667 - every conceivable objection is resolved, before trying a capability
512668 - that improves management, means that no improvement will ever occur.
512669 -
512670 - We are working on expanding the base of experience applying SDS in
512671 - various settings.  SDS has clear advantages over present practice
512672 - that nominally obviate concerns about versioning.
512673 -
512674 -
512675 -
512676 -
512677 -
512678 -
512679 -
512680 -
512681 -
512682 -
512683 -
512684 -
512685 -