CONTACTS 
0201 - Intel Corporation                                                                                                                                                  O-00000704 0201
020101 - Mr. Morris E. Jones; Business Unit Manager
020103 - Cable Network Operation                                                                                                                                          O-00000704 0201

SUBJECTS
Set up standard project accounts

0403 -
0403 -    ..
0404 - Summary/Objective
0405 -
040501 - Follow up ref SDS 31 0000, ref SDS 30 0000.
040502 -
040503 - While we talked Morris retrieved ref DIP 3 0001 submitted on 991020,
040504 - ref SDS 31 0001, asking Morris to let me know if he can meet for a few
040505 - hours on this weekend to start work on a new Primary Subject Index.
040507 -  ..
040508 - Morris said he sees from the letter, ref DIP 3 3630, that we are
040509 - discussing having a meeting this weekend, but he does not understand
040510 - the purpose of the meeting.
040511 -
040512 -     [On 991023 called Morris to follow up. ref SDS 32 0001]
040514 -  ..
040515 - We reviewed the second sentence of the letter that says...
040516 -
040517 -     I want to meet this weekend about creating a new Primary Subject
040518 -     Index based on experience the past 10 years or so working with the
040519 -     current PSI. ref DIP 3 0001
040520 - ..
040521 - The subject index is one way of managing context and complexity
040522 - that converts information into useful intelligence for performing the
040523 - work, so that information is not a "threat" that needs to be
040524 - destroyed, per discussion below. ref SDS 0 2695  On 971007 the U.S.
040525 - Army Corps of Engineers reported that the SDS organic subject
040526 - structure method avoids rework by giving visibility to correlations
040527 - and impacts that are otherwise hidden by limited span of attention.
040528 - ref DRP 1 4680
040530 -  ..
040531 - This weekend ee want to think about improving this method.
040533 -  ..
040534 - Morris recalled that this is one of the technical objectives in the
040535 - proposal to NSF. ref OF 3 6781
040537 -  ..
040538 - He asked if we have heard anything yet from NSF?
040539 - ..
040540 - I advised there has been no notification from NSF.  On 990728
040541 - Sally Nerlove advised that notice of awards will be made in October
040542 - and November. ref SDS 26 0877
040544 -  ..
040545 - However, previously on 990715 Sally seemed to be put off by Com Metrics
040546 - process of clicking for "intelligence," because, like Morris see
040547 - below, ref SDS 0 3721), Sally has slow access to the Internet.
040548 - ref SDS 24 0001  Since technology is improving, this is only a
040549 - temporary issue, but it colors personal feelings in evaluating the
040550 - power and utility of Communication Metrics.
040551 -
040553 -  ..
040554 - Complexity Suppressed by Limited Span of Attention Hides Mistakes
040555 - Intelligence Provides Proactive Risk Management to Manage Context
040556 -
040557 - Asked Morris to review the record on 991010, explaining the cause and
040558 - solution to mistakes in human enterprise, caused by complexity that
040559 - suppresses visibility of sequence, ref SDS 28 3066, which was followed
040560 - up on 991014, ref SDS 29 5600, in a letter to him. ref DIP 2 5933
040562 -  ..
040563 - That record is linked to the letter on "medical mistakes," which
040564 - explains the general problem of "meaning drift," which results from
040565 - complexity, and how adding alignment arrests this otherwise hidden
040566 - risk. ref DIP 1 0001
040568 -  ..
040569 - Also cited Gutenberg. ref SDS 28 3056
040570 - ..
040571 - Morris is going to join a phone meeting in a few minutes.  He
040572 - will try to review the record, and will let me know about meeting on
040573 - the weekend to work on a new Primary Subject Index.
040574 -
040576 -  ..
040577 - Faster Computer May Solve Objection to Clicking for "Intelligence"
040578 -
040579 - I asked why Morris is having such difficulty accessing web mail from
040580 - Welch on the Internet, when Intel has high speed access using DSL,
040581 - cable or whatever?
040582 -
040583 - Morris is is using a 266 Mhz notebook computer with only 64 MB of RAM,
040584 - and this configuration takes a long time to load the web browser,
040585 - because a swap file is needed.  He may not have enough disk space
040586 - either.
040588 -  ..
040589 - He is waiting to upgrade because he needs a long battery life for
040590 - using computer in meetings and on planes.  His current system has a
040591 - seven (7) hour batter life. Evidently the new systems do not have a
040592 - seven hour batter life, so he has not spent the $3K or $4K to get
040593 - himself a computer that meets the demands of his work.
040594 - ..
040595 - Obviously Morris has access to adequate computers at Intel, but
040596 - he wants to use the notebook for convenience of not having to maintain
040597 - multiple systems with management records.  Somebody needs to be
040598 - supporting Morris so he can work efficiently.  It is an ergonomics
040599 - issue.
040600 -
040602 -  ..
0407 -
0408 -
0409 - 2155 called Morris
0410 -
041001 - He never got back to my letter. ref DIP 3 0001  He said he is getting
041002 - 50 - 100 email a day.  He had a lot of 1 on 1 with his boss on their
041003 - new cable networking project.
041004 - ..
041005 - He is traveling tomorrow.
041007 -  ..
041008 - Morris asked me to call him Saturday to see how things look for
041009 - working on the subject indexing project.
041010 - ..
041011 - We discussed again the issue of sequential complexity revealed
041012 - using SDS, explained in the record on 991010, which he still has not
041013 - reviewed. ref SDS 28 3066   It is the same record segment where
041014 - Gutenberg is discussed, cited in the letter yesterday. ref DIP 3 3630
041016 -  ..
041017 - Morris commented that SDS needs to be used by the person running the
041018 - company in order to recognize complexity and give visibility to
041019 - communication that is not aligned with objectives and requirements.
041020 - Then he offered that managing context requires a person experienced
041021 - with a particular field in order to report complexity and alignment.
041022 - ..
041023 - We reviewed the SDS process of assembling information in
041024 - sequence that reveals complexity, does not require special expertise
041025 - nor deep experience, in order to give visibility to an executive about
041026 - gaps in alignment which require attention.  An example is the record
041027 - on 991010. ref SDS 28 6552
041029 -  ..
041030 - Like the alphabet, in the hands of a seasoned executive or experienced
041031 - engineer, SDS has strong utility.  But, the alphabet can, also, be
041032 - used by those less skilled and experienced to perform a lot of useful
041033 - work to support the executive and engineer.  Capturing sequence to
041034 - manage complexity is an example of work that can be done by lessor
041035 - skilled people using SDS that cannot be done by any other means.
041037 -  ..
041038 - This is particularly helpful to executives whose "psyche" prevent them
041039 - from executing good management, reported by Fortune reviewed on
041040 - 990625. ref SDS 23 4914
041041 - ..
041042 - Morris does not seem to understand the SDS alignment process.
041044 -  ..
041045 - We discussed giving Morris some experience with the SDS alignment
041046 - process, so it is a easier to understand.  "Experience" to build
041047 - understanding was discussed on 990718. ref SDS 25 8966  Einstein's
041048 - observation about the value of "experience" was cited on 991014.
041049 - ref SDS 29 3166
041051 -  ..
041052 - Observing how easy it is to check, create and maintain alignment helps
041053 - understand the proces, because it cannot be done in a manual world.
041054 - Religion and law are the only professions with similar attention to
041055 - detail, ref OF 2 4723, and fear of religion and law, discussed below,
041056 - ref SDS 0 2695, prevent understanding the power of the microcosm
041057 - endemic to SDS.  This is similar to 920215 when frustrations occurred
041058 - about converting schedule tasks into diary records, and diary records
041059 - into scheduled tasks. ref SDS 5 5820  It is easy to do, but hard to
041060 - understand without experience.  Seeing it a few times makes the
041061 - explanation easier to understand.
041062 -
041063 -
041064 -
041065 -
041066 -
041067 -
0411 -

