One of the interesting aspects of moving from a development role to QA is that I have become much more involved in managing process rather than just managing projects. Part of this is the nature of QA and part of it is the result of going from having to just manage my own work to having to coordinate a team of 25 people. Process now becomes just as important as technology to get the most out of each day. In today’s world I am asked to respond to changing needs at an ever increasing pace. And while we now live in a much more connected (social) world, meetings still form an important part of these processes. They allow decisions and consensus to be reached amongst teams and other related groups of people. That is why we still need events like Lotusphere. There are still some important things that are best done by taking people away from their desks and daily tasks and putting them together (hopefully physically) to focus on discussion about important topics.

I was recently reminded of the experience I had working for a large company in Australia with over 100,000 employees. As you can imagine with a company of that size it had accumulated a lot of inefficient processes. They decided to make a significant investment to improve those processes. One of the key areas that were identified to be addressed was meetings. Not only where meetings found to consume a significant proportion of many people’s time, it was established that the outcomes of meetings had a huge impact on the operating performance of the organization.

1. Take the average salary of an employee and double it to factor in the costs of providing an employee a desk, keeping them happy, and the opportunity cost of not having them doing something else. Multiply that by the number of people you have in a meeting and you soon start to see the true cost of each meeting.
2. Don’t schedule meetings without considering the availability of attendees. If you don’t your meeting may trigger any number of other meetings having to be rescheduled, or you having to reschedule this one. Lotus Notes has an awesome capability of displaying the availability of attendees and finding suitable time slots. Not everyone uses it. Of course this only works if everyone keeps their availability updated at all times.
3. Insist that meetings start on time. If key people vital to the success of the meeting don’t arrive within five minutes of the starting time, reschedule for a later time. It becomes too expensive to have people sitting around doing nothing, even for 15 minutes. If meetings start being cancelled you find attendees are more likely to be on time, reducing the need for further cancellations. If there are no vital people missing start the meeting on time. People who arrive late soon learn the importance of being on time. Note: Allow 2-3 minutes for people having time devices that are out by a minute or two (in those days these were always watches!)
4. It is even more important to end meetings on time than to start them on time. The ripple effect of meetings ending late is enormous as attendees from one meeting will often flow into a range of meetings being held immediately following ,causing these meetings to be late or rescheduled.
5. Don’t schedule meetings to run 30 minutes, 60 minutes etc. Instead schedule them to run for 25 minutes, 55 minutes etc. People need time to transition from one meeting to another. They need bio breaks and the chance to check their messages or maybe just the chance to collect their thoughts for the next meeting. Note: This doesn’t work unless meetings end on time!
6. Make the most of meeting time by keeping the content of the meeting focused on just those things that can only be done during the meeting. Meetings are not an effective way to present new information and then expect people to absorb that information in real time. Wherever possible ensure people are provided with as much information as possible beforehand so they can absorb it and provided meaningful dialog during the meeting where ideas can be discussed , debated and decisions made.
7. No Surprises!  Meetings tend to be more effective if there are no surprises in the meeting to which everyone must react/adjust.
8. Always have an agenda for the meeting, and stick to it. People can only be well prepared for a meeting if they have a clear understanding of what is to be discussed. Attendees have the chance to seek additional information and clarification before the meeting rather than wasting everyone’s time while in the meeting. Sometimes attendees may be able to suggest additional/alternative attendees that will lead to the meeting being more effective.
9. Keep meetings on track. Too many meetings get bogged down discussing side issues or detailed discussions between a small set of attendees that is often better taken offline rather than wasting the time of others at the meeting. Add up the cost of having all the other people tied up merely observing those private discussions.
10. Before the meeting ends take the time to recap the key decisions made and the action items that were assigned during the meeting to ensure everyone is clear of the meeting outcomes and their responsibilities coming out of the meeting. If the meeting is part of a series of meetings start the next meeting with a review of the action items to ensure they have been completed. If action items vital to this meeting were not completed reschedule the meeting to a later time.
11. Keep regular meetings to the same time/day. Too many times there is someone who participates in a series of meetings who feels his/her time is more important than everyone else’s and every time they have a scheduling conflict they force everyone else to reschedule to accommodate them. This often causes everyone else to have to reschedule other meetings resulting in chaos. Notes may be a great tool for helping you find suitable time slots for a meeting but it still can’t deal with the issues caused by having an attendee list where there is no common empty time slot. The solution… Force yourself to schedule new meetings that don’t impact on the schedule of others or train delegates who are empowered to represent you at meetings where you have a conflict.

Sadly I feel I may have forgotten some of the key points/recommendations made that are still highly relevant to what I am trying to deal with in my current role. Too often I am guilty of merely thinking of a meeting title, selecting an attendee list, and finding a time slot that is empty for everyone.  I click send and my task is complete. I may be scheduling plenty of meetings, but I can probably be doing a lot more to conduct effective meetings. Meetings that don’t waste quite as much of the company’s time. Meetings in which I have empowered attendees to make effective contributions leading to better outcomes for my employer.

So how are the meetings you attend or organize? Are there things you do, or can do, that make a difference?

Recent Blog Posts

273

Lotusphere 2012: Going Mobile Wed, Feb 15th 2012 9:23p Peter Presnell I had the honor of being included as part of the Blogger Program at Lotusphere 2011. Given IBM had paid for my conference ticket to attend the event and they were providing a nice comfortable seat at the front I felt compelled to live blog the OGS. My gadgetry at the event consisted of a aircraft carrier laptop along with a Blackberry Bold. When I looked around me I began to feel like a dinosaur (if not for the aircraft carrier, certainly the Blackberry!). True, I was probably the only blogger t [read] Keywords: domino ibm lotus lotusphere notes traveler apple application applications blackberry blogger enterprise facebook iphone laptop microsoft mobile security social software twitter wifi

