The right invite list is the shortest list that can finish the thing, and you find it by writing a short reason next to every name. If you cannot write the reason, that person is not invited. Everything else about invites is downstream of that one test.
Most lists are not chosen. They are remembered. You open the calendar, start typing, and the autocomplete does the thinking for you.
Adding a name is free for you and costs an hour of theirs. That asymmetry is why almost every invite list I see is too long, and why the fix is a writing job rather than a scheduling one.
Write a reason next to every name
Before you send anything, write one clause beside each person saying what they will do in the room, using a verb.
Approves the number. Remembers why the last attempt died and never wrote it down. Those pass. "Context" does not, and neither does "should probably be there".
The verb is doing the work. It forces a choice: either the person decides something in that room, or they hold something that has never been written down. Anything vaguer than that is a hunch about politics wearing a business hat.
Reasons that fail the test, all of which I have used:
- They were in the last four meetings about this.
- You want them to know it happened.
- Taking them off would feel rude.
- They are senior and you assume they want the option.
- You want company if the decision ages badly.
That last one is the honest version of a lot of invites. Spreading a decision over more calendars buys you a slower decision and a wider pool of people who can later say they had reservations. The decision itself comes out the same.
The names you will be tempted to leave off
A list can also be too short, and that failure costs more than an extra attendee, because the meeting decides something that quietly gets undone afterwards.
Two people belong on the list even when adding them is annoying. The person who can reverse the outcome later, and the person who will do the work you are about to volunteer them for.
Decide without the person who can reverse you and you have booked a second meeting. You just have not put it in the calendar yet.
Then there is the person you left off because they will slow things down. I have done this and told myself it was focus. It is not focus. You have moved the argument to a worse venue, usually a thread three days later where nobody has the whiteboard and everyone has an audience.
Make optional mean something
Marking someone optional changes nothing unless you write the sentence that tells them what they would miss and how they will get it anyway.
Almost nobody reads the optional field. It is a small grey label next to a block that has already eaten an hour of their afternoon, and the safe move is always to attend.
An optional line people believe does three things:
- It names the one part that touches them, and roughly when it lands.
- It promises the outcome arrives in writing whether they show up or not.
- It gives permission to skip that needs no reply.
Written out, it is about two sentences. "Optional for you. The only piece that touches your team is the rollout date near the end, and I will post the outcome in the channel either way, so skipping costs you nothing."
Then keep the promise. Break it twice and optional becomes a word nobody believes from you again, which is expensive in a way you will never see on a calendar.
What to put in the invite itself
The invite body should tell each person why they are on the list, in one line each, above the logistics.
A title and a time is a summons with a video link.
Mine runs to four lines:
- What will be true when the meeting ends.
- One line per required person, naming their job in the room.
- The optional sentence, if anyone is optional.
- The pre-work, with the honest amount of time it takes.
Naming each person's job does something that the agenda cannot. It tells the quiet ones they were wanted for a specific reason, which is the difference between someone who speaks up at minute eight and someone who waits to be asked and then agrees with whatever the room already said.
It also lets people correct you before the meeting instead of during it. If you write "here for the migration risk" and that stopped being their area a while ago, they will tell you, and you will fix the list rather than spending fifteen minutes discovering it live.
How to take someone off a standing invite
Removing a person from a recurring meeting needs a short message sent before the calendar change, never after they notice the block has vanished.
Something close to this works: "I am trimming Thursday down to the people making the call on pricing. You are off the invite from next week. Nothing has changed about your work or your remit, notes go to the channel the same day, and say the word if you want back on."
The words doing the work are "nothing has changed about your work". Without that line, a removed invite reads as a demotion, because on most teams the invite list is the only visible map of who counts.
Tone is the hard part here, and it is where I still get it wrong. What I mean is administrative. What I type at the end of a long day tends to come out clipped, and the person on the other side gets three sentences that sound like a verdict. Closing that gap before the message leaves is the reason I built Unvent: same content, warmer surface, and no apologetic paragraph bolted on the end to make up for it.
Send the people you cut something better
Everyone left off the list should get the outcome in writing, short enough that they prefer the note to having been in the room.
Four lines covers it. What got decided, and what changes for them. Then the date by which they should say so if they disagree. It is the recap shape, pointed at the people who were not in the room.
That last part is what turns a recap into an actual replacement for attendance. A decision with a window on it can be argued with. A decision announced as finished invites either silence or a grudge, and one of those two shows up in your next planning cycle.
This is a slightly worse trade for you than it looks. You spare everyone you cut an hour, and you buy yourself the work of writing clearly about something you have just spent an hour arguing about. Do it anyway, with the care you would give any update people read without you in the room, and the invite list stays small next time because people trust the note.
Watch who reacts when you trim a list. The person who seems relieved was never doing anything in the room, and you can stop feeling bad about that one. The person who is quietly stung probably was doing something, something you could not name because it never appeared in the decision you thought you were making. Ask them what you missed. Half the time the answer is that they were the only one still carrying the last version of this decision, and nobody had ever asked them to write it down.
Trim the list without the chill
Unvent rewrites whatever you are typing, in place, in the tone you pick. The invite that trims a list can still sound like it came from someone who likes working with the person reading it.
Add Unvent to Chrome