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

SUBJECTS
Subject Index Assignments Reflect Organic Structure of Work and Life
Capturing Organizing Information and Adding Intelligence
Learning How to Set Up New Record Receiving a Letter Training Mentori
Flexible Structure Balance Between Power of Flexibility that is Fragi
Procedures Explain Steps for Creating a New SDS Record
Subject Index Difficult to Use Needs Mentoring Training to Support Le
Support Request Telephone Orientation Setting Up a New SDS Record and
New User Learning Orientation Records
New Task in Schedule F1 Shift F1 Failed on Record Dated 021022 Possib

1411 -
1411 -    ..
1412 - Summary/Objective
1413 -
141301 - Follow up ref SDS 54 0000, ref SDS 50 0000.
141302 -
141303 - Provided orientation setting up a new SDS record and using the Subject
141304 - Index, per Gary's request on 030114. ref SDS 0 B1C5  Talked for
141305 - several hours reviewing concepts, practices and specific steps; Gary
141306 - indicated this effort helped him understand on how to use SDS.
141307 - ref SDS 0 VI8I  Gary sent another letter today asking for help to
141308 - maintain global pointers.  Sent an email back with instructions,
141309 - linked to this record, ref SDS 0 OM3G, and then called Gary and we
141310 - worked through the steps together on the telephone. ref SDS 0 DY3I
141311 - Gary sent a second letter with a list of 10 or so ideas on improving
141312 - SDS. ref SDS 0 PE7J
141313 -
141314 -
141315 -
141316 -
141317 -
141319 -  ..
1414 -
1415 -
1416 - Progress
1417 -
141701 - Sample Analysis of Creating New SDS Records Helpful
141702 - Background On Procedures Using SI and Create New Records
141703 -
141704 - Follow up ref SDS 54 B1C5, ref SDS 50 B1C5.
141705 -
141706 - On 030114 Gary requested a telephone call for orientation on using
141707 - instructions in the record on 030111 to create a new SDS record and
141708 - assigning subjects, ref SDS 50 V63K, just as I did for the record on
141709 - 030114, and following Gary's letter on 030108 submitting ideas for
141710 - corrections and improvements. ref SDS 47 0001  On 030116 completed
141711 - review of Gary's letters on 030108. ref SDS 57 0001  On 030117 sent an
141712 - update for the SDS program and records, to Gary, and reminded about
141713 - having teleon he requests. ref SDS 60 SS8J
141715 -  ..
141716 - Gary's letter on 030114 said in part...
141717 -
141718 -      I find that there are operations called out that either I don't
141719 -      quite know how to do or that produce results different from what
141720 -      I expected from the description. ref DRP 7 PR86
141722 -  ..
141723 - Today, we used scenario working with the record on Eric Armstrong's
141724 - request for help finding information, on 030111. ref SDS 50 V63K
141726 -  ..
141727 - Segmenting the Record with Control Fields is a process we need to work
141728 - on, per planning on 030108, ref SDS 47 3E5J, and on 030111.
141729 - ref SDS 50 IH4F
141731 -  ..
141732 - After our discussion, Gary said he feels better prepared to use
141733 - instructions and methods shown in the record on 030111. ref SDS 50
141734 - V63K
141735 -
141736 -
141737 -
141738 -
141739 -
141740 -
1418 -
1419 -

SUBJECTS
Multiple Views Assign Related Subjects in Other Domains
Subject Index Does Not Sort
Johnson, Gary Subject Index Does Not Sort Using F2

2105 -
210601 -  ..
210602 - Subject Indexes Not Sorting in Gary's Records
210603 -
210604 - Follow up ref SDS 54 LZ75, ref SDS 50 7784.
210605 -
210606 - Gary initially cites the record on 030111 that explains how to sort a
210607 - subject index to select alternate subjects, ref SDS 50 7784, and he
210608 - reports a new problem....
210610 -       ..
210611 -      Sorting from the menu does change the order of the SI entries on
210612 -      the page, but there is no order apparent. They are not
210613 -      alphabetically sorted by description which is what I expected.
210614 -      ref DRP 7 PR6G
210616 -  ..
210617 - We tested this and everything seems to work now.  Gary said that
210618 - sorting the subject index places descriptions in alphabetical order.
210619 -
210620 -
210621 -
210622 -
210623 -
2107 -

