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: September 14, 2007 12:42 PM Friday; Rod Welch

Letter to team explaining co-evolution tools practices of SDS.

1...Summary/Objective
2...History SDS Integrate Time Information with Schedule Diary


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

CONTACTS 

SUBJECTS
Everthing Miscellaneous Except SDS Context  Mnagement Everything Rig

2703 -
2703 -    ..
2704 - Summary/Objective
2705 -
270501 - Follow up ref SDS 8 0000, ref SDS 7 0000.
270502 -
270503 -
270504 -
270506 -  ..
2706 -
2707 -
2708 - Progress
2709 -
270901 - History SDS Integrate Time Information with Schedule Diary
270902 -
270903 - Follow up ref SDS 8 414H.
270904 -
270905 - Submitted ref DIT 1 0001 responding to various letters the past few
270906 - weeks...
270907 -
270908 -       Jack suggests reading Everything
270909 -       Miscellaneous......................... 070830, ref SDS 7 I19J
270911 -        ..
270912 -       Gary comments on Everything
270913 -       Miscellaneous......................... 070831, ref SDS 8 I19J
270915 -        ..
270916 -       Jack cites usefulness of granular
270917 -       addressibility........................ 070831, ref SDS 8 OV3G,
270919 -        ..
270920 -       Gary commends purple numbers, worries
270921 -       transformation takes a long time
270922 -       because deferred rewards hard to
270923 -       grasp................................. 070904, ref SDS 5 OV3G
270925 -        ..
270926 -       Jack trying to build mental model of
270927 -       SDS................................... 070907, ref SDS 7 JL5N
270929 -        ..
270930 -       Gary commends Jack's mental model
270931 -       and explains details of
270932 -       SDS design............................ 070907, ref SDS 7 337G
270934 -        ..
270935 -       Jack discusses SDS design abstract to
270936 -       support discipline of Knowledge Asset
270937 -       Management............................ 070907, ref SDS 7 6A3I
270939 -        ..
270940 -       Gary explains co-evolution of SDS and
270941 -       Communication Metrics
270942 -       practices............................. 070913, ref SDS 8 414H
270944 -        ..
270945 -       Jack working on technical paper
270946 -       related to recent
270947 -       discussions........................... 070913, ref SDS 8 6A3I
270949 -  ..
270950 - The letter to Gary, Jack, and Morris says...
270951 -
270952 -    1.  Excellent rendition in your letter yesterday on co-evolution of
270953 -        tools and practice for augmenting intelligence using the
270954 -        discipline of Communication Metrics. ref SDS 8 RM8U,
270955 -        ref DIT 1 0001,
270957 -         ..
270958 -    2.  As shown in the history of SDS on 000723. ref SDS 1 0008 ...the
270959 -        engine of SDS is a "schedule" using a particular methodology
270960 -        begun in 1969. ref SDS 1 CW4G, ref DIT 1 HR6F
270962 -         ..
270963 -    3.  Morris correctly noted the other day on 070907 that the SDS
270964 -        schedule lists things to do on particular dates, like a manual
270965 -        desk calendar where people jot down meetings, calls, prepare or
270966 -        receive documents, issue or receive payments, go to a ball
270967 -        game, etc. ref SDS 6 XI6S, ref SDS 0 RG8S
270969 -         ..
270970 -    4.  The idea of SDS is to plan performance of scheduled tasks with
270971 -        experience from relevant work history, called a "diary."
270972 -        ref DIT 1 HX7Q
270974 -         ..
270975 -    5.  The "diary" component of SDS began in 1969 as simple key words
270976 -        associated with scheduled tasks to indicate objectives, and
270977 -        then actual results achieved.  These results were then rolled
270978 -        over into planning follow up with a new schedule and new
270979 -        keywords using a "suspense file" process learned in the
270980 -        military. ref SDS 1 YE6J  With experience writing legal briefs
270981 -        in the 70s and early 80s, the diary part of the schedule became
270982 -        an actual narrative to make sense of daily events. ref SDS 1
270983 -        LR5F, ref DIT 1 HX8L
270985 -         ..
270986 -    6.  When computers came along in the mid-80s, this Schedule Diary
270987 -        practice was implemented with Morris' macro language, which he
270988 -        spruced up over the years, as needs arose.  The original key
270989 -        word explanation of objectives and results for the schedule,
270990 -        became subject pointers into the diary.  Control Fields were
270991 -        designed to assemble chronology for understanding the evolution
270992 -        of events and ideas based on context, as explained and
270993 -        demonstrated in the meeting with Morris last week. ref SDS 6
270994 -        VG3T, ref DIT 1 HX9K
270996 -         ..
270997 -    7.  Adding "control" to conventional narrative provides a "filing"
270998 -        mechanism so there is a place for everything, rather than
270999 -        classifying everything "miscellaneous," discussed in
271000 -        correspondence today.  Morris noted this in his letter on
271001 -        010425 explaining the idea of SDS that everything is in the
271002 -        right place at the right  time. ref SDS 2 EP7F, ref DIT 1 QY9O
271004 -         ..
271005 -    8.  Gary correctly notes that tools are essential for context
271006 -        management, but not sufficient.  Training and experience
271007 -        thinking about future needs improve ability to organize the
271008 -        record according to objectives, requirements, and commitments.
271009 -        Linking plays an important role, because finding relevant
271010 -        history to cite requires using the subject index to find
271011 -        critical details.  This requires tools to quickly construct and
271012 -        populate subject accounts based on situational awareness.
271013 -        Complementarity between chronology, context, and connections
271014 -        builds synergy for getting things done by making sense of daily
271015 -        events using the plan, perform, report "intelligence" process
271016 -        cited in Gary's analysis. ref DIT 1 HX4Q
271018 -         ..
271019 -    9.  A key factor in co-evolution [question asked by Gary Johnson in
271020 -        a letter on 070904, ref SDS 5 DV9U] is starting with a
271021 -        foundational concept that has "legs."  In this case,
271022 -        integrating time and information with subject pointers turns
271023 -        out to approach a useful theory of "knowledge," so in effect,
271024 -        SDS is riding a wave driven by the power of knowledge.
271025 -        ref DIT 1 HX5T
271027 -         ..
271028 -   10.  Another key factor of co-evolution is experimenting without
271029 -        having to get permission for budget allocation or otherwise,
271030 -        which Morris facilitated by building commands as needed,
271031 -        especially in the 1980s. ref DIT 1 LK3F
271033 -         ..
271034 -   11.  A third factor of successful innovation is using the system for
271035 -        daily work and willingness to stop and invest time to apply
271036 -        experience to refine otherwise "interesting" and "promising"
271037 -        technology into a practical tool for good management, as
271038 -        explained in POIMS. ref OF 3 1X6G, ref DIT 1 HX6T
271040 -         ..
271041 -   12.  Good to see people focusing on improving tools and practices.
271042 -        ref DIT 1 VX4G
271043 -
271044 -
271045 -
271046 -
271047 -
271048 -
271049 -
271050 -
271051 -
271052 -
271053 -
271054 -
271055 -
271056 -
271057 -
2711 -