The Protocol Code Paper No. 07, The Gathering Architecture Papers Author: David Adler. Publisher: GatheringPoint.news. Free and ungated. Web version: https://gatheringarchitecture.com/papers/the-protocol-code This file is the complete plain-text copy of the paper, provided so text-only readers and AI agents can read the full work. ======================================================================== The work has to go somewhere Start with something everyone has done. You are at a reception and someone you have clearly met before walks up, and you have lost their name completely. You can say “Hey! Good to see you!” and keep talking, which hands them a problem: does he know who I am, should I say my name, is he going to ask, do I rescue him. They now spend the next minute working on you instead of talking to you. Or you can say “I’m David — remind me where we met?” You took the hit. They do nothing. Same thirty seconds, same two people, same forgotten name. The only thing that moved was who had to do the thinking. Every social moment has a bit of invisible work in it, and there are only two places that work can go: you, or them. Good manners mean you do it. Bad manners mean they do it. That test explains every rule below, and it is also why the old protocols lasted: the place setting works outside in so no guest has to identify a fish fork under pressure, and the seating chart exists so forty people do not have to sort out status at the door. The host did that thinking in advance. The table is now four thousand people in a convention center with a badge, an app and a QR code, and most of those protocols were retired without replacement. The work did not disappear. It got handed to the guests. Rules marked Traditional are a matter of record; the rest are proposed. Card viewCopy EverythingEvery badgeRegistration and greetersThe hostTable captainsSales and exhibitorsExecutives and VIPsInformation tradingProduction and AVFront of houseWhoever writes the invitation 102 of 102 rules Getting in the door 1–8 1 Keep your right hand empty until you are through the line. Traditional Why: the bar belongs past the receiving line, not before it, because a host should never have to choose between your handshake and your cocktail. You put up with an empty hand so they do not have to deal with the fumble. 2 Say your own name every time, to everyone, including people who know you well. Traditional Why: a host greeting two hundred people cannot pull names up on demand, and the ones who try do it while visibly panicking. Two seconds from you saves them the whole scramble. 3 Bring back the receiving line, and give it an aide. Traditional Why: the aide stands to the line's left, takes each name and announces it, so every guest gets greeted by name inside a known window. Without it, two hundred people spend the night wondering whether the host even knows they came. 4 Four seconds per guest, then move. Traditional Why: the line is a greeting, not a conversation, and the moment somebody starts a real topic, everyone in the queue behind them pays for it. Being brief is the courtesy you owe the people you cannot see. 5 End the line at thirty minutes, finished or not. Traditional Why: a line with no announced end turns a greeting into a trap for the host. Saying when it ends frees them without making anyone feel cut off. 6 Arrive in the first third of the event. Why: walk in at the end and every group is already closed, so the people already talking have to break their conversation open to let you in. Showing up early is the cheapest gift a guest can give a room. 7 If you are the host, stay in one findable place. Why: a host who roams is a host people have to hunt, and hunting is work you quietly assigned to everyone who wanted to say hello. Pick a spot and let the room come to you. 8 Tell one person the three people you are hoping to meet. Why: rooms will connect you happily, but only if they know what you are looking for. Keep it to yourself and everyone has to guess, which they will do badly. How to start a conversation 9–20 9 Say who you are before you ask. "I'm David, I write about the events business." Why: offering gets you exactly the same information as asking, costs them nothing, and shows them how long an answer you are looking for. This is the most important rule in the section — the questions below only work well when this one comes first. 10 When you cannot place their name, say yours first and ask where you met. Why: they are already deciding whether you have forgotten them or are pretending, and that guessing costs them the next minute. Giving your own name first takes the hit: they answer instead of calculating, and the conversation starts on solid ground. 11 At a badged event, do not ask what the badge already says. Why: asking anyway tells them you did not read it, or that you have nothing else, and makes them read their own chest out loud. Spend your question on something the badge cannot tell you. 12 Try "what world do you come from?" Why: it asks which group someone belongs to rather than what they have achieved, so any answer works — the hotel world, the nonprofit world, restaurants, the Hill, Cleveland — and nobody has to guess which credential you are checking. Answer it yourself first and it can never sound like you are sizing them up. 13 Ask what they are working on, not what their job is. Why: a current project is something they are glad to talk about and have already thought about. A job title makes them compose the résumé version of themselves on the spot. 14 Ask how they ended up in this business. Why: nobody planned a career in events. Everybody fell into it sideways, and everybody already has that story ready to tell, so the question costs them nothing and gets you something real. 15 In a room without badges, ask how they know the host. Why: it assumes you already have something in common and cannot be answered wrong. No answer to it makes anyone look small, which is more than most openers can promise. 16 Ask "who should I be talking to that I'm not?" Why: it turns the other person from a target into a guide, which is a better job and one most people enjoy. It also produces the single most useful sentence anybody will say to you all night. 17 Never lead with a request. Why: a hello that ends in an ask makes someone a transaction before they agreed to be one, and forces them to think about saying no in the first minute. Let them meet you before they have to judge you. 18 Do not open by complaining about networking. Why: "God, I hate these things" asks for sympathy, so a stranger has to comfort you before they even know your name. You have given them a job on arrival. 19 Ask a second question about their answer. Why: anyone can ask the first question. The second one is the difference between actual interest and going through the motions, and it is the only charm technique that reliably works. Skip it and the other person has to carry the conversation alone, and they will notice. 20 Use their name once, not three times. Why: once is warm, twice is a reminder, three times is a sales technique, and everyone can hear a sales technique. The moment they start wondering what you are selling, they have stopped listening. Working the room 21–29 21 Look at a badge for a second and a half, no longer. Why: the name tag sits on someone's chest, so past about a second and a half you are not reading it, you are staring at them, and now they have to decide what to do about that. 22 If you cannot read the badge, just ask. Why: leaning in and squinting is worse than the question, because it acts out the awkwardness instead of ending it. Asking costs you a flicker of pride and costs them nothing at all. 23 Leave a gap in your group so people can join. Why: a closed circle of three makes a decision for everyone standing alone within ten feet. Stand in a horseshoe instead and people can join without doing the hardest thing in any room, which is interrupting strangers. 24 If you see someone stranded, go get them. Why: you are already the closest person to the problem, and the host is forty people away. Parker's point is that hosts protect guests; in a room of four thousand, every guest inherits part of that job. 25 When you introduce two people, say what they do, not what they are called. Why: "This is Maya, she rebuilt their whole onsite registration in six weeks" gives two strangers something to talk about. "This is Maya, VP of Operations" makes them invent a subject from a business card while you walk away. 26 Do not answer their story with a better one. Why: topping an anecdote turns a conversation into a contest nobody entered. They came to talk and now they have to compete. 27 Praise what someone chose, not what they were born with. Why: admiring a decision is generous. Admiring an attribute is a judgment, and a judgment needs a response. One lands as warmth; the other makes them figure out what to say back. 28 Turn your body when a fourth person walks up. Why: if the group does not physically open, it has told the newcomer something, and now they have to decide whether to hover at the edge or walk away. A quarter-turn settles it before they have to think about it. 29 If someone is looking for the bathroom and you know where it is, say so. Why: it costs you four words. This is the purest version of the whole test in this document: a small, stupid, avoidable search that you can simply take off their hands. At the banquet table 30–42 The table in this business is not a dinner party. It is a 72-inch round seating ten strangers, in a ballroom with a band, under a centerpiece that blocks half the sightlines, with a program starting in forty minutes. A round is too wide to talk across, so you get two conversations: left and right. 30 Somebody has to start the table, and it may as well be you. Why: it is nobody's assigned job, so it usually does not happen, and then ten adults eat a three-course meal without learning who they are sitting with. The opening is simple: get the names going. This is the single highest-value thing anyone does at a banquet table all night, and the person who does it is remembered for the rest of the event. 31 When you introduce yourself, keep it to about fifteen seconds: your name, what world you come from, and one specific thing you are working on or hoping to find here. Why: the person who goes first sets the length for everyone, so a ninety-second biography forces nine more of them and kills the table for fifteen minutes. Short, and ending on something specific, gives the next person an easy act to follow and gives everyone a hook to come back to over the main course. A title and a company name give them nothing. 32 Lead the table, then get out of the way. Why: starting the names does not make you the master of ceremonies, and the self-appointed MC who runs the table as his own show is a worse outcome than silence. Open it, ask one question everybody can answer — what did you come here to figure out works almost every time — then hand the floor to whoever has not spoken and let it run without you. 33 You have two dinner partners, one on each side, and you owe both. Talk to one through the first courses, then turn to the other when the main course lands. Traditional. The preppy shorthand is "roll with the roast" — the roast arrives, you roll to your other side Why: on a round of ten you are the only company two different people have, and whoever you neglect spends the evening looking at the back of your head. The turn is what gets them both a dinner, and the arriving plate is the cue so nobody has to invent one. 34 If you are hosting the table, start the turn yourself and let everyone follow. Traditional Why: Emily Post set this out in 1922 — the hostess talks one way through the soup and fish, then turns the other, the person she leaves turns to their own other neighbor, and within a moment the whole table has swapped. Nobody has to decide when, or risk being the only one who did, because the host decided for all ten. 35 Do not talk only to the people you came with. Why: the colleague cluster is the most common failure at a banquet table and the most invisible, because everyone inside it is having a nice time. Your team can talk at the office. The three strangers you were seated beside cannot, and they are the only reason the seating chart existed. 36 Pitch your voice to reach three feet, not eight. Why: the Emily Post Institute's own list puts raising your voice across the table among the ten things not to do, and in a loud ballroom the temptation is constant. A voice thrown across a round makes everyone else stop their own conversation to wait you out. 37 Sit where you were put. Traditional Why: somebody spent real hours on that chart, usually balancing buyers against sellers and strangers against friends, and every self-upgrade pushes three other people out of place. The chart already did the thinking you are about to undo. 38 Stay in your seat until the plates clear. Why: working the room during dinner strands whoever you were seated next to, and an empty chair for forty minutes turns their two available conversations into one. Table-hop after the course, not through it. 39 Keep the phone off the table, and if you must work, leave. Why: face-down is not away, and at an industry dinner everyone knows you are working, which makes a phone on the table a standing announcement that this table ranks below your inbox. Step out, deal with it, come back. 40 Pass to the right, taste before you salt, and ask rather than reach. Traditional Why: three small mechanics with the same logic. A standing direction means the table does not renegotiate traffic at every course. Seasoning before tasting insults whoever cooked. And reaching across someone's plate, which Post's list also flags, makes them duck around your arm instead of eating. 41 If you are the host: low centerpieces, no seating by rank, and name a captain for every table. Why: a tall arrangement means half the table physically cannot see the other half, which is a problem you paid a florist to create. Seating by status makes everyone think about the hierarchy through three courses. And a named captain — whose actual job is the names, the turn, and watching for anyone stranded — is the cheapest upgrade available to a banquet, because it assigns work that otherwise falls to nobody. 42 Do not start something big in the ten minutes before the program. Why: a real question asked just before the lights drop gets a rushed answer and then dies mid-sentence, which is worse than not asking. Save it for after the awards, and keep your own toast under ninety seconds while you are at it — past that it stops being generous and becomes a captive audience holding warm plates. How to trade information 43–48 The real currency at an industry table is not small talk. It is specifics: what a venue actually charged, whether that platform actually worked, who is really leaving. Trading has its own protocol. 43 Go first, with something real. Why: "What are you paying for AV these days?" asked cold makes the other person decide, alone and instantly, whether you are a peer or a leak. Lead with your own number and the question answers itself. You cannot ask someone to be the first one exposed and also expect them to be glad about it. 44 Offer something of roughly equal weight to what you want. Why: trading a pleasantry for a real figure is not a trade, it is an extraction, and everyone can feel the difference in the moment. If you want something sensitive, open with something that costs you something. 45 Let what you learn travel, but leave the name behind. Why: this is the actual working rule of every well-informed person in this business. The information moves — that is what makes it worth trading — but attribution stays at the table. Repeat the fact and you are useful. Repeat who told you and you are never told anything again. 46 Never ask someone to break a confidence they are under. Why: asking a person to choose between helping you and keeping their word puts the whole cost of your curiosity on them, and they will remember being asked long after they have forgotten what you wanted. If they are under an NDA, the answer is already no and you knew it. 47 Look at who else is at the table before you answer. Why: a round of ten at an industry dinner routinely contains a competitor, a client, a reporter and somebody's boss. The person asking may not have noticed, so the kindness is to redirect rather than to answer and let them discover afterward what they extracted from you in front of whom. 48 If you cannot answer, say what you cannot answer. Why: "I can't talk about the renewal, but I'll tell you anything you want about the platform" takes five seconds and tells them exactly where the fence is. Going vague instead makes them keep probing, fail, and leave wondering whether they offended you. Phones, cameras and AI 49–55 49 Ask before you let an AI notetaker listen. Why: a notetaker running unannounced during a private conversation at a reception is the modern version of reading someone's mail. Nobody has made a rule about it yet, everybody is doing it, and the person across from you will find out eventually. 50 If it is already recording, say so in your first sentence. Or switch it off. Why: telling someone afterward is not disclosure, it is an apology, and it forces them to go back and re-examine everything they already said. The entire cost of your late honesty lands on them. 51 Do not post the unflattering candid, and ask before any group photo goes up. Why: mid-sentence, mid-bite, mid-anything, you have made a decision about someone's public image on their behalf and then published it. Accept a no without asking them to justify it. 52 Do not airdrop your contact card at someone. Why: a file transfer is not a relationship, and the phone cannot make the introduction for you. All you have done is leave a stranger holding a decision about you. 53 Do not look at the badge scan while they are still talking. Why: scanning someone and then checking your screen tells them exactly where they rank in your next thirty seconds. They will finish their sentence knowing it. 54 Put nothing in the group chat you would not say at the table. Why: the running commentary during a session is visible in more rooms than you think and outlives the session by years. Somebody is always one screenshot away from paying for your joke. 55 Take calls away from the gathering, speak quietly, and never use speakerphone in shared event spaces. Why: your call should not become everyone else's soundtrack. A loud phone conversation interrupts the session, drowns out the people talking beside you, and can put a stranger's private information in the open. Politics and other hot topics 56–65 Some political questions have a deadline and facts attached, and somebody has to decide them. Others have no deadline and no answer. Telling them apart is the whole skill. 56 Say which kind of question you are asking. Why: "Can our attendees get care in this state, and will they feel safe here" can be answered with facts by a deadline. "Is that law right" cannot be answered at all. Naming which one you mean lets the other person answer without first working out whether they are being tested. 57 Assume the room disagrees with you, because it does. Why: your attendee list was built on professional criteria, so it contains the whole political range of the country. Talk as though the room agrees and you have just told a third of it to sit quietly and take it. 58 Remember that the person who disagrees with you risks more than you do. Why: whoever raises the topic risks nothing, because they are already comfortable. Whoever disagrees risks the client, the account, the promotion, the room. Calling it "just a conversation between adults" ignores who is actually exposed. 59 Save real disagreements for a walk, not a table. Why: a genuine argument needs tone, follow-up questions and room to say I hadn't thought of that. Put the same exchange in front of ten onlookers and it becomes a performance with a scoreboard, and now nobody can back down. 60 Never do it from the stage. Why: an audience cannot reply, and a microphone turns your opinion into the house position. Whatever you say up there, your attendees have to sit still and be counted as having heard it. 61 Ask how it is affecting their business, not what they believe. Why: "How is that actually hitting you?" can be answered honestly by someone on any side, and the answers are specific and genuinely interesting. "What do you think about it" asks them to declare a position, which is a much more expensive question. 62 Turn down the argument without turning down the person. Why: "That's one where I lose friends whichever way I go — tell me about the Phoenix move instead" is honest, warm and final, and it beats the fake-neutral mumble everyone can see through. You are protecting the relationship, not pretending to have no views. 63 Never ask a junior person to take a side in front of their boss. Why: "What do you think, Danny?" across a dinner table is not curiosity, it is a test with his livelihood sitting in the room. Whatever Danny says, he is paying for your interesting evening. 64 Vet speakers and sponsors beforehand, never in the room. Why: the old posts, the affiliations, the destination's laws — all of that belongs in a planning meeting with time and legal advice. Find out live and four thousand people get to watch you decide. 65 If you are the host, publish the ground rules before the event. Why: Parker's argument for explicit rules is that they free people rather than restrict them, and a norm published in advance protects the attendee who would otherwise have to invent one at the table. Without it, the loudest person in each room writes the rule for everybody else. Why you are really there 66–75 Wanting something is not the offense. Every adult in a room full of strangers wants something. The offense is the surprise. 66 Say what you came for in the first few minutes. Why: "I'm here because we're hiring a CFO and I'm hoping to meet a few" takes four seconds and turns you from a puzzle into a person with a project. People help projects. They avoid puzzles. 67 Know that a late ask poisons everything that came before it. Why: twenty-five minutes of charm followed by a request makes the other person go back and re-read all twenty-five minutes as technique, and they will. All the goodwill you built gets spent at once, at a worse rate than if you had just said it at the start. 68 Do them a favor first, and do not hint at the return. Why: give them a name, an introduction, a useful piece of information, and then let it go completely. You are about to ask them for something, and arriving with something in hand is how an ask stops feeling like a withdrawal. Everyone can tell the difference between a gift and a down payment, so it only works if you genuinely drop it. 69 One ask per person, per night. Why: the second request turns you from a person into a channel, and from that moment they are managing you instead of talking to you. Take the first answer and come back another day. 70 Make it easy to say no. Why: "If it's not a fit, no explanation needed" costs you nothing and removes the real reason people dodge, which is not the request itself but having to invent a graceful refusal on the spot. An ask with no easy no attached is one most people answer by avoiding you later. 71 Ask for the small version. Why: not the job but the name of the person who hires; not the order but the next meeting; not the date but the coffee. A small ask can be answered right there, which is a kindness, and it is usually all you needed. A big one forces them to overcommit or refuse, and most people will do neither — they will go vague on you and mean it. 72 Never pitch during somebody else's moment. Why: not during the toast, the tribute, the award, the memorial, or the ten minutes after someone's good news. That moment belongs to another person, and a pitch inside it steals from them as much as from the person you are pitching. 73 If you are selling, say so early. Why: everyone in the room already knows what a supplier is doing at a buyer's conference, so the elaborate pretense of a purely social chat is the actual insult. Name it in a sentence and spend the rest of the conversation on something better than concealment. 74 If you are job-hunting, ask how they got their job, and leave the résumé at home. Why: at a party nobody can act on a document or refuse one politely, so handing it over makes your problem into their burden. The how-did-you-get-here question gets you more anyway, and it gets it from somebody who is enjoying the conversation. 75 If you are interested in someone romantically, remember this is their workplace. Why: give one signal, then read the answer, and treat a soft reply as a no, because a polite deflection is the only no many people can safely give at a work event. And never where you hold the power — client over vendor, senior over junior, stage over audience — because someone who cannot leave the conversation freely cannot answer it freely either. How to leave, and what to do after 76–82 76 Say out loud that you are leaving. Why: Science of People argues for stating the ending plainly so nobody is left holding the ambiguity. Silence makes the other person interpret you. A sentence does that work for them. 77 Signal that you are wrapping up before you actually go. Why: Debra Fine, who has taught small talk for two decades, calls it the white-flag approach — wave the final lap before you take it. Reader's Digest's interviews with Fine and Vanessa Van Edwards agree that small, neutral, practical reasons let both people keep their dignity, because the alternative is whiplash. 78 Best of all, hand them to someone else. Why: introduce them to another person and then go, and you have not left them standing alone, which was the real cost of your leaving. It is not an exit at all. It is a gift wearing one. 79 Never look over their shoulder. Why: this is the one everybody does and nobody survives doing. It makes the other person read your face, work out what your attention is doing, and reach a humiliating conclusion by themselves, in real time, mid-sentence — the entire job of your departure, handed over in silence. 80 Do not exit with "let's connect on LinkedIn." Why: it is a confession with a platform attached, and everyone in this industry can translate it instantly. Now they have to pretend along with you. 81 Leave a little early rather than a little late, and say goodbye to the host by name. Why: Mastroianni's advice, drawn from the data rather than from finishing school, is that you will almost certainly guess wrong about what the other person wants, so go at the first decent opportunity — better to be left wanting more than less. And the guest who vanishes leaves the host wondering, while the guest who lingers twenty minutes after goodbye leaves everyone wondering. 82 Follow up the same night, and name the specific thing. Why: "Great to meet you" arriving three days later makes them work out who you were and what you discussed. One line sent before you sleep, naming the actual thing you talked about and the one thing you said you would send, does all of that for them — and it is the only step in this entire document that converts a conversation into a relationship. The things the host should have settled 83–102 What do I wear, do I need cash, why is it so loud, when does this actually start, and how am I getting out. All five are the host's to settle in advance. 83 If you are the host, write the dress code in words a person can act on, and say what you will be wearing. Why: "Jacket, no tie — I'll be in a navy blazer and dark jeans" ends the question permanently for every guest. A named code plus a named example costs you one sentence and removes several hundred private decisions, which is the best return available anywhere in event protocol. 84 Never write "business casual," "festive," "resort chic" or "smart casual" and leave it there. Why: these phrases have no agreed meaning left, so each one is really an invitation to guess and a risk of guessing wrong in a room full of colleagues. If you want to use the phrase, fine — then add the example that tells people what you actually mean by it. 85 Say why, when the clothes have a practical reason. Why: if there is a walk between venues, an outdoor cocktail hour, a famously freezing ballroom, or three hours of standing, your guests cannot know that and you can simply tell them. One clause about shoes or a wrap saves a hundred people a miserable evening they will blame on the event. 86 If you are the guest and the code is unclear, ask the host, not your colleagues. Why: polling three co-workers produces three guesses and spreads your uncertainty around. One message to the organizer gets the real answer, and it also tells them their invitation was unclear, which is a favor. 87 Never make anyone feel wrong about what they wore. Why: by the time you are in the room it is far too late to fix, so a remark about it is pure cost with no possible benefit. If they are visibly uncomfortable, the kind move is to stand next to them and talk about something else. 88 Carry cash, because the people who most depend on tips still cannot take a card. Why: the valet, the bellman, the coat check, the restroom attendant and the shuttle driver are all working on tips, and the quiet shift to cashless moved that problem onto them without anyone deciding to. A few small bills in your pocket is the whole solution, and it is your job, not theirs, to have solved it. 89 Do not ask a service worker for a Venmo handle. Why: it asks a stranger to hand you a payment identity, in front of their supervisor, while they are working, and most of them have no good way to refuse. If you have no cash, say so plainly and thank them properly — that is better than making them manage your payment problem. 90 If you are the host, pre-pay the valet and the coat check. Why: otherwise you have invited several hundred people to an event and handed each of them a small cash emergency on arrival and another on the way out. Covering it costs you a line item and removes the single most common friction point at any hotel event. 91 Tip the people nobody sees. Why: the bartender gets tipped because there is a jar in front of you. The person restocking the buffet, clearing the rounds, running the freight elevator and staffing the coat room is doing the same night with none of the visibility. Noticing them is the version of this whole document that has nothing to do with networking. 92 If you did the inviting, you are paying. Why: the person who said "let's grab dinner" has already set the terms, and anyone who then reaches for the check is guessing about whether they were a guest or a participant. Settle it before the bill arrives, or better, settle it with the server beforehand so there is nothing to negotiate at the table. 93 Set the volume so nobody has to raise their voice, and give the AV team an actual number. Why: "keep it background" means nothing to a sound engineer, and the band will drift up over the night because every band does. A number, a meter and someone whose job is to watch it turns a vague preference into something that can be held. 94 Brief the band that during a networking reception they are the background, and brief them again after every break. Why: musicians are trained to fill a room, which is the opposite of what this room needs, so without an explicit brief they will do their job correctly and ruin yours. Say it before the first set and again after the second, because the volume always creeps. 95 Give the room one quiet corner, and treat that as access, not luxury. Why: a significant share of any adult audience has some hearing loss, and background noise is precisely what makes speech unintelligible for them. Without somewhere quiet, those guests are not having a harder night than everyone else — they are excluded from the entire purpose of the event, silently, and most of them will never mention it. 96 If you are the guest and you are both shouting, move. Why: leaning in and repeating yourself three times makes the other person do the work of reconstructing half your sentences. Saying "I can't hear you — come over here" takes four seconds and hands them a solved problem instead of a strained conversation. 97 Publish the real schedule, not the aspirational one. Why: "Reception 7:00, program begins 7:45" lets a guest decide when to arrive and whether to eat first. A bare "7:00 pm" makes several hundred people each privately guess how much of the first hour is standing around, and the ones who guess wrong spend forty minutes alone in a half-empty room. 98 Start the program at the time you published. Why: holding the room for latecomers punishes everyone who came on time and teaches the whole audience to arrive late next year, at which point you have created the problem you were accommodating. Start on time once and the following year's room fills itself. 99 Say the time you mean, because local and cultural norms genuinely differ. Why: Edward T. Hall's distinction in Beyond Culture (1976) between cultures that treat a schedule as a fixed structure and those that treat it as flexible and event-driven is still the clearest account of why "seven o'clock" means different things in different places. Rather than guessing whether your audience shares your assumption, write what you actually require — "doors at seven, remarks promptly at half past" — and the convention stops mattering. 100 As a guest in an unfamiliar city, arrive at the stated time and let the host correct you. Why: being early costs you ten minutes and a drink. Being an hour off in the other direction means somebody held a seat, delayed a course, or wondered all evening whether you were coming. When you do not know the local rhythm, take the instruction literally and ask the organizer what people actually do. 101 Do not order the car and then start a conversation. Why: once the driver is four minutes away, you are no longer in the room — you are managing an arrival, and the person in front of you is competing with a map on your phone. Finish the conversation, say the goodbyes, then order the car. 102 If you are the host, stage the departure. Why: four hundred people leaving a hotel at once is an event you designed, and left alone it becomes a crush at one door, a surge price, a twenty-minute wait in the cold and a last impression that undoes the whole night. A marked pickup zone, clear signage, a staff member with a list and a staggered ending are all cheap, and the exit is the part everyone remembers most clearly. Sources & practice A hundred rules is a reference document and nobody memorizes one. Pick a role above, read the eight or ten rules that apply, and say them out loud to the team once before doors. Then run the debrief question afterward: where did someone get stuck doing work we should have done for them? Sources: Andrea Wojnicki, Talk About Talk and Inc. · Mastroianni et al., PNAS, 2021 · Priya Parker, The Art of Gathering · The Emily Post Institute on the turning of the table (1922) and ten things not to do at the table · Monster, Politics in the Workplace, July 2025 · Skift Meetings on politics and destinations, 2023 · Science of People · Debra Fine and Vanessa Van Edwards via Reader’s Digest · WHO and OSHA sound levels via restaurant acoustics guidance · Edward T. Hall, Beyond Culture (1976). Companion to the story at GatheringPoint.news. Back to the series