HuddlePopsStart free
Facilitation

Staff meeting ideas for nonprofits that actually get participation

Nonprofit teams tend to be small, mixed, and busy. The meeting formats written for corporate departments do not survive contact with that.

Why nonprofit meetings drift into status updates

Almost every nonprofit staff meeting starts life as a genuine conversation and slowly becomes a round of updates. The reason is structural rather than cultural.

Nonprofit teams are usually small enough that everyone does several jobs, which means everyone has something to report. They are also usually mixed — full time and part time, paid and volunteer, people who have been there fifteen years and people who started in March. And the calendar is tight, so the meeting gets squeezed.

Put those together and the path of least resistance is a round-robin of what everyone did. It feels productive. It is easy to run. And it uses the entire hour on information that could have been an email, leaving no time for the two or three decisions that actually needed the room.

Separate the update from the discussion

The single highest-leverage change is to stop doing both in the same meeting.

Updates are broadcast. They are one person talking, everyone else listening, and no interaction required. That is precisely what written communication is good at, and precisely what a meeting is bad at — a meeting spends everyone's hour to deliver information that most people needed thirty seconds of.

Discussions are the opposite. They need the room, they need people to react to each other, and they cannot happen asynchronously without becoming a very long email thread.

Move updates to a shared document that people read before, and protect the meeting for the things that genuinely need everyone present. This one change usually reclaims half the hour.

Six formats that fit a small nonprofit team

  1. The one-question opener. Start with a single question everyone answers at once, in a word or a line. "What is taking more time than it should this week?" surfaces blockers faster than any round of updates, and it takes ninety seconds.
  2. The decision list. Publish, before the meeting, the specific decisions that need making. Not topics — decisions, phrased as a question with options. A meeting with three decisions on it runs differently from a meeting about three subjects.
  3. Silent start. First five minutes, everyone reads the document in the room. It feels strange exactly once. It guarantees everyone has the context, which is otherwise the thing that derails the next forty minutes.
  4. Rotate who runs it. In a small team this is unusually effective. The person running the meeting listens differently from the person attending it, and rotating spreads that. It also stops the meeting becoming the director's meeting.
  5. The pre-mortem. Before committing to something, ask everyone privately: "It is six months from now and this went badly. What happened?" You will hear risks nobody would raise as an objection in an open discussion.
  6. Close with one round. End by asking everyone for one line: what they are taking away, or what is still unclear. The "still unclear" answers are the valuable ones and they almost never come out unprompted.

The mixed-room problem

Most nonprofit staff meetings contain a hierarchy that nobody acknowledges. The executive director is in the room. So is someone on a six-month funded contract who would like it renewed. So, often, are volunteers who are technically not staff at all but do a third of the work.

That mix changes what gets said. Not because anyone is being political, but because the cost of disagreeing is genuinely different for each of those people, and everyone knows it.

The practical response is to ask the difficult questions in a way that does not require anyone to be seen answering. Not everything — a team that only ever communicates anonymously has a deeper problem. But the questions where the honest answer might be unwelcome are exactly the ones where the visible version will get you a polite, useless response.

What to stop doing

  • Going around the table. The last person has heard everyone else and will mostly agree. It also means the meeting length scales with headcount, which is why it keeps overrunning.
  • "Any other business." It reliably produces either nothing or a twenty-minute tangent at the moment everyone has stopped concentrating. Ask for items in advance.
  • Meeting weekly because you always have. Some teams need weekly. Some need fortnightly and are meeting weekly out of habit, with half the agenda invented to fill it.
  • Ending without naming who does what. A meeting that produces agreement but no owner produces nothing. Name the person and the date before anyone leaves.

A format worth trying next week

If you want one concrete thing to change, try this shape for a sixty-minute meeting.

Five minutes of silent reading. Ninety seconds on one opening question that everyone answers at once. Thirty minutes on the two or three decisions that need the room, with the difficult ones asked privately first and the results shown to everybody. Fifteen minutes of open discussion on whatever the answers surfaced. Five minutes naming owners and dates. Close with one line each on what is still unclear.

That leaves out the updates entirely, and most teams find they do not miss them.

Nonprofit teams do not usually have a participation problem because people do not care. The opposite is normally true — people are there because they care, often for less money than they could earn elsewhere.

They have a participation problem because the meeting is structured so that listening is easier than contributing. Change the structure and the contribution is already there waiting.

Try it in your next meeting

HuddlePops is free to start, and the people answering never need an account. Write one question, share one QR code, and see what the room actually thinks.

Create a free account
Hector Cuevas

Hector founded HuddlePops after watching too many good meetings die in silence. He writes about getting real participation out of rooms that have learned to stay quiet.

Keep reading

Using HuddlePops

How to collect anonymous feedback from your team

Anonymous feedback fails more often than it works. Why that happens, when anonymity is the right tool, and how to ask so that you get something you can act on.

6 min read
Facilitation

How to run a workshop when you're not a trained facilitator

You have been asked to run a session and you have never been taught how. What actually matters, what does not, and the five failure modes worth planning around.

5 min read
All Presentation Strategies