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 2, 2003 07:35 PM Wednesday; Rod Welch

Gary's SDS records shows good progress on Com Metrics.

1...Summary/Objective
2...Links Need Dates for Context and Recovery to Restore Broken Links
3...Save Enters Anchors Above Indented Headings Avoid Redundant Anchors
4...Assignment to Develop Action Item System
5...Conventional Methods on Complex Work Degrades Management to Entropy
6...Authority Critical for Action Item System to be Effective
7...Partnership between Leadership and Technology Drives Action
8...SDS Designed to Navigate through Fog of War on Complex Work
9...Pending and Completed Action Items
10...SDS Supports CFISR Objectives for Better Organizaional Memory
11...CFISR Objectives for Better Organizaional Memory Enabled by SDS
12...Gary's Memory Using SDS Better than Most Shows SDS Support for CFISR
........Second Act Aided by Experience with SDS Organizational Memory
13...Organizational Memory Requires Professional Role
14...Note Taker Needed for Effective Organizational Memory
15...Professional Role Needed for Effective Organizational Memory


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

CONTACTS 

SUBJECTS
SDS New Way of Working that Have to be Learned
Link Dates Critical Binary Forces of Memory
Memory Improved by Dates Links Critical Binary Forces
Links Citations References Intelligence Audit Trail Traceability to O
Dates Links Strengthen Memory Augment Intelligence
Linking Audit Trail Traceability to Original Sources in SDS Records G
Best Practices Link Dates Critical Binary Forces of Memory

1109 -
1109 -    ..
1110 - Summary/Objective
1111 -
111101 - Follow up ref SDS 22 0000.
111102 -
111104 -  ..
111105 - Gary feels Multiedit, which is an editor program, has some features
111106 - that are useuful to SDS.
111107 -
111108 -        http://www.multiedit.com
111109 -
111110 -
111112 -  ..
1112 -
1113 -
1114 - Progress
1115 -
111501 - Links Need Dates for Context and Recovery to Restore Broken Links
111502 -
111503 - Gary's record on 030701 has a few links, as follows...
111504 -
111505 -      Once I noticed that copying a record provides links back to every
111506 -      heading, ref SDS 22 0001, I suggested that there was sufficient
111507 -      information to enable easy creation of a forward link when adding
111508 -      new material to the discussion in the new record.
111510 -       ..
111511 -      Rod added this feature, ref SDS 23 0001, and seems to find it
111512 -      useful in spite of his initial resistance.
111513 -
111514 - ...this is good progress on creating a connected record. ref SDS 25
111515 - 0001
111517 -  ..
111518 - Couple of pointers.....
111519 -
111520 -     a.  Neither link has a date to orient the citation.  Entering
111521 -         dates and explaining the context of a link helps remember
111522 -         correlations, which continues to be useful for applying the
111523 -         same reference in other records.
111525 -          ..
111526 -         There is a notable exception.  Automatic links created for
111527 -         headlines when a new record is created do not have dates,
111528 -         maybe just because of laziness, but in any case when people
111529 -         don't type in the link, there is little memory aid in having
111530 -         the computer create the date.
111532 -          ..
111533 -     b.  The first link has little to no context to help people
111534 -         understand purpose of the link, and what can be expected to be
111535 -         learned.
111537 -  ..
111538 - Gary reports that the new feature to support forward links is handy,
111539 - and further relates having made a few mistakes creating a link, when
111540 - the intent was only to open a link.  He expects more exposure will
111541 - build in a sufficient of care to avoid this problem and without
111542 - noticeable delay nor emotional drain that comes from expending extra
111543 - time for extra care. ref SDS 25 UY44  This was considered in planning
111544 - and evaluation of the new function on 030628. ref SDS 23 F15N
111546 -        ..
111547 -       Recovery by deleting a link, when created by mistake takes
111548 -       almost no extra time, as reported on 030628. ref SDS 23 PN95
111549 -
111550 -
111551 -
111552 -
111553 -
111554 -
1116 -

SUBJECTS
F2 Save Update Archive Pointers
Format for Anchors and Headlines with an Indented Heading
Line Numbers Record Segments Provide Flexible Structure
Indented Headings in Line Numbers Avoid Redundant Anchors on Headline

