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: September 11, 2003 03:10 PM Thursday; Rod Welch

Gary getting SDS on Aerospace company Intranet; boss asks for knowledge capture.

1...Summary/Objective
2...Schedule Slipping combat Budget Reduced by 50%
3...Budget Reduced by 50% and Schedule Slipping
4...Integrating Systems for combat Deliverables Planned
5...Planning to Integrate Systems for combat Deliverables
6...Knowledge Capture Assignment to Develop Template for Micorsoft Word


..............
Click here to comment!

CONTACTS 

SUBJECTS
SDS Records on Intranet ACE

0403 -
0403 -    ..
0404 - Summary/Objective
0405 -
040501 - Follow up ref SDS 5 0000, ref SDS 4 0000.
040502 -
040503 - Gary sent a letter today to a contact at Aerospace company in the Seattle
040504 - facilities, Darryl Satten, confirming prior discussions about need to
040505 - develop capabilities for transferring SDS records on the  combat project
040506 - to the Aerospace company intranet using a system called ACE.
040508 -  ..
040509 - Sent a letter congratulating Gary for taking one small step for
040510 - Aerospace company, and one giant leap for civilization.
040511 -
040512 -
040513 -
040514 -
040515 -
0406 -

SUBJECTS
Schedule Slips 5 Months Repeating Mistakes of Past Major Projects
Integrate Systems on  combat Planned to Reduce Impace on Schedule and B
Budget 2004 Reduced 50% Hiring Plans Reduced Planning to Integrate FC
50% Budget Reduced for 2004 Hiring Plans Reduced Planning to Integrat
Schedule CPM WBS Correlate Action Items to Project Control SDS Tip of
Action Item Review Failed to Meet on Expanding Span of Attention to G
Budget 2004 Reduced 50% Hiring Plans Reduced Planning to Integrate FC
Budget 2004 Reduced 50% Hiring Plans Reduced Planning to Integrate F
Integrate Systems on  combat Planned to Reduce Impace on Schedule and B

