Community Meetings: Hold Regular Live Sessions So Users Shape the System
Learn how a design system team and its users meet on a schedule to share updates, show work, gather feedback, and decide together.
In short
Community meetings are regular live sessions where a design system team and its users share updates, show work, gather feedback and decide together.
12 min readFree
What You Will Learn
A design system is a shared set of parts and rules that product teams use to build screens. Many teams write documents and post requests in tickets, but those tools rarely explain why a change happened or give people a chance to speak. In this lesson you will learn how a community meeting closes that gap. You will see what these meetings are for, which formats and schedules work, how to run one well, and how to follow up so that feedback visibly changes the system.
Key words
- Community meeting
- A recurring, scheduled gathering where the design system team and the people who use the system meet live.
- Design system team
- The small group that builds, looks after, and explains the shared parts and rules.
- Design system user
- Anyone who uses the shared parts, such as designers, developers, and product managers.
- Cadence
- How often a meeting repeats, such as every week, every two weeks, or every month.
- Facilitator
- The person who runs the meeting, keeps it on time, and makes sure everyone gets a turn.
- Agenda
- The planned list of topics for a meeting, with a time and an owner for each one.
- Show and tell
- A short session where someone shows finished or unfinished work and invites questions.
- Action item
- A task that came out of a meeting, with one named owner and a due date.
Why does a design system need live touchpoints?
A design system only stays useful if people trust it, use it, and feel that it belongs to them too. Written guides and tickets are important, but they are one-way. A live meeting lets people ask a question the moment it comes up, hear the reason behind a choice, and see the person who made it. The GOV.UK Design System team puts it plainly: the system depends on a strong community to stay current with research, design, and development. Live sessions are one of the main ways that community stays connected.
Building trust
When the team explains a decision face to face, people are more likely to believe the decision was made for good reasons. A short demo of a new part shows that someone is looking after it, which makes the system feel dependable.
Driving adoption
Teams often skip a new part because they never heard about it. A meeting puts the part in front of the people who would use it, shows them how it works, and lets them say whether it fits their work. Adoption grows when people have seen it working.
Sharing ownership
A system handed down from one team can feel like someone else's rules. When product teams bring their own needs to the meeting and see them addressed, they begin to treat the system as shared property. That shared feeling is what keeps teams from quietly building their own versions.
What are the common formats and how often do they meet?
There is no single right meeting. Teams usually run two or three kinds, each with its own purpose and rhythm. The format decides what the meeting is for, and the cadence decides how much people can count on it. A regular time that people can plan around is often more useful than a big, rare event. The GOV.UK team also noticed that large events take a lot of staff time to organise, which is why a team should choose formats it can keep running.
Weekly or biweekly sync
A short working call for the people who are actively changing parts right now. Use it to unblock questions, review a change that is in progress, and agree on next steps. Keep it small so that decisions happen quickly.
Monthly showcase or demo
A wider session where the team and contributors show finished or nearly finished work, then take questions. This is the best place to explain a new part, such as a Modal, to people who have not followed the daily work. Monthly is often enough for people to keep up without feeling overloaded.
Quarterly direction review
A longer look back at what shipped in the last few months and what the team hopes to focus on next. It is a time to hear big concerns, not to plan the detailed work. Detailed planning belongs in its own lesson.
Pick the cadence first and then keep it steady. If the time or day moves every month, regular users stop attending. Put the meeting on a shared calendar, and announce changes early so that people can adjust.
Tip
Start with one monthly showcase. Add a sync only when a group of people is actively changing parts and needs to talk every week or two.
Who should you invite?
The guest list depends on the format. A sync for builders needs different people from a showcase meant for everyone. Invite the people who will act on the topic, and make sure the people who are affected can hear about it, even if they cannot attend.
Designers
Invite them to shape new parts, test proposals, and bring real screens that show where a part is needed or misused.
Developers
Invite them to check that a part can be built, to raise technical limits, and to tell the team when a part behaves differently from the written guidance.
Product managers
Invite them to explain the needs of their product, to set priorities, and to hear when a change will affect their release dates.
Community help can also come from people outside the core team. The GOV.UK team invites people to join by signing up for its announcements. Open invitations keep the meeting from becoming a private club.
How do you run a meeting well?
A meeting that has no plan wastes everyone's time. The same five habits make almost every community meeting work: a simple agenda, a clear facilitator, shared notes, recorded decisions, and visible follow-up. Each habit is explained below, and the worked example later shows them in use.
How do you write a simple agenda?
An agenda is the plan for the meeting. Use the same parts for a community meeting.
- 1
State one goal
Write the purpose in one sentence, such as: show the new Modal and collect feedback on its close behavior.
- 2
List topics with times
Give each topic a short time box.
- 3
Name a presenter for each topic
Show who will talk about each item. A person who is named in advance can prepare, and the group knows who to ask.
- 4
Leave time for questions and actions
Finish with a short block for open questions and a final review of who will do what before the meeting ends.
- 5
Share it early
Post the agenda before the meeting so that people can decide whether to join and bring questions.
Name a Clear Facilitator
The facilitator is the person who keeps the meeting moving. They open with the goal, call on people in turn, stop side conversations, and close with the decisions and actions. The facilitator does not need to be the most senior person in the room. Many teams rotate the role, so that each person learns to run a meeting and each voice gets heard. A good facilitator is also clear about the difference between a question, a suggestion, and a decision.
Tip
Write the facilitator's name on the agenda. If nobody is named, the meeting will often drift, and nobody will feel responsible for the closing summary.
Take Notes and Record Decisions
Notes are the memory of the meeting. A person who misses the call should be able to read what was shown, what people said, and what the team chose. Notes also protect the team, because a decision that was never written down often gets made again. Keep the notes in one shared place where everyone knows to look.
Notes
A short record of each topic: what was shown, the main points raised, and any questions that are still open. Write them as you go, not from memory afterward.
Decisions
A clear statement of what the group agreed, written in one sentence, with the reason if it matters. For example, a Modal will close only on an explicit action, not on a click outside the box.
Action items
Each one has a single owner and a due date. A note such as 'someone should check this' is not an action item, because nobody can be held to it.
Before the meeting ends, the facilitator should read the decisions and actions back to the group. This gives people a chance to correct a mistake while everyone is still on the call.
Follow Up So Feedback Leads to Change
Feedback that goes nowhere makes people stop giving it. The follow-up is what proves that the meeting was worth attending. The steps below turn a discussion into visible change.
- 1
Publish the notes quickly
Post the notes, decisions, and action items within a day or two, in the same place each time. People who missed the call can then read the outcome without asking.
- 2
Reply to each piece of feedback
Answer each comment with one of three outcomes: accepted and scheduled, declined with a reason, or still open with a date for the next look. Silence tells people their input was ignored.
- 3
Make the change and link to it
When a part changes, point to the updated guidance or the new version, and name the meeting where the idea first came up. This closes the loop.
- 4
Show the result at the next meeting
Open the next session by listing what changed since the last one. Visible progress encourages people to bring more ideas.
- 5
Record the video or summary for latecomers
If you record a session, share the link with a short written summary. Many people will read the summary and never watch the whole call.
Worked Example: The GOV.UK Monthly Chat
The GOV.UK Design System team hosts a monthly session with its wider community. The team describes the monthly chat as a show and tell followed by questions and discussion. Lean coffee is a loose talk where the group chooses topics and talks about them in turn. Here is how one cycle of the session works, step by step.
- 1
Choose the topics in advance
Choosing ahead keeps the hour focused and gives presenters time to prepare.
- 2
Recruit the speakers
Someone on the team finds speakers and help organise the session. Speakers can include the design system team and outside teams with their own case studies.
- 3
Give people notice
Announce the session early so that community members can plan to attend. The team also invites people to join its mailing list to hear about new events.
- 4
Run the session in a set order
A host opens with housekeeping, introduces each speaker, and leads questions after each show and tell. Then the host moves to the lean coffee discussion.
- 5
Keep notes during discussion
For a special session on accessibility in October 2024, the team used an online board to collect notes and comments while the video call ran. The session was a one-hour show and tell and discussion.
- 6
Publish and promote the result
Once the recording is ready, the team shares it with the community so that people who missed the call can watch it and comment.
Tip
Copy the pattern, not the platform. A small team can keep notes in a shared document, post a recording link in its chat channel, and still get the same benefit.
Common Pitfalls
No clear purpose
A meeting with no stated goal tends to become a status update that nobody needs. Write one sentence of purpose before you send the invitation.
Notes that nobody reads
Long notes stored in a hidden folder do not help. Keep the decisions and actions at the top, and post them where people already look.
Feedback that disappears
If no one replies to a comment, people stop speaking. Close every point with an outcome, even when the answer is no.
Check Your Understanding
Use these short scenarios to test the ideas. Each one asks you to choose the plan that fits the situation, not just to repeat a definition.
Quick check
Your design system team ships a new Modal. Product teams keep building their own versions because they did not know it existed or why it changed. Which community meeting should you set up, who should you invite, and what should you do afterward so absent people stay informed?
Quick check
After a biweekly sync, a developer asks the team to reconsider how a Button label works. The group agrees the request is worth checking. Which follow-up best shows that the feedback can lead to change?
Key Takeaways
Community meetings keep a design system a shared product. Choose a format that matches its purpose, such as a short sync for builders, a monthly showcase for everyone, or a quarterly look at direction. Run each meeting with a written agenda, a named facilitator, clear notes, recorded decisions, and single owners for every action. Most of all, follow up in the open, so that people can see their feedback leading to change. Day-to-day chat, drop-in help, and the way work is tracked are covered in other lessons.
Sources
- GOV.UK Design System: Community page (monthly catch-up and community role)
- GOV.UK Design System team playbook: A guide to the Design System monthly chat
- GOV.UK Design System chat, October 2024 event listing (reposted by Alex Hedley)
- GOV.UK Design Notes: Looking at design systems across government (2016 show and tell)
- GOV.UK Design Notes: Setting cross-government design community objectives (Service Thursdays)
- GOV.UK Design System: Design System Day events
- Department for Education guide: Things to help you (show and tells and peer review notes)
- Asana: Meeting agenda templates and examples
- MeetingNotes: How to ace your next community meeting
- Medium: 10 meeting agenda templates for dynamic design teams
Last updated on 17 November 2026
Related lessons
- Design systemsLoading Indicator: Show Users the System Is Working, Clearly and Consistently
- UI/UX basicsStatus Reports: Tell Users What the System Is Doing
- UI/UX basicsPrime User-Relevant Associations: Show Cues That Match What Users Care About
- Design systemsDesign System Examples: How to Read Real Systems as Models
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.