CONTACTS 
0201 - Chips & Tech.
020101 - Mr. Morris E. Jones
020102 - Sr. Vice President

SUBJECTS
Case Studies, Traceability, Continual
Continual Learning Derived from Automating
Conventional Management Practices
Linking Adds Value Writing:  Sources, Time,
Intelligence Adds Value to Information,
Traceability to Original Sources Metric
Root Cause Analysis
Enterprise Management and Workflow
Citations Empower Creativity Understanding
Little Deviations in Beginning to Avoid Crisis Calamity Loss Failure
Informal Communication Expedites Email Conversation Avoids Cost Sched

3013 -
3013 -    ..
3014 - Summary/Objective
3015 -
301501 - Follow up ref SDS 26 1111, ref SDS 24 9922.
301503 -  ..
301504 - Morris attended a seminar last week that presented a case study on the
301505 - Columbia shuttle failure and he received some seminar documents that I
301506 - can examine for application to Communication Metrics.  We developed
301507 - additional ideas for numerical metrics of communications.
301508 -
301509 -     [On 970526 met to review seminar materials. ref SDS 30 7003
301510 -
301511 -
301512 -
301513 -
301515 -  ..
3016 -
3017 -
3018 - Discussion
301901 -  ..
301902 - Case Studies Trace "Root Causes"
301903 -
301904 - Morris explained having attended a seminar last week in Los Angeles on
301905 - communication and management, which is the scope of Communication
301906 - Metrics.  Morris said that the failure of NASA's space shuttle
301907 - "Columbia" was reviewed at the seminar as a "case study" on how
301908 - communication is a big factor in enterprise management.
301909 -
301910 - "Case study" to identify original sources, is another description for
301911 - "root causes," is reviewed on 950830. ref SDS 17 4499.
301913 -  ..
301914 - I mentioned having attended a seminar at Cal Tech in 1992 that also
301915 - discussed the Columbia Space Shuttle, ref SDS 11 4499.
301917 -  ..
301918 - Morris said the people who presented the event he attended were top
301919 - executives and/or key people and so had important insights into that
301920 - problem which are not commonly known by others.  He said the ideas and
301921 - methods presented at the seminar are more advanced than SDS and
301922 - Communication Metrics.
301923 -
301924 -     Morris commented favorably about SDS design on...
301925 -
301926 -             890809, ref SDS 3 8211
301927 -             910523, ref SDS 5 3001
301928 -             910810, ref SDS 8 7793
301929 -             911123, ref SDS 9 0477
301931 -      ..
301932 -     Morris has expressed difficulty understanding SDS design...
301933 -
301934 -             910523, ref SDS 5 2736 and ref SDS 6 9441
301935 -             910716, ref SDS 7 8404
301936 -             920215, ref SDS 10 5820
301938 -  ..
301939 - I asked Morris to explain insights presented at the seminar.
301940 -
301942 -  ..
301943 - Telephone Game Shows Communication Biggest Risk in Enterprise
301944 - Linking Communication Supports Case Study for Root Cause Analysis
301945 -
301946 - Morris advised that the case study reported at Cal Tech, ref SDS 0
301947 - 4401, linked thousands of communications for alignment on wide ranging
301948 - details over 10 years to discover "root causes" of why the Challenger
301949 - Space Shuttle exploded shortly after take-off in 1986.  He explained
301950 - that a lot of highly intelligent graduate students were used in the
301951 - study to trace communications in phone logs, memos, RFIs and other
301952 - records showing the evolution of understandings, instructions and
301953 - actions, in relation to objectives, requirements and commitments.
301955 -  ..
301956 - On 890809 Morris complained that communication needs better listening
301957 - so small problems don't escalate into big problems, ref SDS 3 CJ9J,
301958 - that increase costs, delay and loss. ref SDS 3 126J
301960 -  ..
301961 - I asked if this study shows the value of using SDS for alignment that
301962 - enables Concurrent Discovery to provide proactive problem handling for
301963 - avoiding mistakes, as related in the record on 960620 defining
301964 - Knowledge Space, similar to a spreadsheet for knowledge? ref SDS 21
301965 - 1101 also explained in POIMS, ref OF 1 034J and ref OF 1 6649
301967 -  ..
301968 - Morris noted that links in the study presented at Cal Tech went far
301969 - beyond what is possible with SDS, because they spent a lot of money on
301970 - communication experts who used sophisticated, powerful computers to
301971 - track details.  He recalled top executives who attended the seminar
301972 - were shocked to discover communication becomes very complex, causing
301973 - continuing bumbling, errors, conflict, confusion, and calamity, since
301974 - day-to-day everybody seems to know what's going on at the time.
301975 -
301976 -      [On 000723 history of SDS shows this factor influenced
301977 -      development. ref SDS 37 H44G
301979 -  ..
301980 - This aligns with the report on 960722 that an expensive computer
301981 - system called the "Virtual Design Team" (VDT) developed at Stanford
301982 - shows communications are prone to mistakes due to complexity that is
301983 - difficult to manage. ref SDS 22 2502
301985 -  ..
301986 - I asked if the study reported at Cal Tech reflects Aristotle's rule
301987 - about small mistakes growing into major problems, if left unattended,
301988 - cited in the NWO... paper? ref OF 2 6056 and as reported on 960322,
301989 - ref SDS 20 7749
301991 -  ..
301992 - Morris related the study traced communication to original sources over
301993 - many years, and revealed how small, inoccuous, inconsequential details
301994 - were not aligned with requirements and prior work history, because
301995 - small problems are overlooked due to limited span of attention in
301996 - relation to other activity, i.e., things get lost in the shuffle and
301997 - fall through the cracks due to information overload, and, further,
301998 - because investing time to fix small problems seems like overkill.
301999 - However, the Cal Tech study showed that leaving small problems
302000 - unattended creates a dynamic that grows and combines evolving forces
302001 - into a critical mass that suddenly explodes causing overwhelming
302002 - problems through a complex web of people transferring and slightly
302003 - expanding incorrect understandings that caused incorrect actions, like
302004 - the "telephone game" cited in POIMS. ref OF 1 3943 and also in the New
302005 - World Order paper. ref OF 2 4077
302007 -  ..
302008 - On 921127 Morris worried about inconsequential details becoming major
302009 - problems that nobody can forsee. ref SDS 12 0674  On 890324 problems
302010 - are ignored to avoid accountability and save costs, arguing that
302011 - fixing small problems is overkill. ref SDS 1 LZ5F  On 911123 feel good
302012 - management ignores small problems so there is more time work on big
302013 - problems. ref SDS 9 1331
302014 -
302015 -     [On 971229 telephone game problem explains why communication is
302016 -     difficult. ref SDS 31 1526]
302018 -      ..
302019 -     [On 990712 Morris objects SDS links provide instant precision
302020 -     access to check the record for background, context and verify
302021 -     accuracy; takes a lot of time and responsbility. ref SDS 34 5837
302023 -      ..
302024 -     [On 990924 communication biggest risk in enterprise causes high
302025 -     cost of medical mistakes. ref SDS 35 3077]
302027 -      ..
302028 -     [On 991001 NASA's space orbiter crashes on Mars due to small
302029 -     communication mistake. ref SDS 36 0001]
302031 -      ..
302032 -     [On 000824 case study people object to links that provide instant
302033 -     precision access to background, context, and to verify accuracy.
302034 -     ref SDS 38 AU67
302036 -  ..
302037 - The study Morris attended, appears to reflect a prior event at Cal
302038 - Tech on 921021. ref SDS 11 4499
302040 -  ..
302041 - Morris feels the Cal Tech case study shows a more serious problem than
302042 - SDS addresses by implementing Communication Metrics, explained on
302043 - 950327. ref SDS 15 0001
302044 -
302045 -      [On 990712 Morris reported links in SDS records are overwhelming.
302046 -      ref SDS 34 5837]
302048 -  ..
302049 - We reviewed the case study at PMI event on 940611, which reported
302050 - similar findings from an investigation of an oil tanker crash at sea.
302051 - ref SDS 13 2066
302053 -  ..
302054 - I asked if the Cal Tech seminar proposed any remedies for the
302055 - communication problems uncovered by the study?  Any improvements,
302056 - changes of any kind to strengthen management practices?
302058 -  ..
302059 - What can people do to avoid problems discovered by the study?
302061 -  ..
302062 - For example, in our discussion on 950204 Morris reported having
302063 - attended a similar seminar in New Orleans that explained methods which
302064 - reminded Morris of the way SDS is used.  He felt that was overkill.
302065 - ref SDS 14 5932
302067 -  ..
302068 - As a result, cited the Cal Tech study in NWO... ref OF 2 5931
302069 -
302071 -  ..
302072 - Root Cause Analysis Improves Management Results
302073 -
302074 - I asked if the seminar speakers explained the importance and "value
302075 - added" of links for alignment and root cause analyse, per above?
302076 - ref SDS 0 4401
302077 -
302078 - Morris advised the Cal Tech experts said their study shows linking
302079 - chronologies of communication reveals patterns of cause and effect, or
302080 - "root cause analysis," that aid decision making, and provide lessons
302081 - learned for improving business processes, which are otherwise not
302082 - evident during day-to-day operations.  This aligns with analysis on
302083 - 960322 that found the complexity of daily events makes communication
302084 - the biggest risk in enterprise. ref SDS 20 7749
302085 -     ..
302086 -     Morris did not mention having asked the Cal Tech experts
302087 -     about the view that history is just "water under the bridge" that
302088 -     can be ignored to focus on today and the future, discussed on
302089 -     950822, ref SDS 16 9433
302091 -      ..
302092 -     [On 970526 did some sprinkler repair that yielded more ideas on
302093 -     "root" cause issues. ref SDS 30 2100]
302095 -      ..
302096 -     [On 970526 considered who, when, how and cost of doing root cause
302097 -     analysis on sprinkler project. ref SDS 30 2168]
302099 -      ..
302100 -     [On 990404 Com Metrics uses history for planning. ref SDS 33 9638]
302102 -      ..
302103 -     [On 990924 communication biggest risk in enterprise from analysis
302104 -     of medical mistakes. ref SDS 35 5576]
302105 - ..
302106 - I asked if attendees received any materials from the seminar
302107 - that supports the presentation.
302109 -  ..
302110 - He got a manual and two books.
302111 - ..
302112 - I asked if I could review the seminar materials Morris received
302113 - in order to compare the case study on the Columbia Space Shuttle with
302114 - a seminar I attended on 921021 that covered the same subject, ref SDS
302115 - 11 4499.
302117 -  ..
302118 - Morris said I could do this, so we scheduled a visit at his house on
302119 - Monday, 970526.
302120 -
302121 -     [Met on 970526 and found that seminar materials did not cover
302122 -     space shuttle case study, ref SDS 30 7003.]
302124 -  ..
302125 - I asked if he developed any notes or action items to implement what
302126 - was presented at the seminar?
302128 -  ..
302129 - Morris said he did not prepare any notes, but he attended with a
302130 - colleague from Chips who developed some "planning" for Chips to
302131 - consider, based on after hours discussion they had on the days
302132 - presentations.
302133 - ..
302134 - In our discussion this morning, Morris distinguished "planning"
302135 - from action items by explaining that action items require a due date
302136 - and assignment of someone to perform the work.
302137 -
302138 -
302139 -
302140 -
302141 -
3022 -

SUBJECTS
SDS Marketing, Definition, Metrics, Continual
Metrics (analysis, aligning, testing)
Metrics, Measuring Understanding with
Metrics Talking Needs Alignment to
Paperwork Reports used for Metrics
Turning Out the Lights, Rejecting SDS

5308 -
530901 -  ..
530902 - Numerical Metrics for Communications Can Be Developed
530903 -
530904 - Follow up ref SDS 24 9922, ref SDS 18 7777.
530905 -
530906 - We discussed some ideas about applying numerical metrics to
530907 - communications.
530909 -  ..
530910 - Morris suggests placing a numerical value as part of an SDS link, to
530911 - show the degree of correlation or alignment between two sets of
530912 - communications at different times.  He feels this should be a
530913 - judgement value on a scale of 1 - 10.  These can be accumulated and
530914 - presented in a report.  We could also calculate alignment of text from
530915 - one point in the record to another, by measuring ascii string values.
530916 - The challenge of the latter metric is the range of different ways to
530917 - say the same thing.
530919 -  ..
530920 - Another numerical metric would be the frequency of activity on various
530921 - WBS subjects.  This should fall out of the Subject Index fairly
530922 - directly.
530924 -  ..
530926 -  ..
530927 - Morris said it could be very helpful for managers to know when work is
530928 - occuring on paricular aspects of contracts or project WBS elements.
530930 -  ..
530931 - I explained SDS records report this and it requires expertise to
530932 - handle it carefully in order to avoid political backlish due to
530933 - conflicts with "feel good" management when the light of accountability
530934 - shines too brightly, per ref SDS 23 8444 and, ref SDS 23 5002.  People
530935 - get mad because accountability is stressful, per our discussion on
530936 - 961228, ref SDS 24 8823.
530937 -
530938 -      [On 980405 fear of accountability was reviewed again. ref SDS 32
530939 -      5065]
530941 -  ..
530942 - Morris suggests that rather than showing in the record that a subject
530943 - is not discussed, simply put it a numerical report to an executive.
530944 - He feels this would result in more effective leadership and better
530945 - earnings.
530946 -
530948 -  ..
530949 - Executives Shun Paperwork But Demand More "Metrics"
530950 -
530951 - We did not discuss the goal of Communication Metrics to identify and
530952 - fix mistakes when they are small, rather than prepare a report listing
530953 - mistakes, per our discussion on 951103, ref SDS 18 6003, earlier on
530954 - 961228, ref SDS 24 9922  The aim is to reduce "paperwork" and improve
530955 - productivity and earnings by focusing management on...
530956 -
530957 -                      leadership,
530958 -                      understanding
530959 -                      follow up
530960 -
530961 -    ...per definition at ref SDS 15 7777.
530963 -  ..
530964 - Morris was concerned about executives being inundated by unproductive
530965 - "paperwork" in our discussion on 960301, ref SDS 19 line 187.
530967 -  ..
530968 - I will call him Monday to see if he wants to visit about this stuff.
530969 -
530970 -     [See follow up visit on 970526, ref SDS 30 line 359.]
530971 -
530972 -
530973 -
530974 -
530975 -
530976 -
530977 -
530978 -
530979 -
530980 -
5310 -

SUBJECTS
Facilitators Improve Communication, Need
Meetings, Case Studies
Emotional Intelligence Quotient, EQ
Minutes of Meetings Are Not as Useful as
Conflict Constructive Confrontation, Anger
Diary Chronology Causation History

6808 -
680901 -  ..
680902 - Meeting Management Confrontation Improved by Com Metrics
680903 -
680904 - Discussed Intel's possible interest in Communication Metrics reported
680905 - on 970512. ref SDS 27 6900.
680906 -
680907 - I explained Dave's comment about Intel's management being "people
680908 - intensive" but "moving to Web" based ref DRP 1 8558, per ref SDS 27
680909 - 3333.
680911 -  ..
680912 - Morris confirmed his understanding that Intel describes this method as
680913 - "constructive confrontation" per our telecon on 970123, ref SDS 25
680914 - 11111.  He said they have specific procedures to follow that includes
680915 - a facilitator.  They issue notes of meetings transcribed from issues
680916 - captured as discussion points on large papers hung on the wall during
680917 - meetings, similar to the Asilomar event in 1990, ref SDS 4 7402 and
680918 - ref SDS 4 2299.
680919 -      ..
680920 -      The record of the meeting on Asilomar set out additional
680921 -      sources that need to be considered for effective communication,
680922 -      ref SDS 4 3074.  Normally, these are not considered until 10
680923 -      years later when a seminar presents a "case study" on "root
680924 -      causes" is presented, per Morris' discussion above.
680926 -  ..
680927 - He advised that he feels Dave is very sharp and may have a job of the
680928 - type developed at Apple, called an "Evangelist," who sells customers
680929 - on the idea of using Intel products.
680930 -
680931 -
680932 -
6810 -

SUBJECTS
Memory Management

6903 -
690401 -  ..
690402 - Followed up work at ref SDS 28 line 167.
690404 -  ..
690405 - Morris suggested a method to expand SDS capability by creating
690406 - alternate versions of SDS that have different stuff.  Create a version
690407 - that does only reporting.  It might not require all of the SDS code.
690409 -  ..
690410 - This is an alternative to fixing the compiler and to writing a C
690411 - verson of Medit.
690412 -
690413 -
690414 -
690415 -
6905 -