SUBJECTS
Slippery Slope to Murphy's Law, Downsizing
Out Out Damn Spot Cannot Destroy Information, 991021
Destroying Records to Avoid Discovery, Liability
Intel Meeting Note Procedures
Intel Destroying Records Fear Discovery Knowledge by Others More than
Destroy Records Firms Not Keeping Organizational Memory Knowledge Rep
Confidentiality Balances Intelligence for Collaboration
Organizational Memory Feared Destroyed Avoid Accountability Knowledge
Confidentiality, Secrecy, Security, Privacy
Objection SDS Adds Intelligence to Management by Capturing Organizati
Organizational Memory Fear Accountability Restrains Competence Improv
Out Out Damn Spot SDS Objection Alignment Maintains Accountablity
Deniability Supported by Conversation, Threatened by Writing, SDS
Email Destroyed Deniability Wriggle Room Flexibility Deniability Avo

3516 -
351701 -  ..
351702 - Greasing Slippery Slope of Sloppy Work to Avoid Accountability
351703 - Destroying Information Eliminates Any Chance of Working Intelligently
351704 -
351705 - Morris attended a management seminar yesterday that recommended
351706 - destroying the record of daily work within 45 days in order to avoid
351707 - accountability for poor management.  Previously, on 911121 Morris
351708 - cited trends showing lawyers are advising clients to adopt policies
351709 - for destroying information. ref SDS 2 5920
351711 -  ..
351712 - Reflects fear that organizational memory to build and maintain shared
351713 - meaning cannot be constructive for improving management without also
351714 - causing harm.
351715 -
351716 -       [On 991103 Jim Lovo at USACE cited fear of accountability is the
351717 -       800# gorilla that prevents people from using Communication
351718 -       Metrics for avoiding mistakes to save time and money.
351719 -       ref SDS 33 7308
351721 -  ..
351722 - Morris feels this policy prevents using SDS for adding intelligence to
351723 - the work by capturing organizational memory, because aligning work
351724 - with objectives, requirements and commitments increases accountabile
351725 - for mistakes when work is not aligned.  People proactively covering up
351726 - to avoid accountable for mistakes rather than improving management to
351727 - proactively prevent mistakes aligns with Drucker's point that people
351728 - have given up on improving communication because the task is too
351729 - complex. ref SDS 8 3851
351730 -
351731 -       [On 020802 regulations prohibit destroying email increases
351732 -       demand for intelligence. ref SDS 41 H39G
351734 -  ..
351735 - Destroying intellectual capital to enable deniability for avoiding
351736 - accountablity, destroys the essence of civilization that brings
351737 - continual improvement by balancing binary forces of positive and
351738 - negative incentives.  Without negative consequences of accountability,
351739 - there can be no positive consequences getting credit for doing a good
351740 - job, explained on 970829 reviewing accountability as the essence of
351741 - enterprise. ref SDS 15 6666
351742 -
351743 -       [On 040610 common sense hope by experts on Architecture
351744 -       Committee that deleting information solves information overload,
351745 -       overlooks opportunity to invest intellectual capital.
351746 -       ref SDS 42 XI3H
351748 -  ..
351749 - Destroying the record to avoid accountability greases the slippery
351750 - slope of sloppy work in avoiding diligence to understand complexity of
351751 - sequence by capturing and maintaining context in organizational memory
351752 - that enables proactive management, discussed on 991014. ref SDS 29
351753 - 3066  Ignorance from destroying the record increases risk of error
351754 - exponentially from complexity, also, discussed on 991014. ref SDS 29
351755 - 5600  On 921127 Morris complained about inconsequential details that
351756 - later explode into major problems that reduce productivity, earnings
351757 - and stock prices. ref SDS 6 0674
351759 -  ..
351760 - Destroying the record reflects Morris' analysis on 990527 describing
351761 - how cultural forces prevent improving management due to fear of
351762 - accountability. ref SDS 21 1233 It seems to conflict with Andy Grove's
351763 - call on 980307 for diligence to use copious analysis that avoids the
351764 - ambiguity of mental maps. ref SDS 17 3668
351766 -  ..
351767 - Conflict between good management and fear of accountability creates
351768 - strategic dissonance, also, cited by Grove on 980307. ref SDS 16 5517
351769 -
351770 -      [On 000505 email is proposed as core of Knowledge Management.
351771 -      ref SDS 34 4392
351772 -
351773 -      [On 000517 Sun tried to issue a procedure calling for email to
351774 -      destroyed, but employees objected. ref SDS 35 3360
351776 -       ..
351777 -      [On 000725 Morris wants secrecy discussed at presentation to SRI.
351778 -      ref SDS 36 0001
351780 -       ..
351781 -      [On 000802 secrecy, confidentiality incorporated into business
351782 -      plan. ref SDS 37 5392
351784 -       ..
351785 -      [On 000822 Intel's CEO says bad management, not bad luck causes
351786 -      product delays and reduced earnings. ref SDS 38 019R
351788 -       ..
351789 -      [On 001207 reduced earnings and stock prices indicates bad
351790 -      management must be corrected. ref SDS 39 MZ7G
351792 -       ..
351793 -      [On 010420 paper by industry expert says organizations trying to
351794 -      preserve memory. ref SDS 40 IE4M
351796 -  ..
351797 - On 990718 limited time "greases slippery slope..." ref SDS 25 6120
351799 -  ..
351800 - On 980405 fear of accountablity greases slippery slope. ref SDS 18
351801 - 1849
351803 -  ..
351804 - On 880925 cannot retrieve information. ref SDS 1 8493
351806 -  ..
351807 - CEOs and engineers, who do not like to read and write, reported on
351808 - 990625, ref SDS 23 5394, earlier on 990525. ref SDS 20 0966, and on
351809 - 990527. ref SDS 21 5110, now have another excuse, besides not enough
351810 - time, to avoid writing copious notes, which Grove cites in his book,
351811 - as diligence, and the salvation of Intel, reveiwed on 980307.
351812 - ref SDS 17 3668
351813 -
351815 -      ..
351816 -     Happy Scenario Destroying the Record Shoots Self in the Foot
351817 -
351818 -     Hey Tom, your letter on 990903 says we can release our work
351819 -     to manufacture because the tolerance on the new bus was tested on
351820 -     990724 based on a report dated 990813.  However, the 990813 report
351821 -     is for a meeting which simply says the tests were performed.
351822 -     Yesterday, we got the test report and it indicates further work is
351823 -     needed. Shouldn't we adjust course based on this record?
351824 -
351826 -      ..
351827 -     Tom says not to worry because his letter is going to be destroyed
351828 -     tomorrow since 45 days are up.  Tom recalled two weeks ago Fred in
351829 -     engineering said he heard in a meeting the week before that the
351830 -     test report was wrong.
351832 -      ..
351833 -     Bill asks what is wrong with the report?  I haven't heard about
351834 -     it.
351836 -      ..
351837 -     Tom says I am not sure, but we don't have to worry because in a
351838 -     few days the report will be destroyed.
351840 -      ..
351841 -     Wait a minute!  Everything is not supposed to be destroyed under
351842 -     the new policy, Bill says.  We can't destroy test reports can we?
351843 -
351845 -      ..
351846 -     How can we do our work?
351847 -
351849 -      ..
351850 -     Tom says that's a good point; we need to talk about this.
351851 -
351853 -      ..
351854 -     I have to go to a meeting on a big problem that has come up on
351855 -     another delay to our roll out. We have to come up with a story,
351856 -     but nobody can remember anything, so it will be a lot of
351857 -     "constructive confrontation."  I keep asking the people in
351858 -     Engineering "Don't you people communicate," but they feel there
351859 -     isn't enough time, because their focus is on the technology, not
351860 -     communication.
351862 -      ..
351863 -     This is a tough problem.
351864 -
351866 -      ..
351867 -     We need to talk.
351868 -
351870 -      ..
351871 -     Definitely.
351872 -
351874 -      ..
351875 -     I am going to be in Japan next week, then Europe, then Medesto,
351876 -     Fresno and after that I am scheduled to speak on "integrety," the
351877 -     legacy system of records management, at a big conference in
351878 -     Alviso.  What's your schedule look like for 2001?
351879 -
351881 -      ..
351882 -     Bill says I'm booked too, but am penciled in for the conference in
351883 -     Alviso, maybe we can hook up after your presentation on integrity.
351885 -  ..
351886 - Destroying the record of history aligns with the NWO... paper that
351887 - explains individuals, organizations and entire cultures gradually
351888 - drift off course. ref OF 2 5827  Indeed it is reminisent of "book
351889 - burning" in earlier times.
351891 -  ..
351892 - This was discussed originally on 911121, ref SDS 2 5920; and reviewed
351893 - on 911123 with Stan Mosk, Justice of the California Supreme Court.
351894 - ref SDS 3 0001
351896 -  ..
351897 - On 911212 Dave Bounchristiani, ESQ, cited distinctions between
351898 - securities law and contract law that may justify different ways to
351899 - manage the record. ref SDS 4 8492  On 990419 Dave advised that Com
351900 - Metrics support for "clear, concise, complete" communication is
351901 - effective. ref SDS 19 9420
351903 -  ..
351904 - On 990620 Concurrent Discovery was developed, for a presentation by
351905 - Dave, to avoid the risk of adverse discovery by managing context
351906 - concurrently, similar to concurrent engineering.  This avoids the
351907 - surprise that causes people to fear the law and destroy intelligence.
351908 - ref SDS 12 1101
351909 -
351910 -
351912 -  ..
351913 - Out, Out Damn Spot - Destroying Records is Impossible
351914 - Communication Metrics Adds Connections to Manage Context
351915 - Lack of Context Escalates Risk of Incorrect Interpretation
351916 -
351917 - Morris recognizes that destroying information, discussed above as a
351918 - new industry trend to avoid accountability, ref SDS 0 2695, is the
351919 - antithesis of the Communication Metrics process to invest intellectual
351920 - capital.
351922 -  ..
351923 - Destroying information removes connections to context, eliminating
351924 - any chance of working "intelligently." ref OF 1 0561  It guarantees
351925 - continual mistakes, delays and cost overruns, which only favorable and
351926 - ephemeral market conditions can buy-off, as reported on 990925.
351927 - ref SDS 27 0001
351928 -
351929 -     [On 991023 sent letter to Morris on this. ref SDS 32 5304]
351931 -      ..
351932 -     [On 000517 Sun tried to issue a procedure calling for email to
351933 -     destroyed, but employees objected. ref SDS 35 3360
351935 -      ..
351936 -     [On 010420 paper by industry expert says organizations trying to
351937 -     preserve memory. ref SDS 40 IE4M
351939 -  ..
351940 - Destroying correspondence eliminates Command and Control the record
351941 - that places information in context, explained in POIMS. ref OF 1 1113
351942 - Consequent risk of incorrect interpretation of documents volunteered,
351943 - or obtained through discovery from others, escalates exponentially,
351944 - because after-the-the explanation is discounted as self-serving.
351945 - Moreover, it is impossible for people to remember alignment for a day,
351946 - much less 1 - 5 years ago, the normal period for litigation, with the
351947 - result that every person who testifies for Intel about the meaning and
351948 - intent of a document will have a different story, as occurred in the
351949 - Micosoft trial.
351950 -
351952 -  ..
351953 - Remember MacBeth, or whoever, "Out, out damn spot."
351955 -  ..
351956 - You cannot destroy the "spots," you can only explain the context,
351957 - which requires ability to craft a comprehensible story that accounts
351958 - all of the forces that influenced action.  This requires an accurate
351959 - record.
351961 -  ..
351962 - SDS has a lot of "firepower" that makes it easier to quickly create
351963 - and maintain connections that show decisions and conduct are aligned
351964 - with objectives and requirements, also called "context" management, as
351965 - reported on 950204. ref SDS 9 4995
351966 -
351967 -
351969 -  ..
351970 - Throwing the Baby Out with the Bath Causes More Harm than Good
351971 -
351972 - On 950303 SDS could have helped a Chips's team that came back from
351973 - Paris and couldn't remember important context. ref SDS 10 3333  How
351974 - does a policy to destroy the record distinguish between a good record
351975 - that is needed, and a bad record that needs to be destroyed?
351977 -  ..
351978 - Why not just create a good record?
351980 -  ..
351981 - Accordingly, regardless of what is announced as "official policy" any
351982 - effort to avoid capturing and maintaining the record needed to perform
351983 - the work cannot last.
351984 -
351985 -
351986 -
351987 -
351988 -
351989 -
351990 -
351991 -
351992 -
351993 -
351994 -
351995 -
351996 -
351997 -
351998 -
351999 -
3520 -