SUBJECTS
Diary Summary Shows Multiple Entries for Same Record Need Guidance on
Diary Record Listed in Summary But No Record Exists How to Delete Dat
Help Needed to Delete Extraneous and Duplicate Listings in Diary Summ
Instructions Extraneous and Duplicate Listings in Diary Summary

2306 -
230701 -  ..
230702 - Diary Records Not Found
230703 -
230704 - Follow up ref SDS 28 HR5O.
230705 -
230706 - Received ref DRT 1 0001 from Gary saying....
230707 -
230708 -   1.  I have a duplicate record listed in the diary for December 31,
230709 -       2002. The second record doesn't exist.
230711 -        ..
230712 -       I have attached the diary listing. ref DRT 1 VPUU
230713 -
230714 -          It helps to get a link or explanation that identifies the
230715 -          problem area.
230716 -
230717 -          In this case, found a duplicate for the diary on 021231.
230718 -          ref DRT 1 V28G
230720 -           ..
230721 -          A diary summary on Gary's records shows this problem.  There
230722 -          are two entries on 021231 with the title Confidentiality and
230723 -          publishing SDS records.  Both show the same time for hours
230724 -          and minutes, but only the first one exists. ref SDS 39 0001
230726 -           ..
230727 -          Problem....
230728 -
230729 -              How to delete pointers for the second entry.
230731 -        ..
230732 -   2.  I ran the File -> Maintenance entry, and it reported 3 records
230733 -       from November 4, 2002 as not being needed. I had discovered this
230734 -       manually earlier and moved them into the SDS record area. They
230735 -       do not appear in the Diary. ref DRT 1 IO6F
230736 -
230737 -           Maintenance in the Schedule "File" menu does not solve this
230738 -           problem, see below. ref SDS 0 S566
230740 -        ..
230741 -   3.  Can you tell me what I need to do to fix these sorts of entries?
230743 -        ..
230744 -   4.  Since these are clearly related, I need to understand how SDS
230745 -       maintains Diary lists so that I can correct such problems, an
230746 -       possible write a script to rebuild the necessary files.
230747 -
230748 -
230750 -  ..
230751 - SDS Record Structure for Maintaining Pointers
230752 -
230753 - F2 to save a record runs macro 0702051, which does the following...
230754 -
230755 -     1.  Updates follow ups in SAA based on what is shown in the
230756 -         record.  If there are no follow ups in the record, because
230757 -         they were either done, or the User changed the status, then
230758 -         any follow ups in SAA for this record are removed.
230760 -          ..
230761 -     2.  Copies pointers to following data bases files...
230762 -
230763 -         a.  01 - Record description.....  d: sd uuuuu 04 yy ww
230764 -         b.  02 - Contacts...............  d: sd uuuuu 05 yy ww
230765 -         c.  03 - Files..................  d: sd uuuuu 03 yy ww
230766 -         d.  04+- Control fields.........  d: sd uuuuu 03 yy ww
230768 -          ..
230769 -         ...where....
230770 -
230771 -                 1.  uuuuu = user ID
230772 -                 2.  yy    = year
230773 -                 3.  ww    = week
230775 -  ..
230776 - Pointers for contacts, files and control fields are used to find
230777 - records and record segments that meet report specifications.
230779 -  ..
230780 - Record description pointers are used for the Diary Summary and for
230781 - summary reports on subjects, contacts and files.
230782 -
230783 -
230785 -  ..
230786 - Pointers for Reports and Diary Summaries Can Get Out of Sync
230787 -
230788 - Occassionally, pointer files get out of sync, where a record has been
230789 - deleted and the pointers still exist, which seems to the case with
230790 - Gary's records for 021231, per above. ref SDS 0 OM3G  One way this may
230791 - occur is starting to create a new record, and Medit memory fails,
230792 - which prevents the operation from completing.  When you launch the
230793 - same task again, it creates another with the same time for hhmm, but
230794 - the seconds are different.
230796 -  ..
230797 - When there are mulitple entries in the diary summary for the same
230798 - task, and both exist, this can be corrected by opening one of them and
230799 - using the Delete Record function in the Diary menu.  When, however,
230800 - one of the records does not exist, then the pointer files need to be
230801 - maintained manually.
230802 -
230804 -  ..
230805 - Procedures to Maintain SDS Record Pointers
230806 -
230807 -
230808 -     3.  Open Medit.
230809 -
230810 -     4.  Launch File Access, F1 F3
230812 -          ..
230813 -     5.  Press F3 to change C: to D:
230815 -          ..
230816 -     6.  Press Tab to move the cursor to the second element, and
230817 -         enter the following string...
230818 -
230819 -               D: sd 08 uuuuu 04 yy
230821 -          ..
230822 -         Our approach is to first go find the duplicate entry in the
230823 -         pointers for the record description, and then use the file
230824 -         listing created at that location to edit the other pointer
230825 -         files.
230827 -          ..
230828 -     7.  Press Enter to launch the operation to get a file list for
230829 -         the year where the problem record exists.
230831 -          ..
230832 -         This produces a list for the year 2003 that looks like....
230833 -
230834 -                 3 files found containing 3886 bytes
230835 -             D:\sd\08\00101\04\03\    01    A    1412  103-01-15   0:59
230836 -             D:\sd\08\00101\04\03\    02    A    1450  103-01-19  10:44
230837 -             D:\sd\08\00101\04\03\    03    A    1024  103-01-19  11:13
230839 -          ..
230840 -         The same list for the year 2002 looks like....
230841 -
230842 -                 52 files found containing 68378 bytes
230843 -             D:\sd\08\00101\04\02\    01    A    1873  102-08-23  16:05
230844 -             D:\sd\08\00101\04\02\    02    A     780  103-01-10   7:56
230845 -             D:\sd\08\00101\04\02\    03    A    1174  103-01-10  20:56
230846 -             D:\sd\08\00101\04\02\    04    A    1249  103-01-13  12:37
230847 -             D:\sd\08\00101\04\02\    05         1450  103-01-18  13:03
230848 -             ...
230849 -             ..
230850 -             .
230851 -             D:\sd\08\00101\04\02\    50         1701  103-01-17  14:38
230852 -             D:\sd\08\00101\04\02\    51    A    1418  103-01-10   7:56
230853 -             D:\sd\08\00101\04\02\    52    A    1548  103-01-16   1:32
230855 -          ..
230856 -     8.  Gary's records for 2002 produce a list that looks like....
230857 -
230858 -                 15 files found containing 13402 bytes
230859 -             D:\sd\08\gljdy\04\02\    26    A      85  103-01-10   7:57
230860 -             D:\sd\08\gljdy\04\02\    39    A     171  103-01-10   7:57
230861 -             D:\sd\08\gljdy\04\02\    40    A    1311  103-01-10   7:57
230862 -             D:\sd\08\gljdy\04\02\    41    A    1700  103-01-10   7:57
230863 -             D:\sd\08\gljdy\04\02\    42    A     618  103-01-10   7:57
230864 -             D:\sd\08\gljdy\04\02\    43    A     276  103-01-10   7:57
230865 -             D:\sd\08\gljdy\04\02\    44    A     809  103-01-10   7:57
230866 -             D:\sd\08\gljdy\04\02\    45    A    2925  103-01-10   7:57
230867 -             D:\sd\08\gljdy\04\02\    46    A     937  103-01-10   7:57
230868 -             D:\sd\08\gljdy\04\02\    47    A    1868  103-01-10   7:57
230869 -             D:\sd\08\gljdy\04\02\    48    A     785  103-01-10   7:57
230870 -             D:\sd\08\gljdy\04\02\    49    A     165  103-01-10   7:57
230871 -             D:\sd\08\gljdy\04\02\    50    A     665  103-01-10   7:57
230872 -             D:\sd\08\gljdy\04\02\    51    A     228  103-01-10   7:57
230873 -             D:\sd\08\gljdy\04\02\    52    A     859  103-01-10   7:57
230875 -          ..
230876 -         There are only 15 files, because Gary started using SDS in
230877 -         September 2002, rather than from the beginning of the year.
230879 -          ..
230880 -     9.  Open the weekly pointer file, verify this is the correct date
230881 -         range, and the find the record description line for the
230882 -         problem to correct.
230884 -          ..
230885 -         Generally this entails guessing about which weekly file to
230886 -         open based on the date of the record.  For example, if the
230887 -         record is dated in July, then one might try week 26. Since the
230888 -         problem record is on 021231, we know this is week 52, so move
230889 -         the cursor to that line and press Enter or double click on the
230890 -         line with file for week 52.
230892 -          ..
230893 -         You will see a list that looks like this for the 04 pointers
230894 -         that have 01 record description lines.  Notice it is easy to
230895 -         scroll through the file to the specific date of the problem
230896 -         record.
230897 -
230898 -             021225 092100 GLJDY   01 - Schedule and Diary Summary
230899 -             021225 125823 GLJDY   01 - Open Exchange Server
230900 -             021226 084800 GLJDY   01 - Schedule and Diary Summary
230901 -             021227 083300 GLJDY   01 - Schedule and Diary Summary
230902 -             021228 101100 GLJDY   01 - Schedule and Diary Summary
230903 -             021228 103140 GLJDY   01 - SDS Interface and KM Support
230904 -             021228 140156 GLJDY   01 - Suggestions -- Importing Documents
230905 -             021228 141310 GLJDY   01 - Reformatted MEdit Source Code
230906 -             021231 060100 GLJDY   01 - Schedule and Diary Summary
230907 -             021231 060447 GLJDY   01 - Adding Anchors to Paragraphs Automatically
230908 -             021231 062427 GLJDY   01 - Hidden Villa
230909 -          -- 021231 065618 GLJDY   01 - Confidentiality and Publishing SDS Records
230910 -             021231 065655 GLJDY   01 - Confidentiality and Publishing SDS Records
230911 -             021231 071951 GLJDY   01 - Error in Edit Menu
230912 -             021231 075954 GLJDY   01 - Creating Links in DIT Files
230914 -          ..
230915 -    10.  There are two records for Confidentialty and Publishing SDS
230916 -         records.
230918 -          ..
230919 -         You know from having opened one of them which is the good
230920 -         one.
230922 -          ..
230923 -         Note the TIME, in particular the last two places that make it
230924 -         unique, for the record that is the one to delete, because you
230925 -         need will this information for step 10.
230927 -          ..
230928 -    11.  Move the cursor to the 01 record description line in the 04
230929 -         pointer file and delete the line for the record that does not
230930 -         exist by pressing Alt F8.
230932 -          ..
230933 -    12.  After noting the exact time of the record to delete, and after
230934 -         deleting that line in the description "04" pointer file...
230935 -
230936 -             a.  Presss F2 to save the revised file.
230937 -             b.  Press ESC to close the file and do the next one.
230939 -          ..
230940 -    13.  You are now back in the list of weekly pointer files for the
230941 -         record description lines.  We will do a cycle to delete the
230942 -         corresponding lines for the other pointers.
230943 -
230944 -                 15 files found containing 13402 bytes
230945 -             D:\sd\08\gljdy\04\02\    26    A      85  103-01-10   7:57
230946 -             D:\sd\08\gljdy\04\02\    39    A     171  103-01-10   7:57
230947 -             D:\sd\08\gljdy\04\02\    40    A    1311  103-01-10   7:57
230948 -             D:\sd\08\gljdy\04\02\    41    A    1700  103-01-10   7:57
230949 -             D:\sd\08\gljdy\04\02\    42    A     618  103-01-10   7:57
230950 -             D:\sd\08\gljdy\04\02\    43    A     276  103-01-10   7:57
230951 -             D:\sd\08\gljdy\04\02\    44    A     809  103-01-10   7:57
230952 -             D:\sd\08\gljdy\04\02\    45    A    2925  103-01-10   7:57
230953 -             D:\sd\08\gljdy\04\02\    46    A     937  103-01-10   7:57
230954 -             D:\sd\08\gljdy\04\02\    47    A    1868  103-01-10   7:57
230955 -             D:\sd\08\gljdy\04\02\    48    A     785  103-01-10   7:57
230956 -             D:\sd\08\gljdy\04\02\    49    A     165  103-01-10   7:57
230957 -             D:\sd\08\gljdy\04\02\    50    A     665  103-01-10   7:57
230958 -             D:\sd\08\gljdy\04\02\    51    A     228  103-01-10   7:57
230959 -           x D:\sd\08\gljdy\04\02\    52    A     859  103-01-10   7:57
230960 -                             x
230962 -          ..
230963 -    14.  Move the cursor to the "4" in gljdy\04\02, which is column 17,
230964 -         and change "4" to "1" in order to open the control field
230965 -         pointers and remove control field lines for the missing
230966 -         record.  If these lines are left in the pointer file they will
230967 -         produce an incorrect report, so we want to remove them.
230969 -          ..
230970 -    15.  Repeat steps 7 - 9 beginning at ref SDS 0 YT5X, to remove
230971 -         pointers for the record that does not exist.
230973 -          ..
230974 -         Usually there are multiple control field lines for a record,
230975 -         but only one description line.  So, in the 01, 03 and 05
230976 -         pointer files, use Alt F7 to begin a group delete, and move
230977 -         the cursor the last line for the group to be removed and press
230978 -         Alt F7 again to remove all of the lines for the record that
230979 -         does not exist.
230981 -          ..
230982 -    16.  After removing control field lines in the 01 pointer file,
230983 -         change "1" to "3" in step 12, and repeat steps 7 - 9 to remove
230984 -         all Reference field lines for the record that does not exist.
230986 -          ..
230987 -    17.  After removing Reference field pointers in the 03 pointer
230988 -         file, change "3" to "5" in step 12, and repeat steps 7 - 9 to
230989 -         remove all Contact lines for the record that does not exist.
230991 -  ..
230992 - Once the 01 record description line is removed from the 04 pointer
230993 - file, the duplicate entry in the Diary Summary will be corrected.
230994 -
230996 -  ..
2310 -
2311 -
2312 - 1236
2313 -
231301 - Sent an email to Grary with these instructions, and then called to
231302 - discuss implementation on this matter and the other problems listed
231303 - above. ref SDS 0 B1C5
231305 -  ..
231306 - During our call, we stepped through the steps explained above, and
231307 - Gary indicated he has a better understanding of how to maintain SDS
231308 - record global pointers.
231309 -
231310 -
231311 -
231312 -
2314 -

