TrainingConferencesAbout UsContact UsAdvertiseSQE.com

StickyMinds.com: brain food for building better software

Join

Join

Clarify Your Search Criteria
Tips on Using Our Search Feature(s)
StickyMinds.com Home
ResourcesEventsTopicsPowerPassJobs
Software Testing & QA Online Community  >  Detail: The ROTI Method for Gauging Meeting Effectiveness


A StickyMinds.com Original
Article Picture
The ROTI Method for Gauging Meeting Effectiveness

By Esther Derby

Send This Content to a FriendGet a Short Link to This ContentPrint This ContentSee User Comments About This Content

Summary: When I visit software organizations, I often hear complaints that we spend too much time in meetings! Many people spend a significant portion of each day in meetings. Wouldn’t it be great to give some of that time back? You can return time to your staff by eliminating unnecessary meetings and improving the ones that remain on the calendar. And when staff has more time, it means your group is more likely to meet its goals.


Tricentis
Be Clear on the Purpose of the Meeting  
If there isn’t a goal, a meeting usually doesn’t help. Bring people together when you have a specific goal or purpose for the meeting. My rule of thumb is to have one and only one purpose for a meeting. If you feel you have to have two purposes in the meeting, separate them within the meeting. Give each issue a time limit and after that issue has been solved declare that part of the meeting over.  
 
Then move on to problem solving. Prioritize the problems and excuse the people not directly involved in the problems you intend to cover. If you start problem solving on the first issue, you may not be able to get to the most important issues. Most likely, the people not directly involved in solving the specific problem will feel their time is not well spent. 
 
Have a Plan 
An agenda helps lay out the steps you’ll go through to accomplish the purpose of the meeting. Distributing an agenda beforehand allows people time to prepare or to assess whether their attendance at the meeting will add value. The agenda might look like this: 
  • Review decision criteria from June meeting (5 minutes) 
  • Site visit summary and assessment from Vendor 1, Vendor A, Vendor Q (20 minutes each) 
  • [break] (10 minutes) 
  • Review ranking process (5 minutes) 
  • Rank vendors against criteria (60 minutes) 
  • Next steps—actions and assignments (15 minutes) 
  • Meeting wrap-up (10 minutes)
An over-stuffed agenda is a common problem. I saw a meeting agenda that listed twenty topics for a one-hour meeting. Three minutes per discussion topic might be reasonable—or it might not. Thinking through the agenda will help avoid the horrible, rolling agenda problem: when we don’t finish the agenda, we roll those items into the next week. So we have an overstuffed agenda again! 
 
Invite the Right People 
Invite the people needed to accomplish the purpose of the meeting. If the goal of the meeting is to make a decision, are the people who have the responsibility and authority to make the decision in the room? Don’t complicate matters and muddy the meeting by including innocent bystanders. 
 
Decide if a Meeting Is Really Needed 
It really helps to have a group together to understand all sides of a complex problem, reach a group decision, generate ideas or alternatives, and solve problems. If the purpose of the meeting is to disseminate information, an email might suffice, unless the information is emotionally charged. Very few people will be upset if you reduce the number of meetings on their calendar. 
 
Consider replacing a serial status report meeting with one-on-one meetings. By eliminating the serial status meeting, you’ll free up staff time. I can almost guarantee that you’ll hear about problems and obstacles in a one-on-one meeting that won’t come up in a group setting, unless there is very high trust in your group. 
 
Create a Meeting that Makes the Best Use of the Participant’s Time 
Brandon, a manager in an internal IT department, noticed that people were looking bored in his weekly two-hour staff meeting. Brandon spent ten minutes on corporate and department information, and then each team had roughly thirty-five minutes to update him on status. Brandon tried to spice up the meeting with jokes, fun activities, and treats. It didn’t help. 
 
Brandon’s group worked with three separate products with little crossover. Except for the first ten minutes, the discussion was irrelevant to two-thirds of the group. Cookies weren’t a big enough payoff to make up for being bored for seventy minutes out of every meeting. 
 
Brandon dropped his weekly staff meeting in favor of an email that outlined important information that all three groups needed to know. And he set up separate forty-minute meetings for each team. This arrangement didn’t take up any more of his time and gave back over an hour each week to team members. 
 