317

Becoming Agile: Meetings Sun, Feb 12th 2012 5:27p Peter Presnell One of the interesting aspects of moving from a development role to QA is that I have become much more involved in managing process rather than just managing projects. Part of this is the nature of QA and part of it is the result of going from having to just manage my own work to having to coordinate a team of 25 people. Process now becomes just as important as technology to get the most out of each day. In today’s world I am asked to respond to changing needs at an ever increasing pac [read] Keywords: lotus lotusphere notes development

462

Lotusphere 2012: The Good, The Bad, and The Ugly Sun, Feb 5th 2012 4:15p Peter Presnell Lotusphere is over for another year. 2012 was my third Lotusphere. This year was a crazy crazy week just as it had been in each of the two previous years. I had the chance to renew many treasured friendships as well as meet many people for the first time. My employer, GBS, has offices all around the world, so Lotusphere also provides a chance for me to meet face to face with a great many of the people with whom I work every day. I see signs that the event is changing. Many legends of the past n [read] Keywords: connections ibm lotus lotusphere symphony blogging community laptop mobile office social software twitter wifi

334

Getting The Most From Lotusphere Tue, Jan 10th 2012 7:39p Peter Presnell This year will be my third Lotusphere and first IBM Connect. Compared with a great many people attending I am still a newbie. I certainly was not as well prepared as I would have like for my first (or second) Lotusphere and so I would like share a few tips of some of the many things I have learnt in my preparation for this year. The community itself exists all year round. Lotusphere is the only time in which many of us are together in the same place at the same time. When I try to prioriti [read] Keywords: administration connections ibm lotusphere notes community google ideajam mobile network

293

RAT -- Part 2: Smoke Testing Sun, Jan 8th 2012 9:02p Peter Presnell In Part 1 of this series, I provided a general summary of some of the key concepts of Rapid Application Testing. Today I would like to take a closer look at one of the more important aspects of RAT.... Smoke tests. When developing a set of test cases to test an application the most important are smoke tests. Smoke tests can mean different things to different people. For me, smoke tests are the tests you choose to run each and every time you have a new version of the software to be tested. Beca [read] Keywords: domino lotusphere application applications bleedyellow bleedyellow.com

212

My Lotusphere Predictions Thu, Jan 5th 2012 6:15p Peter Presnell Lotusphere is now less than ten days away. The extended weather forecast for Disney World now covers the start of the big event. As the most of us in the yellowverse know, Lotusphere marks the true start of each year. 2011 the year of Get Social Do Business is drawing to an end giving way to 2012 the year of Business Made Social. Thousands of the yellow faithful are now starting to pack in preparation for the annual pilgrimage to the holy shrines of Kimonos, BALD, the Beach Party, Nerd Girl e [read] Keywords: connections ibm lotus lotusphere notes notes client application applications microsoft mobile outlook social software

173

RAT -- Part I: Rapid Application Testing Tue, Nov 29th 2011 8:25p Peter Presnell Welcome to the first in a new multi-part series in which I explore a range of ideas related to a style of testing I have developed for my own use at GBS I call Rapid Application Testing. Rapid Application Development For many years I have worked as a Lotus Notes Developer creating and maintaining a large number of Lotus Notes applications. In almost all of these projects I used a development methodology known as Rapid Application Development (RAD). RAD is not a measure of how long it takes [read] Keywords: lotus notes application applications bug database development

112

Notes 8.5.3: The Notes/Domino Awakening - Part 3 Sun, Oct 16th 2011 4:09p Peter Presnell In part 2 of this series I covered the emergence of the social mail client and how Notes 8.5.3 is likely to be the minimum requirement for this new client. I also explored the possibility that this new client may provide access to information held in 3rd party mail clients along with other information sources. So lets now look at how Notes 8.5.3 is likely to have long term impacts on the way we develop Notes applications.... In the beginning Notes was known as a “groupware” [read] Keywords: domino ibm notes R5 xpages application applications bleedyellow bleedyellow.com community development facebook java linkedin mobile openntf social software twitter

80

Notes 8.5.3: The Notes/Domino Awakening - Part 2 Wed, Oct 12th 2011 7:29p Peter Presnell In part 1 of this series I discussed the social awakening and its relevance to the way IT products and services are increasingly being selected/demanded by a workforce empowered by the social tools that connect and inform them . The Social Mail Client – The Arrival Of Project Vulcan A lot has been said about organizations who are migrating away from Notes mail to other mail platforms. Part of the drive for this is the growing demand from e-mail users familiar with e-mail clients su [read] Keywords: connections domino ibm lotus lotusphere notes notes client notesdomino application applications bleedyellow bleedyellow.com bug development facebook mobile outlook skype twitter

85

Notes 8.5.3: The Notes/Domino Awakening Sun, Oct 9th 2011 8:42a Peter Presnell The IT Awakening The IT world is changing rapidly. It (IT) is no longer able to dictate the hardware or software it places on its user's desk. Many users don't even want it on their desk any more! They want (demand?) it to be on their favorite phone or tablet device. The social revolution that has lead to the overthrow of governments in the Middle East is also starting to change the IT landscape inside many organizations. Case Studies Over the years RIM built a position of mark [read] Keywords: domino ibm lotus lotusphere notes quickr R5 applications best practice blackberry facebook firefox linkedin microsoft office outlook rim sap social software twitter