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: February 13, 2002 09:42 AM Wednesday; Rod Welch

Gary do a project review Com Metrics scope of services

1...Summary/Objective
2...Linking Supported by Microsoft Word Outlook in Gary's Correspondence
3...Intelligence Capture Organizational Memory Convert into Knowledge
4...Knowledge Add Intelligence to Information from Organizational Memory
5...Organizational Memory Intelligence Converts Information into Knowledge
........Eureka - Collaboration Using IT with Microsoft Programs
........Intelligence Processes Information Acquired by Human Senses
6...Audit Trail Can be Supported by Aerospace company If Forced to Do So
7...Aerospace company Capable of Adding Alignment to Management Refuses to Do So
8...Bad Management Can be Helped by Efficient Tools and New Work Role
......Not Ready to Adopt Good Management So Must be Specified
......Good Management Must be Specified Because Nobody is Ready
9...Specify Good Management Overcome Overwhelming Tendency Bad Management
10...Post-project Review Evaluate Com Metrics to Improve Aerospace company Management
11...Try Using SDS Need Compensation for Welch
12...Background Shows Demand for KM Growing, Gary Can Help Advance SDS

ACTION ITEMS.................. Click here to comment!

1...It would be very helpful for Gary to do some kind of professional

CONTACTS 
0201 - Dynamic Alternatives                                                                                                                                               O-00000793 0101
020101 - Mr. Garold L. Johnson                                                                                                                                            O-00000793 0101

SUBJECTS
Gary Wants to Collaborate on KM Development Path
Alliances Communicate on SDS Com Metrics POIMS Critical Marketing Devel   Culture of 
Link Communication to POIMS for Foundation to Build Culture of Knowle
Microsoft Word Outlook Email Linking Addressability Anchors on Every
SDS Deployment Experience Use Buy Try Customer Need Terms for Use tha