Work on Improving Meeting Effectiveness 
If you host an ongoing periodic meeting, you have a great opportunity to make incremental improvements. Start asking for feedback on your meetings, and be willing to make changes based on the information you receive. At the end of the meeting, ask participants to rate their Return on Time Invested (ROTI) using this scale: 
 
0 = Lost Principle: No Benefit Received for Time Invested 
1 = a little better than 0 
2 = Break-Even: Received Benefit Equal to Time Invested 
3 = a little less than 4 
4 = High Return on Investment: Received Benefit Greater than Time Invested 
 
I’m happy if most people feel the meeting was a break-even investment. Still, there’s almost always room for improvement. As each participant states his/her rating, build a histogram that shows the results. It might look like this:  
Meeting ROTI 
4 | 
3 || 
2 |||| 
1 | 
0 | 
 
Even if everyone rated the meeting at four, it’s worth doing the next step to find out why the meeting worked well so you can repeat your success. Ask the people who rated the meeting a two or above what specifically they feel they  
received for their time investment. Ask the people who rated the meeting at zero or one what they wanted but didn’t get.  
 
Then ask what specifically worked, what didn’t work, and for possible changes. Even if everyone gave equally positive feedback, it’s worth doing the next step to find out why the meeting worked well so you can repeat your success. Don’t assume that a rating of zero means you did a poor job. A zero rating may simply mean that the person didn’t care about the topic. That’s easily fixed by publishing an agenda ahead of time. The benefit you receive for your time can come in several forms, depending on the purpose of the meeting. 
 
Here's where you get value in meetings: 
 
Information Sharing:  
Did you receive answers to questions or hear information that allowed you to overcome an obstacle, move forward on your tasks, or avoid rework?  
 
Decision-Making:  
Did the meeting result in a decision that allowed you to move forward?  
 
Problem Solving:  
Were the people in the meeting able to succinctly state a problem, generate candidate solutions, or decide on a course of action? 
 
Work Planning: Did you leave the meeting with a clear idea of what you and your colleagues will be working on this week? Do you understand the goal you’re striving for and understand what the priorities are?  
 
What do you find makes a meeting effective? What have you done to improve meetings in your group?  
 
Acknowledgements 
I first learned about the ROTI method for gauging meeting effectiveness and gathering feedback from my colleague  
Steve Smith. You may visit his website at http://www.stevenmsmith.com/.


About the Author
Esther Derby provides high-leverage facilitation to start projects on a solid footing, assess the current state, and capture lessons learned. She also coaches technical people making the transition into management and is one of the founders of the AYE Conference (www.ayeconference.com). Read more of Esther’s musings on the wonderful world of software at www.estherderby.com and on her weblog at www.estherderby.com/weblog/blogger.html. Her email is derby@estherderby.com.

Back to Top
 

StickyMinds.com Weekly Column From 7/28/03 

Member Comments
Add Your CommentExpand Comments
 
Comment:    
by Giovanni Carlo Liuzza 8/7/2003

There are useful rules to develop and conduct effective Meeting. A more ambitious objective is that to conduct a team to achieve an effective communication, to become a cohesive team that communicates efficiently. The relational key is often the true substantial key of the success of a project

 
 
Comment:    
by Richard Whitehead 8/6/2003

I liked the article. Two points I have found to be very useful. 1) Even when you have an agenda, people will tend to run on about a topic that is important to them. It is important not to kill a valuable discussion, but it is also important not to kill your agenda. Cut them off by scheduling a break-out meeting for the people directly involved, or even a separate meeting for the whole group with just that one topic on the agenda. 2) There can be a phenomenon of "agenda creep" just like "requirements creep" on a project. Beware of people (even yourself, sometimes!) adding items to your agenda - always think about whether the right people will...Read On

 
 
Comment:    
by Tek Wallah 7/29/2003

It occurred to me today that very few of the meetings I attend these days follow the traditional format. Most are ‘teleconferences’ with more people attending by telephone than in person. It has both the advantage and disadvantage that most people multitask – working at their desk while keeping half an ear on the conversation. I don’t think we’ve worked out the ‘rules’ for running a successful online meeting yet. Perhaps that would be a fruitful topic for another article?

 
 
Comment:    
by Gene Fellner 7/29/2003

