This book includes a plain text version that is designed for high accessibility. To use this version please follow this link.
other duties as assigned


Unspoken Katharine Cline President, Preferred Meeting Management M


y very first meeting was a medical meeting — a five-day conference. The first night


was designed as a welcome reception, in which all of the keynote speakers appeared and we checked them off the list. You know, everything’s fine — you don’t have to worry about anyone not showing up. Until the next morning. We’re wait-


ing, and waiting, and waiting, and it’s my first conference, so I’m really not sure how long to wait for our first key- note speaker to come. Everything’s set except for him, but we’d already seen him the night before. So we check the restaurants. He’s not there. We call his room. No one answers. We continue to try to search for him,


110 PCMA CONVENE JULY 2012


thinking he’s walking around, and I end up going to call him from the house phone again as well as send someone up to knock on the door. Before the person gets up there to knock on the door, I’m calling on the phone, and the person who answers is a woman, screaming incoherently. It turns out that this is a woman who was there with our keynote speaker for the evening: He had died in bed with his secretary. He passed away in his sleep, and she is finding herself in bed with a dead person. The hotel and security took it from


there. The woman was removed from the premises very quickly. We rear- ranged the meeting, so basically, we moved the endnote speaker to the keynote — he volunteered to do that


and was prepared to do that, so it really worked out quite well. It wasn’t a con- ference in which you had to worry about the flow of the meeting and the sessions, because it was all the same topic. And for the endnote, we did a wrap-up panel with all the keynote speakers. I’d been involved with meetings for


several years before that point, but not as a coordinator. So I knew enough about meetings and the unpredictable- ness of them to know that on any given day, a lot of different things can happen, and that your job on site is really to troubleshoot. But I had no idea that that would be one of the troubleshoot- ing things that I’d have to do.


. — As told to Christopher Durso PCMA.ORG


ILLUSTRATION BY GRAHAM ROUMIEU


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116