THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: July 22, 1998 01:44 PM Wednesday; Rod Welch

Meeting with Morris on Medit, Comm Metrics Web page graphics.

1...Summary/Objective
2...Gfname - New Command to Extract Filename to Counters
3...Planning - Editor File Menu same as SDS File Menu for HTML Save
4...01220 Save Editor file to Temp HTML directory on h
5...Reengineer SDS Difficult Design Counterintuitive Hard Understand
6...Programming SDS for Communication Metrics is Difficult
7...Support in New Editor for Creating Windows SDS Program
8...Counterintuitive Reverse Engineer SDS for Com Metrics Difficult
9...Intel's Management Produces High Volume of Email using Powerpoint
10...Morris reads and responds to email during meetings, because often only
11...Morris stores email on the hard disk; but, some Intel managers store
12...Meeting Procedures Posted on Wall of Intel Conference Rooms
13...Morris Takes Notes on Notebook Computer During Meetings
14...Intel's "Scribe" Can Be Supported by Adding "Intelligence"
15...Powerpoint "Foil" Summaries Improved by Connecting to Details
16...Intel's Meeting Procedures Offer Path Toward Effective "Intelligence"
17...Clear, Concise and Complete Meeting Notes Require Support
18...Meeting Productivity Improved by Consistency in Quality of Notes
19...Learning SDS Frustrating for Managers
20...Managers Frustrated by Difficulty Learning SDS
21...Critical Mass of Knowledge Needed to Jump Start Learning
22...Communication Managers Ensure Productivity and Learning Growth


..............
Click here to comment!

CONTACTS 
0201 - Chips & Technologies, Inc
020101 - Mr. Morris E. Jones
020102 - Sr. Vice President

SUBJECTS
Save to HTML Directory for Web Site
Editor, F02
Gfname (get filename), 980722

