THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
S U M M A R Y
DIARY: June 15, 2004 10:22 AM Tuesday;
Letter to Gary on SDS for Aerospace company standard on organizational memory.
2...Organizational Memory SDS Standard Proposed for Aerospace company ASB
3...SDS Standard Proposed for Aerospace company ASB Organizational Memory
4...Saving Time Working on Familiar Things in Familiar Ways
5...Foundational Documents Developed with SDS Records Linked to History
6...Document Construction in Organiztaional Memory for Command Control
7...Command Control Document Construction in Organiztaional Memory
8...Dilemma Learning SDS, and Working with IT Both Frustrating
9...Case Study 3-layer Architecture Deployment Example Using SDS
10...Teach Mentor Examples Illustrate Demonstrate SDS Support for Documents
11...Documents Teach Mentor Examples Illustrate Demonstrate SDS Support
12...Technical Documents Supported by SDS for Working Intelligently
13...Information Technology Transform to Culture of Knowledge Experiment
........Aerospace company Architecture Committee Wants Standard for Collaboration
........Collaboration from Intelligence Support Aerospace company Wants Standard
........Meetings Collaboration Intelligence Support by SDS Standard
........Explaining SDS Hard Takes Persistance Writing to Understand
........Persistance Developing Explanation Culture of Knowledge
........Management Cognitive Computer Science Integrate Not Easy
........Hard Explaining Counterintuitive New Way Working Intelligently
Click here to comment!
ASB Planning 1st Draft Organizational Memory SDS Standard Proposed f
Proposal ASB SDS Architecure Requirements Gary Gil Collaborate to Pr
Sample Format Language for Approved Software Boeing Commercial Airpl
Organizational Memory SDS Standard Proposed for Boeing ASB
Meetings Collaboration Intelligence Application Propose SDS Standard
Communication Metrics Negative Attitude Business Metrics Dislike Fea
Organizatinoal Memory Filed SDS Standard in ASB for Aerospace Compan
4109 - ..
4110 - Summary/Objective
411101 - Follow up ref SDS 46 0000, ref SDS 44 9855.
411103 - Gary has made progress on submitting a proposal for SDS setting a
411104 - standard on organizational memory at Aerospace company. ref SDS 0 Y55R
411105 - Yesterday, Gary sent a letter transmitting files. There was no
411106 - explanation of what was sent, why, nor what action was intended.
411107 - ref SDS 0 R57W Turned out the files are initial work to prepare
411108 - technical documents for the proposal on SDS using Aerospace company's
411109 - ASB form. ref SDS 0 R58U Microsoft Word and other programs were used
411110 - to avoid wasting time learning to use SDS for preparing documents.
411111 - ref SDS 0 R58U Background shows that preparing documents with SDS
411112 - makes finding relevant sources and making connections to verify
411113 - accuracy and expand span of attention fast and easy. ref SDS 0 R54Q
411114 - However, people need examples and help learning new practices.
411115 - ref SDS 0 E54K Often there is not enough time on the job to retool
411116 - skills; stopping to invest time in learning presents an unacceptable
411117 - risk. ref SDS 0 QW5L As a result, transformation from IT to a culture
411118 - of knowledge presents big challenges learning the 8 steps for
411119 - intelligence support. ref SDS 0 LD4I Frustration occurs from a
411120 - dilemma where learning SDS that makes good management fast and easy
411121 - takes time away from using familiar tools in familiar ways, and using
411122 - familiar tools do not support good management preparing documents with
411123 - connections to relevant history and sources. ref SDS 0 WA5K This
411124 - experience presents a lesson learned that transformation entails
411125 - continual education with support services and mentoring that provide
411126 - examples showing how to use SDS for specific applications. ref SDS 0
411127 - 6X5J We decided to apply SDS support to preparing the 1st draft of the
411128 - ASB. Gary and Gil will get experience showing how documents are
411129 - prepared that add intelligence to information in the documents. This
411130 - training exercise will provide a template for using SDS on the 2nd
411131 - draft. ref SDS 0 ER4M Planning for the 1st draft can apply prior
411132 - analysis, SDS foundational documents and professional sources.
411133 - ref SDS 0 3T9K
411140 - ..
4114 - Progress
411501 - Organizational Memory SDS Standard Proposed for Aerospace company ASB
411502 - SDS Standard Proposed for Aerospace company ASB Organizational Memory
411504 - Follow up ref SDS 46 0X5F, ref SDS 43 YE3P.
411506 - Gary called and advised he has made progress meeting with Gil and
411507 - talking with Susan Hammar on filing a proposal for an SDS standard at
411508 - the Aerospace company. Gary's idea is to limit the initial filing to
411509 - using SDS for the familiar application he has learned so far preparing
411510 - records for meeting minutes. He feels "collaboration" can be easily
411511 - grasped. Decided to file the standard in the ASB for "organizational
411512 - memory," rather than the full scope of POIMS support for Communication
411513 - Metrics. This fits the model of enabling intelligence support, which
411514 - starts with organizational memory, shown in the record on 010924.
411515 - ref SDS 22 L46F
411517 - ..
411518 - Gary feels Communication Metrics causes negative attitudes among
411519 - colleagues at the Aerospace company because business metrics for cost
411520 - and schedule control are applied arbitrarily. Fear and anger against
411521 - command and control management practices were reviewed on 931130 with
411522 - analysis of Drucker's book "Management Practices, Tasks,
411523 - Responsibilities. ref SDS 3 9677
411525 - [On 040625 1st draft ASB form is prepared on SDS setting a
411526 - standard for organizational memory that enables intelligence
411527 - support. ref SDS 49 PR5X
411529 - ..
411530 - [On 040720 ASB form is finalized on SDS setting a standard for
411531 - organizational memory that enables intelligence support.
411532 - ref SDS 53 PR5X
411534 - ..
411535 - [On 050119 Gary reports business metrics are disliked on the
411536 - job, leading to negative marketing image for Communication
411537 - Metrics. ref SDS 56 ET3W
411539 - ..
411540 - [...below, collaboration standard is discussed further.
411541 - ref SDS 0 R67W
411543 - ..
411544 - [On 040720 ASB form finalized on SDS setting a standard for
411545 - organizational memory that enables intelligence support on
411546 - meetings. ref SDS 53 QL7N
411548 - ..
411549 - Submitted a letter confirming discussions yesterday that Gary has
411550 - started work on preparing the ASB per planning on 040610, ref SDS 46
411551 - 9T8F, and based on sources listed at that time in the same record.
411552 - ref SDS 46 UT5K
411554 - 1. Subject: SDS Review for Aerospace company Standard
411555 - Date: Tue, 15 Jun 2004 23:37:11 -0700
411559 - ..
411560 - 2. This confirms our discussion yesterday on progress getting SDS
411561 - approved for a Aerospace company standard, which at this time
411562 - you are limiting to a standard for "organizational memory," as
411563 - set out in POIMS. ref OF 3 01TU
411565 - ..
411566 - 3. Yesterday, you submitted four (4) computer files prepared to
411567 - present requirements on SDS support for a system of
411568 - "organizational memory," conveyed by your letter shown below.
411569 - A fifth (5th) file seems to be the results of the Architecture
411570 - Committee that voted on approving SDS as a Aerospace company
411571 - standard, part of which you submitted separately attached to a
411572 - letter on 040610. ref SDS 46 FF6I Note that review of
411573 - documents is aided by an explanation of what documents are
411574 - submitted and how the documents are related, and what tasks are
411575 - expected to be performed.
411577 - ..
411578 - When documents are submitted, there should be an inventory list, and
411579 - an explanation on the purpose of each document listed, how the
411580 - documents relate to one another, and what action is contemplated.
411582 - ..
411583 - Letter Gary continues...
411585 - 4. In our call, you explained that the file named "objectives" was
411586 - prepared with Microsoft Word to save time on defining
411587 - requirements for...
411589 - "organizational memory"
411591 - ..
411592 - 5. This is the only file that is intended for submission to the
411593 - Architecture Committee, and it is based on a second Word.doc
411594 - file with the filename "requirements." To save time, the 2nd
411595 - file was created by copying your SDS record on 040525 where you
411596 - had previously developed "Requirements for AIC Software Board".
411597 - ref SDS 45 0001 You seemed to indicate that after the
411598 - Objectives file is completed, to save time, it will be
411599 - converted into ascii text with HTML and then to save more time,
411600 - content from the html file will be copied into the ASB file
411601 - online with cut and paste for display on the Aerospace company
411602 - website, which is also an HTML file.
Save Time Working on Familiar Things in Familiar Ways Foundational D
Dilemma Learning SDS to Work Intelligently Frustrating Because Famil
Learn SDS Beyond Wordprocessing and Spreadsheets Resisted Frustrated
Slippery Slope Laziness Greased by Limited Time
Bandwidth Think Not Enough Time for Communication Metrics
Case Study Familiar Tools Working on Familiar Things Transformation
Technical Document Preparing Application SDS Experience Needed Under
691001 - ..
691002 - Saving Time Working on Familiar Things in Familiar Ways
691003 - Foundational Documents Developed with SDS Records Linked to History
691004 - Document Construction in Organiztaional Memory for Command Control
691005 - Command Control Document Construction in Organiztaional Memory
691007 - Follow up ref SDS 30 0001, ref SDS 29 234G.
691009 - 6. We discussed briefly, yesterday, how documents constructed in
691010 - Knowledge Space, called out in POIMS, ref OF 6 1107, for
691011 - display on a web browser, as intended in this case for the ASB
691012 - file to set a standard for SDS at Aerospace company, are routinely created
691013 - using the "plan, perform, report" design set out in POIMS,
691014 - ref OF 5 6649, that supports planning and research to connect
691015 - document content with relevant history, also explained in
691016 - POIMS, ref OF 5 0859, rather than Microsoft Word, described by
691017 - Gary today, per above. ref SDS 0 R58U SDS foundational
691018 - documents are examples of methodology to quickly draw on work
691019 - history, i.e., personal and organizational memory, and to
691020 - figure out objectives, resolve conflicts, plan strategy like
691021 - "develop comprehensive requirements, then decide the minimum
691022 - needed to gain approval by Architecture Committee" -- again,
691023 - plan, perform and report.
691025 - ..
691026 - Examples using SDS to implement this method for creating SDS
691027 - foundational documents are...
691029 - a. POIMS......................... 010321. ref SDS 20 0001
691030 - b. NWO........................... 950812. ref SDS 7 0001
691031 - c. NWO........................... 950816. ref SDS 8 0001
691032 - d. Typical Day Scenario.......... 010321. ref SDS 27 0001
691034 - ..
691035 - 7. These examples illustrate how SDS is used to save time and
691036 - money applying the ideas explained in the documents. That
691037 - might be a good objective to help the Committee and prospective
691038 - users at Aerospace company grasp the meaning and opportunity of using
691039 - "good management" to "work intelligently."
691041 - [On 040625 prepared 1st draft of ASB file using SDS plan,
691042 - perform, report method. ref SDS 49 SW5I
691044 - ..
691045 - [On 040709 Gary commends SDS support for preparing
691046 - technical documents, based on experience working with the
691047 - ASB project to set a standard for SDS intelligence support
691048 - using organizational memory. ref SDS 51 RG7H
691050 - ..
691051 - [On 040709 developed planning for Gary to prepare edits on
691052 - 1st draft to create a 2nd draft that can be submitted to
691053 - Aerospace company. ref SDS 51 RH34
691055 - ..
691056 - [On 040720 prepared 2nd draft for submission to Aerospace
691057 - company. ref SDS 53 0001
691059 - ..
691060 - [On 040802 Gary's schedule changed; not enough time to edit
691061 - 1st draft ASB to prepare a 2nd draft for submission to
691062 - Aerospace company. ref SDS 54 0001
691064 - ..
691065 - [On 050125 Gary considering implementing SDS support for
691066 - intelligence using organiztional memory to prepare
691067 - technical documents. ref SDS 57 HG9O
691069 - ..
691070 - Gary explained during the call today, that he used tools from the list
691071 - on 030407, ref SDS 29 0001, to save time preparing the ASB proposal
691072 - for an SDS standard at Aerospace company, as noted above. ref SDS 0
691073 - R58U Working with familiar tools in familiar ways seems faster and
691074 - easier than learning a new way of working by retooling skills to
691075 - construct documents with SDS. ref OF 5 0859 and cited below,
691076 - ref SDS 0 R64V On 030506 Gary planned to implement POIMS requirements
691077 - for connecting document content to sources, authority, and relevant
691078 - history. ref SDS 30 0001 Below, Gary's record on 040916 explains
691079 - using SDS to prepare technical documents is not a familiar practice.
691080 - ref SDS 0 SS5I
691082 - [On 040915 Gary not aware SDS support for root cause analysis.
691083 - ref SDS 55 OX89
691085 - ..
691086 - To implement a new way of working called out by Engelbart on 991222,
691087 - ref SDS 16 C742, people need examples, experience and support learning
691088 - how to analyse documents connected to original sources, listed on
691089 - 950204, ref SDS 6 7499, and similarly, people need help learning to
691090 - write documents with support called out in POIMS. ref OF 5 0859
691092 - ..
691093 - Learning to retool personal skills to implement a new way of working
691094 - takes time, which often is not available on the job when there are
691095 - many demands for getting things done. To stop and invest time for
691096 - learning well enough to have confidence that the end result will be
691097 - better than using familiar tools in familiar ways is always difficult
691098 - and often not possible, noted in the letter to Gary, per below,
691099 - ref SDS 0 R64V, and so contributes to extending the time for
691100 - transformation to 50 years, reported in Gary's letter on 011210.
691101 - ref SDS 24 R66K
691103 - ..
691104 - Investing time to learn a new way of working entails risk that
691105 - benefits may not exceed costs, which only experience can answer. This
691106 - is the calculation Morris had in mind on 890809 commenting about
691107 - reticence to learn SDS, ref SDS 1 6139, and cited in the letter to
691108 - Gary, shown below. ref SDS 0 R64V Therefore the potential gain must
691109 - be significantly greater than using existing methods in order to
691110 - justify taking the risk. On 931130 Drucker cites a 10 fold
691111 - improvement is needed to swap out established systems, and this seems
691112 - to pertain to retooling skills as well. ref SDS 2 8955
691114 - [On 050125 Gary considering using SDS for preparing technical
691115 - documents. ref SDS 57 RS37
691117 - ..
691118 - SDS improves many tasks people commonly perform on the job by a factor
691119 - of 10, reported on 931215. ref SDS 4 TB9H However, people also need
691120 - assurance that ability to perform tasks faster yields better overall
691121 - productivity that increases income. On On 971008 USACE issued report
691122 - showing cost savings from using SDS is in the range of 10:1.
691123 - ref SDS 12 5775 However, despite these findings, until people gain
691124 - direct experience, or until there is enough "common knowledge" among
691125 - peers about benefits, people lack faith in reporting that seems
691126 - conflicting with personal experience. This suggests the only path for
691127 - helping early adopters retool personal skills is to provide direct
691128 - experience, as we are doing at Aerospace company.
691130 - ..
691131 - Slow progress reported today applying 8 steps using Com Metrics,
691132 - planned in Gary's letter on 040402, ref SDS 40 TO8V, aligns with...
691134 - Case study shows familiar
691135 - tools used in familiar ways
691136 - easier less frustrating than
691137 - learning integrated work
691138 - practices people resist
691139 - transformation to new way
691140 - of working...................... 021227, ref SDS 28 874H
691142 - ..
691143 - Change resisted; people
691144 - prefer failure to enduring
691145 - frustration learning new
691146 - methods......................... 030813, ref SDS 32 2G9U
691148 - ..
691149 - NASA chief relates culture
691150 - of bureaucracy resists
691151 - improvement..................... 030826, ref SDS 33 1G9L
691153 - ..
691154 - Bureaucracy command and
691155 - control of people discourages
691156 - experimentation discover
691157 - improvement giving people
691158 - command and control of
691159 - the work........................ 040203, ref SDS 38 E44K
Lesson Learned 3-layer Architecture Deployment Transformation Learn
Dilemma Learning SDS to Work Intelligently Frustrating Because Famil
Dilemma Learning SDS Work Intelligently Frustrating Because Familiar
Learn SDS Beyond Wordprocessing and Spreadsheets Resisted Frustrated
Slippery Slope Laziness Greased by Limited Time
Save Time Working on Familiar Things in Familiar Ways Foundational D
Time Limited for Jerry to Learn and Use SDS Should Assign Com Manage
Feel Good Management Driven by Emotional Decisions Management Develo
Transformation 3-layer Architecture Learn SDS People Need SDS Softwa
NASA Management Gets It Understands Safety First Does Not Get It tha
Com Analyst Define New Work Role Professional Role Retool Skills Con
Deployment 3-layer Architecture Transformation Learn SDS People Need
Documents Prepare Manage Technical Documents Unaware SDS Supports Do
A91601 - ..
A91602 - Dilemma Learning SDS, and Working with IT Both Frustrating
A91603 - Case Study 3-layer Architecture Deployment Example Using SDS
A91604 - Teach Mentor Examples Illustrate Demonstrate SDS Support for Documents
A91605 - Documents Teach Mentor Examples Illustrate Demonstrate SDS Support
A91607 - Gary advised that, after trying conventional methods to save time, per
A91608 - above, ref SDS 0 DN8O, experience the past few weeks working on the
A91609 - ASB document for an SDS standard at Aerospace company shows that
A91610 - familiar tools used in familiar ways require a lot of time and hard
A91611 - work to draw on planning, for example on 040513, ref SDS 43 GV6N, and
A91612 - later on 040610 where plans were made to explain SDS support for
A91613 - converting useless information into useful intelligence, ref SDS 46
A91614 - YN3H, and to draw on SDS foundational documents, and other relevant
A91615 - sources to support the ASB. Gary's experience finding that
A91616 - information technology requires a lot of hard work to use good
A91617 - management, aligns with research at SRI by the OHS/DKR team, reported
A91618 - on 000307. ref SDS 17 5182
A91620 - ..
A91621 - This presents a dilemma...
A91623 - a. Learning SDS to work intelligently is frustrating because
A91624 - familiar tools and familiar ways are faster and easier, making
A91625 - good management look like unnecessary overkill.
A91627 - ..
A91628 - b. Familiar tools used for familiar things is frustrating because
A91629 - working intelligently is a lot of hard work, making good
A91630 - management look like unnecessary overkill.
A91632 - ..
A91633 - Doug Engelbart proposed that people need a warming up period before
A91634 - gracefully trying new way of working, and that this period requires
A91635 - support services demonstrating, mentoring, and educating a new way of
A91636 - working is within reach that adds value which justifies investing time
A91637 - on retooling skills so that people can reach out to use new tools in
A91638 - new ways, rather than familiar tools in familiar ways, reported on
A91639 - 000327. ref SDS 18 1530
A91641 - ..
A91642 - Lack of experience reported today on preparing documents with SDS
A91643 - caused reliance on familiar tools and popular methods for information
A91644 - technology (IT), ref SDS 0 DN8O, that drive frustrations of dilemma,
A91645 - per above. ref SDS 0 WA5K Below, review shows more experience is
A91646 - needed to understand SDS support for preparing and managing technical
A91647 - documents, ref SDS 0 SS5I, which aligns with a study showing slow
A91648 - transformation to apply 8-steps for Com Metrics, per above.
A91649 - ref SDS 0 QW6U
A91651 - ..
A91652 - This record presents a "lesson learned" that continual education
A91653 - through mentoring is a critical part of learning a new way of working,
A91654 - and that people need support services to experience the process of
A91655 - working intelligently. People, also, need examples of work product
A91656 - that demonstrate using SDS for routine daily tasks, like meetings,
A91657 - calls, planning, analysis, preparing documents, etc., under the
A91658 - 3-layer architecture for transformation, planned in the strategy on
A91659 - 040102. ref SDS 37 8Q3N This record suggests that using a greater
A91660 - share of the 8 steps for Communication Metrics, planned in the letter
A91661 - on 040402, ref SDS 40 TO95, requires support services Doug described
A91662 - on 000307, per above. ref SDS 0 WO8H After being ordered on 960924 to
A91663 - use SDS in a way that was not expected to be effective, ref SDS 9
A91664 - NQ3O, Tom Keesling at USACE discovered people need experience to
A91665 - understand the scope of SDS application. on 961101. ref SDS 10 8888
A91666 - Bill DeHar made a similar observation at PG&E on 941004. ref SDS 5
A91667 - 0785
A91669 - ..
A91670 - [...below, decided Rod will prepare 1st draft as training
A91671 - exercise. ref SDS 0 ER4M
A91673 - ..
A91674 - [On 040709 Gary wants to expand using SDS for engineering
A91675 - management, based on experience managing documents for the ASB
A91676 - filing on SDS that used the SDS plan, perform, report
A91677 - "intelligence" cycle; ref SDS 51 RG7H
A91679 - ..
A91680 - A lot of evidence shows new markets grow for disruptive technologies
A91681 - through transformation from...
A91683 - 1. Awareness
A91684 - 2. Interest
A91685 - 3. Need
A91686 - 4. Belief
A91687 - 5. Faith
A91688 - 6. Want
A91689 - 7. Demand
A91691 - ..
A91692 - Faith presents an innovation loop that requires experience to grow,
A91693 - but resists risk of investment without faith... It's a dilemma.
A91695 - ..
A91696 - Achieving transformation from awareness to demand occurs...
A91698 - 1. Experiment pilot test to discover
A91699 - opportunity to improve when
A91700 - sunshine profits occur, rather
A91701 - than wait to clutch at ever
A91702 - straw while the ship is
A91703 - sinking, Andy Grove............... 980307, ref SDS 13 3416
A91705 - ..
A91706 - 2. Steady exposure to support
A91707 - services that provide free
A91708 - work product demonstrate
A91709 - consistent, significant
A91710 - benefits, in order to gain
A91711 - enough confidence for
A91712 - people to try a new way of
A91713 - working, Doug Engelbart........... 000327, ref SDS 18 1530
A91715 - ..
A91716 - 3. Persistance present new ideas
A91717 - explaining experience getting
A91718 - better results correlate theory
A91719 - with practice expands circle of
A91720 - advocates Don Rumsfeld,
A91721 - Secretary of Defense.............. 020131, ref SDS 25 6L5K
A91723 - ..
A91724 - 4. 3-layer architecture transforms
A91725 - people using existing skills
A91726 - without learning anyting new
A91727 - by adding value to organizational
A91728 - memory so everyone can work
A91729 - intelligently by only a few
A91730 - people using SDS.................. 020820, ref SDS 26 X53K
A91732 - ..
A91733 - 5. Steady-as-she-goes 3-layer
A91734 - architecture grows demand for
A91735 - new way working by being
A91736 - persistant delivering useful
A91737 - work product...................... 030524, ref SDS 31 9X62
A91739 - ..
A91740 - 6. Relentless pressure delivering
A91741 - the goods that help people
A91742 - transforms culture from negative
A91743 - resistance into positive
A91744 - synergy for working
A91745 - intelligently..................... 031211, ref SDS 36 PE5Y
A91747 - ..
A91748 - 7. 2nd act maintains pressure
A91749 - presenting theory of knowledge
A91750 - in foundational documents for
A91751 - continual education that
A91752 - explains experience with new
A91753 - way of working using
A91754 - organizational memory............. 040102, ref SDS 37 1L30
A91756 - ..
A91757 - 8. Strategy grow demand by
A91758 - maintaining exposure to
A91759 - theory and benefits
A91760 - through education and
A91761 - practice.......................... 040102, ref SDS 37 1656
A91763 - ..
A91764 - 9. Professional papers expand
A91765 - pressure to wider circle
A91766 - enables continual learning
A91767 - through steady education
A91768 - strategy step 1................... 040102, ref SDS 37 JH4G
A91771 - ..
A91772 - As a result, during the call today, we decided to support
A91773 - transformation with the 3-layer architecture model of deployment, see
A91774 - POIMS. ref OF 6 XQ9F Will use documents Gary submitted today,
A91775 - ref SDS 0 R57W, to prepare a 1st draft of the ASB that illustrates how
A91776 - to prepare documents connected to relevant planning, history, and
A91777 - sources, per above. ref SDS 0 WO8H Gary and Gil can then use the 1st
A91778 - draft as a template to prepare a final draft for submission to Aerospace company,
A91779 - with Gary using SDS along the lines of the 1st draft.
A91781 - [On 040618 Aerospace company objectives on Gary's project with US Army for
A91782 - systems to manage and organize the work for efficient operations
A91783 - and effective collaboration. ref SDS 48 DT7K
A91785 - ..
A91786 - [On 040625 prepared 1st draft ASB proposing standard at Aerospace company
A91787 - for organizational memory that enables intelligence support by
A91788 - SDS. ref SDS 49 0S5O
A91790 - ..
A91791 - [On 040709 reviewed 1st draft. ref SDS 51 RG7H
A91793 - ..
A91794 - [On 040709 developed planning for 2nd draft that will be
A91795 - submitted to Aerospace company. ref SDS 51 RH34
A91797 - ..
A91798 - Planning, history and sources for ASB on standard for SDS at
A91799 - Aerospace company...
A91801 - Sources are listed on Welch
A91802 - web site................................
A91804 - http://www.welchco.com/00601.HTM
A91806 - ..
A91807 - SDS contract with Aerospace company
A91808 - defines Com Metrics and
A91809 - organizational memory............ 040317, ref SDS 39 PQ6P
A91811 - ..
A91812 - Planning on 040415 to explain
A91813 - SDS to Aerospace company Architecture
A91814 - committee........................ 040415, ref SDS 41 3E5N
A91816 - ..
A91817 - SDS proposal to Aerospace company
A91818 - Architecture Committee cites
A91819 - SDS contract specification
A91820 - for scope in "situation"
A91821 - section.......................... 040426, ref SDS 42 0001
A91823 - ..
A91824 - AIC comments during initial
A91825 - review panel guide scope of
A91826 - ASB for SDS standard that is
A91827 - distinguished from Microsoft
A91828 - technologies..................... 040513, ref SDS 43 YD4S
A91830 - ..
A91831 - Planning additional scope to
A91832 - present in ASB on standard for
A91833 - SDS granular addressability,
A91834 - explicit links, flexible organic
A91835 - structure, context management,
A91836 - Knowledge Space XYZ axes,
A91837 - finding information, multiple
A91838 - views, interoperability,
A91839 - integrate cost and schedule
A91840 - with Communication Metrics,
A91841 - integrate documents, contacts,
A91842 - time, information management
A91843 - for working intelligently
A91844 - that improves command control
A91845 - of daily work, in the ASB for
A91846 - an SDS standard.................. 040513, ref SDS 43 UO7G
A91848 - ..
A91849 - AIC requirements scope to
A91850 - avoid duplication with
A91851 - existing Aerospace company standards
A91852 - reported by Gary................. 040525, ref SDS 45 W37P
Conventional IT Methods Can Use SDS as Resource without Having to Le
Technical Document Management System Gary Discusses Industry Practic
Engineering Management Contemporaneous Documentation of Decisions
Experience Not Using SDS Ignorance Cultural Blinders Frustrated Scie
Technical Document Management System Gary Not Having Experience Feel
AL0801 - ..
AL0802 - Technical Documents Supported by SDS for Working Intelligently
AL0803 - Information Technology Transform to Culture of Knowledge Experiment
AL0805 - On 040616 Gary discusses challenges, ways and means for applying SDS
AL0806 - to a formalized information management process used in big
AL0807 - organizations to construct technical documents. ref SDS 47 IX3U This
AL0808 - record aligns with the report today that Gary was not aware SDS makes
AL0809 - good management fast and easy for preparing technical documents, per
AL0810 - above. ref SDS 0 DN8O Planned to support preparing the 1st draft that
AL0811 - will demonstrate this application. ref SDS 0 ER4M
AL0813 - [On 040630 Gary submits formal explanation of information
AL0814 - management that uses "fusion" to develop intelligence.
AL0815 - ref SDS 50 ON5N
AL0817 - ..
AL0818 - [On 040709 experience working on ASB proposal supports
AL0819 - explanation in POIMS on using organizational memory for
AL0820 - collaboration on engineering management; Gary feels that
AL0821 - SDS adds value to traditional methods, and suggests
AL0822 - expanding SDS support for managing documents. ref SDS 51
AL0823 - O47O
AL0825 - ..
AL0826 - [On 040915 Gary not aware SDS support for root cause
AL0827 - analysis. ref SDS 55 OX89
AL0829 - ..
AL0830 - We can experiment to discover a good balance using SDS for planning,
AL0831 - organizing, and sourcing, per above, ref SDS 0 E54K, and citing POIMS,
AL0832 - ref OF 5 0859, that supplements information technology described in
AL0833 - Gary's record on 040416, ref SDS 47 S55I, in order to avoid entropy
AL0834 - reported in the study by USAFIT, reviewed on 970707, ref SDS 11 0108,
AL0835 - and which Gary cited as a big problem on the job in his letter on
AL0836 - 011006. ref SDS 23 O99K
AL0838 - ..
AL0839 - Can we develop a good working balance under current cultural norms to
AL0840 - integrate "working intelligently," using SDS, with "working for
AL0841 - appearance" using Microsoft Word, et al, per requirements in POIMS.
AL0842 - ref OF 5 0959
AL0844 - [On 040625 developed procedures to manage ASB filing on SDS
AL0845 - standard which is 420K, twice the size SDS can typically
AL0846 - handle. ref SDS 49 SW5I
AL0848 - ..
AL0849 - [On 040709 Gary wants to expand using SDS for engineering
AL0850 - management, based on experience managing documents for the
AL0851 - ASB filing on SDS that used the SDS plan, perform, report
AL0852 - "intelligence" cycle; ref SDS 51 RG7H
AL0854 - ..
AL0855 - [On 040714 working on generalizing support for managing
AL0856 - large documents in SDS by assembling file segments for
AL0857 - display in a browser, like NWO, POIMS and ASB, ref SDS 52
AL0858 - G56O, requests for support using Knowledge Space case study
AL0859 - on how experience grows demand for SDS support. ref SDS 52
AL0860 - 525L
AL0862 - ..
AL0863 - Formal documents like a book, a specification, a report have been
AL0864 - managed routinely in SDS for 20 years. Gary makes a good point that
AL0865 - in the document preparation stage, getting a document into a form,
AL0866 - where the details can be managed in SDS, requires a big challenge of
AL0867 - investing time, when there are many meetings and other chores to
AL0868 - attend. ref SDS 47 IW65
AL0870 - ..
AL0871 - Sounds like more staff is needed to perform this study in order to
AL0872 - improve the work, as Paul mentioned to Gary on 031008. ref SDS 35 JU4T
AL0874 - ..
AL0875 - Letter to Gary continues...
AL0877 - c. You explained in our call that Microsoft Word was used, rather
AL0878 - than creating an SDS record, in order to "save time." [see
AL0879 - analysis above, ref SDS 0 DN8O] Part of this is the trade-off
AL0880 - between investing time to learn HTML functions supported by
AL0881 - SDS, rather than rely on functions in Microsoft programs that
AL0882 - are already familiar. Another factor is that, having invested
AL0883 - time to learn Microsoft Word, there is hesitancy to use SDS,
AL0884 - per Morris' report on 890809. ref SDS 1 6139
AL0886 - ..
AL0887 - d. Desire to work on familiar things in familiar ways, cited by
AL0888 - Andy Grove based on experience working at Intel, reviewed on
AL0889 - 980307, ref SDS 14 1657, is another dimension of the challenge
AL0890 - to bridge the gap between the two (2) worlds by advancing from
AL0891 - information to a culture of knowledge.
AL0893 - ..
AL0894 - On 040616 Gary discusses document preparation requirements for using
AL0895 - Microsoft Word to maintain consistent formating. ref SDS 47 S55I
AL0897 - ..
AL0898 - In a subsequent telephone call, Gary mentioned that formal documents
AL0899 - are submitted to a formatting department that conforms documents with
AL0900 - Aerospace company formatting standards.
AL0902 - ..
AL0903 - Letter to Gary continues...
AL0905 - e. The other two (2) documents received in your letter yesterday,
AL0906 - per below, were ASCII text files showing examples of software
AL0907 - programs that are already shown on the Aerospace company software
AL0908 - standards list. These files provide a template showing
AL0909 - categories to include and the scope of work for each category.
AL0911 - ..
AL0912 - f. We agreed that the objectives doc that has been prepared for
AL0913 - SDS does not fit the model of these two examples on the Aerospace company
AL0914 - website. You plan to research this with Susan and members of
AL0915 - the Architecture Committee in order to clarify the request to
AL0916 - develop "requirements" for SDS and/or collaboration.
ASB Planning 1st Draft Organizational Memory SDS Standard Proposed f
ASB Planning Collaboration Standard SDS Enables Accurate Understandi
Collaboration SDS Multiple Users Changes Attitudes about Good Manage
Information Overload Management Imploding Needs SDS Collaboration
SRI Management Needs SDS Com Metrics Listening, Communication Unders
Version Control Multiple People Working on Same Document File, Morri
Meetings Collaboration Standard Intelligence Application Propose SDS
Collaboration Documents Prepare Organic Structure Versioning Authors
Architecture Committee Report SDS Approved for Next Level Review Com
Meetings Collaboration Intelligence Application Propose SDS Standard
B91301 - ..
B91302 - Aerospace company Architecture Committee Wants Standard for Collaboration
B91303 - Collaboration from Intelligence Support Aerospace company Wants Standard
B91304 - Meetings Collaboration Intelligence Support by SDS Standard
B91306 - g. Does the Committee want "requirements for "collaboration"
B91307 - software that might be listed elsewhere, and then a description
B91308 - for SDS that fits the model of the two examples to explain how
B91309 - SDS meets requirements adopted for "collaboration," or do they
B91310 - want SDS to be presented differently from the other Aerospace company
B91311 - approved software, per above? ref SDS 0 Y55X
B91313 - ..
B91314 - h. Another factor to consider is that, if SDS is to set a standard
B91315 - for "organizational memory," and, if Aerospace company wants a
B91316 - standard for "collaboration," then an explanation is needed on
B91317 - the relationship between organizational memory and
B91318 - collaboration. Ideas on this are in POIMS discussing Knowledge
B91319 - Management. ref OF 4 O87L
B91321 - [On 040709 planning on collaboration procedures using SDS
B91322 - for preparing technical documents developed. ref SDS 51 GA5N
Persistance Develop Explanation Culture of Knowledge Using SDS for I
2nd Draft Rod Prepare ASB Gary Does Not Have Enough Time
Difficult to Understand Knowledge Management SDS Core Capability
SDS Counterintuitive Design Difficult for People Get It Disappointin
BM0701 - ..
BM0702 - Explaining SDS Hard Takes Persistance Writing to Understand
BM0703 - Persistance Developing Explanation Culture of Knowledge
BM0704 - Management Cognitive Computer Science Integrate Not Easy
BM0705 - Hard Explaining Counterintuitive New Way Working Intelligently
BM0708 - Letter to Gary continues...
BM0710 - i. Finally, we reviewed difficulty people have explaining
BM0711 - collaboration, knowledge management, intelligence,
BM0712 - communication and other efforts to support management in a way
BM0713 - that can be addressed effectively by technology. This
BM0714 - difficulty arises from lack of experience everyone using
BM0715 - technology to augment intelligence, and the need for
BM0716 - integrating management, cognitive and computer science. In
BM0717 - sum, it ain't easy!
BM0719 - ..
BM0720 - j. On 000716, professor Ransdell cautioned that we must expect
BM0721 - slow going on gaining acceptance of seminal ideas advancing
BM0722 - from information to knowledge. ref SDS 19 7838
BM0724 - ..
BM0725 - This is another dimension of being persistant writing to discover
BM0726 - understanding which helps to learn how to explain SDS to other people,
BM0727 - in addition to being persistant learning to use SDS for a new way of
BM0728 - working, per above. ref SDS 0 WA5K
BM0730 - [On 040802 Gary's schedule changed; not enough time to edit
BM0731 - 1st draft ASB to prepare a 2nd draft that explains SDS
BM0732 - succinctly for submission to Aerospace company. ref SDS 54 RH5O
BM0734 - ..
BM0735 - 020131 to be persistant writing up explanations for new ideas, because
BM0736 - this yields training and knowledge on how to explain difficult ideas
BM0737 - that are counterintuitive because they are new. ref SDS 25 6L5K
BM0739 - ..
BM0740 - Letter to Gary continues...
BM0742 - k. This means we have to expect to do things over a few times,
BM0743 - after trying out initial ideas. Creating an SDS record for the
BM0744 - task might help by going through the exercise of saying "Here
BM0745 - is an idea I have on what is important about SDS. Where is
BM0746 - this idea supported in foundational documents, and what
BM0747 - experience in the record supports the concept?"
BM0749 - ..
BM0750 - l. So, you are strongly congratulated for taking up the challenge
BM0751 - by applying your skills and experience developing requirements
BM0752 - for information technologies.
BM0754 - [...today, decides to support work on preparing 1st draft
BM0755 - as a training exercise on using SDS for technical documents
BM0756 - and on how to explain transformation from information to a
BM0757 - culture of knowledge. ref SDS 0 ER4M
BM0759 - ..
BM0760 - m. Now that I have "saved time" by avoiding the step of first
BM0761 - creating an SDS record to work out these ideas, I can get you
BM0762 - started working on them, and then use this letter as a basis
BM0763 - for preparing an SDS record to develop action items and
BM0764 - organization to invest intellectual capital at a convenient
BM0765 - time.
BM0767 - ..
BM0768 - n. We also discussed explaining that SDS is designed to support an
BM0769 - architecture that the developer calls POIMS, which is fully
BM0770 - explained at the website...
BM0772 - ..
BM0773 - [On 040625 incorporated POIMS into ASB filing. ref SDS 49
BM0774 - PR5X
BM0776 - ..
BM0777 - [On 040720 POIMS was retained in the 2nd draft. ref SDS 53
BM0778 - PR5X
BM0780 - ..
BM0781 - o. Aerospace company is initially implementing the "organizational memory"
BM0782 - component of the architecture. Then define "organizational
BM0783 - memory" based POIMS explanation of "intellectual capital,"
BM0784 - ref OF 5 1101, and explain this is supported by Doug
BM0785 - Engelbart's work that defines "daily working information" as
BM0786 - shown in the record on 000327, ref SDS 18 3971, which further
BM0787 - cites Doug's original article. You can go on to cite other
BM0788 - folks like Gelertner, Drucker, Covey, etc.
BM0790 - ..
BM0791 - [On 040720 2nd draft organizational memory was used for SDS
BM0792 - Standard, ref SDS 53 PR5X, and Engelbart, Drucker, Covery,
BM0793 - etc., were cited in References. ref SDS 53 CE4N
BM0795 - ..
BM0796 - p. Jeff Conklin's work defining "organizational memory" and
BM0797 - reviewed on 010420 provides another source that may be helpful.
BM0798 - ref SDS 21 IE4M
BM0800 - [On 040720 Conklin's observation that organizations have a
BM0801 - weak ability to remember the past was cited in Business Case
BM0802 - section. ref SDS 53 DM58
BM0804 - ..
BM0805 - q. Have to run.
BM0807 - ..
BM0808 - r. Rod
BM0810 - ..
BM0811 - s. Post Script:
BM0813 - We use correspondence, like this letter, to convert memory of
BM0814 - verbal discussion, pondering, musing and thinking, see
BM0815 - explanation on 950204 of the problem SDS solves. ref SDS 6
BM0816 - 0550, into a physical object that provides permanence, and
BM0817 - something that can be managed, and to verify accuracy, and to
BM0818 - flesh out ideas, sharpen personal understanding, provide a
BM0819 - deliverable to others they can use to understand their own
BM0820 - ideas in the context of objectives, requirements, commitments
BM0821 - and relevant history. Having taken time to help ourselves and
BM0822 - others to understand and follow up correctly, we can invest
BM0823 - this intellectual capital in an SDS record to continue getting
BM0824 - benefits, rather than allow critical detail to become useless
BM0825 - information that people want to delete, as related by a Aerospace company
BM0826 - member of the Architecture Committee, reviewed on 040610.
BM0827 - ref SDS 46 CT4L
BM0829 - ..
BM0830 - t. There are so many good reasons for sending confirming letters
BM0831 - in the environment of SDS Knowledge Space that it is exhausting
BM0832 - just trying to list them all.