1311 -
131201 -  ..
131202 - Schedule Slipping  combat Budget Reduced by 50%
131203 - Budget Reduced by 50% and Schedule Slipping
131204 - Integrating Systems for  combat Deliverables Planned
131205 - Planning to Integrate Systems for  combat Deliverables
131206 -
131207 - Gary called later in the afternoon and advised that he was asked to
131208 - attend an unscheduled meeting today on planning and integrating
131209 - systesms to reduce the impact on achieving original project schedule
131210 - goals.  He further explained that the 2004 budget has been reduced by
131211 - 50%.  This aligns with the report on 030830 that the schedule has
131212 - slipped by 5 months. ref SDS 5 W166  Today, further schedule revisions
131213 - were reviewed to balance budget cuts, with the aim to plan for getting
131214 - as much done as possible under the circumstances.
131215 -
131216 -     [On 040716 budget cut for  combat because of slow progress; 75% of
131217 -     critical technologies immature. ref SDS 9 0001
131219 -  ..
131220 - The team developing plans to integrate systems seemed to have a good
131221 - understanding for technical objectives and solutions.  There was
131222 - continuing concern that coordination with the customer on identifying
131223 - requirements is causing frustration and confusion that slows progress
131224 - on the work.
131226 -  ..
131227 - On 030826 Gary discusses plans for action item review. ref SDS 3 VV5I
131228 - A few days later, on 030828 Gary planned to review action items with
131229 - Paul Lowe; there was consideration to include Gary's boss, Steve,
131230 - because the customer asked for access to the history of work, and so
131231 - showing a history of attention and progress on action items shows
131232 - attentive management. ref SDS 4 SF3Q  Later Gary submitted a printed
131233 - report showing pending action items to Paul, and requested notice when
131234 - Paul can meet for review.
131236 -  ..
131237 - Gary related today that Paul has not had time to meet on reviewing the
131238 - action item report Gary submitted last week.  Failure to review action
131239 - items causes slow progress that results in missing schedule and budget
131240 - targets reported today. ref SDS 0 504F
131241 -
131242 -
131243 -
131244 -
131245 -
131246 -
1313 -

SUBJECTS
Lessons Learned Capture Knowledge Steve Assigns Engineer at Aerospace c  pany to
Knowledge Capture Steve Assigns Engineer at Aerospace company to Invest  ate for
Goldman, Steve Requests Knowledge Capture Steve Assigns Engineer at B
Knowledge Capture Steve Assigns Engineer at Aerospace company to Invest  ate for

1806 -
180701 -  ..
180702 - Knowledge Capture Assignment to Develop Template for Micorsoft Word
180703 -
180704 - Follow up ref SDS 5 TY9H.
180705 -
180706 - Gary's boss, Steve, has asked another member of the team to work on
180707 - finding a template for Microsoft Word to support "knowledge capture"
180708 - for reporting project history.  Gary mentioned that he helped Steve
180709 - identify the phrase "knowledge capture" for summarizing the objective
180710 - to preserve lessons learned from daily operations on the  combat project
180711 - that can guide the work going forward, as Gary is doing with SDS using
180712 - Communication Metrics practices, explained on 001219. ref SDS 1 4W4L
180713 - The first of the eight (8) steps calls for capturing the record.
180714 - ref SDS 1 YR7O
180715 -
180716 -     [On 040203 growing demand for SDS work product shows this
180717 -     assignment has been accomplished. ref SDS 8 JX5M
180719 -  ..
180720 - This initiative appears to support Bruce's report on 030830 that hard
180721 - won experience on past projects yielded important lessons that are
180722 - difficult to remember without a record of project history because the
180723 - patterns of cause and effect are complex and therefore subtle, i.e.,
180724 - counterintutiive, which makes the lessons hard to learn. ref SDS 5
180725 - TY9H
180727 -  ..
180728 - This new assignment is another small step toward transformation from
180729 - information to a culture of knolwedge, when Gary worried about being
180730 - too successful capturing relevant history of organizational memory
180731 - would lead to more demands on his time than one person can meet,
180732 - reviewed on 030830. ref SDS 5 8490  It is not clear that Steve is
180733 - planning to give Gary help, but investigating tools is a first step in
180734 - that direction.
180736 -  ..
180737 - Previously, Steve wanted a "history button" to improve meetings, and
180738 - at that time, Paul Lowe identified Gary as the "history button" on the
180739 -  combat project, because Gary is using SDS for performing Communication
180740 - Metrics to support the project, reported on 030821. ref SDS 2 NH5N
180742 -  ..
180743 - On 030828 Steve evidently was asked by customer reps with the US Army
180744 - if project history related during a meeting to explain progress on the
180745 - work was documented.  The record indicates that Steve reported to the
180746 - customer that Gary is keeping a good record of project history.
180747 - ref SDS 4 SE7L
180749 -  ..
180750 - This representation, along with providing access to the project record
180751 - on Aerospace company's Intranet, called ACE, also, requested on 030828,
180752 - ref SDS 4 SE5X, support Gary's letter today to Darryl on installing
180753 - the SDS record on ACE. per above. ref SDS 0 0001
180755 -  ..
180756 - The record of (1) identifying Gary as the "history button" on the
180757 - project; and, (2) telling the customer that Gary is keeping a good
180758 - history, conflict with asking someone else to investigate finding a
180759 - template for using Microsoft Word to capture project history.  Lapses
180760 - and conflicts in human memory demonstrate limited span of attention
180761 - causing lack of awareness that capturing history is capturing
180762 - knowledge.  Conflicting actions from failure to remember correlations,
180763 - implications and nuance from project history are caused by information
180764 - overload that prevents people from investing time for deliberative
180765 - analysis to align understandings from one moment to the next, because
180766 - the tools they are using do not support command and control of the
180767 - record, as called out in POIMS. ref OF 6 1113
180769 -  ..
180770 - Gary later talked to the person given this new assignment and expects
180771 - to demonstrate how SDS implements Communication Metrics, explained on
180772 - 001219, ref SDS 1 4W4L, that accomplishes Steve's request for
180773 - knowledge capture, per above, ref SDS 0 HA6I, as Steve related
180774 - previously to the US Army on 020828, ref SDS 0 HA70, and noted by Paul
180775 - Lowe in comments during a meeting where Steve asked for a "history
180776 - button," reported on 030821. ref SDS 2 NH5N
180777 -
180778 -     [On 040102 history using SDS shows support for capturing lessons
180779 -     learned. ref SDS 7 OL8K
180781 -      ..
180782 -     [On 040302 growing demand for SDS work product shows this
180783 -     assignment has been accomplished. ref SDS 8 JX5M
180784 -
180785 -
180786 -
180787 -
180788 -
180789 -
180790 -
180791 -
180792 -
180793 -
180794 -
1808 -