If you are chairing an accessibility committee, you already know how to run a meeting. You have run plenty of them, in different jobs and different rooms, and this chapter is not going to teach you the basics. Think of it instead as a roundup of what tends to work in the particular context of an accessibility committee meeting, collected from committees that worked and from ones that quietly fell apart. Most of it applies to meetings in general, and you will recognize a good deal of it from your own experience. But there are many kinds of meetings in life, and this chapter is about this one.
So you had the first meeting. People introduced themselves, you talked about why everybody is there, you sorted out the roles, and everybody left the room, or the video call, feeling that something good is starting. And then a month goes by, and it is time for the second meeting, and this is where committees usually start to drift, because nobody is quite sure what is supposed to happen once everybody sits down again.
I get this question a lot, and it is a fair question: what do we actually do when we meet? Let me answer it the way I think about it, because the answer shapes everything else in this chapter. A committee meeting is a coordination point, not the work itself. The work happens between meetings, when people write the emails, test the kiosk, talk to the facilities team, or do whatever their action item says. The meeting exists so that everybody knows what the work is, who is doing it, and what was decided since last time. If you keep that in mind, most meeting problems solve themselves, because you can always ask of any agenda item whether it is moving something forward or whether you are just talking about it.
A standing agenda
I keep a standing agenda, and I rarely deviate from it, because a predictable structure is what makes people prepare and what keeps the conversation from wandering. We start by reviewing the action items from last time, by name, out loud. I do this at the beginning of every meeting, no exceptions. Nothing kills momentum faster than assignments that quietly evaporate between meetings, and the public review is what keeps them from evaporating, because nobody wants to be the person who reports “I did not get to it” three months in a row.
Then we talk about what came in since last time: barrier reports from employees, from visitors, from the community, from anyone who found a problem.
Then we go through the list of things to discuss. It does not have to be one item. Sometimes it is more than that, and that is fine. We just need to go through all of them. Of course it helps if it is not a ton. What matters more is that we do not put more on the agenda than we can actually handle within the hour. If you regularly need more than an hour, then either your agenda is too big or your discussions are too loose, and either way the fix is structure, not a longer meeting, because a two-hour meeting does not solve a structural problem, it just gives it more room.
Then new business, which is the space for things that came up since the agenda went out and cannot wait a month. And we finish by making sure the action items are assigned. On this I am strict: an action item always belongs to one or two people, or however many it actually needs, but never to everybody in general. Everybody in the room knows who is working on what, and those people report back next time, because in my experience an assignment that belongs to everybody somehow belongs to nobody. I would rather have a short list of named owners than a long list of good intentions.
Notice what is not on the agenda. There is no slot for general discussion of accessibility as a topic, and that is deliberate. You can fill an unlimited number of meetings talking about accessibility in the abstract and accomplish nothing at all, and I have watched committees do exactly that for months. The meeting is for moving specific things forward. If a topic needs real discussion, it gets its own slot with a clear question attached, for example whether the committee should recommend that the new vendor contract include an accessibility clause, yes or no. Not “let us discuss procurement”, which is not a question and will not produce an answer no matter how long you talk about it.
And think about when you meet. Not over lunch unless you are feeding people. Not at a time that excludes the people with caregiving responsibilities or the colleagues in other time zones. We will talk more about the schedule as an accessibility decision in the next chapter, but it is an effectiveness decision too, because a meeting that half the committee cannot attend is not an effective meeting no matter how well you run the hour itself.
The boring infrastructure
Committees die from logistics, not from disagreement, and I have seen more committees fade out over calendar chaos than over any substantive dispute. Somebody has to own the calendar invite, the agenda, and the notes, and it has to be clear who that somebody is, not assumed, not “we will figure it out”, but a name. Send the agenda at least two days ahead so people can prepare, because a meeting where everybody is reading the material for the first time is a meeting where nothing gets decided. Take notes every time and share them afterwards. The notes are the committee’s memory, and they are also how absent members stay included, which matters more than people think, because sooner or later somebody important will miss a meeting and need to catch up, and the notes are the only way that happens.
The meeting is facilitated by the chair. If the chair is absent, the co-chair steps in. An accessibility committee meeting is more structured than a casual conversation, and I want the facilitation in the hands of the people who carry the committee’s direction. Note-taking is a different matter: rotate it, let somebody else take the notes each time, and give people a break from it, because taking good notes is real work and it should not always fall on the same person.
Every meeting should produce something
I said it about the first meeting and I will say it about every meeting after it: finish with an action item. It does not have to be a large thing. “Maria will contact HR about the captioning budget by Friday” counts, and frankly those small concrete assignments are the ones that keep a committee alive, because they are finishable. Write it down, assign a name and a date, put it on the action item list, and check it next time. What matters is that every person in the room can point to something that moved because the meeting happened, because that is the difference between a working group and a discussion group.
And the action items need a home of their own. They can appear in the agenda, and they can appear in the notes, but neither of those is the primary source. There should be a separate list just for action items, and that list is where you look when you want to know the state of the committee’s work. Each entry carries the action item itself, the person or persons responsible, the due date, the completion status, and a notes field. The notes are where you write what has been done, what is still missing, and what you are waiting for. But the point of the list is that it is easy to scan: one glance tells you whether something is completed or not, and the bottom line is simple. If it is not marked complete, it is not done yet.
And celebrate the small wins out loud. Fixed the broken elevator announcement? Got captions turned on for the all-hands meeting? Say so in the meeting and put it in the notes. Committees run on volunteer energy, and volunteer energy runs on visible progress. People will keep showing up if they can see that showing up changes things, and they will stop showing up the moment the meeting feels like a ritual with no results, no matter how much they care about the cause.
When meetings go wrong
The failure modes are always the same, and I have seen all of them more than once. No agenda, so the loudest person sets the topic. One person talks the whole time while everyone else checks out. Decisions happen in the hallway afterwards among three people, and the rest of the committee finds out later, which breeds exactly the kind of resentment that kills volunteer groups. Action items get assigned to “we” instead of a person, which means nobody in particular, and everybody knows it. If you recognize your committee in any of these, I have to say the fix is not a motivational speech. It is the agenda, the notes, and the named assignments from the previous sections. Structure is what makes volunteer groups function, and the lack of it is what makes them fall apart, slowly and then all at once.
In the early life of a committee, the meeting is really the product. Get the meeting right, structured and producing something every time, and the rest of the work has a place to live. Get it wrong, and you will have a mailing list instead of a committee. The next chapter is about the other half of getting it right: making sure the meeting itself is accessible to everyone.
No comments! Be the first commenter?