THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net
S U M M A R Y
DIARY: January 25, 2005 02:37 PM Tuesday;
Rod Welch
Gary called about using SDS for preparing technical documents.
1...Summary/Objective
..............
Click here to comment!
CONTACTS
SUBJECTS
Technical Documents 2 Worlds IT Wordprocessing Appearance Knowledge
3-layer Architecture Bridge 2 Worlds Structure for SDS to Perform Kn
PDF Convert to Text Using Microsoft Word Addon Works Better than Omn
Strategic Vision Gary Johnson SDS Supports Com Metrics 2 Worlds Brid
Invested Time Developing Efficient Ways to Print Documents for Infor
Save Time Working on Familiar Things in Familiar Ways Foundational D
Documents Expand SDS Support Collaboration SDS Engineering Managemen
Align Link Communication Objectives Requirements Commitments Working
4210 -
4210 - ..
4211 - Summary/Objective
4212 -
421201 - Follow up ref SDS 10 0000, ref SDS 9 KU85.
421202 -
421203 - Made some progress today on transformation from documents to Knowledge
421204 - Space. Gary is considering using SDS for preparing technical
421205 - documents based on work this past year that demonstrated practices.
421206 -
421207 -
421209 - ..
4213 -
4214 -
4215 - Progress
4216 -
421601 - Submitted ref DIT 1 0001 to Gary confirming telecon discussion on his
421602 - work using SDS for engineering management on preparing technical
421603 - documents. On 040402 Gary reported to colleagues on the job that his
421604 - goal for this year is to learn a greater share of SDS features for
421605 - performing the eight (8) steps of Communication Metrics. ref SDS 6
421606 - TO8V This addresses Woody's question on 041118 on requirements for
421607 - SDS support. ref SDS 9 KU85 Initially, Gary sent an email saying...
421608 -
421609 - Here are my recent records. The only one of real interest is the
421610 - record today on Planning and Creating Technical Documents, which
421611 - covers recent experience with the document I am currently working.
421613 - ..
421614 - Thanks,
421616 - ..
421617 - The letter to Gary says...
421618 -
421619 - 1. Pleased to hear today that you have begun considering SDS for
421620 - editing and managing work on technical documents at Boeing, per
421621 - your call this morning.
421623 - ..
421624 - 2. This applies the general rule of slowing down to learn how to
421625 - speed up, where the long way around is the short way there.
421627 - ..
421628 - We discussed on the telephone today that Gary has begun applying SDS
421629 - for Communication Metrics on preparing technical documents. This
421630 - gives people command and control of the record, set out in POIMS.
421631 - ref OF 5 TO6N
421633 - ..
421634 - Managing knowledge to construct documents takes a lot of hard work
421635 - without SDS, reported on 000307. ref SDS 2 767G This creates a
421636 - 2-worlds problem of transformation from documents to Knowledge Space
421637 - in order to save lives, time, and money, explained in NWO, ref OF 14
421638 - TF6H, because people initially feel that working intelligently is
421639 - unnecessary overkill, explained in POIMS ref OF 7 4079
421641 - ..
421642 - Doug Engelbart suggests a gracefull change occurs, reviewed on 000327,
421643 - ref SDS 3 1530, but actually bridging the gap between information and
421644 - knowledge is a significant emotional and traumatic struggle for
421645 - reasons Morris cited on 890809, ref SDS 1 2079, and illustrated by
421646 - experience with the ASB filing on SDS for a standard on intelligence
421647 - support, reported on 040615. ref SDS 7 DN8O
421649 - ..
421650 - Gary feels there is a trade-off between using SDS to improve the
421651 - quality of the work, or using information technology to improve the
421652 - appearance of the work. Most people equate better appearance with
421653 - better quality, rather than better accuracy, thoroughness, and
421654 - analysis using dynamic linking to "connect the dots" showing causation
421655 - that are enabled by SDS support for Knowledge Space.
421657 - ..
421658 - We discussed today that an interim approach to transformation is
421659 - preparing documents in Microsoft Word and enter contemporaneous notes
421660 - on what was done and why in SDS, along with who was consulted, peer
421661 - review, links to meetings and sources, explained in POIMS. ref OF 5
421662 - TO6N
421664 - ..
421665 - Letter to Gary continues...
421666 -
421667 - 3. Departing from a familiar paths risks a known outcome against
421668 - hope for a better outcome for which there is little evidence
421669 - save the elegance of an idea; but, which, almost certainly,
421670 - will be worse the first few times around while we struggle to
421671 - discover and refine a better process. ref DIT 1 JL6I Risks of
421672 - first adopters pioneering a path to the future were reviewed in
421673 - the record on 040615 when SDS was used to prepare a technical
421674 - document on the SDS standard for intelligence support that
421675 - applies organizational memory. ref SDS 7 QW6U Later on 040709
421676 - Gary found SDS intelligence support was helpful for preparing
421677 - technical documents, ref SDS 8 RG7H, which today seems is being
421678 - considered for implementation. This follows the pattern of
421679 - exposure, awareness, gaining experience, then trying a new way
421680 - of working, set in strategy and plans on 040102. ref SDS 5 8Q3N
421682 - ..
421683 - 4. Congratulations, applause, "...at-a-boys" abound for ultimate
421684 - results, yet most of those on the ground at the time scream
421685 - against, resist, and obstruct change, ref DIT 1 TM7J, because
421686 - immediate needs are always delayed by the process of
421687 - discovering and testing advance. For example, using SDS yields
421688 - ideas for improvements, and making those improvements delays
421689 - doing the work, which SDS is designed to improve, by hours,
421690 - days, week, months. This creates pressures to avoid
421691 - fundamental improvement, which can only be overcome
421692 - occasionally when enabling forces come into alignment, and
421693 - people are around with vision and courage to act on faith in
421694 - ideas and perhaps the experience of someone else that indicates
421695 - better results might occur by departing from familiar ways.
421697 - ..
421698 - 5. That is why revolutionary results require pioneers with faith
421699 - to take risks venturing into unfamiliar territory, as you
421700 - relate today, based on the strength of available evidence.
421701 - ref DIT 1 QN9G
421703 - ..
421704 - 6. Welcome to the revolution. ref DIT 1 YN9L
421706 - ..
421707 - 7. Your record on 050110 anticipates problems converting docs
421708 - created in HTML, which SDS supports, with Microsoft Word as a
421709 - document file. ref DIT 1 00W2 Please comment on this in
421710 - relation to the attached doc file converted from POIMS.
421712 - ..
421713 - 8. When time permits, call to discuss your record today. I looked
421714 - through it, as you requested, and perhaps there are some useful
421715 - implementation ideas once we collaborate a bit on issues,
421716 - obstacles, and opportunities. ref DIT 1 ZP5M
421718 - ..
421719 - Gary called back and seemed to comment that this experiment, which was
421720 - performed on the technical document for the ASB filing on SDS, shows
421721 - that technical documents can be created in SDS to add links for
421722 - command control, then read into a word file to provide formatting that
421723 - meets company requirements for appearance.
421724 -
421725 -
421726 -
421727 -
421728 -
421729 -
421730 -
421731 -
421732 -
421733 -
421734 -
421735 -
421736 -
421737 -
421738 -
421739 -
421740 -
421741 -
421742 -
421743 -
421744 -
421745 -
421746 -
421747 -
421748 -
421749 -
421750 -
421751 -
421752 -
421753 -
421754 -
421755 -
421756 -
421757 -
421758 -
421759 -
421760 -
421761 -
421762 -
421763 -
421764 -
421765 -
421766 -
421767 -
421768 -
421769 -
421770 -
4218 -