Methods, Not Methodology (4): Effective Meetings
来源:互联网 发布:歌曲网络认识你 编辑:程序博客网 时间:2024/06/05 23:57
The Problems
Two problems:
- Even there're already tons of articles and books talking about the meeting efficiency and effectiveness, but "too many meetings", "meeting takes too long" are still the most popular items in retrospective meetings.
- People complained the meeting efficiency but did nothing to change it, especially never changed the behavior of themselves.
What can we do to improve it?
The General Reasons
- Well, the first problem (too many meetings) is actually not a meeting problem. It's a problem related to team maturity.
- The second problem(People keen to blame others but never change themselves) is also a problem has nothing about meeting.
- Lack of awareness of effective rules is always a reason candidate.
The Observed New Reasons
I won't repeat well known reasons here. I just share something new based on my observation. "new" is not really new. It means something people keen to ignore even they know it, whatever consciously or subconsciously. Here they are:
- Lack of attention to the purpose of holding a meeting
- Lack of attention to the purpose of a specific meeting
- Emphasizing the function/skills of facilitator removes some obligation from individual attendees.
Also I noticed the existing guidelines are usually verbose. There could be a short checklist to reminder people some principles, bad smells and good practices. At the end I will try to provide one.
The Purpose of Holding a Meeting
When should we call for a meeting? When there's some discussion (bidirectional communication) needed. It means:
- Don't hold a meeting when you just want to announce something
- Don't hold a meeting when you just want some kinds of report
- Don't attend a meeting if you don't want to say something
- Don't attend a meeting if you don't need to say something. Do something else valuable.
The purpose also defines attendees:
- Don't gather people together if you just want to talk to them one by one, or one group by one group
The Purpose of a Specific Meeting
You can discuss a single fact/idea from infinite perspectives, but only few of them are related to current purpose. Just visualize / highlight / emphasize the purpose of this meeting at any time you think it's wandering off the topic.
Individual Responsibility
We emphasized the facilitating skills too much. It gives an illusion that it's the facilitator's responsibility to make the meeting efficient and effective. It's true, but it doesn't mean the individual attendees do not need to do anything. On the contrary, attendee's behavior is more important than the facilitator's skill in terms of the efficiency and effectiveness. For example, when attending a meeting, ensure yourself:
- Follow the rules and practices
- Help to maintain the rules and practices
- Be prepared
- Raise your concern, contribute your thought
- Don’t interrupt others, give others opportunity to interrupt you
- …
A Pocket Guide for Efficient and Effective Meeting
One Page Common Sense
- Agenda
- Ground Rules
- Be Prepared
- Focused
- Robert’s Rules of Order
Bad Smells
- Dominating individuals : Control them
- Silent individuals : Ask them
- Silent groups : Separate meeting
- Premature voting : Discuss and share understanding first
Practices
- General ground rules
- on time
- one conversation
- no phone ring
- Speak in turn
- Yellow card and red card : warning the speaker in a polite and visual way
- Time-boxed for non-essential topic.
- Summarize
- Parking lot : put extend topic there, keep track on the main topic
- Define the scope
Individual Responsibilities (Repeated):
- Follow the rules and practices
- Help to maintain the rules and practices
- Be prepared
- Raise your concern, contribute your thought
- Don’t interrupt others, give others opportunity to interrupt you
Validated Meeting
- Make sure everyone leaves knowing the next step, and the reason.
Other blogs of the Methods, Not Methodology series:
- Methods, Not Methodology (I): Validated Code Review
- Methods, Not Methodology (2): Effective and Validated 5 Whys
- Methods, Not Methodology (3): Knowing Everything at the Beginning?
- Methods, Not Methodology (4): Effective Meetings
- Methods, Not Methodology (2): Effective and Validated 5 Whys
- Methods, Not Methodology (I): Validated Code Review
- Methods, Not Methodology (5): Predict without Estimation
- Methods, Not Methodology (3): Knowing Everything at the Beginning?
- Meetings
- Meetings
- {Effective Java} Chap 7 Methods
- toj2894 Meetings
- 2894. Meetings
- It's Not Just Standing Up: Patterns of Daily Stand-up Meetings
- Deprecated Thread methods are not supported.
- Abstract methods do not specify a body
- Effective Objective-C 2.0: Method Swizzling to Debug Opaque Methods
- Common Sentences for Scientific Writing (4 Chapter 2. Proposed methodology)
- Programming Methodology?
- website methodology
- 17.5.4 Override methods
- java程序打包成jar文件(自己实践和查网页解决,以中科院分词工具ICTCLAS5.0 为例)
- java动态代理学习笔记
- oracle sqlldr 数据导入错误Field in data file exceeds maximum length解决
- HTML5web开发框架
- Java的位运算符详解实例——与(&)、非(~)、或(|)、异或(^)
- Methods, Not Methodology (4): Effective Meetings
- 自定义加载Spring配置文件
- 你应该知道的Linux操作技巧
- 屌丝程序员的2012
- linux usb drivers开发
- 类与对象
- VS2008/C++环境配置 使用GDI+
- macosx下使用wireshark,报错There are no interfaces on which a capture can be done
- 由浅入深探究mysql索引结构原理、性能分析与优化