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

SUBJECTS
SDS, Business Development, Product Support,
Dir Structure, Conflict Resolution
Conflicting Understandings Causes Anger,
Anger Charges of Not Telling Truth when
Confrontation as Meeting Method
Management productivity, Needs Integration
70% of Day Wasted in Meetings, Only 10% of
Dialogue Inadequate, Need Preparation,
Intel Confrontational Meetings Process
Take Notes on Notebook Computer During Meetings
Meetings Write Notes on Notebook Computer During Meetings
Confrontation Conflict to Improve Meeting Management by Yelling and H
Accuracy Communication Intel Procedures Constructive Confrontation to
What's a Metrics Intelligence Alignment Example Bumbling Memory Fails

2916 -
2916 -    ..
2917 - Summary/Objective
2918 -
291801 - Follow up ref SDS 40 0000, ref SDS 39 0000.
291802 -
291803 - He has been in Sacramento for two days solving a problem Intel thought
291804 - was a Chips matter, but it turned out to an Intel matter.
291805 -
291807 -  ..
291808 - Management/Meeting Method - Confrontation and Conflict
291809 -
291810 - Morris explained Intel seems to use "constructive confrontation" at
291811 - meetings to help people resolve differences in understandings and form
291812 - shared meaning.  Meetings become very emotional, with people pointing
291813 - fingers accusing each other of not telling the truth, and so can take
291814 - a long time, sometimes from 4 - 8 hours, as participants work through
291815 - conflicting recollections of prior events and consider implications
291816 - for future impacts, similar to experience at Chips reported on 940327,
291817 - ref SDS 5 J47F, and reflecting discussions with Dave Vannier on 950927
291818 - about the challenge of information overload at Intel, ref SDS 18 5002,
291819 - and on the harm of relying on guess and gossip, ref SDS 18 7447, as
291820 - seen on 960721 showing poor productivity from meetings between Chips,
291821 - Intel and Lockheed. ref SDS 29 0896
291822 -
291823 -     [On 040505 Paris peace conference in 1919 heads of state began
291824 -     holding meetings hoping to avoid keeping records, but found the
291825 -     top people in the world could not remember enough to perform daily
291826 -     work; eventually leadership yielded to an even stronger fear of
291827 -     accountable for failing to get anything done, and so a record of
291828 -     organizational memory was prepared and this change in management
291829 -     practice yielded results that expedited progress. ref SDS 57 MQ49
291831 -  ..
291832 - Morris has worried many times that meetings reduce productivity, for
291833 - example on 950228, ref SDS 9 1994, and earlier on 940114. ref SDS 4
291834 - O15M   He made the same point in our call on 890809, noting that
291835 - communication takes up 80% of the time, but mistakes occur because
291836 - people don't listen. ref SDS 2 CJ9J
291838 -  ..
291839 - This record supports the study reported on 960205 showing people waste
291840 - 70% of the day in unproductive meetings. ref SDS 23 5222
291842 -  ..
291843 - An example involving Intel and Chips is the meeting on 960326 to
291844 - prepare for the Asilomar Conference. ref SDS 26 LO5G
291846 -        ..
291847 -       [On 970603 Dave wanted to improve management productivity by
291848 -       adding "metrics" to communications. ref SDS 43 5803
291850 -        ..
291851 -       [On 970829 Intel's method seems to be supported by management
291852 -       text calling for listening with "empathy." ref SDS 44 NJ5L
291854 -        ..
291855 -       [On 980307 Andy Grove's book "Only the Paranoid Survive"
291856 -       mentions confrontation methods used at Intel meetings.
291857 -       ref SDS 46 0261]
291859 -        ..
291860 -       [On 980722 explanation of Intel procedures for conducting
291861 -       meetings requires an agenda and "scribe." ref SDS 47 2937]
291863 -        ..
291864 -       [On 981223 Tom Keesling explains that people get mad when
291865 -       frustrated because people remember differently. ref SDS 48 HS8J
291867 -        ..
291868 -       [On 000822 bad management caused product delays, losses,
291869 -       conflicts; Intel dropped the ball. ref SDS 49 019R
291871 -        ..
291872 -       [On 000922 Intel earnings reduced, stock drops. ref SDS 50 0001
291874 -        ..
291875 -       [On 010828 Jack Park says pinning everybody down makes people
291876 -       mad. ref SDS 51 R04L
291878 -        ..
291879 -       [On 020217 review Roy Roebuck's explanation of advantage of SDS
291880 -       to improve accuracy that avoids mistakes in memory and so makes
291881 -       meetings productive. ref SDS 53 9360
291883 -        ..
291884 -       [On 020927 the movie "The Maltease Falcon" showed that a common
291885 -       business practice in the 1930s and 40s was for someone to take
291886 -       notes during meetings where important, complex information was
291887 -       presented, so that someone could get it all down. ref SDS 54
291888 -       W682
291890 -        ..
291891 -       [On 040129 Gary Johnson reviews Bert Decker's ideas on the
291892 -       importance of taking into account emotions, ref SDS 56 WO7Y, and
291893 -       advocates working by conversation, placing less emphasis on
291894 -       writing. ref SDS 56 WO9W
291895 -
291897 -  ..
291898 - Morris uses his notebook computer during meetings to take notes, and
291899 - to work on other stuff when the discussion does not relate to
291900 - Intel-Chips issues.
291901 -
291902 -       [On 980722 Morris explained his ability to answer email on his
291903 -       computer during meetings at Intel. ref SDS 47 4826]
291905 -        ..
291906 -       [On 030206 Morris explained new capability to use instant
291907 -       messaging to chat in side discussions with other people during
291908 -       meetings. ref SDS 55 MK4J
291910 -  ..
291911 - This is somewhat analogous to our meetings on Asilomar, see 960223.
291912 - ref SDS 26 8007, ref SDS 26 8442
291913 -
291914 -          [On 970524 discussed Communication Metrics goals and methods
291915 -          with Morris again. ref SDS 42 0335.]
291916 -
291917 -          [On 970829 text book on management recognizes communication
291918 -          is difficult due to limited span of attention, and calls for
291919 -          "empathic listening" that seems to reflect Intel's meeting
291920 -          methods, ref SDS 44 0808.]
291922 -           ..
291923 -          [On 970603 Communication Metrics was considered to improve
291924 -          management productivity at Intel. ref SDS 43 5803]
291926 -           ..
291927 -          [On 971001 calculation of cost savings from Communication
291928 -          Metrics to reduce rework caused by limited span of attention
291929 -          that causes acrimony and confrontation, ref SDS 45 4472.]
291931 -       ..
291932 -      Intel's acceptance of conflict appears to contrast with others
291933 -      who use psychologists to avoid heated expressions that disrupt
291934 -      meetings and harm productivity. see on 951101, ref SDS 21 5500;
291935 -      on 951103, ref SDS 22 4355; and on 960721, ref SDS 29 0896
291937 -       ..
291938 -      Frustrations about lack of productivity and difficulty aligning
291939 -      understandings from meeting communications was also discussed on
291940 -      960510. ref SDS 28 2943
291942 -       ..
291943 -      PG&E meetings devoted a lot of time to discussing differences in
291944 -      recollections, analysed on 941211. ref SDS 6 6488
291946 -       ..
291947 -      Communication Metrics to discover and resolve conflict was
291948 -      explained on 961017. ref SDS 33 1381  Another example from PG&E
291949 -      on 941214. ref SDS 7 9677.  The concept of using notice to
291950 -      discover differences in time to avoid harm came into the record
291951 -      on 880908. ref SDS 1 4920
291953 -       ..
291954 -      Example from Corps of Engineers on handling conflicts in
291955 -      understandings from meetings and disputes about accuracy of
291956 -      meeting notes, is explained on 961126. ref SDS 34 8845
291958 -       ..
291959 -      Marcy Puhnaty reported the SDS record was accurate when used for
291960 -      Communication Metrics to support a meeting with Intel preparing
291961 -      for the PMI Asilomar Conference. ref SDS 27 3004
291963 -       ..
291964 -      [On 970512 Dave Vannier said that communication at Intel is
291965 -      "people intensive." ref SDS 41 3333]
291966 -
291968 -  ..
291969 - Morris has not yet retrieved ref DIP 1 0000 transmitting the record at
291970 - ref SDS 38 0000, and the SDS data structure, ref OF 1 0000.
291972 -  ..
291973 - He has purchased a book on C, so we need to get together and do some
291974 - initial work on it.
291975 -
291976 -
291977 -
291978 -
291979 -
291980 -
291981 -
2920 -