1407 -
1407 -    ..
1408 - Summary/Objective
1409 -
140901 - Follow up ref SDS 82 0001, ref SDS 80 0000.
140902 -
140903 - Letter today again asks Gary to use links that apply addressability in
140904 - SDS records, as a first step to using good management by advancing
140905 - beyond information technology.  Also, suggested Gary prepare a post-
140906 - project review for the space station software project he is completing
140907 - under assignment to Aerospace company.  Review can assess experience working with
140908 - SDS for improving bad management Gary has identified on the Aerospace company
140909 - project. ref SDS 0 P64K  Gary responds with links prepared using
140910 - Microsoft programs and applying addressability in Knowledge Space
140911 - created with SDS.  This demonstrates IT can be applied with diligence
140912 - to support collaboration on building a culture of knowledge.  Gary
140913 - believes people at Aerospace company and Enron care capable of using good
140914 - management, as he demonstrates today, but must be forced to do so.
140915 - ref SDS 0 P64K  Gary does not comment on the record indicating that
140916 - good management takes too much time, ref SDS 0 6L3J; and, he does not
140917 - comment on the request to prepare a post-project review that presents
140918 - recommendations to support good management by specifying Com Metrics
140919 - scope of services. ref SDS 0 U14O  He remains open to using SDS under
140920 - terms that reasonably compensate Welch. ref SDS 0 R25G
140922 -       ..
140923 -      [On 020216 thank Gary for persistance to accomplish links using
140924 -      addressability in Knowledge Space provided by SDS, ref SDS 90
140925 -      0001 and ask about review comments on scope of services for Com
140926 -      Metrics to use SDS under requirements for good management
140927 -      performing contracts. ref SDS 90 U14O
140928 -
140929 -
140930 -
140931 -
140932 -
140933 -
140934 -
140935 -
140937 -  ..
1410 -
1411 -
1412 - Progress
141301 -  ..
141302 - Linking Supported by Microsoft Word Outlook in Gary's Correspondence
141303 -
141304 - Submitted ref DIT 1 0001 responding to Gary's letter notifying of
141305 - setting out goals for KM, and planning for his assignment at Aerospace company to
141306 - end, per his letter ref DRP 5 0001 on 020114. ref SDS 82 O46F
141307 -
141308 - Note anomaly of calling for addressability in Gary's goals for KM,
141309 - ref DIT 1 YC6J, but not using links to addressability, reported on
141310 - 020114. ref SDS 82 3H7J
141312 -  ..
141313 - Using links is a big part of solution to problem Gary raised in his
141314 - letter on 011006. ref SDS 66 MO6F
141315 -
141316 -      Received ref DRT 1 0001 from Gary in which he uses links to
141317 -      specific locations with anchors in the record.  This accomplishes
141318 -      the request for using a process of linking to grow a culture of
141319 -      knowledge based on POIMS, see below. ref SDS 0 425M
141321 -           ..
141322 -          Jack Park asked to link the record, 011206, ref SDS 67 JP4F
141323 -          Gary cited as bright star.......... 011206, ref SDS 67 Y13I
141324 -          Set goal for Gary to do links...... 011210, ref SDS 68 EG5M
141325 -          Linking condition for using SDS.... 011214, ref SDS 70 KD6G
141326 -          Asked Gary for links to anchors.... 011222, ref SDS 74 BF5K
141327 -          Reminded Gary about need for links. 011222, ref SDS 75 O56M
141328 -          Linking still action item.......... 020104, ref SDS 76 BW5N
141329 -          Gary says linking to SDS records
141330 -          is hard because he wants purple
141331 -          numbers developed by Eugene Kim.... 020106, ref SDS 77 W69L
141332 -          Instructions for linking were
141333 -          submitted to Gary.................. 020106, ref SDS 77 YO5J
141334 -          Gary plans to try instructions..... 020107, ref SDS 78 W69L
141335 -          Links omitted from Gary's analysis. 020108, ref SDS 80 O84M
141336 -          Links no in Gary's correspondence.. 020114, ref SDS 82 O84M
141337 -          Gary's goals addressability........ 020114, ref SDS 82 3H7J
141338 -      ..
141339 -      He seems to be using Outlook and Word to create
141340 -      correspondence with links, and if he sends the stuff as HTML,
141341 -      then the links remain, and if not they are stripped. ref DRT 1
141342 -      TQ5O
141344 -       ..
141345 -      This supports in part Morris' explanation on 020110 that links
141346 -      can be created with Microsoft programs. ref SDS 81 5HYX
141347 -      Previously, on 010720 he made a similar point. ref SDS 58 XM5F
141348 -      ..
141349 -      Need Gary's comments on Morris' idea on 020110 to convert
141350 -      Microsoft Word into SDS, ref SDS 81 S97L, in light of analysis on
141351 -      020110 and Gary's comments on 010408. ref SDS 53 AU4O
141352 -
141353 -          [On 020216 letter to Gary asks about this point. ref SDS 90
141354 -          0001
141355 -
141356 -          [On 020217 Gary says this can be done. ref SDS 91 6E4N
141358 -       ..
141359 -      Gary advises that links created in Word or Outlook and sent as
141360 -      text, are removed, but links submitted as HTML are transmitted
141361 -      successfully.  An alternative is to use text and copy Internet
141362 -      address into the text of email using instructions on 020106.
141363 -      ref SDS 77 YO5J  Possibly this does not work in Outlook, as it
141364 -      does in Netscape.  If so, this is another example of things
141365 -      working differently in different tools, with the result that
141366 -      productivity suffers.
141367 -
141368 -
141369 -
141370 -
141371 -
1414 -

SUBJECTS
Intelligence Debugs Management Discovers Alignment Problems Before Mi
Intelligence Organization Indexing by Subject Continuous Information
POIMS Link Communication Shows Commitment to SDS and KM for Awarding
POIMS Defines Intelligence Requires Capturing Information Organizatio
Ambassadors for Change
Foundation KM POIMS Culture of Knowledge Link SDS in Communication

2008 -
200901 -  ..
200902 - Intelligence Capture Organizational Memory Convert into Knowledge
200903 - Knowledge Add Intelligence to Information from Organizational Memory
200904 - Organizational Memory Intelligence Converts Information into Knowledge
200905 -
200906 - Gary uses the linking capability explained above to ask about the
200907 - explanation of intelligence in POIMS, stating....
200908 -
200909 -     In the POIMS paper you cite Intelligence: as Organize, Analyse,
200910 -     Align, Summarize, Feedback. ref OF 1 0367
200912 -      ..
200913 -     It seems to me that there is a step that involves acquiring
200914 -     knowledge -- creating, remembering, collecting, etc. before
200915 -     organizing can proceed. I find that when I surf the web looking
200916 -     for a specific kind of information, I generally do only enough
200917 -     organizing of the data so that I don't lose it, and then I start
200918 -     organizing the pieces. Linking is not a fast activity,
200919 -     particularly when I don't have a linked form of the record.
200920 -     Finding a specific piece of information in the record with just a
200921 -     browser is not trivial. ref DRP 6 IT8M
200923 -  ..
200924 - A couple of important points are derived from this comment...
200925 -
200926 -    1.  Gary uses linking, per above, ref SDS 0 P59L, for the purpose
200927 -        of reviewing POIMS, which shows significant progress on an
200928 -        action item set on 011210. ref SDS 68 C56O
200930 -         ..
200931 -        Eureka - Collaboration Using IT with Microsoft Programs
200932 -
200933 -
200934 -    2.  Gary uses linking to "collaborate" on defining intelligence,
200935 -        knowledge and information, so that these definitions can be
200936 -        used consistently in wider communication to foster a culture of
200937 -        knowledge based on POIMS, called out in the record on 011210,
200938 -        ref SDS 68 EG5M and previously on 011206. ref SDS 67 JP4F
200939 -        ..
200940 -        On 000120 collaboration using links in the record was
200941 -        first demonstrated, and first applied to define "knowledge" as
200942 -        distinct from "information" for the purpose of developing KM.
200943 -        ref SDS 26 5063  About 3 months later on 000405 Doug Engelbart
200944 -        called for all communication to apply addressability, as Gary
200945 -        does today. ref SDS 28 2484  On 000407 there was a reminder
200946 -        that knowledge needs to be defined separately from information.
200947 -        ref SDS 30 2805  On 000503 "knowledge" was rejected as a
200948 -        marketing buzz word, ref SDS 32 5033, and on 000615 the entire
200949 -        OHS/DKR team meeting at SRI, which is a research organization
200950 -        for advancing the nation and civilization, as reported on
200951 -        000725, ref SDS 37 0897, concurred that there is not enough
200952 -        knowledge to create KM, because knowledge is too difficult to
200953 -        understand. ref SDS 34 6271  On 001025 Doug Engelbart issued a
200954 -        letter calling for linking to specific parts of communication
200955 -        that are relevant to specific issues, and representations, as
200956 -        foundational to develop KM.  On 001121 SDS was offered to
200957 -        enable people to carry out this requirement to understand and
200958 -        create KM. ref SDS 40 XU8I  On 001122 there was great
200959 -        disappointment and despair about difficulty developing KM.
200960 -        ref SDS 41 0001  However, on 001126 there was a proposal to use
200961 -        IT with greater diligence instead of SDS for linking the
200962 -        record. ref SDS 42 QW8I  That same day, an OHS/DKR contributor
200963 -        disclosed it is very difficult using IT to link the record, and
200964 -        so requires a great deal of diligence. ref SDS 42 B15I  In all
200965 -        that time, there was never a single link using addressability
200966 -        in the record supplied regularly by SDS, and never a single
200967 -        comment or inquiry, as Gary makes today, on the meaning of
200968 -        information, knowledge and intelligence set out in POIMS,
200969 -        despite the opportunity for doing so having been presented over
200970 -        and over and over.... again.  As well, there has not been one
200971 -        inch of progress toward KM.
200972 -        ..
200973 -        For example, on 010111 Pat Lincoln, Director of Computer
200974 -        Science at SRI, who has supported Doug Engelbart's efforts to
200975 -        advance beyond IT, noted that collaboration has not advanced,
200976 -        except through SDS. ref SDS 51 3X4I
200978 -         ..
200979 -        This record makes Gary's achievement using IT for linking to
200980 -        addressability in Knowledge Space created by SDS, and Gary's
200981 -        willingness to bother asking about intelligence and knowledge
200982 -        explained in POIMS, a momentous occasion.  It vindicates in
200983 -        some respects Eugene's suggestion on 001126 that people use IT
200984 -        to perform and learn about KM, and it lends comfort to Morris'
200985 -        belief reported on 020110 that Microsoft programs can be used
200986 -        to accomplish aspects of SDS capability. ref SDS 81 S97L
200987 -        ..
200988 -    3.  These difficulties using IT for Knowledge Management to
200989 -        collaborate may explain why Enron, Aerospace company and others are in
200990 -        trouble, noted below by Gary. ref SDS 0 P64K  When too many
200991 -        people are having too many problems using tools they like, as
200992 -        reported on 011003, ref SDS 64 EC5N, productivity, earnings and
200993 -        stock prices fall.  The report on 001207 that the economy is
200994 -        contracting, ref SDS 45 V54M, may indicate that damage caused
200995 -        by inevitable bad apples, illustrated by Enron and Aerospace company, is
200996 -        negligible compared to problems caused by using IT for KM noted
200997 -        on 001126, ref SDS 42 B15I, and later cited by Gary on 010408.
200998 -        ref SDS 53 AU4O
201000 -         ..
201001 -        The binary tension between diligence and laziness, reviewed
201002 -        recently on 010908, ref SDS 60 YF5O, is resolved every day in
201003 -        the work place through demand that productivity, earnings and
201004 -        stock prices be improved by investing 20 minutes to learn
201005 -        better methods, reported on 890809. ref SDS 3 5U6K and further
201006 -        at ref SDS 3 2U4F
201007 -        ..
201008 -        In sum, the amount of diligence needed to manage
201009 -        effectively using IT, by for example maintaining an audit trail
201010 -        of daily communication, illustrated in this record, and looks
201011 -        to many like "overkill," reported on 890324, ref SDS 1 LZ5F,
201012 -        exceeds the time and attention span of most people, so that
201013 -        failure is not due to ill will, but to reliance on IT that
201014 -        overwhelms human span of attention....
201016 -             ..
201017 -            IT implodes into guess and gossip.... NWO, ref OF 4 TQ4O
201018 -            IT overwhelms human mental biology... NWO, ref OF 4 4925
201019 -            IT accelerates meaning drift......... NWO, ref OF 4 156O
201020 -            IT creates "pretty" time bombs..... POIMS, ref OF 1 8844
201022 -         ..
201023 -        SDS technology takes less diligence to convert information into
201024 -        knowledge.  Making good management faster and easier to improve
201025 -        productivity, earnings and stock prices reduces temptation to
201026 -        fall back on taking the short cut of bad management that causes
201027 -        a spiral of bumbling, ignoring and covering up mistakes, then
201028 -        crisis, conflict and calamity.
201029 -
201031 -         ..
201032 -        Intelligence Processes Information Acquired by Human Senses
201033 -
201034 -
201035 -    4.  Gary is correct that something has to be "acquired" as a
201036 -        predicate to applying intelligence.  The model presented in
201037 -        POIMS is that knowledge is not acquired, but rather is created
201038 -        by processing information with intelligence.  The section Gary
201039 -        cites states in part...
201040 -
201041 -           ....intelligence is a process that captures information from
201042 -           sensory perception through sight and sound from seeing,
201043 -           reading, talking and hearing, but, as well, from rhythms of
201044 -           movement... Information is connected into patterns of
201045 -           sequence based on context and chronology, i.e., time.
201046 -           ref OF 1 0367
201047 -        ..
201048 -        Thus, in this model, information comes from sensory
201049 -        perception, and knowledge is an output from an intelligence
201050 -        process that adds organization, analysis, alignment, summary
201051 -        and feedback, to information.  Alignment comes from the
201052 -        connections seen as links in SDS records showing chronology of
201053 -        cause and effect.
201055 -         ..
201056 -        Knowledge in SDS records can also be called....
201057 -
201058 -                     the record
201059 -                     intelligence
201060 -                     report
201061 -                     information (loosely)
201062 -                     organizational memory
201063 -                     history
201064 -                     intellectual capital
201065 -                     knowledge repository
201066 -                     case studies
201067 -                     root cause analysis
201068 -                     analysis
201069 -                     continual learning
201070 -                     organizational learning
201071 -
201072 -        ...as further explained in POIMS. ref OF 1 14GE
201073 -        ..
201074 -        Next step is to maintain and expand discussion to reach
201075 -        agreement on definitions, and to widen the circle of people
201076 -        collaborating on this matter.
201077 -
201078 -            [On 020217 Gary submits another letter than links the
201079 -            record. ref SDS 91 ZK6J
201080 -
201081 -            [On 020313 Gary submits SDS records with links added to
201082 -            anchors for facilitating linking by copying the link
201083 -            address.
201085 -             ..
201086 -            [On 020320 added this feature to SDS.
201087 -
201088 -
201089 -
201090 -
201091 -
201092 -
201093 -
2011 -

SUBJECTS
Not Ready for SDS Aerospace company Cannot Write List of Action Items
Good Management Aerospace company Not Ready to Improve Avoid Discovery    Bad Mana
Good Management Consistently Routinely Difficult to Maintain Stressfu
Specify New Way Working Like CPM Cost Control Need Experience Pilot T
Bad Management Overwhelming Desire Fear Technology Changes Too Fast N
Bad Management Cheaper than Good Management in the Moment Failure Cos
Front-end Investment Difficult Managers to Make, Wideman

4309 -
431001 -  ..
431002 - Audit Trail Can be Supported by Aerospace company If Forced to Do So
431003 - Aerospace company Capable of Adding Alignment to Management Refuses to Do So
431004 - Bad Management Can be Helped by Efficient Tools and New Work Role
431005 -
431006 - Letter to Gary points out that bad management impacts the entire
431007 - economy, ref DIT 1 PN9J, reported on 001207, ref SDS 45 V54M, and
431008 - recent report on 020204 of continued weakness due to difficulties at
431009 - Enron, ref SDS 87 0001, which are attributed to continual bumbling
431010 - caused by refusal to use good management practices, also, reported on
431011 - 020204. ref SDS 86 EX5O
431013 -       ..
431014 -      Gary's letter today seems to attribute bad management at Enron to
431015 -      deliberate refusal to execute objectives, requirements and
431016 -      commitments. ref DRT 1 QM7G
431018 -          ..
431019 -         Aligns somewhat with Fortune article reviewed on 990625 that
431020 -         says CEOs fail because they refuse to execute good management
431021 -         practices. ref SDS 24 7344  Documentation, similar to SDS, is
431022 -         a practice followed by effective CEOs, ref SDS 24 1024, but
431023 -         most CEOs don't feel like doing it, ref SDS 24 4914, as Gary
431024 -         notes in his letter today. ref DRT 1 QM7G
431026 -          ..
431027 -         Henry Kissinger relates in his book Diplomacy, reviewed on
431028 -         940609, the contagion of bumbling becomes pervasive when
431029 -         complexity overwhelms people due to lack of intelligence.
431030 -         ref SDS 11 4238
431032 -       ..
431033 -      Gary feels Aerospace company has capability to provide an audit trail
431034 -      showing alignment between daily work and objectives, requirements
431035 -      and commitments, but Aerospace company refuses to use good management, as at
431036 -      Enron, reported on 020204, ref SDS 86 P49F, because Aerospace company is
431037 -      afraid of accountability if someone notices how much trouble they
431038 -      are really in. ref DRT 1 UW8F
431040 -          ..
431041 -         This seems to support the proposition that good management,
431042 -         set out on 020204, ref SDS 87 6B9O, must be specified as
431043 -         explicit contract requirements, with sanctions for failure to
431044 -         perform, in order to protect the interests of taxpayers from
431045 -         organizations who succumb to the strong attraction of bad
431046 -         mangaement, reported on 010908. ref SDS 60 YF5O
431048 -          ..
431049 -         Per Secretary of Defense remarks on 020131, Gary's analysis
431050 -         belongs in post-project review along with ideas for
431051 -         improvement, per below. ref SDS 0 U14O
431053 -          ..
431054 -         Arguing that Aerospace company has technology and expertise to perform
431055 -         good management, e.g., an audit trail, overlooks differences
431056 -         between IT that can be used to perform good management, as
431057 -         Gary demonstrates today, and using SDS that is designed to
431058 -         make good management fast and easy 24 hours a day, and 7 days
431059 -         a week, as discussed above, ref SDS 0 ZT6I, and earlier with
431060 -         Morris on 020110. ref SDS 81 HP8J and ref SDS 81 UF5M   On
431061 -         921205 ability to use good practices consistently is the test.
431062 -         ref SDS 10 9503
431064 -          ..
431065 -         Per above, the record shows that while good management can be
431066 -         supported in part by Microsoft technology, the extra effort
431067 -         exceeds the diligence of most people. ref SDS 0 E54H
431069 -          ..
431070 -         For example, organizing the record is difficult, reported on
431071 -         000221, ref SDS 27 7455, and previously on 890523. ref SDS 2
431072 -         SQ5L On 010916  Eric Armstrong noticed SDS has mechanisms that
431073 -         obviously work. ref SDS 61 0001  Eric also reported an IT
431074 -         system he observed supported organization, but takes a "long
431075 -         time." ref SDS 62 4J4J  The fact that IT takes a long time to
431076 -         organize the record, may reflect Aerospace company's failure to use good
431077 -         management, i.e., it can be done, but is not fast and easy
431078 -         with the tools they have, so performance falls off, and soon
431079 -         there is no organizational memory to guide the work, no audit
431080 -         trail and so endless bumbling.
431082 -          ..
431083 -         Another example, on 011214 Gary noted it is difficult to get
431084 -         people at Aerospace company to write a list of action items. ref SDS 70
431085 -         YB4G  SDS makes it easier to do this, and so nominally it may
431086 -         be easier to get people to do something that is easy.
431088 -          ..
431089 -         Action items become complex and difficult to manage without
431090 -         SDS, as reported at USACE on 980305. ref SDS 20 5922
431092 -          ..
431093 -         USACE staff on 970110 refused to capture organizational memory
431094 -         using conventional methods available at Aerospace company and other
431095 -         organizations, but were willing and did rely on Com Metrics
431096 -         because experience showed this was useful. ref SDS 19 2487
431098 -          ..
431099 -         Contractor who opposed Com Metrics reported that experience
431100 -         showed SDS was more effective than expected, reported on
431101 -         970107. ref SDS 18 4953
431103 -          ..
431104 -         Another example is the record on 921021 reporting that the
431105 -         crash of the Columbia Space Shuttle in 1986 led to express
431106 -         requirements for expensive management procedures to maintain
431107 -         an audit trail showing performance of communication
431108 -         requirements. ref SDS 9 4499  This seemed to work until 991001
431109 -         when lax procedures at NASA again caused the loss of $125M
431110 -         space probe that crashed on Mars. ref SDS 25 0001
431112 -          ..
431113 -         Enron is another example reported on 020204, ref SDS 86 EX5O,
431114 -         and further reflects experience with Tudor Engineers failing
431115 -         to perform controls and audit trail on Broadwater Dam in 1988,
431116 -         which was not discovered until 911116. ref SDS 5 0001
431118 -          ..
431119 -         More importantly, Gary overlooks critical difference between
431120 -         "documentation" and "controls" using an audit trail, which is
431121 -         feared and hated as accountability, and using SDS that
431122 -         provides intelligence for doing the work with proactive
431123 -         management, as set out on 020204 reviewing the Enron matter.
431124 -         ref SDS 86 1Q3M
431126 -          ..
431127 -         Bumbling from ignorance, fear and denial are excused as cost
431128 -         savings and expediting which can only be overcome by people
431129 -         experiencing the advantages of intelligence.
431131 -          ..
431132 -         Most people never get the opportunity to discover the power of
431133 -         intelligence capturing organizational memory and using an
431134 -         audit trail because they have no experience using these
431135 -         methods, as reported by Morris on 010924. ref SDS 63 NK4J
431136 -         Thus, bad management is not unique to Aerospace company and Enron, but
431137 -         rather is pervasive.  This is why a Communication Manager is
431138 -         needed to jump start good management practices, so people can
431139 -         discover the power of working intelligently, and that this
431140 -         brings credit for better productivity, earnings and stock
431141 -         prices, rather than accountability from being blamed for
431142 -         mistakes.
431143 -
431144 -
431146 -       ..
431147 -      Not Ready to Adopt Good Management So Must be Specified
431148 -      Good Management Must be Specified Because Nobody is Ready
431149 -
431150 -      Gary points out that Aerospace company will not improve unless forced by
431151 -      contract or possibly statute, to adopt good management practices.
431152 -      ref DRT 1 IW4H
431153 -
431154 -         On 011214 Gary indicated Aerospace company is not ready to use good
431155 -         management practices enabled by SDS. ref SDS 70 WH6O
431157 -          ..
431158 -         Aligns with the record showing tendency to use bad management
431159 -         is overwhelming, and so can only be addressed by making good
431160 -         management a contract requirement.
431162 -          ..
431163 -         Confirms understanding in Gary's letter on 020114, ref SDS 82
431164 -         00V4; and previously, on 011006 he noted that improvement is
431165 -         hopeless. ref SDS 66 MO6F
431167 -          ..
431168 -         Aligns with letter to DCMA earlier today proposed specifying
431169 -         Com Metrics to enable good management, similar to specifying
431170 -         C/SCSC. ref SDS 89 645G  The letter said that good management
431171 -         will only be used if there is an express requirement that
431172 -         conditions payment as incentive to perform good management,
431173 -         ref SDS 89 D66G, as proposed by Max Blodgett on 960105.
431174 -         ref SDS 16 1008
431176 -          ..
431177 -         Should provide supplemental notice to Stuart about support in
431178 -         Gary's letter for proposal that good management must be
431179 -         specified.
431180 -
431181 -             [On 020227 discussed with Stuart. ref SDS 92 MM4V
431183 -          ..
431184 -         DOD has standing with Congress to lobby for a statute that
431185 -         requires alignment in communication to complement alignment in
431186 -         finances.
431188 -          ..
431189 -         Whether people are "ready" to use good management is not
431190 -         relevant, because there is no rational basis for accepting bad
431191 -         management.  Everyday, people attend meetings all around the
431192 -         world and nobody is ever "ready," yet this does not stop
431193 -         people from attending.  For example, on 960205 an article
431194 -         reports that managers waste 70% of the day in unproductive
431195 -         meetings because people are not prepared, i.e., they are not
431196 -         ready. ref SDS 17 5902  The fact that people are not ready
431197 -         does not excuse failure to improve?
431198 -
431199 -
431200 -
431201 -
431202 -
4313 -

SUBJECTS
Post-Project Review Aerospace company Scope of Services Com Metrics Rev  w in Re
Scope of Services Com Metrics Transitions Organization to Prepare for
Aerospace company Post-project Review Case Study Evaluate Use of SDS fo  Com Met
DCMA Budget Cuts Cannot Hire Consultants Propose Specifying Com Metri

5006 -
500701 -  ..
500702 - Specify Good Management Overcome Overwhelming Tendency Bad Management
500703 - Post-project Review Evaluate Com Metrics to Improve Aerospace company Management
500704 -
500705 - Suggested post-project review discuss opportunity for adding
500706 - intelligence, ref DIT 1 H14O, and asking Gary about comments on scope
500707 - of services for Com Metrics to complement traditional project
500708 - management support, ref DRP 7 4929, and cite Don Rumsfeld's request
500709 - for ideas to advance innovation for intelligence support to enable
500710 - proactive management. ref SDS 84 QF4H
500712 -       ..
500713 -      Gary comments favorably on Rumsfeld's remarks at the War College
500714 -      about the need for DOD to adopt proactive management. ref DRT 1
500715 -      IW4H  What is needed, however, is proactive initiative, as
500716 -      requested by Rumsfeld. ref SDS 84 QE4H
500718 -       ..
500719 -      Gary does not discuss doing a post-project review of his Aerospace company
500720 -      work, as a basis for reviewing Com Metrics Scope of Services.
500721 -      ref DRP 7 4929
500723 -       ..
500724 -      Gary describes above overwhelming tendency to use bad management,
500725 -      ref SDS 0 E24M, that requires specifying good management, as a
500726 -      contract requirement, like C/SCSC, rather than relying on self-
500727 -      interest to encourage contractors to use good management, since
500728 -      competitive bidding and short-term perspective prevent making
500729 -      front-end investment needed for good management, as noted by Max
500730 -      Blodgett on 960105. ref SDS 16 1008
500732 -       ..
500733 -      It would be very helpful for Gary to do some kind of professional
500734 -      analysis of how Com Metrics scope or services relates to his
500735 -      experience at Aerospace company based on analysis in this record and
500736 -      experience at Enron.
500738 -       ..
500739 -      Project review to develop lessons learned is the place for Gary's
500740 -      ideas and perspective on management of the Aerospace company project, per
500741 -      above. ref SDS 0 P64K  This would support incorporating Com
500742 -      Metrics into project requirements for competitive bidding
500743 -      proposed by Max Blodgett on 960105. ref SDS 16 1008
500745 -       ..
500746 -      Aligns with request to DCMA to review Com Metrics scope of
500747 -      services, per letter this morning. ref SDS 89 645G
500749 -       ..
500750 -      Defense budget increase was reported on 020204, ref SDS 85 0001,
500751 -      which includes money for Aerospace company projects, ref SDS 85 WG4F  This
500752 -      could be used as incentive to use good management by specifying
500753 -      Com Metrics scope of services.
500754 -
500755 -
500756 -
500757 -
500758 -
500759 -
500760 -
500761 -
5008 -

SUBJECTS
SDS Gary Wants to Try Using SDS but Need Formula for Compensation He
SDS Use Buy Try Customer Need Terms for Use that Protect Welch
Leadership Broader Vision Helps People who Fear Writing Obtain Analys

5905 -
590601 -  ..
590602 - Try Using SDS Need Compensation for Welch
590603 -
590604 - Gary willing to use SDS if we can work out some way for Welch to
590605 - get a fair exchange out of it. ref DRT 1 BL9N
590606 -
590607 -     Confirms understanding in Gary's letter on 020114. ref SDS 82 00V4
590609 -      ..
590610 -     On 011214 set condition precedent that Gary show movement toward
590611 -     KM by linking the record. ref SDS 70 KD6G
590613 -      ..
590614 -     Today, Gary got started on this effort, per above. ref SDS 0 DW9I
590616 -      ..
590617 -     Need to review with Morris and with Gary how to go about setting
590618 -     terms and conditions for this, since it is a major goal to get
590619 -     others to use SDS.
590620 -
590621 -         [On 020924 Gary sent SDS program. ref SDS 93 0001
590623 -      ..
590624 -     My feeling is that Com Metrics scope of services is the way to
590625 -     start this process of getting people ready to use SDS, but I could
590626 -     be wrong on this point.
590627 -
590628 -
590629 -
590630 -
590631 -
590632 -
590633 -
5907 -

SUBJECTS
Background History Gary's Interest in KM and SDS

6003 -
600401 -  ..
600402 - Background Shows Demand for KM Growing, Gary Can Help Advance SDS
600403 -
600404 - Follow up ref SDS 82 O8SS, ref SDS 80 O8SS.
600405 -
600406 - Gary's participation in SDS has been invited based on strong views
600407 - about need for KM to advance beyond IT, as set out in our
600408 - correspondence....
600410 -       ..
600411 -      Review Com Metrics scope of services......020213, ref SDS 0 U14O
600412 -      Linking progress on objectives............020213, ref SDS 0 P59L
600413 -      Culture of knowledge, linking.............020213, ref SDS 0 P59L
600414 -      SDS would like to use.....................020213, ref SDS 0 R25G
600415 -      Goals for KM, wants addressability........020114, ref SDS 82 3H7J
600416 -      Collaborate with Morris on SDS update.....020108, ref SDS 80 O8SS
600417 -      IT failing, demand growing for KM.........011006, ref SDS 66 MO6F
600418 -      Gary wants to dialog about KM.............011006, ref SDS 66 JQ6K
600419 -      Gary supports POIMS criteria..............011006, ref SDS 66 M24K
600420 -      Collaboration not primary aim of KM.......011006, ref SDS 66 536J
600421 -      Intelligence, org memory helps everybody..011006, ref SDS 66 KY7J
600422 -      Ltr suggests alliance with Gary...........011004, ref SDS 65 T86O
600423 -      Analysis, writing resisted................011004, ref SDS 65 TV3G
600424 -      Letter to Gary on alliance for SDS........010719, ref SDS 57 OL8I
600425 -      Gary asked about SDS......................010719, ref SDS 57 0001
600426 -      Gary tried create KM several times........010719, ref SDS 57 GH7I
600427 -      Gary requests theory of knowledge.........010719, ref SDS 57 YR9J
600428 -      KM begin with personal management.........010408, ref SDS 53 FT4N
600429 -      Attribution important to KM movement......001224, ref SDS 50 0001
600430 -      KM/OHS requirements.......................001222, ref SDS 49 AK9I
600431 -      Social problems solved by KM..............001221, ref SDS 48 513O
600432 -      Competency and values.....................001220, ref SDS 47 BV3W
600433 -      Purpose of KM.............................001219, ref SDS 46 6A9N
600434 -      Solutions from individuals small groups...001219, ref SDS 46 1613
600436 -    ..
600437 -   [On 020924 Gary began using SDS. ref SDS 93 0001
600439 -    ..
600440 -   [On 030126 extended use of SDS to Aerospace company project. ref SDS 94 TB4F
600441 -
600442 -
600443 -
600444 -
600445 -
600446 -
600447 -
600448 -
600449 -
600450 -
600451 -
6005 -
Distribution. . . . See "CONTACTS"