0805 -
0805 -    ..
0806 - Summary/Objective
0807 -
080701 - Follow up ref SDS 45 0000, ref SDS 40 0000.
080702 -
080703 - Morris completed the main objective of creating a command to capture
080704 - the filename in counters. ref SDS 0 2351  This took about 30 minutes.
080705 - We spent the next several hours reviewing SDS code, considering ideas
080706 - for improving the new editor so I can create SDS functionality that
080707 - can then be used under Windows. ref SDS 0 3280  The discussion covered
080708 - a range of management needs based on Morris' experience working with
080709 - Intel. see ref SDS 0 4826
080710 -
080711 -    [On 980813 asked Morris to comment on improvements to web site on
080712 -    subjects discussed today. ref SDS 52 0000]
080713 -
080714 -
080716 -  ..
0808 -
0809 -
0810 - Progress
081101 -  ..
081102 - Gfname - New Command to Extract Filename to Counters
081103 - Planning - Editor File Menu same as SDS File Menu for HTML Save
081104 -
081105 - Follow up ref SDS 45 5543.
081106 -
081107 - Morris created a new Medit command, gfname, ref OF 2 5584, that moves
081108 - values for the filename in ASCII characters into counters starting
081109 - with counter 1, and sets the value of the counter after the last
081110 - character in the filename to 0, so that macro 1180 and 1181 will work
081111 - without a lot of extra stuff.
081113 -  ..
081114 - Testing showed it accomplishes the current need.
081115 -
081116 -      [On 990502 applied to User ID. ref SDS 58 7105
081117 -
081119 -  ..
081120 - 01220  Save Editor file to Temp HTML directory on h
081121 -
081122 - Follow up ref SDS 45 5808, ref SDS 40 2718.
081123 -
081124 - Line 60, ref OF 1 9648, -label saHTML, used the new gfname command,
081125 - created by Morris above, ref SDS 0 2351, to transfer the filename.
081127 -  ..
081128 - Line 70, ref OF 1 3556, this is the second entry for the save to the
081129 - local drive.
081131 -  ..
081132 - Morris mentioned today that code to justify text can be created
081133 - without the JJ commands in Medit.
081134 -
081135 -     [On 980724 developed better justify code. ref SDS 48 3200]
081136 -
081137 -
081138 -
081139 -
081140 -
081141 -
081142 -
081143 -
0812 -

SUBJECTS
Programming SDS Difficult to Reverse Engineer, Morris Jones
SDS Difficult Reverse Engineer
Reverse Engineer SDS Difficult Code Hard to Understand
Propose Macro Language for SDS
Medit C Version Update to Run SDS on Windows Solve Memory Problem
Memory Problem Solved with Windows Version But Morris Only Has 3 Days
Macro Language C Version Medit Update so SDS Macros Run
Reverse Engineer SDS Difficult Need Experience Using SDS to Understa
SDS Reverse Engineer Difficult Counterintuitive Unique Nobody Has Ex

2611 -
261201 -  ..
261202 - Reengineer SDS Difficult Design Counterintuitive Hard Understand
261203 - Programming SDS for Communication Metrics is Difficult
261204 - Support in New Editor for Creating Windows SDS Program
261205 - Counterintuitive Reverse Engineer SDS for Com Metrics Difficult
261206 -
261207 - Morris has an idea about creating a macro language for me in his new
261208 - editor to facilitate creating a Windows app for SDS.  An initial goal
261209 - is to solve the compiler problem in the current program.
261210 -
261211 - He pointed out a number of advantages to using a different kind of
261212 - file format from the current editor environment.
261214 -  ..
261215 - Morris examined the list of Medit commands, ref OF 2 3359, that have
261216 - been added to support SDS since about 1984, to evaluate what needs to
261217 - be added to the new Editor.
261219 -  ..
261220 - Morris said he has looked at code for the SDS program that I have
261221 - installed on his computer at various times over the years.  He
261222 - indicated today that tasks SDS accomplishes are hard to understand and
261223 - correlate to the underlying code.  Software engineers have life
261224 - experience with writing and mathematics that guide understanding for
261225 - designing and reverse engineering wordprocessing and spreadsheet
261226 - programs.  He feels SDS is different because nobody has experience
261227 - doing SDS tasks, so it is hard to "reverse engineer" the SDS program.
261228 -
261229 -     [On 010208 Morris feels changes to assembly code to increase
261230 -     memory for SDS would take 1 week to code and 6 months to debug.
261231 -     ref SDS 74 6Q8H
261233 -      ..
261234 -     [On 020108 Morris discusses upgrading C version of Medit to run
261235 -     SDS macros. ref SDS 78 O86M
261237 -      ..
261238 -     [On 040505 Gary submits information to upgrade 16-bit assembly
261239 -     code for Medit to 32-bit code that addresses more memory in
261240 -     Windows. ref SDS 84 QU8K; Morris does not have enough time to
261241 -     implement this level of improvement. ref SDS 84 TW43
261243 -  ..
261244 - The difficulty is grasping SDS design concepts for cognitive
261245 - processes, because they seem to conflict with common sense, as related
261246 - in the record on 910529, ref SDS 3 9989, but are critical to
261247 - accomplish the visible advantages of SDS, explained in POIMS,
261248 - ref OF 3 2050, per our telecon on 920215. ref SDS 5 5820
261250 -  ..
261251 - We did not have time to examine the SDS record that is linked to the
261252 - development code, and shows concepts, detailed implementation analysis
261253 - and chronology of development, and maintenance for each system.
261254 -
261255 -     [On 000425 KM seems to be a secret of SDS. ref SDS 69 0480
261256 -
261257 -     [On 000723 Cliff Joslyn visited and observed SDS being used, and
261258 -     Cliff has seen SDS foundational documents on the Internet, along
261259 -     with many records; Cliff disclosed he is trying to develop an
261260 -     SDS-type program an LANL, but they are having difficulty making
261261 -     progress. ref SDS 70 1312
261263 -      ..
261264 -     [On 001219 Matt Placek with Wegener Engineering in Flordia offered
261265 -     to purchase SDS. ref SDS 72 0001 Later on 001231 Matt disclosed
261266 -     that Wegener's objective was to obtain SDS to study trade secrets
261267 -     for developing new products. ref SDS 73 7K5N
261269 -      ..
261270 -     [On 010924 Morris commented again that nobody has experience doing
261271 -     SDS tasks for capturing and managing organizational memory, so
261272 -     nobody understands how to create SDS. ref SDS 76 XT5F
261274 -      ..
261275 -     [On 011101 ask for comments on letting a computer scientist pilot
261276 -     test SDS. ref SDS 77 0001
261278 -      ..
261279 -     [On 040404 Gary's letter to Morris says the editor is difficult to
261280 -     replicate for creating an upgraded version of SDS. ref SDS 83 R37N
261282 -      ..
261283 -     [On 070907 Jack Park has been trying to build a mental model of
261284 -     SDS for years. ref SDS 87 GM9T
261285 -
261286 -
261287 -
261288 -
261289 -
2613 -

SUBJECTS
Intel Power Point Picture Program Prepare for Meetings and Distribute
Meeting Management Needs Note Taker
Facilitator Improves Meetings Without
Email Does Not Improve Productivity,
New Realities Information Overload
Consistent Good Practice Needs Metrics,
Visualization is Supplemented
Meeting Minutes Improved by Communication
Scribe, Communication Manager until Tools
Email Read During Meetings, Causes Mistakes
Attention Span Limited Causes Mistakes
Management Practices Ignored to Save Time, Increase Cost, Delay
Documentation Avoided, Causes Delay, Extra Cost
Intel Procedures Make Meetings Productive Require Publishing Agenda P
Agenda Prepare Prior to Meeting and Scribe Must Distribute Record Aft
Communicaiton Manager Scribe Distribute Record After Meeting Using Po

5718 -
571901 -  ..
571902 - Intel's Management Produces High Volume of Email using Powerpoint
571903 -
571904 - Morris advised that Intel's email system accumulates a lot of comments
571905 - from affected managers and engineers around the world that results in
571906 - him routinely receiving several email a day that exceed 1MB.
571908 -  ..
571909 - He indicated these email messages are largely comprised of Powerpoint
571910 - presentation slides (also used for meeting presentations, see below,
571911 - ref SDS 0 4105) and spreadsheets, which provide minimal explanation of
571912 - background, context, objectives, policies, commitments, constraints,
571913 - impacts, correlations, implications and nuance.
571915 -  ..
571916 - Morris explained his practice of trying to read everything received
571917 - each day that impacts objectives, requirements and commitments.  He
571918 - makes timely response where necessary so that a backlog of unread and
571919 - unanswered correspondence does not continually build up.  He deletes
571920 - everything else to avoid getting confused about what has been
571921 - answered.  This new practice improves prior procedures reported on
571922 - 960325 when Morris did not have time to read email, ref SDS 20 6692,
571923 - and more recently on 960721 Morris reported not having enough time to
571924 - read a "bunch" of email. ref SDS 26 0096
571926 -  ..
571927 - He feels that many people do not use this practice.  On 951214
571928 - Rochelle Weichman, Director, MIT Management of Technology Program, in
571929 - Sloan School of Management, is a rare exception who makes a point of
571930 - reading her email. ref SDS 17 I741  HBR reports that most people do
571931 - not have time to read their email correspondence, reviewed on 940510.
571932 - ref SDS 11 5567
571934 -      ..
571935 -     [On 980808 added explanation in Communication Metrics web site of
571936 -     "intelligence" function to connect summary to relevant details.
571937 -     ref SDS 51 0615
571939 -      ..
571940 -     [On 980905 Morris advised he gets email that is short and covers
571941 -     one subject. ref SDS 55 4088
571943 -      ..
571944 -     [On 980905 Morris explained that traditional management practices
571945 -     to read and respond to correspondence have declined since the
571946 -     1970s when concern about accountability began to rise with the
571947 -     advance of better communication technology. ref SDS 55 0714
571949 -      ..
571950 -     [On 990718 notified Morris that analysis in email is cursory and
571951 -     incomplete. ref SDS 62 5251]
571953 -      ..
571954 -     [On 991001 delayed release of Intel's 820 chipset was not caused
571955 -     by poor communication because 30,000 or so email were issued on
571956 -     the problem. ref SDS 63 5772]
571958 -      ..
571959 -     [On 000326 Traction solves email problem. ref SDS 68 5877
571961 -  ..
571962 - On 950927 Dave Vannier cited email as Intel's least productive
571963 - business system. ref SDS 15 4939
571965 -  ..
571966 - Morris reads and responds to email during meetings, because often only
571967 - a small part of meetings he attends impacts his work.  He feels good
571968 - about being able to focus attention on email while also recognizing
571969 - correlations and implications from dialog during meetings that
571970 - requires him to comment and/or remember, as mentioned in our
571971 - discussion on 970123. ref SDS 27 0260  Feel good management was
571972 - discussed on 911123. ref SDS 4 4930  (Below, taking notes during
571973 - meetings. ref SDS 0 2937)
571974 -
571975 -     [On 070907 Morris asked about temporary storage for email to
571976 -     incorporate into an organized storage system that makes finding
571977 -     critical work history fast and easy. ref SDS 86 PRPX
571979 -      ..
571980 -     [On 080531 timely response to email demonstrated, and possible
571981 -     backlog of pending email to read. ref SDS 88 U266
571983 -  ..
571984 - Research on 900303 indicates the human mind is an "experience" rather
571985 - than a "logic" machine. ref SDS 2 3002  Later work on 970829 cited
571986 - limited span of attention supresses relevant experience when needed to
571987 - understand correlations, implications and nuance of new information.
571988 - ref SDS 30 1153  Business systems strive to capture experience as a
571989 - means to improve management productivity; at this time the favorite
571990 - description is a "Repsoitory of Experience."  An example was reviewed
571991 - on 970521. ref SDS 28 4700  Other terms have been "data base," "file
571992 - cabinet," LAN, briefcase, the floor, the back seat of a car or the
571993 - trunk, a coffee table at home, a glove compartment in a car, and desk
571994 - drawers.  IBM came up with "Business Intelligence" on 980226.
571995 - ref SDS 33 0000
571997 -      ..
571998 -     [On 030206 Morris explains new practice of side discussions using
571999 -     technology for Chatting with a notebook computer while attending
572000 -     meetings. ref SDS 82 MK4J
572002 -  ..
572003 - Reading and answering email during meetings divert attention and so
572004 - compound suppression of relevant experience needed to understand and
572005 - follow up that make communication effective.  On 890809 Morris
572006 - reported the need for better listening to improve productiviey of
572007 - management. ref SDS 1 CJ9J
572008 -
572009 -     [On 980808 created explanation in Communication Metrics home page
572010 -     that a "Repository of Experience" and "Lessons Learned" is
572011 -     automatically created using Communication Metrics. ref SDS 50 1638
572013 -      ..
572014 -     [On 990303 George Miller's famous paper on the Magical Number 7
572015 -     relates biological limits for span of attention that causes
572016 -     mistakes. ref SDS 57 5328
572018 -      ..
572019 -     [On 990527 information was overlooked due to limited span of
572020 -     attention reading email during meetings. ref SDS 60 3276]
572022 -      ..
572023 -     [On 990718 cursory analysis overlooks critical details.
572024 -     ref SDS 62 5251]
572026 -      ..
572027 -     [On 991009 Morris confirmed reading email off-line during meetings
572028 -     and on airplane flights. ref SDS 64 3077]
572030 -  ..
572031 - Morris indicated that cumulative email comments are not aligned with
572032 - external sources and prior comments.  Each is an ad hoc, spur of the
572033 - moment impression, similar to verbal conversation that occurs in a
572034 - meeting.  Morris' practice of answering email while attending meetings
572035 - fits this model of reaction response, rather than analyse and align.
572037 -  ..
572038 - There is not a method to integrate information from email into the
572039 - work flow, nor to link work with the email commentary.
572040 -
572042 -  ..
572043 - Morris stores email on the hard disk; but, some Intel managers store
572044 - their email on a web site where it is accessible for follow up.  He is
572045 - able to remember which file has the information he needs to perform
572046 - the work each day.
572048 -  ..
572049 - Previously, on 960406 Morris complained that nobody can find
572050 - information when needed, so the report today may indicate a solution
572051 - to the prior problem has been found. ref SDS 22 4249
572052 -
572053 -     [On 980819 Merrill Malvini at Unisys uses similar methods. see at
572054 -     ref SDS 54 2394]
572056 -      ..
572057 -     [On 021108 Bill Gates plans new project to add capability in
572058 -     Microsoft programs that makes finding information fast and easy.
572059 -     ref SDS 81 EF5I
572060 -
572061 -
572062 -
572063 -
572064 -
572065 -
5721 -

SUBJECTS
Meetings Procedures Industry Management Standards to Make People Pro
Jones, Morris Meetings Industry Management Procedures Standards to M
Intel Good Procedures for Meetings Posted in Every Conference Room t
Intel Meetings Procedures Posted on Wall of Conference Rooms to Faci
Agenda Distrubuted Prior to Meetings Scribe Assigned to Prepare Meet
Scribe Assigned to Prepare Meeting Minutes, Procedures for Good Mana
Jones, Morris Reads Responds to Email During Meetings Using Notebook
Intel Read Respond to Email During Meetings Using Notebook Computer,

6510 -
651101 -  ..
651102 - Meeting Procedures Posted on Wall of Intel Conference Rooms
651103 - Morris Takes Notes on Notebook Computer During Meetings
651104 - Intel's "Scribe" Can Be Supported by Adding "Intelligence"
651105 -
651106 - Follow up ref SDS 27 1111.
651107 -
651108 - Morris explained good procedures Intel has developed for conducting
651109 - meetings that are posted in every meeting room to remind everybody
651110 - about required steps for preparing agendas to distribute prior to
651111 - meeting, and a "Scribe" is assigned to prepare meeting notes.  The
651112 - notes are supposed to be issued within one (1) day of a meeting, and
651113 - typically cover action items and summarize important understandings.
651114 -
651115 -        [On 000116 Morris reports 50% of records for meetings are
651116 -        useful. ref SDS 67 3456
651118 -         ..
651119 -        [On 020217 reviewed DOD requirements for meetings as primary
651120 -        business unit of management, ref SDS 80 1332; primary weakness
651121 -        is command and control of the record fails, ref SDS 80 9360;
651122 -        found that SDS supports requirements for command and control of
651123 -        the work. ref SDS 80 3105
651125 -         ..
651126 -        [On 030206 Morris explained new requirements for publishing
651127 -        agendas prior to meetings, agreeing on action items and using
651128 -        netmeeting software. ref SDS 82 A092
651130 -         ..
651131 -        [On 050523 cognitive overhead is a fancy term for being
651132 -        prepared to conduct a productive meeting, and writing up the
651133 -        record to ensure the meeting is productive. ref SDS 85 KX6F
651135 -      ..
651136 -     Typically, the only notes of a meeting in some organizations are
651137 -     the Powerpoint pictures and talking points.  Intel's effort to get
651138 -     someone to write up some organizational memory and add
651139 -     intelligence is a big step forward, if that is actually occurring.
651141 -         ..
651142 -        [...below, the agenda is a Powerpoint file. ref SDS 0 4105
651144 -  ..
651145 - Morris related his practice of using a notebook computer to take
651146 - contemporaneous notes during meetings.  I have observed and marvelled
651147 - at his skill in using a notebook computer to type quickly enough for
651148 - keeping up with conversation.
651149 -
651150 -    [On 991202 Dave Buoncristiani uses this practice. ref SDS 66 4556]
651152 -  ..
651153 - We did not discuss today...
651154 -
651155 -    1.  Determining when to interrupt reading and sending email during
651156 -        meetings, in order to transcribe notes of something said in the
651157 -        meeting, per above, ref SDS 0 0464, since both cannot be done
651158 -        at once.
651160 -         ..
651161 -    2.  Using a notebook computer when meeting with a superior one on
651162 -        one, or in small groups.
651164 -         ..
651165 -    3.  How or when connections are created between understandings in
651166 -        correspondence, memos, calls, reports, and the record of prior
651167 -        events, and a current meeting.
651169 -         ..
651170 -    4.  How or when is the record organized for working "intelligently"
651171 -        to make finding relevant parts of the record fast and easy when
651172 -        needed to make connections for understanding cause and effect,
651173 -        for integrating new information into the record, and for
651174 -        preparing a comprehensive story that makes work history useful?
651176 -         ..
651177 -        Previously, on 960406 Morris complained that nobody can find
651178 -        information when needed. ref SDS 22 4249
651180 -           ..
651181 -          [On 990718 Morris work practice exhibits cursory
651182 -          understanding. ref SDS 62 5251
651184 -           ..
651185 -          [On 991108 history of alphabet technology shows it took 300
651186 -          years to learn that writing history requires adding analysis
651187 -          to oral communication, rather than merely recording what is
651188 -          said. ref SDS 65 5628
651190 -           ..
651191 -          [On 000116 Morris reports 50% of records for meetings are
651192 -          useful. ref SDS 67 3456
651194 -           ..
651195 -          [On 010425 Morris described SDS self-evident benefits for
651196 -          finding information is a "utopia" because everything is in
651197 -          the right place at the right time. ref SDS 75 EP7F
651199 -           ..
651200 -          [On 021108 Bill Gates plans new project to add capability in
651201 -          Microsoft programs that makes finding information fast and
651202 -          easy. ref SDS 81 EF5I
651204 -  ..
651205 - Intel's procedures align with need to improve meetings reported in an
651206 - article reviewed on 960205 finding that managers waste 70% of the day
651207 - in meetings. ref SDS 19 5222 and showing that wasting time is very
651208 - expensive. ref SDS 19 1640
651210 -  ..
651211 - On 960103 Dave Vannier advised that Intel relies on summary and style
651212 - at meetings, because there is not enough time to understand substance.
651213 - ref SDS 18 8409  On 970910 there was a report that executives do not
651214 - have time to "think." ref SDS 31 3479  Morris says above that he reads
651215 - email in meetings. ref SDS 0 0464  On 960507 Dave related Intel's idea
651216 - to use graphics instead of Com Metrics to improve management.
651217 - ref SDS 23 1111  On 940609 Henry Kissinger cited reliance on pictures
651218 - and dialog, rather than written analysis, leads to constant mistakes,
651219 - which he calls "Alice in Wonderland" management. ref SDS 12 4238   On
651220 - 970123 Intel meetings are emotional events that express conflicting
651221 - understandings, rather than shared meaning developed and maintained by
651222 - Communication Metrics. ref SDS 27 1111
651224 -  ..
651225 - On 970603 Dave wanted to improve Intel management by maintaining
651226 - alignment with project goals and commitements. ref SDS 29 5803
651227 -
651228 -     Analysis, alignment and organization cannot occur from emotional
651229 -     expressions and pictures, which means common understanding cannot
651230 -     be developed nor maintained, particularly under Intel's practice
651231 -     of sending Powerpoint slides used for agendas, as the meeting
651232 -     notes, ref SDS 0 4105, per Morris' explanation above of receiving
651233 -     email. ref SDS 0 4826
651235 -      ..
651236 -     What is actually discussed is not in the Powerpoint slide.
651238 -      ..
651239 -     This practice seems to conflict with Andy Grove's personal
651240 -     practice of taking copious notes, see 980307. ref SDS 35 3668 and
651241 -     ref SDS 35 3101
651243 -  ..
651244 - The challenge of holding productive meetings is reviewed in the record
651245 - on 940114. ref SDS 10 2290  An article reviewed on 960205 explains the
651246 - cause of low productivity in meetings. ref SDS 19 5902
651247 -
651248 -     [On 990525 report engineers do not like to write and management
651249 -     does not support requirements to document work. ref SDS 59 0966]
651251 -      ..
651252 -     [On 990625 medical practice has strong policies for capturing the
651253 -     record of patient medical history. ref SDS 61 0806; but doctors do
651254 -     not have time to execute requirements. ref SDS 61 0889]
651255 -
651256 -
651257 -
651258 -
6513 -

SUBJECTS
Intel Power Point Picture Program Prepare for Meetings and Distribute
Style and Image More Important than Content Because Not Enough Time t

6804 -
680501 -  ..
680502 - Powerpoint "Foil" Summaries Improved by Connecting to Details
680503 -
680504 - Morris advised that Intel uses Powerpoint for meeting agendas, which
680505 - reflects the "foil" method of visualization and summary that Marcy
680506 - explained on 960326. ref SDS 21 7402  An example of Intel's Powerpoint
680507 - methods is the outline for the Asilimar Conference submitted at the
680508 - meeting on 960627. ref SDS 25 2912
680510 -  ..
680511 - On 980405, Morris developed a graphic that illustrates the challenge
680512 - of maintaining alignment. ref SDS 37 2573
680513 -
680514 -     [On 980813 asked Morris if explanation in POIMS for "intelligence"
680515 -     helps executives see how the Internet can be used to improve
680516 -     management and earnings. ref SDS 52 6438]
680518 -      ..
680519 -     [On 020204 Enron collapsed into bankruptcy because board was
680520 -     swayed by Powerpoint presentation that failed to align decision
680521 -     with objectives, requirements and commitments. ref SDS 79 KM4F
680522 -
680524 -  ..
680525 - Intel's Meeting Procedures Offer Path Toward Effective "Intelligence"
680526 -
680527 - Intel's methods are a good start toward an "intelligence" role that
680528 - connects summary to details developed during meetings, adds alignment
680529 - with original sources and controlling forces, and prepares analysis of
680530 - correlations and implications with respect to commitments, objectives
680531 - and requirements.
680533 -  ..
680534 - Morris indicated that the "scribe" is often the person who calls the
680535 - meeting rather than an independent professiona..  He recalled having
680536 - attended meetings where Andy Grove was accompanied by two technical
680537 - assistants (TAs) who took notes for him.
680539 -  ..
680540 - Morris advised that meeting rooms have these procedures posted as
680541 - reminders of good practice.
680542 - ..
680543 - Morris feels a lot of Intel managers are careful and thorough in
680544 - capturing important details at meetings.  He related having made a
680545 - comment at one meeting about a task that needed to be accomplished,
680546 - and later he received notes of the meeting that cited his request for
680547 - action.
680548 -
680550 -  ..
680551 - Clear, Concise and Complete Meeting Notes Require Support
680552 - Meeting Productivity Improved by Consistency in Quality of Notes
680553 -
680554 - Morris indicated one area of possible improvement is more consistency
680555 - in meeting notes.  It is hard to be clear, concise and complete, as
680556 - developed on 960620. ref SDS 24 1643
680557 -
680558 - On 951010 Bill Walsh cited the importance of consistency in using
680559 - good work practices.  ref SDS 16 9558
680560 -
680561 -     [On 980723 added explanation of how to provide be clear, concise
680562 -     and complete communications, in Welch web site. ref SDS 47 2759]
680564 -  ..
680565 - One reason for poor meeting notes is that good notes conflict with
680566 - "feel good" management practice that fears accountability, reviewed on
680567 - 980405. ref SDS 36 5065
680568 - ..
680569 - Intel has a half-day training program on taking meeting notes.
680571 -  ..
680572 - I explained my sense that it is difficult to train for being
680573 - consistent in using good practices.  Often short-term perspective and
680574 - limited span of attention hide the need for care in being clear,
680575 - concise and complete.
680577 -  ..
680578 - Morris seemed to indicate that the engineering side of Intel has a lot
680579 - of procedures to track design issues that are part of the SDS program,
680580 - but these procedures are not used by management.
680581 -
680582 -     [On 980807 article managers overwhelmed by information overload.
680583 -     ref SDS 49 2426]
680585 -      ..
680586 -     [On 990525 Morris reported engineers don't have time to perform
680587 -     documentation requirements, and management does not support
680588 -     performance of requirements. ref SDS 59 0966]
680590 -      ..
680591 -     [On 990625 medical practice has strong policies for capturing the
680592 -     record of patient medical history. ref SDS 61 0806; but doctors do
680593 -     not have time to execute requirements. ref SDS 61 0889]
680594 - ..
680595 - Using Powerpoint slides for both agendas, ref SDS 0 4105, seems
680596 - like an advantage in getting consistency for subjects discussed, but
680597 - may be a disadvantage for accomplishing understanding and follow up,
680598 - because Powerpoint is not an effective way to analyse what was
680599 - discussed.
680600 -
680601 -     [On 980815 article says U.S. foreign policy "Intelligence"
680602 -     failures stem from too much information using pictures, and not
680603 -     enough understanding that is provided by analysis. ref SDS 53 1173
680604 -
680605 -
680606 -
6807 -

SUBJECTS
Difficult to Understand
Distinguished from Other Systems/Methods
Counterintuitive Programmers Don't Know What to Program to Improve Ma
Secret SDS Only KM Design, 000425
20 Min Anger Frustration Difficult to Learn SDS Links Counterintuitiv
20-60 Min Pilot Test, Conflicts Knowledge Pays Off Days, Weeks, Month
Shocking Observe Complexity of Management Details
Frustrated KM Too Difficult Giving Up Technology Cannot Improve Manag
Learn New Way Working Connections Augment Intelligence Don't Boggle M

9111 -
911201 -  ..
911202 - Learning SDS Frustrating for Managers
911203 - Managers Frustrated by Difficulty Learning SDS
911204 - Critical Mass of Knowledge Needed to Jump Start Learning
911205 - Communication Managers Ensure Productivity and Learning Growth
911206 -
911207 - Morris noted the frustration executives feel when confronted by having
911208 - to learn SDS to improve management practice for saving lives, time and
911209 - money.  Previously, on 950223 he characterized Communication Metrics
911210 - as "overkill," even though management experts recommend that
911211 - executives strive to accomplish the functions supported by SDS.
911212 - ref SDS 13 5931
911214 -  ..
911215 - As well, on 921127 Morris was frustrated because inconsequential
911216 - details turn out later to become major problems. ref SDS 7 0674  Which
911217 - then is more frustrating, losing lives, time, money, maybe a business,
911218 - or learning SDS?
911219 -
911220 -     [On 001207 too many people having too many problems cause
911221 -     productivity, earnings and stock prices to decline. ref SDS 71
911222 -     V54M
911224 -  ..
911225 - Morris did not say so expressly, but some frustration may arise
911226 - because SDS is supported by the editor that he created, and so it
911227 - seems like the SDS application should be more intuitive or natural for
911228 - him.  Disappointment at not being able to learn it quickly, results in
911229 - comments today that Communication Metrics is rhetoric and SDS is not
911230 - needed because it is only an editor, and anyone can do Communication
911231 - Metrics, if only the have the time and skill, and enough secretaries
911232 - and 3 x 5 cards, and so on and so forth. see for example the record on
911233 - 950223. ref SDS 13 9933
911234 -
911235 -     [On 990301 SDS was discounted as not really essential for
911236 -     Communication Metrics to be effective. ref SDS 56 6615]
911238 -  ..
911239 - Frustration is increased from being unable to understand SDS code
911240 - implementing a computer language he created. ref SDS 0 3744,
911242 -  ..
911243 - A critical mass of new concepts and functions need to be learned in
911244 - order to produce technology that enbles continual learning called out
911245 - by the Tofflers, Drucker, Covey, and others, reported on 950911.
911246 - ref SDS 14 2222  The general concept reflects theories of evolution
911247 - that growth is dormant for long periods, until a confluence of factors
911248 - accumulates that permits rapid change.
911250 -  ..
911251 - Andy Grove cites difficulty managers have learning new methods that
911252 - requires strong leadership, reported on 980307. ref SDS 34 3740
911254 -  ..
911255 - This challenge reflects experience with SDS on 920215. ref SDS 6 5820
911257 -  ..
911258 - The Communication Manager fulfills an important mission of ensuring
911259 - that despite difficulties learning better methods, essential
911260 - intelligence is developed so the organization can succeed, and this
911261 - provides an incentive and learning environment for others to
911262 - transition into new skills. ref SDS 35 4485
911263 -
911264 -     [On 980815 article on failures in foreigh policy "intelligence"
911265 -     failures show critical role of dedicated resources for generating
911266 -     analysis, organization, alignment and summary of information. see
911267 -     ref SDS 53 6424]
911268 -
911269 -
911270 -
911271 -
911272 -
911273 -
911274 -
911275 -
911276 -
911277 -
911278 -
911279 -
911280 -
9113 -
Distribution. . . . See "CONTACTS"