1506 -
150701 -  ..
150702 - Save Enters Anchors Above Indented Headings Avoid Redundant Anchors
150703 -
150704 - Gary's record today shows the following....
150705 -
150706 -     091010 -
150707 -   + 091011 - [WF5I
150708 -     0911 -
150709 -     0912 -
150710 -     0913 - Actions
150711 -     0914 -
150712 -   + 091401 - [SG5N
150713 -     091402 - Create weekly activity sheet
150714 -     091403 - -----------------------------
150715 -     091404 - Follow up rff SDS 21 SG5N, rff SDS 20 SG5N
150716 -     091405 -
150717 -     091406 - Added an 'Update' button to run the macro.
150719 -  ..
150720 - We discussed this recently.  Since F2 automatically enters an anchor
150721 - above an indented heading, the anchor above the headline in the
150722 - example above is redundant.  It doesn't hurt anything, but looks
150723 - "funny" -- connoting "overkill." that "boggles the mind."
150725 -  ..
150726 - Gary mentioned this occurs, because he has gotten into the habit of
150727 - leaving a blank line above headlines.  We have discussed that this is
150728 - not necessary to get an anchor for headlines below an indented heading,
150729 - as in the example above, and also shown by this record, also above.
150730 - ref SDS 0 Y87F
150731 -
150732 -
150733 -
150734 -
1508 -

SUBJECTS
Distribute SDS Records on Aerospace company Intranet Gary Looking for M  hods
Server Not Available at this Time for Distributing SDS Records on a B
3-layer Architecture Strategy Build Experience Base Improve Work With
Action Item System Gary Assigned to Develop for Project
Command Control May be Lost if Delay Starting Program of of Co
Action Item System Gary Assigned to Develop for Project Considering M
SDS Helpful Action Items Distributed Beginning on 030508 Reported Hel
Visibility Distribute SDS Records on Aerospace company Intranet Gary Lo  ing for
Assessment SDS Helpful Action Items Distributed Beginning on 030508 R
Action Items Drawn from Analysis Alignment Subjects Context
Action Item System Gary Assigned to Develop for Project Considering M
Using Excell Word Microsoft Outlook at Aerospace company for CS Meeting  Plannin
2 Worlds Bridging Gap Not Enough Time for 8 Steps Using SDS to Work I
Not Enough Time to Use SDS 8 Steps According to Design for Adding Sub

9216 -
921701 -  ..
921702 - Assignment to Develop Action Item System
921703 -
921704 - Follow up ref SDS 18 5B91.
921705 -
921706 - Gary's record on 030701 shows planning for an action item system,
921707 - which Gary called and asked about recently. ref SDS 24 0001
921708 -
921709 -     [On 030826 Gary plans action item review with Aerospace company management
921710 -     and using SDS report methods. ref SDS 30 ES6N
921712 -  ..
921713 - Action Item management in SDS is summarized on 951209. ref SDS 5 NL6L
921715 -  ..
921716 - This is another dimension of "2 worlds" that impacts transformation
921717 - from IT to a culture of knowledge, discussed recently on 030617.
921718 - ref SDS 19 R279
921720 -  ..
921721 - Action items are part of command and control of the work, discussed in
921722 - POIMS. ref OF 6 1113  On 030506 reviewed urgency using SDS for CFISR
921723 - support to gain command of the record on the project, otherwise
921724 - control of the work to improve CFISR will slip away. ref SDS 17 Q57I
921725 -
921726 -     [On 030826 reviewed SDS action item reporting procedures for
921727 -     assembling report to review with managemnt. ref SDS 30 D49I
921729 -  ..
921730 - Gary has mentioned previously keeping track of action items in Excel
921731 - and perhaps in Microsoft Word; Gary's analysis on 030701 says in
921732 - part....
921733 -
921734 -      In a complete system, action items can have predecessors which
921735 -      must be completed before this action can be started. An action is
921736 -      pending if it has predecessors that are not complete. A start
921737 -      date can act as a predecessor. ref SDS 24 0085
921738 -
921739 - ...and cites a more detailed list of elements for tracking action
921740 - items in Gary's record on 030626. ref SDS 20 0085
921742 -  ..
921743 - Context derived from deliberative analysis using SDS, as set out in
921744 - POIMS, ref OF 4 2300, is critical part of making action items useful.
921745 - Gary's discussion of "predecessor" tasks reflects the importance of
921746 - context.
921748 -  ..
921749 - SDS action item support is considered in Gary's record yesterday....
921750 -
921751 -      SDS not accessible to group, based on analysis in a prior record
921752 -      on 030626 that says SDS might support a lot of what is needed,
921753 -      ref SDS 20 GY4M, based on features, also, listed on 030626.
921754 -      ref SDS 20 0085
921755 -
921756 - ...there is no indication of reviewing SDS theory and practice on
921757 - action items, shown for example on 950612. ref SDS 2 E24Y
921758 -
921759 -     [On 030826 Gary plans action item review with Aerospace company management
921760 -     and using SDS report methods. ref SDS 30 ES6N
921762 -  ..
921763 - SDS 3-layer architecture makes SDS "accessible" to everyone, developed
921764 - on 020820. ref SDS 13 0001  Gary has experimented with distributing
921765 - intelligence via email. On 970107 there is evidence that SDS manages
921766 - the work better than people expect, ref SDS 6 4953, because SDS
921767 - improves intelligence, listening, understanding and follow up, which
921768 - are the critical ingredients for getting things done on time and
921769 - within budget.
921770 -
921771 -
921773 -  ..
921774 - Conventional Methods on Complex Work Degrades Management to Entropy
921775 -
921776 - Gary lists a lot of common features for tracking action items, then
921777 - notes that....
921778 -
921779 -           This list works quite well for simple actions, but gets
921780 -           unwieldy for larger activities unless it becomes a separate
921781 -           document. ref SDS 20 GU59
921783 -  ..
921784 - Conventional methods for tracking action items fail because there is
921785 - not a critical mass of functionality to perform the work of adding
921786 - alignment with contextual organization that makes action meaningful.
921787 - The pace and volume of work creates complexity (i.e., the fog of war)
921788 - that overwhelms span of attention to force cursory understanding and
921789 - follow up by reliance on remembering only the gist of the story.  This
921790 - causes cursory understanding due to limited span of attention, leading
921791 - to continual bumbling that excalates costs and delay from performing
921792 - rework.  Gary's analysis of conventional methods aligns with work on
921793 - 010720 when Morris reported that Microsoft has programs to track
921794 - action items, but few people use all the capability, and so things
921795 - breakdown. ref SDS 10 0K5K  More recently on 030108 Morris noted that
921796 - managing action items with conventional methods is frustrating because
921797 - people "game the system," and then the manager monitoring action items
921798 - gets blamed when the truth comes out that the actual work does not
921799 - reflect system "reporting." ref SDS 14 PVWS
921800 -
921801 -      Gary's general point that complex work and complex communications
921802 -      overwhelm complex action item systems is supported by a study
921803 -      USAFIT published showing that managing big projects degrades to
921804 -      entropy and fails because conventional tools cannot keep up,
921805 -      reviewed on 970707. ref SDS 7 0108
921806 -
921807 -          [On 030826 Gary plans action item review with Aerospace company
921808 -          management and using SDS report methods. ref SDS 30 ES6N
921809 -
921810 -
921812 -  ..
921813 - Authority Critical for Action Item System to be Effective
921814 - Partnership between Leadership and Technology Drives Action
921815 -
921816 - Part of the solution is placing management of action items under
921817 - authority to direct the work, as related on 030108. ref SDS 14 C55N
921818 - The role of authority in management was reviewed on 950705.
921819 - ref SDS 3 8965  In other words, "action" implies a duty to act, and if
921820 - there are no consequences for failing to act, then the duty is without
921821 - effect.  This requires a better partnership between leadership and
921822 - technology.  If leadership does not have adequate tools, things will
921823 - fail; but, similarly, if there is no leadership with authority to
921824 - direct the work, then the technology will not be effective.
921826 -  ..
921827 - Stating this rule more directly, Gary asked on 011006 why big projects
921828 - get fouled up so quickly? ref SDS 11 O99K  In a small company, the
921829 - owner is directing the work based on personal self-interest backed by
921830 - authority to commit resources.  This self-interest dynamic is impacted
921831 - by a close relationship between income and progress on action items
921832 - that drives use of authority to get things done.  On a big project in
921833 - a big organization, no one's income seems significantly threatened by
921834 - failure to perform (i.e., neither gains nor losses), so people place
921835 - their faith in systems of "collaboration" using technology which
921836 - everyone is supposed to check, take action on and keep up to date.
921837 - Inability to perform on this expectation due to lack of authority and
921838 - perceived lack of impact applied through the force of self-interest
921839 - dynamics causes failure.
921840 -
921841 -          [On 030826 Gary plans action item review with Aerospace company
921842 -          management and using SDS report methods. ref SDS 30 ES6N
921844 -  ..
921845 - The importance of partnership between technology and leadership is one
921846 - reason why SDS records are not issued in the name of the Communication
921847 - Manager, but rather in the name of the Project Manager or someone who
921848 - has authority to direct the work.  So, too, any action item system
921849 - should be issued in the name of someone responsible for results and
921850 - who has the authority to hire and fire and to approve payments.
921851 -
921853 -  ..
921854 - SDS Designed to Navigate through Fog of War on Complex Work
921855 -
921856 - Since SDS is designed to track daily actions based on chronology and
921857 - context, using the program according to this design provides a
921858 - continual process of triangulation that maintains alignment, which is
921859 - needed for navigating through the "fog of war" that occurs on complex
921860 - projects.
921862 -  ..
921863 - Gary continues analysis of SDS potential to support Action Items
921864 -
921865 -      It might be feasible to use the Action Item report, properly
921866 -      massaged, as a tool in the meeting. ref SDS 24 GY4M
921867 -
921868 -          [On 030826 Gary plans action item review with Aerospace company
921869 -          management and using SDS report methods. ref SDS 30 ES6N
921871 -  ..
921872 - Experience using the current Action Item system summarized on 951209,
921873 - ref SDS 5 NL6L, will yield ideas on improvements, as Gary has
921874 - demonstrated the past few months.  A concern is getting ahead and
921875 - making "improvements" before gaining experience with the existing
921876 - system.  Another concern is widening the gap between "2 worlds" by
921877 - getting ensnarled using another sysem that will require a lot time,
921878 - which reduces time available for SDS.  Tough problem.
921880 -  ..
921881 - The key part of making meetings effective is to brief key people prior
921882 - to meetings so they are alerted of issues and background and results
921883 - needed from the meeting on various issues, i.e., action items.
921885 -  ..
921886 - Gary continues analysis of SDS potential to support Action Items
921887 -
921888 -      If I designed an Action Item tracking system in SDS, I could use
921889 -      it for my tracking and for tracking public items by creating
921890 -      specialized reports. This isn't as good as it could be, since it
921891 -      doesn't help anyone else. ref SDS 24 J48H
921892 -
921893 -          [On 030826 Gary plans action item review with Aerospace company
921894 -          management and using SDS report methods. ref SDS 30 ES6N
921896 -  ..
921897 - Action Item management in SDS is summarized on 951209. ref SDS 5 NL6L
921898 -
921900 -  ..
921901 - Pending and Completed Action Items
921902 -
921903 - Work on managing status is reported on 951127. ref SDS 4 7007
921904 -
921905 -
921906 -
921907 -
921908 -
9220 -

SUBJECTS
Aerospace company Intranet Gary Looking for Methods to Distribute SDS R  ords So
Email Distribution Using Outlook Adequate to Introduce Aerospace compan  Staff o
CS Staff Meeting Notes Show Improvement Crafting Useful Record Organi
Distribution SDS Records Objection Line Numbers in SDS Objected by FC
Email Distribution Using Outlook Adequate to Introduce Aerospace compan  Staff o
Command Control May be Lost if Delay Starting Program of of Co
CFISR Enabled by SDS Organizational Memory Adds Intelligence to Infor
Memory Better than Most Nancy Approves Distribution of SDS
Belief Gets It For the Moment that Management in 21st Century Require
Attitudes Change Experience SDS Demonstrate Memory Better than Most,
Better Memory than Most You've Got Everything Captured and More Using

BI13 -
BI1401 -  ..
BI1402 - SDS Supports CFISR Objectives for Better Organizaional Memory
BI1403 - CFISR Objectives for Better Organizaional Memory Enabled by SDS
BI1404 - Gary's Memory Using SDS Better than Most Shows SDS Support for CFISR
BI1405 -
BI1406 - Follow up ref SDS 21 0001, ref SDS 8 9499.
BI1407 -
BI1408 - A letter to Gary cited below, responds to a copy of a letter, which is
BI1409 - only in the record as an attachment to the letter sent to Gary,
BI1410 - ref DIT 1 0002, noted below.  The letter received from Gary, and to
BI1411 - which the letter below responds, is addressed to....
BI1412 -
BI1415 -  ..
BI1416 - ...and in turn responds to Nancy's letter on 030630 that approves
BI1417 - distribution of the record for a meeting on CSF Architecture.
BI1418 - ref DIT 1 0003
BI1420 -  ..
BI1421 - Nancy's letter to Gary says in part...
BI1422 -
BI1423 -        I looked over my meeting notes.  You've got everything captured
BI1424 -        and more!  We can fold some of these items into the agenda for
BI1425 -        the CFISR M&S working group meeting I want to set up.
BI1426 -        ref DIT 1 EX9H
BI1428 -  ..
BI1429 - This follows up work on 030626 when Nancy planned to submit feedback
BI1430 - to support accuracy of the record. ref SDS 21 PA4V  Gary's feeling
BI1431 - that Nancy is starting to "get it," ref SDS 0 1D4N, shows progress on
BI1432 - meeting difficult challenge of transformation to initially gain
BI1433 - acceptance of using SDS for a new way of working on the project, cited
BI1434 - on 030416 ref SDS 16 JS6F
BI1435 -
BI1436 -
BI1438 -         ..
BI1439 -        Second Act Aided by Experience with SDS Organizational Memory
BI1440 -
BI1441 -
BI1442 - Submitted ref DIT 1 0001 to Gary saying....
BI1443 -
BI1444 -    1.  Good work -- "You've got everything captured and more," noted
BI1445 -        by Nancy concerning your record on CSF Architecture meetings,
BI1446 -        ref SDS 0 IX8L, sounds like you have a better memory than most.
BI1447 -        A similar to report on 990303, ref SDS 8 9499, aids "second
BI1448 -        act" follow up discussions on CFISR with Nancy planned in your
BI1449 -        letter on 030626. ref SDS 21 YL6L
BI1450 -
BI1451 -            [On 030715 letter to Gary plans follow up meeting with
BI1452 -            Nancy to demonsrate support for CFISR ref SDS 26 0001
BI1454 -             ..
BI1455 -            [On 030821 Gary is the "history button" on major DOD
BI1456 -            project, growing awareness that SDS enables command and
BI1457 -            control of the record. ref SDS 29 SO52
BI1459 -         ..
BI1460 -    2.  Correlation between Nancy's assessment on 030630 with Merry's
BI1461 -        evaluation on 990303 suggests common experience might relate to
BI1462 -        common tools and methods, ref DIT 1 C27H, that strengthen
BI1463 -        organizational memory, explained, also, on 990303. ref SDS 8
BI1464 -        SU5I
BI1466 -         ..
BI1467 -    3.  Better memory noted by Nancy in her letter on 030630, per
BI1468 -        above, ref SDS 0 IX8L, should be studied to support CFISR
BI1469 -        objectives for strengthening command and control, ref DIT 1
BI1470 -        Q28G, which Nancy, also, discussed in the same letter, and
BI1471 -        lines up with planning on 030626 for a "second act."
BI1472 -        ref SDS 21 YM5P  Nancy's attitude appears to support presenting
BI1473 -        DOD requirements for good management enabled by SDS, also,
BI1474 -        discussed on 030626. ref SDS 21 LC8N
BI1476 -         ..
BI1477 -    4.  As we've been saying... Steady as she goes!! ref DIT 1 W49F
BI1478 -
BI1479 -
BI1481 -  ..
BI1482 - Received another letter today from Gary saying....
BI1483 -
BI1484 -    1.  Rod,
BI1485 -
BI1486 -        I think she gets it!
BI1487 -
BI1488 -    2.  Thanks,
BI1489 -
BI1490 -        Gary
BI1491 -        x 2-4936
BI1492 -
BI1493 -
BI1494 -
BI1495 -
BI1496 -
BI15 -

SUBJECTS
Organizational Memory Requires Professional Role
Understanding Fragile Gets It For the Moment that Management in 21st
Professional Discipline Com Manager Co-evolve Education Training Cult
Scribe Note Taker Meeting Minutes Executive Aid Organizational Memory
Attitudes Change Transformation Steady-as-she-goes Exposure Brings Ex
Progress Using SDS at Aerospace company According to the Design Enables  iscover
Experience Knowledge History Organizational Memory Scribe Note Taker
Situational Awareness Transitory Understanding Fragile Gets It For th

DL10 -
DL1101 -  ..
DL1102 - Organizational Memory Requires Professional Role
DL1103 - Note Taker Needed for Effective Organizational Memory
DL1104 - Professional Role Needed for Effective Organizational Memory
DL1105 -
DL1106 - Gary also transmitted a copy of a letter he received from Nancy
DL1107 - saying....
DL1108 -
DL1109 -    1.  From: Dr. Nancy ********r
DL1110 -        Sent: Tuesday, July 01, 2003 12:58 PM
DL1111 -        To: EXT-J*****n, Garold L
DL1112 -        Subject: RE: TEM notes
DL1114 -         ..
DL1115 -    2.  A challenge for all of us, I agree! They need professional note
DL1116 -        takers whose only job is to develop meeting reports or  we
DL1117 -        should get recorded transcripts or something for these kinds of
DL1118 -        marathons. None of us has the time to do these kinds of things
DL1119 -        and still do our main job - you have my sympathies!
DL1121 -         ..
DL1122 -        Nancy,
DL1123 -
DL1124 -            [On 030821 Gary is the "history button" for the project.
DL1125 -            ref SDS 29 NH5N
DL1126 -
DL1127 -            [On 030821 Gary recognized as the "history button" for the
DL1128 -            project places entire burden of capturing and managing
DL1129 -            organizational memory on Gary, ref SDS 29 JR5M, which, as
DL1130 -            Nancy notes, is too much for one person.
DL1132 -             ..
DL1133 -            [On 030830 Gary worried he will be spread too thin, unable
DL1134 -            to do a professional job, if demand grows beyond ability of
DL1135 -            one person to provide all of the organiztinoal memory on
DL1136 -            the project. ref SDS 31 8490
DL1138 -             ..
DL1139 -            [On 031008 Paul recognizes Gary needs help; one person
DL1140 -            cannot provide all support for Communication Metrics on the
DL1141 -            project. ref SDS 32 JU4T
DL1142 -
DL1144 -  ..
DL1145 - Nancy's letter recognizing need for professional role demonstrates
DL1146 - beginnings of change in attitude that overcomes resistance to good
DL1147 - management cited by Jason Yuen on 990505. ref SDS 9 4732
DL1148 -
DL1149 -            [On 040102 annual review shows emerging picture from
DL1150 -            connecting more dots that suggest potential for
DL1151 -            transformation. ref SDS 33 W63I
DL1153 -  ..
DL1154 - Nancy was responding to Gary's report earlier in the day on difficulty
DL1155 - capturing the record on three (3) days of meetings, beginning on
DL1156 - 030415, ref SDS 15 0001, as shown by Gary's letter to Nancy saying...
DL1158 -         ..
DL1159 -    1.  I agree that they aren't as good as they could be, but just
DL1160 -        trying to keep up with 3 days was a challenge.
DL1162 -         ..
DL1163 -    2.  I will see what Paul and Bruce have to say.
DL1164 -
DL1165 -        Thanks,
DL1167 -         ..
DL1168 -        Gary
DL1169 -        x 2-4936
DL1170 -
DL1171 -
DL1173 -  ..
DL1174 - Based on the foregoning, showing promise of momentary awareness about
DL1175 - need for a professional role to capture organizational memory, work
DL1176 - history, submitted following letter to Gary today saying...
DL1178 -         ..
DL1179 -    1.  Gary,
DL1181 -         ..
DL1182 -    2.  Great progress reported in your letter today. ref SDS 0 1D4N
DL1184 -         ..
DL1185 -    3.  Nancy "gets it," noted in your letter today, ref SDS 0 1D4N, by
DL1186 -        understanding, for the moment, that "intelligence" is
DL1187 -        professional work that takes time. ref SDS 0 MG6O  This
DL1188 -        understanding is fragile and so slips away if not reinforced by
DL1189 -        experience and explanations of theory and practice, as seen by
DL1190 -        the record at Broadwater Dam, PG&E, USACE, et al.  See for
DL1191 -        example telecon on 950123. ref SDS 1 7Y4I
DL1192 -
DL1193 -            [On 030715 letter to Gary plans follow up meeting with
DL1194 -            Nancy to demonsrate support for CFISR ref SDS 26 WH56
DL1196 -             ..
DL1197 -            [On 030730 Gary's boss, Steve, shows growing awareness of
DL1198 -            SDS and that attitudes change about need for good
DL1199 -            management. ref SDS 27 TT9O
DL1201 -             ..
DL1202 -            [On 030804 Gary met with Nancy to demonstrate SDS planning
DL1203 -            to submit follow up. ref SDS 28 OI37
DL1205 -         ..
DL1206 -    4.  Your efforts putting in extra time using SDS provides
DL1207 -        experience on the project that builds a foundation of enabling
DL1208 -        forces shown by Nancy's recognition that good management takes
DL1209 -        time. Keeping my fingers crossed that the "second act" you are
DL1210 -        planning to visit with Nancy about the SDS format of Knowledge
DL1211 -        Space, as discussed on 030626. ref SDS 21 YL6L, will build
DL1212 -        momentum based on Nancy's interest in CFISR to strengthen
DL1213 -        command and control, as explained in POIMS. ref OF 6 1113
DL1214 -
DL1215 -           [On 040201 Gary commended for extra effort that helps people
DL1216 -           overcome ignorance, fear and denial to enable transformation
DL1217 -           from information to a culutre of knowledge. ref SDS 33 4E4I
DL1219 -         ..
DL1220 -    5.  In particular, the hope is to guide discussion toward the
DL1221 -        notion that Nancy's suggestion about getting a transcript of a
DL1222 -        meeting to reduce the burden on people to capture and organize
DL1223 -        and effective record, will not provide intelligence needed for
DL1224 -        getting things done any more than getting a Powerpoint file,
DL1225 -        because while the latter is a summary without substance, a
DL1226 -        transcript is equally useless, like the pile of books you posed
DL1227 -        the other day in explaining the need for structure in the
DL1228 -        record.  This is heading toward the KM dilemma that better
DL1229 -        management requires a critical mass of improvements, which
DL1230 -        normally looks like overkill and so prevents serious
DL1231 -        consideration.  Hopefully, we can keep taking steps toward
DL1232 -        transformation from IT to good management that requires new
DL1233 -        roles and new tools, shown by Roy Roebuck's analysis at DOD on
DL1234 -        the need to create organizational memory, reviewed in response
DL1235 -        to your question on who cares about SDS support for good
DL1236 -        management, reviewed on 020217. ref SDS 12 1332
DL1238 -         ..
DL1239 -    6.  So, today we have dug someone out of the system who cares
DL1240 -        somewhat about productivity and earnings, and recognizes
DL1241 -        intelligence is an ingredient.  As we discussed in our call
DL1242 -        today, there is bound to be a contracting officer out there
DL1243 -        somewhere in the woods on the project, who shares Nancy's
DL1244 -        perspective enough, to ask the contractor to follow
DL1245 -        requirements in FAR for good management practice.  Maybe the
DL1246 -        USACE report can nudge things along. ref DRP 2 6172
DL1247 -
DL1248 -           [On 030804 Gary reports having met with Nancy to demonstrate
DL1249 -           SDS and planning follow up letter on alignment with
DL1250 -           requirements for CFISR. ref SDS 28 OH6J
DL1252 -            ..
DL1253 -           [On 040102 annual review shows emerging picture from
DL1254 -           connecting more dots that suggest potential for
DL1255 -           transformation. ref SDS 33 W63I
DL1257 -         ..
DL1258 -        Rod
DL1259 -
DL1260 -
DL1261 -
DL1262 -
DL13 -