CONTACTS
SUBJECTS
SDS Windows Version Data Structures Begin Development Determine Scop
1503 -
1503 - ..
1504 - Summary/Objective
1505 -
150501 - Follow up ref SDS 10 3280, ref SDS 28 QU61.
150502 -
150503 - Excellent progress today implementing Gary's product outline received
150504 - a few weeks ago. ref SDS 0 645L Morris proposed good ideas on version
150505 - control, ref SDS 0 6I4N, and scheduling. ref SDS 0 XI6S He plans to
150506 - submit design ideas leading to specifications for comment. ref SDS 0
150507 - JR97 Jack Park submitted a letter with interesting perspective, which
150508 - supports efforts to request his participation. ref SDS 0 RW5I Getting
150509 - experience using SDS will expedite building a Windows version, and
150510 - getting younger people involved will help ensure continuity of
150511 - transformation. ref SDS 0 RW8H
150512 -
150513 - [On 071106 meeting continue work on SDS features; planning to
150514 - start Windows version by creating a new Contacts system.
150515 - ref SDS 37 0001
150516 -
150517 -
150518 -
150519 -
150520 -
150522 - ..
1506 -
1507 -
1508 - Background
1509 -
150901 - On 040503 Morris did not have time to work on SDS upgrade due to heavy
150902 - schedule at work, teaching, family, and community involvement.
150903 - ref SDS 28 QU50 Morris retired from Intel in January. His schedule
150904 - over the past 9 months has settled, possibly leaving time for SDS
150905 - work.
150907 - ..
150908 - Work leading up to launch efforts today includes...
150909 -
150910 - 1. Case study prior considerations on creating SDS Windows version
150911 - beginning on 900303 is shown in the record on 040505,
150912 - ref SDS 28 QU61, and cites Gary's letter to Morris on 040404.
150913 - ref SDS 25 PRWV
150915 - ..
150916 - 2. Assembly language programming to expand SDS memory with Medit
150917 - upgrade for 32-bit Windows applications was researched by Gary
150918 - in his letter on 040503. ref SDS 28 QU8K At that time, Morris
150919 - indicated this can be accomplished, but his schedule working at
150920 - Intel and teaching graduate engineering did not leave enough
150921 - time to perform the work. ref SDS 28 QU50 Following
150922 - retirement from Intel, Morris has expanded teaching work load
150923 - and other activities; may have more time now, but doing the
150924 - assembly update will still be a big job.
150925 -
150926 - [On 081104 Morris starting editor for SDS using Java
150927 - rather than C or assembly, ref SDS 43 2W6I, which
150928 - presents issues of scope, functionality, and
150929 - longevity. ref SDS 43 VO3P
150931 - ..
150932 - [On 081123 Gary's letter to Morris cites merit
150933 - building a modern 64-bit version of the current SDS
150934 - program without trying to understand it all that much.
150935 - ref SDS 44 KH5G
150937 - ..
150938 - 3. SDS current design is shown in a schematic.
150939 -
150940 - a. General structure. ref OF 8 PL7I
150942 - ..
150943 - b. Data structures and flow. ref OF 8 8558
150945 - ..
150946 - c. SDS record fields, and Control structures. ref OF 8 0788
150947 -
150948 - [...below, objectives to integrate a critical mass of
150949 - complementary features and functions. ref SDS 0 1998
150951 - ..
150952 - 4. SDS new design was proposed today by Morris to create SDS
150953 - without the Medit macro code, and instead program a de novo
150954 - Windows version using C programming language with new data
150955 - structures developed in past few weeks, discussed further
150956 - below. ref SDS 0 JQ88 Background Morris trying to develop C
150957 - version of SDS shows...
150958 -
150959 - a. Morris' letter on 950221 submitted an outline of scope and
150960 - features for SDS. ref SDS 6 JC7O
150961 -
150962 - [On 080206 Morris plans to substitute a commercial
150963 - editor to modernize SDS, ref SDS 41 HE6N; improves
150964 - writing with fewer function keys and better formatting
150965 - that flows text to the right margin based on adusting
150966 - the screen size, ref SDS 41 ND8N; this eliminates
150967 - flexible structure that is not in much demand by
150968 - customers. ref SDS 41 QV4O
150970 - ..
150971 - b. Gary updated Morris' 950221 outline of SDS scope and
150972 - features in an email dated 070823 which is incorporated
150973 - into his record on the same date. ref SDS 35 J04M
150974 -
150975 - [...below, objectives to integrate a critical mass of
150976 - complementary features and functions. ref SDS 0 1998
150978 - ..
150979 - [...below, Gary's list of SDS features is listed.
150980 - ref SDS 0 GU4K
150982 - ..
150983 - [On 071222 Morris requests again the list of SDS
150984 - features, because the list today cannot be found in
150985 - his records. ref SDS 39 3V35
150987 - ..
150988 - [On 071222 Gary recalled having submitted a list of
150989 - features for SDS. ref SDS 39 LX8M
150991 - ..
150992 - [On 071222 Gary explains SDS records are identified by
150993 - granular structure of time, that complements granular
150994 - addressability and indexing comprising 3 dimensional
150995 - axis of Knowledge Space. ref SDS 39 PA6P
150996 -
150997 -
150998 -
150999 -
1510 -
SUBJECTS
Document Management Version Control Multi-user System Software Data
4403 -
4404 - Progress
440501 - ..
440502 - Morris discussed today...
440503 -
440504 - 1. Version Control Record Integrity Lock Down
440505 - Deliberative Analysis Reduce Mistakes Increase Innovation
440506 - Refine Accuracy Expand Span of Attention over Days Weeks Months
440507 -
440508 - Should SDS records be "locked down" for integrity purposes in
440509 - the case of litigation?
440511 - ..
440512 - Backing up each day is currently built into the SDS launch
440513 - process. Archiving daily backups monthly for 5 - 10 years
440514 - provides a running history of record formation
440516 - ..
440517 - Morris cited experience at Intel using "lock down" to prevent
440518 - people from padding the record with incorrect representations,
440519 - which he feels impedes using SDS records for evidence in
440520 - litigation.
440522 - ..
440523 - Morris proposed that once a record is "submitted," then further
440524 - analysis should be done in a separate record. He indicated
440525 - that forced "lock down" to prevent editing archived diary
440526 - records would further avoid "broken links" if a record is
440527 - revised by, for example, deleting a paragraph with an anchor,
440528 - or merging paragraphs.
440530 - ..
440531 - While not discussed today, Jack Park presented thoughtful
440532 - feedback a few days ago on 070823, with a copy to Morris and
440533 - Gary saying...
440534 -
440535 - And speaking of links: what's the point of putting up all
440536 - that gook about SDS, New World Order, Day in the life, etc,
440537 - if it's full of broken links? How do you expect to sell
440538 - anything if the product you want people to buy isn't
440539 - working well?
440541 - ..
440542 - In that case, Jack did not call nor otherwise identify any
440543 - specific broken link. Calling to provide close order support
440544 - for corrections is common, especially today with the ubiquitous
440545 - cell phone. Absent specific guidance, spot checking...
440546 -
440547 - http://www/Welchco.com
440548 -
440549 - ...found no broken links, which frustrated correction; so
440550 - additional feedback would be helpful to refine accuracy. In
440551 - any case, integrity of links is an important factor in
440552 - usefulness of the record.
440554 - ..
440555 - During the meeting today, we reviewed the record for the past
440556 - 20 years creating SDS records. Occassionally, links "break,"
440557 - but this is not a significant drag on productivity that
440558 - justifies "locking down" SDS records. In the same way that
440559 - brakes fail, turn signals "break," but nobody suggests "locking
440560 - down" the car in the garage. People repair brakes on cars;
440561 - repairing broken links in SDS records is must faster and
440562 - easier.
440564 - ..
440565 - Version control was a big "snag" that prevented progress on
440566 - OHS/DKR by Eric Armstrong reported in his letter received on
440567 - 001106. ref SDS 16 FO88 He explained that design for Knowledge
440568 - Management presents big challenges. ref SDS 16 FO53
440570 - ..
440571 - "Lock down" of SDS records for use in dispute resolution
440572 - conflicts with the purpose of SDS to avoid disputes by
440573 - empowering people to work quickly and accurately for saving
440574 - lives, time, and money. (see POIMS, ref OF 4 6D9K) These
440575 - "savings" occur through the "plan, perform, report" process of
440576 - "deliberative analysis" explained in POIMS, ref OF 5 2300, that
440577 - leverages cognition for "working intelligently," also,
440578 - explained in POIMS. ref OF 3 1X6G Deliberation using 8-steps
440579 - of Communication Metrics for "thinking through writing,"
440580 - ref OF 6 685K, expands spontaneous impressions of the moment to
440581 - discover correlations, implications, and nuance that are hidden
440582 - by numerous forms of "lock down" until disaster strikes.
440583 - Concurrent discovery continually makes sense of complexity in
440584 - time to take effective action prevents disaster, see NWO.
440585 - ref OF 11 1780
440586 -
440587 -
4406 -
SUBJECTS
Lincoln's Sword The Presidency and the Power of Words Douglas L Wils
Deliberative Analysis Intelligence Briefing Remind Clarify Scope Pro
4904 -
490501 - ..
490502 - Sensemaking Concurrent Discovery Connect Cause Effect Knowledge
490503 - Writing Style Lincoln Deliberation 3x5 Card Idea Management
490504 - 3x5 Cards Capture Ideas Deliberative Analysis Writing Style
490505 - Lincoln Thinking Through Writing Deliberative Analysis
490506 -
490507 - Thinking through writing explained in POIMS, ref OF 7 3742,
490508 - leverages intelligence with deliberative analysis supported by
490509 - the SDS "report" process described in POIMS. ref OF 5 2300
490510 - Regularly capturing information and ideas in written text
490511 - enables constructing connections that grow understanding of
490512 - expanding complexity. The power of words to construct sensible
490513 - views supports the power of knowledge for connecting the dots
490514 - of cause and effect that control the future, and based on the
490515 - "locality principle," reviewed on 040312. ref SDS 24 YH4G
490517 - ..
490518 - Technology makes this work faster and easier with 8-steps for
490519 - Communication Metrics. The SDS process of capturing and
490520 - organizing the record has roots in traditional 3x5 card filing
490521 - and records management, noted by Morris on 950223. ref SDS 7
490522 - 9933 Background on using records management to get things done
490523 - correctly leading to a modern practice of Knowledge Management
490524 - is shown in a case study on 070126. ref SDS 32 QC8L
490526 - ..
490527 - Abraham Lincoln developed a practice of making sense of complex
490528 - issues by making many preliminary notes, and assembled them in
490529 - different ways to construct particular letters, speeches,
490530 - reports, articles, etc., which he further continually refined
490531 - many, many times, even after the fact in order to craft useful
490532 - understandings for taking effective action.
490533 -
490534 - International Herald Tribune
490536 - ..
490537 - Book Review:
490539 - ..
490540 - Lincoln's Sword: The Presidency and the Power of Words
490541 - (343 pages, $26.95. Alfred A. Knopf)
490542 -
490543 - http://www.iht.com/articles/2006/12/20/features/bookthu.php
490545 - ..
490546 - December 20, 2006
490548 - ..
490549 - Reviewed by Michiko Kakutani
490551 - ..
490552 - In his new book, Douglas L Wilson - co-director of the
490553 - Lincoln Studies Center at Knox College in Galesburg,
490554 - Illinois, and the author of "Honor's Voice," a critically
490555 - acclaimed study of the younger Lincoln - looks at the role
490556 - that writing played in Lincoln's presidency, focusing on
490557 - the circumstances that shaped particular documents and the
490558 - evolution of those documents through the president's
490559 - meticulous process of revision.
490561 - ..
490562 - He notes that Lincoln often scribbled down ideas on scraps
490563 - of paper and that he was a skilled reviser of his own work.
490565 - ..
490566 - Another review of Wilson's book says...
490567 -
490568 - Powells.com
490569 -
490570 - Robert Lincoln recalled his father as 'a very deliberate
490571 - writer, anything but rapid.' It is Lincoln's very
490572 - deliberate, painstaking, multi-draft process that Wilson
490573 - seeks to document. Readers deeply immersed in Lincoln
490574 - trivia will find Wilson's intricate forensics inviting.
490575 - Others, nurturing a more casual interest, will fast find
490576 - themselves drowned in details of subtle variations between
490577 - drafts of Lincoln's various major addresses, all so
490578 - carefully dissected in order to reveal the mechanical,
490579 - trial-and-error process that lay behind Lincoln's soaring
490580 - eloquence." Publishers Weekly (Copyright Reed Business
490581 - Information, Inc.)
490583 - ..
490584 - http://www.powells.com/cgi-bin/biblio?isbn=9781400040391&atch=h&atchi=144027486
490585 -
490586 -
490587 -
4906 -
SUBJECTS
Document Management Version Control Data Base Management Record Inte
7803 -
780401 - ..
780402 - Proactive Management Requires Efficient Timely Deliberation
780403 -
780404 - "Lock down" would prevent refining and clarifying chronology,
780405 - context, and connections to increase understanding, i.e.,
780406 - "sensemaking," mentioned by Jack Park on 040622, ref SDS 29
780407 - FM5W, that guides timely, accurate performance of the work. We
780408 - are not trying to win a lawsuit 3 - 5 years down the road. We
780409 - are trying to discover problems in time to take effective
780410 - action that avoids escalation into major mistakes, conflicts,
780411 - and crisis that cause loss of lives, time, and money, citied by
780412 - Morris on 921127. ref SDS 5 0674
780414 - ..
780415 - SDS records are not a "secret" that someone suddenly produces
780416 - in court to prove xyz. The record is routinely distributed to
780417 - provide notice and obtain feedback that continually refines
780418 - accuracy understanding cause and effect, i.e., "knowledge,"
780419 - that guides daily work. noted by Peirce, reviewed on 000515.
780420 - ref SDS 14 7380 If subsequent editing materially changes
780421 - original representations which misleads others causing damage,
780422 - this is abundantly clear from records produced by others.
780424 - ..
780425 - About .1% of daily work reaches judicial review. Preventing
780426 - efficient intelligence support for 99.9% of the work in order
780427 - to maybe improve chances of success on .1% defines the notion
780428 - of counterproductive. This record for example; the record
780429 - fixing the garbage disposal, mowing the lawn, going to the
780430 - movies, writing a letter, visiting mom, configuring the
780431 - computer, why bother with multiple records in order to
780432 - understand the story sufficiently to get things done correctly,
780433 - and plan follow up comprehensively.
780435 - ..
780436 - Morris seemed to indicate today that the practice of notice has
780437 - fallen out of fashion. Regardless of fashion that ebbs and
780438 - flows, notice of alignment manifests the locality principle
780439 - intrinsic to nature, reported on 040312, ref SDS 24 YH4G, and
780440 - to Western jurisprudence, noted in NWO. ref OF 12 P69F
780442 - ..
780443 - Kaiser uses "lock down" procedures for an electronic medical
780444 - chart to manage patient history, reported on 061208.
780445 - ref SDS 31 N54K This has compounded errors transforming small
780446 - problems into continual bumbling leading to stress, conflict,
780447 - crisis, and chaos, also, noted on 061208, ref SDS 31 FE4I, see
780448 - as well case study on 040416. ref SDS 27 GN7J
780450 - ..
780451 - Consideration was therefore given today during the meeting to
780452 - balance objectives of SDS to build, grow, and refine
780453 - understanding in order to improve the work and help people get
780454 - things done with the power of knowledge for controlling the
780455 - future. Often creating a record takes several days, sometimes
780456 - a week or more in the case of complex issues. For example the
780457 - record on 070524 meeting at UCSF, ref SDS 33 0001, has 10,000
780458 - words, 432 subjects, 33 record segments, 433 links, and 82
780459 - headings; another record the next day at Kaiser on 070525,
780460 - ref SDS 34 0001, has, also, about 10K words, 454 subjects, 30
780461 - segments, 435 links, and 71 headings. This work cannot be done
780462 - in a day.
780463 -
780464 -
780465 -
7805 -
SUBJECTS
Control Field Subject Index Context Management Big Picture Avoid Pay
A603 -
A60401 - ..
A60402 - 2. Control Fields Accounting and Billings (Functions) and Subjects
A60403 -
A60404 - Morris spent a good deal of time today asking about Control
A60405 - Fields. He asked how SDS supports accounting and billings, and
A60406 - observed the secondary Control Field structure that enables
A60407 - managing accounts receivable and payable, in addition to
A60408 - supporting payroll and billing systems.
A60410 - ..
A60411 - SDS per se does not perform accounting tasks. It provides a
A60412 - medium for consistent, uniform data entry which provides data
A60413 - for accounting software, and builds an audit trail from work
A60414 - history, including decisions, and analysis that explain the
A60415 - cause of expenses and income, so that folks can make
A60416 - adjustments to control the future. (see "Command and Control"
A60417 - in POIMS, ref OF 7 1113)
A60419 - ..
A60420 - Control Fields create record segments that associate related
A60421 - context for "controlled visibility," similar to chapters in a
A60422 - book. People control content of reports by extracting portions
A60423 - of disparate SDS records to construct a chronology showing
A60424 - cause and effect based on the organic structure of context,
A60425 - similar to the way people use 3 x 5 cards, explained in POIMS.
A60426 - ref OF 5 143L, and in NWO. ref OF 13 QR7F During a call on
A60427 - 950223, Morris discussed SDS support for organizing the record
A60428 - with Control Fields. ref SDS 7 9933
A60430 - ..
A60431 - Control Fields provide a flexible structure chosen by the user
A60432 - based on needs of the work and time available for tracking
A60433 - complex, contextual details, as explained on 890523.
A60434 - ref SDS 1 LU55 An example of complexity that occurs in context
A60435 - management for a simple "picture" is shown in the record on
A60436 - 890523. ref SDS 1 G14K Except for posting the amount of time
A60437 - expended performing work, users never type anything into
A60438 - Control Fields. Data entry occurs from opening a data base and
A60439 - selecting accounts by pressing "Enter" or "double clicking."
A60440 - The data base is closed and account data is entered in the
A60441 - Control Field in the SDS record.
A60442 -
A60444 - ..
A60445 - Big Picture Integrates Details Avoid Paying the Devil's Price
A60446 -
A60447 - Subjects are the most complex part of this system, because they
A60448 - have a DNA-like organic structure that continually grows,
A60449 - unlike cost accounts which are relativley stable.
A60451 - ..
A60452 - The record on 890523 explains flexible structure that
A60453 - constructs and maintains order essential to understand cause
A60454 - and effect. ref SDS 1 P13O SDS supports the practice of
A60455 - evolving work breakdown structure (WBS) to understand order in
A60456 - complex correlations, implications, and nuance from the "big
A60457 - picture" of daily work. ref SDS 1 G14K Organizing details to
A60458 - make sense of expanding complexity turns experience into useful
A60459 - history. Accurate history showing the order of cause and
A60460 - effect avoids paying the price of assumption, commonly
A60461 - described as using "common sense" (also called "paradigms") to
A60462 - fill in gaps of ambiguity remembering only the "gist of the
A60463 - story," noted by Campbell in his book "The Improbable Machine,"
A60464 - reviewed on 900303. ref SDS 2 4456 Discovering, constructing,
A60465 - and maintaining order helps avoid the "Devil in the Details,"
A60466 - explained in NWO. ref OF 11 9449
A60468 - ..
A60469 - Jack Park is familiar with complexity of context management
A60470 - from research reported on 000221. ref SDS 12 L58O Morris
A60471 - discussed "fractionalized subjects" during a meeting on 970116.
A60472 - ref SDS 9 1732
A60473 -
A60474 -
A60475 -
A60476 -
A60477 -
A605 -
SUBJECTS
Data Base Design SDS or List File Users SDS Records Schedule Current
AP03 -
AP0401 - ..
AP0402 - 3. SDS Data base design beginning in 1985
AP0403 - C-programming Language Developement Platform SDS Windows Applicaiton
AP0405 - ..
AP0406 - Morris feels SDS can be programmed for a Windows application
AP0407 - using the C programming language, as discussed previously.
AP0408 - This would be different from prior planning on 040505 to
AP0409 - upgrage the C version of Medit for increasing memory of the
AP0410 - current version of SDS. ref SDS 28 0001 Case study on 040505
AP0411 - shows long history planning and efforts to develop C
AP0412 - programming version of SDS. ref SDS 28 QU61
AP0413 -
AP0414 - [On 080104 Morris considering using Java instead of c
AP0415 - programming language for development platform to create SDS
AP0416 - Windows application. ref SDS 40 OM6Y
AP0418 - ..
AP0419 - Morris asked if SDS is a "data base" or a "list file"? Not
AP0420 - sure about the last term, but the indication seemed to be that
AP0421 - if the architecture is a "data base" this might use SQL, which
AP0422 - would be slow, whereas an alternative design would be faster.
AP0423 - Morris noted the importance of speed.
AP0424 -
AP0425 - [On 071106 review challenges developing Knowledge Management
AP0426 - tools due to difficulty understanding "knowlede."
AP0427 - ref SDS 37 W889
AP0428 -
AP0430 - ..
AP0431 - 4. Objectives and Features SDS Windows Application
AP0432 - Critical Mass Complementary Functions Data Bases Yield Synergy
AP0433 -
AP0434 - Morris asked today for objectives and functions of SDS.
AP0436 - ..
AP0437 - As noted above, ref SDS 0 645L, Morris developed an outline of
AP0438 - product scope in a letter received on 950221. ref SDS 6 JC7O
AP0440 - ..
AP0441 - [On 071212 Morris asks for SDS features again. ref SDS 38
AP0442 - W889
AP0444 - ..
AP0445 - [On 071222 Morris asks for SDS essential features again.
AP0446 - ref SDS 39 3V35
AP0448 - ..
AP0449 - SDS supports a new way of working that integrates a critical
AP0450 - mass of complementary functions so that each supports the
AP0451 - other, listed in POIMS. ref OF 5 2688 Review on 030416 shows
AP0452 - Gary makes this point, ref SDS 21 7P5F, in his record a few
AP0453 - days earlier on 030413. ref SDS 20 0001 Review on 030708 shows
AP0454 - Gary discussed SDS productivity, ref SDS 22 LV8G, in his record
AP0455 - on 030709 explaining benefits of synergy. ref SDS 23 FX65 Gary
AP0456 - again presents synergy from complementary features that each
AP0457 - support the other, reported 040415. ref SDS 26 L560 Last year
AP0458 - on 060207 he stated that trying to replicate SDS must provide
AP0459 - synergy among components. Concetrating on any single aspect
AP0460 - will dissipate the power of productivity. ref SDS 30 8P42
AP0461 -
AP0462 - 1. Contracting provides a new vision of "Time" management that
AP0463 - links the present with the past and the future. ref OF 5
AP0464 - 2688
AP0466 - ..
AP0467 - 2. Engineering uses thorough "Document" management."
AP0468 - ref OF 5 1293
AP0470 - ..
AP0471 - 3. Sales professionals use "Contacts" management." ref OF 5
AP0472 - 1296 ..
AP0474 - ..
AP0475 - 4. Research scientists use alphabet technology for capturing
AP0476 - each step of experiments to study cause and effect that
AP0477 - discovers new knowledge. Similarly, test pilots report
AP0478 - each task and results while flying. Back on the ground,
AP0479 - pilots prepare deliberative analysis by writing a story
AP0480 - that aligns data captured during the flight with objectives
AP0481 - and prior understandings. Reconciling conflicts in
AP0482 - analysis reveals issues not apparent while performing
AP0483 - tasks, because the "heat of battle" requires full attention
AP0484 - and energy, and the "fog of war" conceals critical
AP0485 - correlations, implications and nuance. Investing time for
AP0486 - deliberative analysis in science and engineering expands
AP0487 - span of attention to deepen understanding. ref OF 5 1Z99 ..
AP0489 - ..
AP0490 - 5. Banking, ecology, conservation, and farming show that
AP0491 - "investing" and recycling yield big rewards; similarly
AP0492 - investing time to recycle information grows knowledge and
AP0493 - ideas. ref OF 5 0668
AP0495 - ..
AP0496 - 6. Legal practice uses citations to discover and maintain
AP0497 - alignment of cause and effect with controlling forces in
AP0498 - law, regulation, contracts, commitments; alignment reduces
AP0499 - errors and the time required to apply decisions
AP0500 - consistently. ref OF 5 1247
AP0502 - ..
AP0503 - 7. Detectives use 3 x 5 cards for organizing disparate facts
AP0504 - of investigations and then move the cards on a display
AP0505 - board to form multiple views, scenarios and theories for
AP0506 - discovering patterns of cause and effect that solve the
AP0507 - case. ref OF 5 143L
AP0509 - ..
AP0510 - 8. Accounting uses organic, structured systems of
AP0511 - identification, summaries, audit trail, and double-entry
AP0512 - verification under the rule that little deviations cause
AP0513 - big problems. ref OF 5 8936
AP0515 - ..
AP0516 - 9. Computer programmers debug the work to improve productivity
AP0517 - with quality control that corrects defective reasoning.
AP0518 - ref OF 5 1258
AP0520 - ..
AP0521 - 10. Journalism provides outlining, headlines and highlighting
AP0522 - to report information that "connects the dots" from "data"
AP0523 - into daily news stories about who, what, when, where and
AP0524 - why events occur based on chronology that accumulates into
AP0525 - history for understanding cause and effect. POIMS
AP0526 - requirements for precision access strengthen traditional
AP0527 - journalism with a dynamic model of organizational memory
AP0528 - (see NWO) that facilitates working intelligently.
AP0529 - ref OF 5 1261
AP0531 - ..
AP0532 - 11. Intelligence experts analyse cause and effect, and
AP0533 - summarize details so that a lot of important information
AP0534 - can be absorbed quickly and accurately by decision makers.
AP0535 - ref OF 5 12F2
AP0537 - ..
AP0538 - 5. SDS Features and Components
AP0539 -
AP0540 - Gary's SDS record on 070823, ref SDS 35 WJ5H, also cited above,
AP0541 - ref SDS 0 Y88F, updates Morris' outline on 950221, ref SDS 6
AP0542 - JC7O, of SDS components that generate and apply the following
AP0543 - "data bases"...
AP0544 -
AP0545 - a. Users
AP0547 - ..
AP0548 - b. SDS records
AP0550 - ..
AP0551 - 1) Schedule
AP0552 - 2) Current diary records
AP0553 - 3) Archived diary records
AP0555 - ..
AP0556 - c. Documents
AP0557 -
AP0558 - 1) Received formal correspondence
AP0559 - 2) Issued formal correspondence
AP0560 - 3) Other, i.e., everything else
AP0562 - ..
AP0563 - d. Contacts
AP0564 -
AP0565 - 1) Organizations
AP0566 - 2) Individuals
AP0568 - ..
AP0569 - e. Subjects
AP0570 -
AP0571 -
AP0572 -
AP06 -
SUBJECTS
Document Log References SDS Records Create Write Manage Documents In
BG03 -
BG0401 - ..
BG0402 - 6. Document Log
BG0403 -
BG0404 - Morris initially indicated an impression that the "document
BG0405 - log" is a separate system. We reviewed Gary's record on 070823
BG0406 - showing this is part of the SDS record Reference field.
BG0407 - ref SDS 35 WJ5X This was then demonstrated by observing an SDS
BG0408 - record on the computer.
BG0410 - ..
BG0411 - Purpose of the document log integrated within SDS records
BG0412 - applies a "command" or "control center" concept, as a component
BG0413 - of "Knowledge Space," and so leads to a practice of "Knowledge
BG0414 - Management" explained by a few paragraphs in POIMS. ref OF 5
BG0415 - TO6N
BG0417 - ..
BG0418 - We did not actually look at an SDS doc log listing today; only
BG0419 - demonstrated how content gets captured in the SDS record, and
BG0420 - is listed for linking purposes in the Reference field.
BG0421 -
BG0422 -
BG0423 -
BG05 -
SUBJECTS
Temporary Store Documents from Internet Email Pending Post to Docume
CG03 -
CG0401 - ..
CG0402 - Temporary Storage Pending Post to Doc Log Data Base
CG0403 -
CG0404 - Morris described a problem he wants to address arising from
CG0405 - getting "300" email per day. General Hatch raised the same
CG0406 - issue during the meeting on 960410. ref SDS 8 5839 On 980722
CG0407 - Morris described a practice of timely response to email.
CG0408 - ref SDS 10 0464
CG0410 - ..
CG0411 - Today, Morris asked about moving a letter from the Outlook
CG0412 - directory/inventory into a temporary directory until there is
CG0413 - time to create an SDS record and create a permenant address.
CG0414 - The idea is to designate the file for work before span of
CG0415 - attention is overwhelmed by the large volume of daily traffic.
CG0416 -
CG0417 - [On 080531 timely response to email demonstrated, and
CG0418 - possible backlog of pending email to read. ref SDS 42 U266
CG0420 - ..
CG0421 - This is a common scenario.
CG0423 - ..
CG0424 - Requirements for temporary storage are evident in operating
CG0425 - system directories to store files temporarily.
CG0427 - ..
CG0428 - This requirements occurs routinely moving documents from email
CG0429 - programs into SDS Knowledge Space for command and control of
CG0430 - the record. Similarly, when a document is received downloading
CG0431 - research from the Internet in HTML, Word, PDF, Powerpoint
CG0432 - formats, the original form is saved to a temporary directory
CG0433 - with a manageable filename, and then when time permits, the
CG0434 - record is received into SDS for management, i.e., analysis of
CG0435 - correlations, implications, and nuance, action items, etc.
CG0436 - This work requires adding anchors to the document, and so it is
CG0437 - converted into ASCII, and assigned to a particular directory
CG0438 - environment.
CG0440 - ..
CG0441 - Currently, files are stored on an interim basis in any of 4 or
CG0442 - so temporary directories...
CG0443 -
CG0444 - 10
CG0445 - 11
CG0446 - 12
CG0447 - 13
CG0448 - sds 10
CG0450 - ..
CG0451 - Further reviewed issue of documents stored by user for
CG0452 - performing work, and stored commonly system-wide, similarly to
CG0453 - the ACE system used on the FCS project at Boeing.
CG0454 -
CG0455 -
CG0456 -
CG0457 -
CG05 -
SUBJECTS
Schedule Design SDS Aid Mental Process Integrate Thinking Doing List
CZ03 -
CZ0401 - ..
CZ0402 - 7. Schedule - Consider Outlook Calendar Format
CZ0403 -
CZ0404 - Morris notes the SDS schedule provides a list of things to do,
CZ0405 - and does not meet industry standards for "scheduling software."
CZ0407 - ..
CZ0408 - There are a lot of tasks professional scheduling people do that
CZ0409 - go beyond the writ of SDS, e.g., scheduling conference rooms,
CZ0410 - scheduling professional events, etc.
CZ0412 - ..
CZ0413 - History of SDS listed on 000723 shows the "schedule" strives to
CZ0414 - meet requirements for leveraging intelligence, ref SDS 15 CW4G,
CZ0415 - and explained in POIMS. ref OF 5 1101 Balancing accuracy
CZ0416 - against limited time is a Knowledge Management dilemma which
CZ0417 - can only be solved with tools designed to "routinize" cognitive
CZ0418 - science, noted by Drucker in his Atlantic Monthly article,
CZ0419 - reviewed on 991025. ref SDS 11 0785
CZ0421 - ..
CZ0422 - Experience using SDS shows that listing tasks in a Schedule
CZ0423 - integrated with a diary aids the mental process of integrating
CZ0424 - time and information, described in SDS as thinking and doing.
CZ0425 - ref OF 3 2049
CZ0427 - ..
CZ0428 - Morris proposes the SDS schedule offer an Outlook scope with a
CZ0429 - familiar calendar format. This would support scheduling his
CZ0430 - teaching assignments, and things like repetitive meetings.
CZ0431 - Gary has long supported this requirement. Formatting schedule
CZ0432 - "bells and whistles" should not crowd out primary requirements
CZ0433 - to integrate time and information, explained in POIMS,
CZ0434 - ref OF 3 0367, and illustrated by the logo, which Morris
CZ0435 - originally helped create, and which Gary's wife refined a few
CZ0436 - years ago, also, shown in POIMS. ref OF 7 1116
CZ0438 - ..
CZ0439 - Discussed arranging to incorporate content of SDS records from
CZ0440 - prior related events as a template to report work on each
CZ0441 - succeeding event.
CZ0443 - ..
CZ0444 - Morris asked how tasks are moved from one date to another when
CZ0445 - changes occur. This was demonstrated.
CZ0447 - ..
CZ0448 - Clarified that SDS records for scheduled tasks have the same
CZ0449 - format as current and archived diary records, as noted in
CZ0450 - Gary's outline on 070823. ref SDS 35 WJ5H
CZ0451 -
CZ0452 -
CZ0453 -
CZ05 -
SUBJECTS
Diary Records Converted from Schedule Tasks SDS Plan Perform Report
DH03 -
DH0401 - ..
DH0402 - 8. SDS Design Counterintuitive
DH0403 - Diary Records Transformed from Scheduled Tasks
DH0404 - Scheduled Tasks Transformed into Diary Records
DH0405 -
DH0406 - Morris asked how a schedule record gets converted into a diary
DH0407 - record?
DH0409 - ..
DH0410 - This was previously reviewed on 910520. ref SDS 3 NY4G On
DH0411 - 920215 Morris reported the SDS intelligence process of plan,
DH0412 - perform, report is hard to apply. ref SDS 4 5820 On 010924 we
DH0413 - discussed the counterintuitive SDS design. ref SDS 19 JS6G
DH0415 - ..
DH0416 - Today, we opened an SDS diary record. Morris noticed the date
DH0417 - and time posted at the top of the record above the description
DH0418 - field uniquely positions information in SDS "Knowledge Space,"
DH0419 - explained in POIMS. ref OF 6 YP7G
DH0421 - ..
DH0422 - Gary's report on 070823 explains the program develops unique
DH0423 - record ID for diary records from the date and time entered in
DH0424 - the schedule for starting the work. ref SDS 35 J04M
DH0425 -
DH0426 -
DH0427 -
DH05 -
SUBJECTS
Follow Up Action Items SDS Windows Application Design Development Pl
DK03 -
DK0401 - ..
DK0402 - Follow Up Planning and Opportunities
DK0403 -
DK0404 - Morris plans to write up requirements and specifications over the next
DK0405 - few days, and submit for comments, which continues iterative
DK0406 - development work Gary initiated a few weeks ago.
DK0407 -
DK0408 - [On 070914 delay on SDS project; Morris encountered issue that
DK0409 - takes precedence; may be able to continue work in 5 - 10 days.
DK0410 - ref SDS 36 5F5H
DK0412 - ..
DK0413 - [On 071106 decided to start code on SDS Contacts system, rather
DK0414 - than write up requirements for SDS.
DK0416 - ..
DK0417 - [On 071212 Morris feels "vision" for new version of SDS beginning
DK0418 - to emerge, ref SDS 38 ST3J, plans again to prepare product
DK0419 - requirements and specifications for Windows application of SDS.
DK0420 - ref SDS 38 KT4H
DK0422 - ..
DK0423 - Concurrent with the meeting today, Jack Park submitted insightful
DK0424 - comments on SDS, extending prior analysis on 001130. ref SDS 18 0001
DK0425 - In Jack's letter today, he notes SDS entails a discipline that reduces
DK0426 - the burden of cognitive overhead, commonly called "diligence,"
DK0427 - explained in NWO. ref OF 15 LH6K Jack's letter today reflects the
DK0428 - history of SDS that co-evolved tools and procedures grounded in time
DK0429 - and information management processes, noted above, ref SDS 0 RV8M, and
DK0430 - summarized in the practice of Communication Metrics, listed in POIMS.
DK0431 - ref OF 6 685K
DK0433 - ..
DK0434 - Equally, Jack's letter on 000403 recognized the importance of a new
DK0435 - professional discipline to implement the practices and procedures
DK0436 - enabled by SDS. ref SDS 13 2112
DK0438 - ..
DK0439 - Consideration should be made on inviting Jack to participate in the
DK0440 - new SDS effort. There is always a problem that "too many cooks spoil
DK0441 - the broth," however there is also opportunity that Jack might
DK0442 - complement the recipe with "special sauce" (to extend the culinary
DK0443 - metaphore).
DK0445 - ..
DK0446 - Discussion today shows the importance of experience using SDS for
DK0447 - understanding requirements that enable making improvements. This has
DK0448 - been a continuing challenge illustrated by the record on 001126.
DK0449 - ref SDS 17 QW8I People naturally want to build things they know about
DK0450 - from experience using tools already available. This causes
DK0451 - frustration, anger, and resentment when what they build does not
DK0452 - improve the work. The tendency is to classify anything that is
DK0453 - difficult to build and hard to understand, i.e., counterintutive, as
DK0454 - unnecessary overkill, rather than start over to build what is needed.
DK0456 - ..
DK0457 - Another dimension to this undertaking is getting younger people
DK0458 - involved. All of us who were willing to make any effort for the
DK0459 - "cause" 30 years ago, are now over 50. We may not have 30 years to
DK0460 - get the work done, particularly starting from scratch, as being
DK0461 - proposed. We need to be alert and innovative finding young talent
DK0462 - with potential for vision to see, courage to act, and will to
DK0463 - persevere no matter what.
DK0464 -
DK0485 -
DK0486 -
DK0487 -
DK0488 -
DK0489 -
DK05 -