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: April 21, 2004 01:16 PM Wednesday; Rod Welch

Gary submits Aerospace company requirements for conducting meetings.

1...Summary/Objective


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

CONTACTS 

SUBJECTS
Information Overload Garden Eden Email Meetings Grazing Foraging
Not Enough Time to Write Notes, Executives Need Com Manager
50% Meetings Useful Record Prepared Communication Biggest Risk Enter
Meetings Procedures Good Management Mandatory at Aerospace company but   t Perf   07
Meetings Procedures Industry Management Standards to Make People Pro
Report Meeting Contemporaraneous Using SDS and a Headset in Real Tim
Facilitator Improves Meetings Without Speaking Com Manager Prepares
Subject Meetings Wander Away in Conversation Dialog Email SDS Links
Meetings Productivity Improved by SDS Intelligence
Facilitate Meetings Be Prepared Writing Record Organizational Memory
Meetings Listening Intelligence Understanding Follow Up Alignment
Agenda Distrubuted Prior to Meetings Scribe Assigned to Prepare Meet
Scribe Assigned to Prepare Meeting Minutes, Procedures for Good Mana

3015 -
3015 -    ..
3016 - Summary/Objective
3017 -
301701 - Follow up ref SDS 5 2937, ref SDS 6 3456.
301702 -
301703 - Received ref DRT 1 0001 dated today from Gary listing good management
301704 - practices that are "mandatory" at Aerospace company for conducting productive
301705 - meetings.
301706 -
301707 -    1.  This is from the *mandatory* Teamwork Training at Aerospace company:
301709 -         ..
301710 -    2.  Effective meeting preparation involves planning the purpose, agenda, time,
301711 -        and information
301712 -
301713 -        •  The purpose explains why the meeting is being held
301714 -
301715 -        •  The agenda outlines the specific items to be covered
301717 -            ..
301718 -        •  The time indicates the expected length and breakdown of the
301719 -           meeting
301721 -            ..
301722 -        •  The information covers all the documentation or
301723 -           presentations that will be necessary for the meeting
301725 -         ..
301726 -    3.  The facilitation of the meeting involves four key roles:
301728 -         ..
301729 -        The Team Leader is responsible for managing the agenda of the
301730 -        meeting
301731 -
301732 -        •  The Coordinator/Facilitator tries to keep everyone involved
301733 -           and participating
301735 -            ..
301736 -        •  The Recorder records the important decisions and action
301737 -           items made by the team
301739 -            ..
301740 -        •  The Meeting Participant shares in the responsibility of
301741 -           making the meeting a success by s/he contributing to the
301742 -           process
301744 -         ..
301745 -    4.  As I said, their own materials tell them what to do, and they
301746 -        aren't doing it.
301748 -  ..
301749 - Gary's letter, per above, ref SDS 0 0001, reflects reporting in his
301750 - record, also, today on 040421. ref SDS 12 0001
301752 -  ..
301753 - Gary commented yesterday on the challenge people face applying a level
301754 - of diligence consistently that enables good management. ref SDS 11
301755 - 6J6T  An example is planning by the OHS/DKR group on 001126 to use
301756 - information technology for managing "knowledge," rather than SDS.
301757 - ref SDS 7 4E3X
301759 -  ..
301760 - "Mandatory" practices are rarely used because requirements and
301761 - practices for good management are "hidden in plain sight" for
301762 - conducting meetings.  For example, on 980722 Morris reported that good
301763 - practices are posted on the wall in conference rooms at Intel.
301764 - ref SDS 5 2937  Later on 000116 50% of the records for meetings are
301765 - useful. ref SDS 6 3456  A common industry practice is to rely on the
301766 - Powerpoint file to report results of meetings, shown in the record on
301767 - 980722. ref SDS 5 4105  On 960317 an accurate record, like SDS
301768 - supports, ref SDS 4 3004, seems "futuristic," noted earlier at Intel
301769 - on 960315. ref SDS 3 4545  Equally, ISO criteria for management calls
301770 - for traceability to original sources, reviewed on 950721. ref SDS 1
301771 - 1740  Later on 951026 compliance professionals report that
301772 - organizations prepare requirements for good management in order to
301773 - obtain ISO recogniation, illustrated by the list submitted today, per
301774 - above, ref SDS 0 0001, but are unable to perform the requirements,
301775 - ref SDS 2 3245, further noted by Gary today. ref SDS 0 F53Q
301777 -  ..
301778 - On 020217 DOD requirements recognize that meetings are the primary
301779 - "business unit" of management. ref SDS 8 1332  Command and control
301780 - fails, however, because people cannot find information relevant to
301781 - current context derived moment-to-moment from situational awareness,
301782 - ref SDS 8 9360  A program manager at DOD reported that SDS supports
301783 - requirements for command and control of the work. ref SDS 8 3105
301785 -  ..
301786 - DOD sets out "mandatory" requirements for good management in FAR that
301787 - have the force of law, ref SDS 9 XV7L, but cannot obtain compliance,
301788 - reported on 020504. ref SDS 9 NS6F
301790 -  ..
301791 - On 030826 Sean O'Keefe explains that when people cannot accomplish
301792 - requirements for good management using tools, methods and skills at
301793 - hand, then "mandatory" requirements are applied as "suggestions" and a
301794 - goals to reach, rather than report failure to perform due to lack of
301795 - time and money. ref SDS 10 8K4G
301796 -
301797 -
301798 -
301799 -
301800 -
301801 -
301802 -
301803 -
301804 -
301805 -
3019 -