SUBJECTS
Usability of SDS Functionality of SDS
2nd Impressions of SDS Functionality and Usability

270401 -  ..
270402 - Ideas for Improving SDS
270403 -
270404 - Follow up ref SDS 24 VJ6N, ref SDS 31 VJ6N.
270405 -
270406 - Received ref DRT 2 0001 from Gary who submits references to 10 or so
270407 - different SDS records he has created that evaluate SDS and suggest
270408 - ideas for improvements, per planning on 011210. ref SDS 19 XW54
270410 -  ..
270411 - Gary says today....
270412 -
270413 -   a.  I have been playing with some ideas. Please see these records (I
270414 -       will try to remember to do the upload this time!), ref DRT 2
270415 -       0001
270417 -        ..
270418 -   b.  Note that my little tool to get URLs is very handy for some of
270419 -       this! ref DRT 2 345N
270420 -
270421 -          Has Gary submitted a record explaining this new tool?
270422 -
270423 -          How is the tool applied; from within an email program, or in
270424 -          SDS?  What calls it?
270426 -        ..
270427 -   c.  Don't concern yourself with getting to any of this any time
270428 -       soon. I am giving you this list because there is no index of the
270429 -       web pages. ref DRT 2 346H
270431 -  ..
270432 - In order to review these ideas for taking action, we need the actual
270433 - SDS records to develop traceability, as explained in the record on
270434 - 030108. ref SDS 47 PX6X
270436 -        ..
270437 -   d.  Improvements and Impressions of SDS
270439 -            ..
270440 -       1.  Searching for Diary Records. ref SDS 63 0001
270441 -
270442 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/19/112749.HTM
270443 -
270444 -                [On 030410 Gary doing more work on requirements for
270445 -                improving SDS; adding links to POIMS helps maintain
270446 -                alignment with objectives. ref SDS 75 KF6M
270448 -            ..
270449 -       2.  Entering Records From Notes. ref SDS 62 0001
270450 -
270451 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/19/111623.HTM
270453 -            ..
270454 -       3.  Line Numbering in SDS. ref SDS 61 0001
270455 -
270456 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/19/055635.HTM
270457 -
270458 -              This record also discusses using purple numbers to add
270459 -              links to the end of a para in SDS. ref SDS 61 KI6K
270461 -                  ..
270462 -                 [On 030120 called Gary, he wants to develop code that
270463 -                 puts an anchor on every para, rather than use Alt F9,
270464 -                 and suggests Purple Numbers because that can be done
270465 -                 with code outside SDS. ref SDS 67 0001
270467 -                  ..
270468 -                 [On 030121 modified SDS to add explicit links to most
270469 -                 every para under rules of context, using F2 to save a
270470 -                 record. ref SDS 68 0001
270472 -            ..
270473 -       4.  Bookmarking Records -- Features for New SDS. ref SDS 64 0001
270474 -
270475 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/19/113420.HTM
270477 -            ..
270478 -       5.  Desk Set movie -- Lessons and Ideas. ref SDS 59 0001
270479 -
270480 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/17/005417.HTM
270482 -            ..
270483 -           Gary's reflections on implications of cultural artifacts for
270484 -           work process philosophy, align with recent analysis of using
270485 -           support for capturing accurate understandings of daily
270486 -           communication, shown by the movie "The Maltease Falcon,"
270487 -           which was discussed with Morris on 020927. ref SDS 22 W682
270489 -            ..
270490 -           Gary's point about human intervention reflects the
270491 -           explanation of human mental metrics that occur in parallel
270492 -           all at once, explained on 950204. ref SDS 5 HE6J
270494 -            ..
270495 -       6.  Features for New SDS -- Editor, ref SDS 51 0001
270496 -
270497 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/12/105827.HTM
270499 -            ..
270500 -       7.  SDS Improvement Ideas, ref SDS 52 0001
270501 -
270502 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/12/223612.HTM
270504 -            ..
270505 -       8.  SDS -- Indexing and Fixing Problems, ref SDS 49 0001
270506 -
270507 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/09/073900.HTM
270509 -            ..
270510 -       9.  Multiple Perspectives on SDS -- Important to understanding
270511 -           some of what follows. ref SDS 65 0001
270512 -
270513 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/19/121559.HTM
270515 -            ..
270516 -      10.  Uniform Notes: Implementing SDS software, ref SDS 53 0001
270517 -
270518 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/14/030241.HTM
270520 -        ..
270521 -   e.  The following cover some of my experience (good and bad) with
270522 -       learning SDS.
270524 -            ..
270525 -      11.  Editing in SDS reported on 030115. ref SDS 56 YM9P
270526 -
270527 -              http://www.welchco.com/sd/08/GLJDY/02/03/01/15/021058.HTM
270529 -            ..
270530 -           Frustrations learning SDS reflect the challenge of learning
270531 -           a new way of working, cited by Gary below. ref SDS 0 U56L
270532 -
270533 -            [On 030120 letter to Gary addresses frustrations about
270534 -            learning curve for transformation from information to a
270535 -            culture of knowledge. ref SDS 66 5P49
270537 -             ..
270538 -            [On 030227 Gary raised usability issues, ref SDS 72 LL7I,
270539 -            cited need for efficient keyboard. ref SDS 72 AR42
270541 -             ..
270542 -            [On 030124 developed new function to shift text to uniform
270543 -            left margin. ref SDS 70 0001
270544 -
270545 -
270546 -
270547 -
2706 -

SUBJECTS
SDS Evaluation Applies Technology to Implement Philosophical Scientif
Cognitive Science SDS Uses Technology to Support and Apply Ideas on A
Integrate Cricial Mass Common Tasks So Each Supports the Other Advant
Johnson, Gary SDS Improves Management Contracts Eight (8) Steps Aid T
Integrate Cricial Mass Common Tasks So Each Supports the Other Advant
Integrate Time Information Enhance Alphabet Technology
Art Management Harmony Poetry Balance Competing Objectives Resources

4709 -
471001 -  ..
471002 - Art of Automated Management Integrates Core Competencies
471003 - Integration Critical Mass Common Tasks Key Advantage of SDS
471004 - New Way of Working Using Automated Integration of Common Tasks
471005 - SDS Applies Technology to Augment Intelligence and Integrates Tasks
471006 -
471007 - Gary continues in his letter today saying...
471008 -
471009 -      12.  Assessment of SDS Software -- Not ready for prime time,
471010 -           ref DRT 2 346X, but look at it anyway. ref SDS 58 0001
471012 -            ..
471013 -           Gary's record on 030116 cites SDS support for the philosophy
471014 -           and science on knowledge work, ref SDS 58 0W6L, which aligns
471015 -           well with Peter Drucker's call for technology to "routinize"
471016 -           tasks using ideas from cognitive science, reviewed 991025.
471017 -           ref SDS 9 0785  The philosophy of SDS enables the science of
471018 -           Communication Metrics based on integration that enables
471019 -           complementary tasks so there is harmony and balance in
471020 -           performing work, as explained in POIMS. ref OF 2 8559
471021 -
471022 -                [On 030316 Gary reports that power of SDS is based on
471023 -                the integrated design of complementary tools.
471024 -                ref SDS 74 EV4N
471026 -                 ..
471027 -                [On 030410 Gary doing more work on requirements for
471028 -                improving SDS; adding links to POIMS helps maintain
471029 -                alignment with objectives. ref SDS 75 KF6M
471031 -                 ..
471032 -                [On 030416 reviewed Gary's record on 030413 explaining
471033 -                how SDS improves productivity. ref SDS 76 7P5F
471035 -            ..
471036 -           Gary's record on 030116, ref SDS 58 0S6G, aligns with prior
471037 -           analysis of linking and related methods in Gary's letter on
471038 -           021126 citing the role of integration, ref SDS 32 A15L  This
471039 -           supports the explanation in POIMS on integrating a critical
471040 -           mass of common tasks, ref OF 3 2688, so that each supports
471041 -           the other. ref SDS 58 0S6G  Gary indicates the advantage of
471042 -           SDS is integrating a wide range of commons features in a
471043 -           single system. ref SDS 58 WS5L  He feels this is a new way
471044 -           of working, ref SDS 58 PU3I, which aligns with Morris'
471045 -           analysis on 911123. ref SDS 2 0477, showing progess on using
471046 -           technology to improve the art of management. ref OF 1 6221
471047 -           Appears to address Doug Engelbart's goal for a whole new way
471048 -           of thinking about the way people work, reported on 991222.
471049 -           ref SDS 10 3696
471050 -
471051 -               [On 030316 Gary relates that power of SDS is integrating
471052 -               a critical mass of core tasks. ref SDS 74 EV4N
471054 -            ..
471055 -           The evaluation today supplements Gary's letter on 021120,
471056 -           ref SDS 31 NN9H, and his initial impressions submitted on
471057 -           021016. ref SDS 24 SYRR  Assessment today further supports
471058 -           Gary's report on 020618 that SDS changes attitudes about
471059 -           investing time for good management. ref SDS 20 MU6H  This
471060 -           accomplishes the action item on 001120 for Gary to consider
471061 -           the role of integration as an essential feature. ref SDS 31
471062 -           PA4F
471064 -            ..
471065 -           Integrated tasks can be frustrating to learn, as Gary
471066 -           reports above, ref SDS 0 UF5K, and explained by Morris on
471067 -           890809, ref SDS 1 6162, because the process of human mental
471068 -           metrics is counterintuitive, reported on 920215. ref SDS 3
471069 -           5820  None-the-less integration is essential for better
471070 -           productivity to advance civilization, and paritcularly to
471071 -           work through the growing problem of information overload by
471072 -           enabling people to routinely convert a greater share of
471073 -           daily working information into useful knowledge quickly and
471074 -           accurately, that avoids the problem of meaning drift set out
471075 -           in POIMS. ref OF 2 049O
471076 -
471077 -               [On 030316 Gary reports struggle to work through
471078 -               learning curve for integrated tasks. ref SDS 74 EV53
471080 -            ..
471081 -           Gary's support for integration a powerful new way of working
471082 -           aligns with Bill Gates' notice on 021108 that Microsoft is
471083 -           planning a new project to integrate commands so people can
471084 -           use more than 10% of the power in Microsoft programs.
471085 -           ref SDS 29 EFBE
471086 -
471087 -              [On 030120 letter to Gary addresses frustrations about
471088 -              learning curve for transformation from information to a
471089 -              culture of knowledge. ref SDS 66 5P49
471091 -               ..
471092 -              [On 030121 automated adding addressability to SDS records
471093 -              on the Internet that enables people to routinely create a
471094 -              connected record showing cause and effect. ref SDS 68
471095 -              AO4M
471097 -               ..
471098 -              [On 030309 ask Gary about improving the diagram at the
471099 -              end of POIMS that summarizes concept of automated
471100 -              integration that requires a design to balance and
471101 -              complement tasks, described as "harmony" in POIMS.
471102 -              ref SDS 73 V94H
471103 -
471104 -
471105 -
4712 -

SUBJECTS
Integrated Design Complex Change Life-style Commitment to Use Good Ma
Thinking Doing Information Gratifies Senses, Reduces Time to Create K
Dilemma Integrated Design Makes Converting Informatoin into Knowledge
Meetings Dilemma Cannot Attend Every Meeting and Write Everything Dow

510601 -            ..
510602 -           Knowledge Management Dilemma Managed by SDS Design
510603 -           Judgement Resolves Dilemma Between Thinking and Doing
510604 -           Integrating Good Management Requires Exercising Judgement
510605 -
510606 -           Integrated tasks, cited by Gary today are an advantage, per
510607 -           above, ref SDS 0 346X, and are, also, frustrating to use
510608 -           when applied without judgement, similar to the problem of
510609 -           opening every link in an SDS record.  On 990419 developed
510610 -           procedure for "judicious review" to open links based on
510611 -           current needs, and reserve opening other links when the need
510612 -           arises for another occassion.
510614 -            ..
510615 -           Similar issues arise in creatig the record.  Merely because
510616 -           SDS has a lot more power for creating a record that ties
510617 -           things together does not require tying everything together
510618 -           at once.  Like the human mind the record can grow and expand
510619 -           connections as needed.  And, since the capacity is unlimited
510620 -           and since time is limited, this presents a dilemma.
510622 -            ..
510623 -           Gaining control over lower levels of organic structure in
510624 -           the microcosm of the mind reveals the power and complexity
510625 -           of intelligence, which is normally hidden from the conscious
510626 -           span of attention.  Ease of making connections to understand
510627 -           cause and effect draws the mind deeper into another dilemma:
510628 -           how much time to spend thinking with SDS and how much time
510629 -           to spend doing things that implement the thinking?  Just as
510630 -           we have to force ourselves to "think," so too, we have to
510631 -           make a judgement about when to implement, when to do things.
510632 -           When do we stop planning and reporting and start doing.  SDS
510633 -           design that integrates plan, perform, report provides a
510634 -           structure for exercising judgement effectively, but does not
510635 -           eliminate the requirement for judgement, and for many people
510636 -           this is taxing, stressful and frustrating.  Some people
510637 -           resolve the dilemma by adopting the rule that since nobody
510638 -           can write everything down, we won't make any effort to do
510639 -           more than can be done with traditional manual methods for
510640 -           converting information into knowledge using pen and paper, a
510641 -           tape recorder, wordprocessing, email, etc.
510642 -
510643 -              [On 030120 Gary using SDS for reporting to aid planning;
510644 -              frustrated about reporting that largely after-the-fact.
510645 -              ref SDS 66 3O7K  Analysis shows SDS supports dynamics of
510646 -              daily life, ref SDS 66 5N88, and helps resolve knowledge
510647 -              management dilemma for allocating time between thinking
510648 -              and doing. ref SDS 66 E75F
510650 -               ..
510651 -              [On 030123 using SDS is frustrating because making the
510652 -              process to convert information into knowledge fast and
510653 -              easy changes attitudes about investing time for analysis,
510654 -              and when time is short, people face a dilemma about
510655 -              allocating time between thinking and doing (e.g.,
510656 -              capturing the record in SDS to plan and prepare for an
510657 -              effective meeting, and attending a meeting) because the
510658 -              mind can absorb an endless amount of information for
510659 -              making mistakes, but is more limited in ability to create
510660 -              knowledge, even with the best tools and this causes
510661 -              frustration that valuable knowledge is being lost.
510662 -              ref SDS 69 Y55G
510664 -               ..
510665 -              [On 030126 discussed developing an MOU to guide Gary
510666 -              using SDS at Aerospace company and leading to formal agreement.
510667 -              ref SDS 71 0001
510669 -               ..
510670 -              [On 030309 Gary making progress developing work practice
510671 -              to apply SDS on Aerospace company project that entails constant
510672 -              meetings and continual review of large documents.
510673 -              ref SDS 73 JU84
510674 -
510675 -
510676 -
510677 -
510678 -
510679 -
510680 -
510681 -
510682 -
510683 -
510684 -
510685 -
510686 -
510687 -
5107 -