CONTACTS 
0201 - Dynamic Alternatives                         562 802 1639
020101 - Mr. Garold L. Johnson
020102 - dynalt@dynalt.com

SUBJECTS
Errors Problems Using SDS Today
Diary Record Listed in Summary But No Record Exists How to Delete Dat
Diary Records Missing Delete Pointers to Missing Records
Pointers Delete When Switch Back from Current Diary to Schedule Task
Pointers Maintain Remove From Weekly Pointer Files for Missing Diary
Maintain Pointers Remove From Weekly Pointer Files for Missing Diary

1308 -
1308 -    ..
1309 - Summary/Objective
1310 -
131001 - Follow up ref SDS 84 0000, ref SDS 82 0000.
131002 -
131003 - Gary got more information on configuring the keyboard; this will make
131004 - using SDS easier, similar to the way MS DOS solved performance issues.
131005 - ref SDS 0 9Y7O  Gary did a subject report for information on Writing a
131006 - Letter.  He used correct procedures, which shows progress learning to
131007 - use SDS, but got error messages that revealed a problem with SDS code.
131008 - The next day, I fixed this problem, ref SDS 0 044F, and made a note to
131009 - work with Gary on using links and Writing a Letter. ref SDS 0 VY5F
131010 - Gary is focusing on the goal to implement a new way of working using
131011 - concurrent reporting. ref SDS 0 5Z4P  He has shown remarkable patience
131012 - and skill solving problems caused by the fragility of flexible
131013 - structure and poor programming in SDS. ref SDS 0 TG4M  His letters on
131014 - progress and issues have been outstanding, and are fast and easy to
131015 - incorporate into SDS records. ref SDS 0 OW8I  This daily analysis
131016 - provides experience for transitioning to use SDS.  As this occurs, we
131017 - can work out new forms of "best practices" to improve collaboration.
131018 - ref SDS 0 PJ5J  An example is managing commitments through Action
131019 - Items.  Gary explains a software program for "Getting Things Done" by
131020 - improving productivity of Outlook, which has been a goal of Microsoft
131021 - for a long time. ref SDS 0 NQ7K  Commitments are an important part of
131022 - SDS support for integrated management. ref SDS 0 S59O  A few examples
131023 - show SDS makes "multiple visibility" fast and easy by assembling
131024 - action items for different subjects. ref SDS 0 ND5J
131025 -
131026 -     [On 021110 responded to Gary's letters, updated SDS and sent
131027 -     corrected Subject Index. ref SDS 88 0001
131028 -
131029 -
131030 -
131031 -
131032 -
131034 -  ..
1311 -
1312 -
1313 - Progress
1314 -
131401 - Errors and Problems Using SDS
131402 -
131403 - Follow up ref SDS 84 QQ6O, ref SDS 82 QQ6O.
131404 -
131405 - Received ref DRT 1 0001 from Gary on learning SDS features over the
131406 - past few days, adding to information he submitted on 021106 in his
131407 - letter. ref DRP 5 0001
131408 -
131410 -      ..
131411 -     Diary Records Not Found
131412 -
131413 -     Follow up ref SDS 84 HR5O.
131414 -
131415 -     Below, Gary got another message while doing a subject report that
131416 -     a particular record is missing. ref SDS 0 NM9K
131418 -      ..
131419 -     He asks how to clear this error. ref DRT 1 HP8O
131421 -      ..
131422 -     As noted below, in this case the problem is with the SDS code that
131423 -     was not configured correctly to support drawing a report for
131424 -     other Users, possibly to favor confidentiality instead; but, the
131425 -     code should do both.
131426 -
131427 -         [On 021110 made temporary correction to the code, and set
131428 -         action item to strengthen support for both confidentiality and
131429 -         collaboration. ref SDS 87 0001
131431 -      ..
131432 -     Clearing the error message requires getting pointers and records
131433 -     in sync.  In the case of a subject report there is a pointer in
131434 -     the subjects pointer data base, but there is no record for it, so
131435 -     the pointers for the missing record must be removed, as explained
131436 -     in the record on 021106 concerning the same problem that occurs
131437 -     occasionally with a Diary Summary. ref SDS 84 PPUP
131438 -
131439 -         [On 021110 review of the problem Gary reports today results in
131440 -         action item to modify error reporting so that frustration is
131441 -         avoided of not getting anything when some things are missing
131442 -         from a report. ref SDS 87 CV8H
131443 -
131444 -
131445 -
131446 -
131447 -
131448 -
1315 -

SUBJECTS
Subject Index Has Been Significantly Changed from SDS Stand  ds Where
Reports Subject Using SDS Organic Structures in Subject Index
Subject Report for Another User ID Report Missing Records
Writing a Letter Filling Out Doc Log Fields
Reports Fail When Record Missing
Johnson, Gary Reports Fail When Record Missing Should Complete Report
Writing a Letter

3009 -
301001 -  ..
301002 - Subject Reports For Another User Error Message that Record Missing
301003 -
301004 - Follow up ref SDS 84 VY5F, ref SDS 82 VY5F.
301005 -
301006 - Gary says...
301007 -
301008 -     I tried to search Rod's records for anything on Writing A Letter.
301009 -     There is a Subject Index entry, so I did F1 F9 to start a search,
301010 -     decremented the month, and typed Rod's ID over mine. ref DRT 1
301011 -     TY7F
301013 -  ..
301014 - This is a correct procedure - shows good progress on intuitive steps
301015 - to draw reports on another User's records for collaboration.
301016 -
301017 -     Need to support Gary on procedures for "Writing a Letter." and on
301018 -     linking, as shown in this record, and planned in the record on
301019 -     021013. ref SDS 65 I38S
301020 -
301021 -         [On 021119 training by phone reviewed procedures for writing
301022 -         and receiving letters. ref SDS 90 5G3K
301024 -          ..
301025 -         [On 021120 Gary reports progress learning and using links,
301026 -         ref SDS 91 SF6J, using procedures set out in the record on
301027 -         021120. ref SDS 91 OG9M
301028 -
301030 -  ..
301031 - There are many subjects on "Writing a Letter" so we need the actual
301032 - account in order to test, replicate and hopefully correct the problem
301033 - Gary reports today.
301035 -  ..
301036 - Did Gary open a session of SDS in my name, and used my SI, or if he
301037 - used only subjects in his SI. For example Gary's SI on my computer,
301038 - which is fairly recent, shows...
301039 -
301040 -
301041 -                         04 00074 AP 021010b
301042 -                         04 00074 10 05 06
301043 -                         04 00074 01 10 01 13
301044 -                         04 00074 02 13 02 12
301045 -                         04 00074 10 05 06 BCG
301046 -
301047 - ...so it helps get the particular account in order to run the same
301048 - report on another set of records to see what happens.
301050 -  ..
301051 - Gary continues...
301053 -      ..
301054 -     I got an error saying that a Diary record was missing.
301055 -
301056 -        October 9, 2002 09:21:28 PM        DIARY
301057 -
301058 -        Pointer: d: sd 08 GLJDY 04 02 41
301060 -      ..
301061 -     There is indeed no such record showing in the Diary. ref DRT 1
301062 -     E38I
301064 -  ..
301065 - This record is on my computer. ref SDS 60 0001
301067 -  ..
301068 - Since Gary has my records, let's see if I can replicate the error.
301070 -  ..
301071 - I ran subject reports during an SDS session under my name on each of
301072 - the above subjects, and they were all successful.
301074 -  ..
301075 - In particular a full file report on the account...
301076 -
301077 -
301078 -                         04 00074 10 05 06
301079 -
301080 -
301081 - ...displayed the record on 021009, ref SDS 60 0001, that caused the
301082 - error message reported by Gary.  The subject account...
301083 -
301084 -                         04 00074 10 05 06
301085 -
301086 -
301087 - ...was assigned to the record for some reason, since the substance of
301088 - the record does not seem to relate to training on writing a letter
301089 - using SDS, so I removed it.
301091 -  ..
301092 - Ran the same report using SDS under Gary's name and his User ID, and
301093 - got a report showing the record.
301095 -  ..
301096 - So, this does not replicate the error.
301098 -  ..
301099 - Ran the same report using SDS under Gary's name and substituting my
301100 - User ID, and got an error message report showing the record....
301101 -
301102 -               October 27, 2002 04:39:38 PM
301103 -
301104 -               Pointer: d: sd 08 GLJDY 04 02 43
301106 -  ..
301107 - There is a record for 021027 162938, and it is on the subject of
301108 - writing a letter. ref SDS 75 0001
301110 -  ..
301111 - This aligns somewhat with the experience reported by Gary, except the
301112 - missing record reported by Gary was for 021009, per above. ref SDS 0
301113 - NM9K  However, we both got the same confusing error message of a
301114 - pointer file for current user rather than the User for which the
301115 - report was run.
301117 -  ..
301118 - A situation can arise where a record exists, but does not have the
301119 - particular subject assigned in the record which is specified in the
301120 - report.  If the account had been assigned to the record at some point,
301121 - and later removed, and then a manual save was done, rather than use F2
301122 - that updates pointers, then the subject account is still in the
301123 - pointer file, and so needs to be removed, as explained in the record
301124 - on 021106. ref SDS 84 443G
301126 -  ..
301127 - Gary asks...
301128 -
301129 -     Next question is why was it searching GLJDY pointers anyway since
301130 -     the only user was 00101? ref DRT 1 G09I
301132 -  ..
301133 - That's what I would like to know?
301135 -  ..
301136 - Another important question is why is there no error message when the
301137 - same spec is run under an SDS session using my name, but does crash
301138 - when run under Gary's name?  These two situations should yield the
301139 - same result, not different results.  Possibly the User ID conflict
301140 - addresses this second question.
301142 -  ..
301143 - Ran report again with debug 100 on by pressing Ctrl F3.
301145 -  ..
301146 - This shows that the code is processing the following report spec...
301147 -
301148 -        User ID:  00101
301149 -
301150 -        Date
301151 -        From         To
301152 -        2002 09 11   2002 11 10     04 00074 10 05 06
301153 -
301154 -
301155 - ...and returning a correct list of records for User 00101, but when
301156 - it reads in the stuff to build the report, it is getting records for
301157 - User GLJDY, rather than 00101.
301158 -
301159 -    [On 021110 analysed code that runs subject reports and discovered
301160 -    an issue that relates to balancing confidentiality and
301161 -    collaboration; modified code temporarily and set action item to
301162 -    revise the code. ref SDS 87 0001
301163 -
301164 -
301165 -
301166 -
301167 -
301168 -
301169 -
301170 -
3012 -

SUBJECTS
Subject Index Assignments Reflect Organic Structure of Work and Life
Subject Index Access from Control Field in SDS Records Modifying Savi
Subjects Modifying Saving and Applying Organic Structures
Subject Index Modifying Saving Applying After Access from SDS Record

3606 -
360701 -  ..
360702 - Subjects Not Loading to Record When Accessed from Control Field
360703 -
360704 -
360705 - Gary reports....
360707 -      ..
360708 -     == Error Creating New Subject Index Level
360710 -      ..
360711 -     I used a control field to go to a specific location in the Subject
360712 -     Index, and then tried to create a new level under that topic. The
360713 -     resulting record format was incomplete. ref DRT 1 S35N
360715 -  ..
360716 - Not clear why this did not work.  It is a common practice done often
360717 - every day.  Need to get some more information or observe what steps
360718 - that led to this problem.
360720 -  ..
360721 - Gary continues...
360722 -
360723 -     I escaped from that and went back to the same place by navigating
360724 -     the Subject structure. This time the new level formatted
360725 -     correctly. ref DRT 1 SF6K
360727 -  ..
360728 - This record shows good patience and effort to work through issues.
360730 -  ..
360731 - Gary continues...
360732 -
360733 -     I am also not certain how the directory structure and the SI
360734 -     interact. What does the directory structure have to do with it?
360735 -     ref DRT 1 PF6O
360737 -  ..
360738 - Files are stored on the disk based on the subject structure.  For
360739 - example Gary's letter is identified by the organic structure....
360740 -
360741 -                04 00074
360743 -  ..
360744 - That is where his letter is stored on the disk, as shown in the
360745 - Reference field above. ref DRT 1 0001
360746 -
360747 -
360748 -
360749 -
3608 -

SUBJECTS
25.Bat and 001 DIR Command Different Format for Windows 98 Not Assemb
DIR /Z Command DOS4 /Z Switch Requires Revising SDS Code for Archivin
Pointers Global Using OTS for Sort, Select
Subject, 06112
Archive and Reports Use DIR /Z Switch for DOS4 Macros 001 and 0011 Bo
25.bat Global Pointers Archive SDS Records

4508 -
450901 -  ..
450902 - DOS4 Failing Using Switches for Compliance with MS DOS to Run SDS
450903 - Subject Reports and Archiving Failing Under 4DOS, Try MS DOS
450904 - 25.bat Archive Op and Subject Failing Under 4DOS, Might Try MS DOS
450905 -
450906 - Follow up ref SDS 84 YX7I, ref SDS 82 YX7I.
450907 -
450908 - Gary reports today...
450909 -
450910 -    == Using MSDOS Fixes Several Problems
450912 -     ..
450913 -    Changing to MSDOS also appears to have corrected the problems with
450914 -    searching the Subject Index. ref DRP 5 PQSS
450916 -  ..
450917 - Benefits using MS DOS are shown by Gary's success doing subject
450918 - reports, reported above. ref SDS 84 VY5F
450919 -
450920 -
450921 -
450922 -
450923 -
450924 -
450925 -
4510 -
4511 -

SUBJECTS
Ergonomic Keyboard for Efficient Use of SDS Gary Has Omnikey Keyboard
Keyboard Omnikey with Function Keys Optimized for SDS Need to Set Dip
Keyboard Function Keys Optimized for SDS Gary Has an Omnikey 5001 Key
Progress Gary Seems to be Making Excellent Headway Learning SDS

5106 -
5107 - 1654
510801 -  ..
510802 - Keyboard for Ergonomic Use of SDS Enables High Speed Production
510803 -
510804 - Follow up ref SDS 84 9Y7O, ref SDS 82 9Y7O.
510805 -
510806 - Gary reports progress getting the keyboard configured for SDS...
510807 -
510808 -    == Ergonomic Keyboard
510810 -     ..
510811 -    Don Stratt emailed me a test program that it rather nifty.
510813 -     ..
510814 -    He can take payment using PayPal, so that is easy. ref DRT 1 CQ9O
510816 -     ..
510817 -    I need to have Joyce help with the DIP switches and test to see if
510818 -    we can get the keys relocated. If that works then we can get the
510819 -    key caps changed so that the legends reflect the locations.
510820 -    ref DRT 1 ZQ4L
510821 -
510822 -      [On 021227 Gary reports using other programs for editing
510823 -      indicating the keyboard is still pending. ref SDS 94 874H
510824 -
510825 -
510826 -
5109 -
5110 -

SUBJECTS
Keynote Program Tracking Progress
Using SDS and Using Keynote to Report Progress on Setup and Learning
SDS Learning Capture Record with KeyNote
Plan Perform Report SDS New Way Working Augment Intelligence Thinking
Editing Linking Easier than SDS Using KeyNote to Track History
SDS Program Learning Format Conventions Takes Time
Flexible Structure Harder to Learn Easier to Make Mistakes than Tradi
Learn SDS Need Time to Understand Integrated Functions Features Compl
Management Complex Integrated Craft Learning SDS Takes More than 20 M
Learn 20 Minutes Average User Wants Functionality for Average Results
Above Average User Cares About Above Average Results Will Invest More
Above Average Users Create Intelligence Improves Performance for Aver
Teaching Com Manager Helps People Learn SDS on the Job
Johnson, Gary 2 Months Learn SDS Flexible Structures Com Manager Teac
Attitude Ignorance Fear Denial Silence POIMS Things We Don't Talk Abo
Learn Invest Time Above Average User Cares About Above Average Result
New Way Working Augment Intellignece Thinking Through Writing Concurr
CaseMap 4 Software for Lawyers to Manages Lawsuits Supports Chronolog
SDS New Way of Working Using Eight (8) Steps to Implement SDS Plan Pe

A521 -
A52201 -  ..
A52202 - New Way of Working Track Progress Concurrently, Plan Perform Report
A52203 -
A52204 - Follow up ref SDS 56 5Z4P.
A52205 -
A52206 - Gary reports today...
A52207 -
A52208 -    == Starting to Use SDS Concurrent With Work
A52210 -     ..
A52211 -    I am starting to use SDS concurrently with working to a greater
A52212 -    extent. I am not completely there yet as I mostly interleave SDS
A52213 -    with work, but at least I am now (mostly) creating a record
A52214 -    concurrently with doing the work. ref DRT 1 P45I
A52216 -     ..
A52217 -    Next is to work more in the direction of using planning in SDS to
A52218 -    drive the work. ref DRT 1 556F
A52220 -  ..
A52221 - This shows substantial progress on using SDS for the design objective
A52222 - to use a "plan, perform, report" process.  Gary's earlier records
A52223 - on...
A52224 -
A52225 -   1.  Keynote to report problems using SDS.... 021004, ref SDS 57 EZ8L
A52226 -   2.  Using Keynote to report work............ 021009, ref SDS 61 0001
A52227 -   3.  Develop Keynote for categorization...... 021011, ref SDS 64 LS5L
A52228 -   4.  Tracking work in Keynote................ 021016, ref SDS 67 0001
A52229 -   5.  History entered after-the-fact rather
A52230 -       than concurrently....................... 021022, ref SDS 70 0001
A52231 -   6.  KeyNote to manage subjects.............. 021022, ref SDS 71 PU5O
A52232 -   7.  KeyNote integrate with SDS (line 0503).. 021101, ref SDS 77 0001
A52233 -   8.  KeyNote seems easier to link............ 021102, ref SDS 78 F85O
A52235 -  ..
A52236 - ...demonstrate that weakness of SDS code hinders transformation from
A52237 - traditional work methods that report organizational memory (work
A52238 - history) after the fact, apply the SDS design for concurrent discovery
A52239 - to augment intelligence, as explained in POIMS, ref OF 1 6649, by
A52240 - enabling people to think and plan through writing, also explained in
A52241 - POIMS. ref OF 1 3742
A52243 -  ..
A52244 - Gary's attitude being persistent studying SDS, despite frustrations of
A52245 - mistakes and initial confusion that occur while gaining experience
A52246 - using a new way of working with flexible structure, is remarkable and
A52247 - helpful, even for early adopters who expect to invest more time for
A52248 - pilot testing than the average customer.  This attitude aligns with
A52249 - Andy Grove's point in his book "Only the Paranoid Survive" saying that
A52250 - people have to "study" to prepare for new realities that require a
A52251 - stronger set of skills, reported on 980307. ref SDS 13 1657 and
A52252 - ref SDS 13 3495
A52253 -
A52254 -     [On 021120 Gary reports progress understanding how to make new
A52255 -     tasks, and linking daily work to relevant history. ref SDS 91 SF6J
A52257 -  ..
A52258 - Gary's ability to work through problems, and continue, rather than
A52259 - give up, as so many are doing these days, e.g., reported on 020812,
A52260 - ref SDS 53 659F, indicates that people need about 2 months to gain
A52261 - enough confidence with SDS to use of all the features.  This reflects
A52262 - the fact that, unlike other programs, a lot of SDS features need to be
A52263 - used regularly in order for productivity to rise.  If people only use
A52264 - the Schedule, there are better products, including using a vest pocket
A52265 - calendar or a Palm Pilot.  There are better journal programs, and
A52266 - better programs for contacts and for wordprocessing to do outlining
A52267 - and write a letter, report or specification.  Gary has noted there are
A52268 - many programs, like KeyNote and Microsoft Word, that have better
A52269 - editing features than SDS.  This makes the advantage of SDS a little
A52270 - elusive until people gain experience using all of the features
A52271 - together and discover that integrating time and information has big
A52272 - benefits, as Morris pointed out on 010924. ref SDS 47 XT5F  This takes
A52273 - about 2 months, and so Gary is getting close to this breakthrough.
A52274 -
A52275 -
A52276 -
A52277 -
A52278 -
A523 -

SUBJECTS
How Best to Communicate on Learning SDS - Since SDS Handles Any Commu
Collaboration Communicate Best Practices on Technical Support Learnin
Communication Best Practices Management Traceability Original Sources

A80501 -  ..
A80502 - Any Communication Method Effective Supported by SDS
A80503 - SDS Aids and Collaboration Best Practices with New Practices
A80504 - Gary's Communication Methods Effective Supported by SDS Record
A80505 -
A80506 -
A80507 - Gary observes and asks in his first letter today...
A80508 -
A80509 -    How Best to Communicate Problems to Rod....
A80511 -     ..
A80512 -    I am developing quite a list of SDS problems and operational issues
A80513 -    that I need to make sure get onto Rod's radar. ref DRT 1 Q46H
A80515 -  ..
A80516 - Issues Gary raises are being tracked in SDS, as shown by this record,
A80517 - and the list of pending action items in another record for today.
A80518 - ref SDS 86 0001
A80520 -  ..
A80521 - Gary continues...
A80522 -
A80523 -    Not all of them need immediate attention, but the entire idea of
A80524 -    recording my experiences is to uncover these sorts of issues.
A80525 -    ref DRT 1 I53F
A80527 -  ..
A80528 - SDS is designed to help people capture a greater share of daily
A80529 - experience, and add "intelligence" using eight (8) steps set out in
A80530 - the record on 001219. ref SDS 44 4W4L  As Gary's confidence using SDS
A80531 - grows, the record of daily work experience will become more helpful.
A80532 - In the meantime, any communication method is adequate for bringing up
A80533 - issues that need attention, as seen by this record.
A80535 -  ..
A80536 - Gary continues...
A80537 -
A80538 -    Some of these are places where my understanding is inadequate
A80539 -    either of the operation or of the philosophy behind SDS.
A80540 -    ref DRT 1 U53J
A80541 -
A80542 -    Others are minor issues of consistency, correctness of
A80543 -    documentation, appearance, etc. ref DRT 1 R53N
A80545 -     ..
A80546 -    There are still others, however that indicate either bugs or design
A80547 -    issues with SDS. ref DRT 1 164H
A80549 -     ..
A80550 -    In any case, the idea is to capture all of this and get it into a
A80551 -    form where the issues can be resolved systematically. ref DRT 1
A80552 -    864L
A80554 -     ..
A80555 -    == Question
A80557 -     ..
A80558 -    Is this format helpful in communicating my experiences with
A80559 -    SDS and the issues I find? Is there a better way to do it?
A80561 -     ..
A80562 -    I want to be certain that I convey anything that I run into so that
A80563 -    it can bet recorded for later review. ref DRT 1 H65F
A80565 -  ..
A80566 - The format Gary has been using illustrated by his several letters
A80567 - today is very helpful and effective for communication and
A80568 - collaboration.
A80570 -  ..
A80571 - Review on 950721 of ISO requirements shows that continual learning,
A80572 - ref SDS 6 2846, and traceability to original sources are best
A80573 - practices for management communication and collaboration. ref SDS 6
A80574 - 1740
A80576 -  ..
A80577 - SDS enables a new way of working to strengthen communication "best
A80578 - practices" with new practices.  Gary's progress capturing work history
A80579 - concurrent with doing the work, per above, ref SDS 0 5Z4P, will soon
A80580 - enable communication simply by transmitting SDS records.  Other
A80581 - methods like email, wordprocessing and KeyNote are very effective, as
A80582 - seen by this record, since SDS can support any method that people
A80583 - prefer.
A80585 -  ..
A80586 - We will be experimenting to develop protocols that leverage SDS when
A80587 - many people are using the program.
A80588 -
A80589 -
A80590 -
A80591 -
A80592 -
A806 -

SUBJECTS
Getting Things Done by David Allen
Action Items Listed in Reference Field of Schedule Analysis and Adjus
Get Things Done David Allen System Needs SDS for Context of Objective
Integrate Objectives Requirements Commitments
Management Consulting Help Business Build Strong Road to Success
Workflow Improvement through Personal Coaching
Management Consulting Training Coaching Improves Ability to Get Thing
Culture Knowledge Foster Communication Link Cite SDS POIMS for Founda
Getting Things Done Technography Meeting Support Help Grow Culture of
Johnson, Gary Cites Getting Things Done Technography Help Grow Cultur
Allen, David Getting Things Done Software Program Has Ideas and Capab

AK13 -
AK1401 -  ..
AK1402 - Action Items Managed by SDS Help Track Progress on Commitments
AK1403 - Visibility Expands Span of Attention Avoids Meaning Drift
AK1404 - Getting Things by Integrating Objectives Requirements Commitments
AK1405 -
AK1406 - Received ref DRT 2 0001 from Gary explaining a management approach he
AK1407 - has encountered; he says....
AK1408 -
AK1409 -    Getting Things Done is the name of an approach to task management
AK1410 -    created by David Allen www.davidco.com
AK1411 -
AK1412 -         http://www.davidco.com/
AK1414 -  ..
AK1415 - This location describes David Allen's work....
AK1416 -
AK1417 -
AK1418 -         http://www.davidco.com/who_we_are.php
AK1419 -
AK1420 -
AK1421 -      The David Allen Company is a professional training, coaching, and
AK1422 -      management consulting organization, based in Ojai, California,
AK1423 -      USA. Its purpose is to improve the quality of life by providing
AK1424 -      the world's best information, education, and products that
AK1425 -      enhance personal and interactive productivity.
AK1427 -  ..
AK1428 - David Allen Company has a software product....
AK1429 -
AK1430 -                        Getting Things Done
AK1431 -
AK1432 - ...that sells for $49.95, explained as...
AK1433 -
AK1434 -         Now you can put David Allen's Getting Things Done methodology
AK1435 -         to work for you in Microsoft Outlook to help you transform
AK1436 -         your mountain of email into a stream of success.
AK1438 -  ..
AK1439 - "Getting Things Done" software to make Microsoft Outlook productive
AK1440 - aligns with Steve Balmer's goals for Microsoft reported on 010510.
AK1441 - ref SDS 45 YG5K  David Allen Company products and services sound
AK1442 - similar to Techography support for "co-working" to facilitate meetings
AK1443 - and improve productivity by helping people use software, reviewed on
AK1444 - 000120, ref SDS 37 2300
AK1446 -  ..
AK1447 - Gary cited Technography's products and services in a letter on 011222.
AK1448 - ref SDS 49 AV4J  There may have been information today indicating that
AK1449 - Technography has added features that are like SDS.  The record on ths
AK1450 - is unclear.
AK1452 -  ..
AK1453 - People, like the folks at David Allen Company and Technography who are
AK1454 - working on creating features that are common to SDS, are, in turn, an
AK1455 - enabling force to transform culture toward awareness of SDS support
AK1456 - for a new way of working, explained in POIMS, ref OF 1 6649, and
AK1457 - implemented by eight (8) steps set out in the record on 001219.
AK1458 - ref SDS 44 4W4L  This reduces the period of 50 years required for a
AK1459 - new way of working to become accepted, reported by Gary on 011210.
AK1460 - ref SDS 48 R66K
AK1461 -
AK1462 -     [On 021118 Gary submits information on Pathmaker. ref SDS 89 ET9F
AK1464 -      ..
AK1465 -     [On 021118 Gary submits information on Information Mapping.
AK1466 -     ref SDS 89 WE5L
AK1468 -      ..
AK1469 -     [On 021119 Gary explains Information Mapping supports organizing
AK1470 -     the record. ref SDS 90 WE5L
AK1472 -      ..
AK1473 -     [On 021126 Gary cites CaseMap 4 for supporting SDS features.
AK1474 -     ref SDS 93 91WP
AK1476 -      ..
AK1477 -     [On 021123 Gary reviews David Allen's work on project management
AK1478 -     in relation to SDS capabilities. ref SDS 92 0001
AK1480 -      ..
AK1481 -     [On 030413 Gary cites David Allen on defining a "project" for ways
AK1482 -     to strengthen SDS. ref SDS 95 007P
AK1484 -  ..
AK1485 - SDS enables consistent use of good management advocated by David
AK1486 - Allen, Technography, Drucker, Covey and others down through the ages.
AK1487 - When consultants leave the scene, human biology drives people back to
AK1488 - bad management, reported on 921205. ref SDS 2 6633  More recently on
AK1489 - 010908 Jack Park reported overwhelming tendency to fall back on bad
AK1490 - management. ref SDS 46 UV4H  SDS makes good management fast and easy,
AK1491 - as Gary reported on 020618, ref SDS 51 MU6H, so that more people can
AK1492 - sustain using good practices learned from consultants and at seminars.
AK1493 - More people using good practices more often reduces the rate of
AK1494 - decline toward failure, explained on 970707. ref SDS 10 0108  Fewer
AK1495 - problems increases productivity, earnings and stock prices, reported
AK1496 - on 001207. ref SDS 43 V54M
AK1498 -  ..
AK1499 - Gary continues...
AK1500 -
AK1501 -    The essence of this approach appears to be getting *all* of your
AK1502 -    commitments into a database where they can be manipulated and
AK1503 -    accessed. This results in being able to stop worrying about them,
AK1504 -    confident that they will all be managed. ref DRT 2 X26F
AK1506 -  ..
AK1507 - Managing commitments is important.  Good management integrates action
AK1508 - on objectives, requirements and commitments.  Tracking commitments
AK1509 - alone is not effective.  SDS uses organic structures in the subject
AK1510 - index and other features to manage work in the context of objectives,
AK1511 - requirements and commitments.  Integration adds value by getting
AK1512 - things done on time and within budget.  USACE reported ROI of 10:1
AK1513 - using SDS for Com Metrics. ref DRP 2 0001  Advantages of integrated
AK1514 - management were reported by Kerzner on 950202. ref SDS 5 6M7L
AK1516 -  ..
AK1517 - Gary's experience with SDS and Getting Things Done will yield valuable
AK1518 - ideas.
AK1520 -  ..
AK1521 - Gary continues...
AK1522 -
AK1523 -    It also depends on selective visibility of projects so that you are
AK1524 -    not always looking at everything. It recognizes that not all of the
AK1525 -    projects in your life are active all the time, which many other
AK1526 -    systems do not do. ref DRT 2 8L7F
AK1528 -  ..
AK1529 - POIMS explains a concept of "controlled visibility, ref OF 1 1103,
AK1530 - that supports "Command and Control of the Record," ref OF 1 1113, to
AK1531 - expand span of attention, which sound similar to the idea behind
AK1532 - "Getting Things Done."
AK1534 -  ..
AK1535 - Gary continues...
AK1536 -
AK1537 -    My CanDo list idea that presents only tasks that can be done
AK1538 -    immediately because there are no required tasks before it would be
AK1539 -    a nice addition to this. ref DRT 2 008G
AK1540 -
AK1541 -    GTD does insist that tasks get broken down into atomic actions that
AK1542 -    can be completed. If a active task continues to get postponed, it
AK1543 -    gets examined for the possibility that it really contains multiple
AK1544 -    steps, and is broke down if needed. It can also be discarded if you
AK1545 -    decide that you simply have no intention of doing it. This may be
AK1546 -    the most valuable piece of technology that GTD has to contribute to
AK1547 -    SDS. ref DRT 2 XL7O
AK1549 -     ..
AK1550 -    I don't yet see any easy way that SDS can provide this multiple
AK1551 -    visibility. It should be possibly to establish Diary records as
AK1552 -    project records and use a subject search to locate them all, but
AK1553 -    that is going to be a kludge without a more sophisticated search (A
AK1554 -    but not B). ref DRT 2 004I
AK1556 -  ..
AK1557 - "Atomic actions" sound like SDS support for managing the microcosm of
AK1558 - daily work through organic structures supported by SDS, explained in
AK1559 - POIMS. ref OF 1 SV5N
AK1561 -  ..
AK1562 - Multiple visibility in SDS may be seen in part from the record of
AK1563 - commitments and tasks tracked on the following projects...
AK1564 -
AK1565 -     • Oakland Harbor project.................. 961126, ref SDS 41 0001
AK1567 -     • Dynamic Alternatives Pilot Test SDS..... 021109,  ..
AK1570 - These reports take only a few seconds to assemble the record over
AK1571 - days, weeks, years and decades.
AK1573 -  ..
AK1574 - SDS positions issues in context with an audit trail for traceability
AK1575 - to original sources.  Tasks can be broken down into smaller steps
AK1576 - using SDS organic structures in the Subject Index, that can be tracked
AK1577 - separately as part of a "work plan," schedule or WBS (see, for
AK1578 - example, recent work on 021105. ref SDS 82 238O)
AK1580 -  ..
AK1581 - On 970107 a contractor on the Oakland Harbor project, who initially
AK1582 - did not see how SDS improved getting things done, found that SDS is
AK1583 - effective. ref SDS 9 4953  On 970308 USACE reported SDS enables a
AK1584 - system of Communication Metrics that improves management, ref DRP 1
AK1585 - 6172, and singled out action items as a strong part of SDS support.
AK1586 - ref DRP 1 3773  The Corps also noted that advantages of SDS are hard
AK1587 - to see at first, ref DRP 1 0797, as Gary points out in his letter
AK1588 - today.
AK1590 -  ..
AK1591 - Gary continues....
AK1592 -
AK1593 -    It may be possible to change status by changing the subjects.
AK1594 -    Suppose that the status were used as the last part of the subject
AK1595 -    indicator? Then changing status would be as simple as replacing it
AK1596 -    in the control field and updating the record. ref DRT 2 6M9H
AK1598 -     ..
AK1599 -    I need to speak with Rod about this as well as whether it is
AK1600 -    possible to have SDS do a subject search for just a prefix of the
AK1601 -    subject or whether I need to include the project and the item in
AK1602 -    the subjects (which could be done). ref DRT 2 006J
AK1604 -  ..
AK1605 - Gary makes a good point asking how to apply organic structures in the
AK1606 - subject index.  Expanding or narrowing the scope of reports is fast
AK1607 - and easy using SDS simply by pealing off letters in the account
AK1608 - structure.
AK1610 -  ..
AK1611 - Gary asks...
AK1612 -
AK1613 -    Still, it would be nice to find all records for a project not
AK1614 -    marked Done. ref DRT 2 NM4I
AK1615 -
AK1616 -    At the moment, I am adding planning records as I think of other
AK1617 -    things that I am forgetting. This is working so far, but I think
AK1618 -    that I will soon get a list that is longer than convenient. When
AK1619 -    today's schedule exceeds a screen, I will start having difficulty
AK1620 -    with it. ref DRT 2 UM4L
AK1622 -  ..
AK1623 - Examples of SDS work product that may meet some of Gary's objectives
AK1624 - are listed above. ref SDS 0 ND5J
AK1625 -
AK1626 -
AK1627 -
AK1628 -
AK1629 -
AK1630 -
AK1631 -
AK1632 -
AK1633 -
AK1634 -
AK1635 -
AK17 -