I saw a wonderful training film on this topic more than fifteen years ago and it is still the best I've seen. It was a British production entitled "Meetings Bloody Meetings," starring John Cleese of Monty Python and "A Fish Called Wanda," who recently replaced Q in the James Bond movies. It starts off with a new employee asking what the meeting will be about, and Cleese answers, "What do you mean? We have it every week!" When the newbie persists and asks why everyone needs to attend, Cleese says in exasperation, "Because it's the WEEKLY MEETING!" It all goes downhill from there on a journey only Cleese could lead. I highly recommend it for...Read On

Author's Response:
7/29/2003    
Hi, Gene -- That sound hillarious! I'm going to look for this film! Esther

 
 
Comment:    
by Gunasekarran Veerapillai 7/28/2003

Yes Esther. These are some good pointers to the PMs on conducting project Meetings. I have seen some Project Managers calling the team abruptly without any notice for some information sharing. A meeting without an agenda would drift away from the focus area.The number of participants is another factor, which determines the fruitful utility of the meetings. In Project meetings with large number of participants, most of them would be sitting idle without any valuable contribution. Unless one contributes to the agenda, their intake from the meeting proceedings will always be less. PMs should study the requirements of each person participating...Read On

Author's Response:
7/29/2003    
Hi,Gunasekarran -- You make a good point about the costs of impromptu meetings. I think there are probably some times when it does make sense to pull a team together for a quick unscheduled meeting… most of the time though, these meetings have a productivity price tag -- people scramble to re-schedule their meetings and drop their work. And the cost goes up when the call comes from higher in the organization – an impromptu meeting request from a VP can have a ripple effect throughout the organization. I wonder if any one sits down and calculates the cost before calling one of these meetings? (We could probably guess the answer.) Esther

 
 
Comment:    
by Robert E. Lee 7/28/2003

Nice points, Esther. Luke Hohmann points out that meetings creep into waste through participants fearing to "be there when something might be said." He recommends distributing agendas ahead of time, and distributing meeting notes so people not present can review what was discussed if they were not present. The agenda distribution allows people to come prepared, while the minutes distribution alleviates "I'd better attend just in case" attendees. The result is trimmer meetings that don't accumulate non-participants.

Author's Response:
7/29/2003    
Hi,Bob -- The flip side of distributing the agenda before hand is communicating relevant information after the meeting. I've seen groups where the extra attendees pile on because showing up at every meeting is the only way to find out what's going on. Some teams have one person act as their "scout:" he goes to all the meeting to bring back news to the rest of the team! It's better than having everyone go, but not as good as being intentional about communicating meeting results. Esther

 
 
Comment:    
by yogita sahoo 7/28/2003

We have faced similar problems with lengthy and unfocused meetings. Meetings with preset goals can still go hay-way if coordinators and attendees do not do the ground job prior to meetings. It's important not to get a RAW brainstorming topic or something that would invariably turn into lengthy discussions to meetings. Such topics should be half-dealt before the meeting. Another thing that helps is to prepare a "minutes of the meeting" and email it to the attendees. It should layout the important topics discussed, decisions made and action plans decided during the meeting. It helps everyone compile the essence of a meeting.... Really enjoyed...Read On

Author's Response:
7/28/2003    
Hi, Yogita -- Good point about distributing a record of the meeting. I've observed one problem with having one person take the minutes: they reflect what that person heard, which may be different from what other people heard. One way to solve that problem is to have someone record the minutes in public view as the meeting progreses. That way, if the recorder writes down something that doesn't quite capture what was intended, it can be fixed right then. I use flip chart paper and markers to do this, other people use whiteboards or capture the record using a PC and a projector. The important thing is that everyone can see what is being captured. Esther

 
 
Comment:    
by Gerold Keefer 7/28/2003

hello esther, thanks for pointing to one of the most crucial capabilities of an organisation: effective meetings. it would help to bring the purpose of your article more precisely accross, if the ROTI method referenced in the headline would have been actually described in the text. currently i see some good general hints. my personal eye-opener with regard to meetings was the article at www.rpi.edu/~goldsd3/sdd/debugging-meetings.pdf: "debugging meetings". regards,

Author's Response:
7/28/2003    
Hi, Gerold -- I've posted the details of the ROTI method on my blog http://www.estherderby.com/weblog/archive/2003_07_01_archive.html#105939914241597042 Esther

 
Back to Top



 
Ads By Google
What's This?
 
 



About Us   |   Contact Us   |   Terms & Conditions   |   Privacy Policy   |   RSS Feed



© 2013 StickyMinds.com. All rights reserved.
PNSQC

Tricentis



Agile Development Conference & Better Software Conference West