Communication Channel: Where Design System Teams and Users Talk Clearly
Learn how to pick, set up, and run the named places where a design system team answers questions, shares news, and hears feedback.
In short
A communication channel is a named place where a design system team answers questions, shares news and hears feedback, picked and run on purpose.
14 min readFree
Why does a design system need one known place to talk?
A design system is a shared set of parts and rules that many product teams use. Those teams will have questions, find bugs, and want to suggest changes. If nobody tells them where to go, they ask whoever they know, post in random chats, or wait and guess. A communication channel fixes that. It is a named, dedicated place where the design system team and its users ask questions, share updates, and give feedback. Examples include a Slack or Discord channel, a discussion board inside GitHub, or a mailing list. This lesson is about choosing, setting up, and running those places so people know where to go and what to expect.
Key words
- Channel
- A named place set aside for one kind of conversation, such as a Slack channel or a discussion board.
- Design system team
- The people who build, maintain, and explain the shared parts and rules.
- Users
- The designers and builders who use the system inside their own products.
- Category
- A named section inside a discussion board, used for one purpose.
- Thread
- A chain of replies attached to one message, so talk about one topic stays together.
- Triage
- Sorting new questions and requests by type, urgency, and owner so the right person picks them up.
- Pinned
- Fixed to the top of a channel so the message stays visible.
- Breaking change
- An update that makes something stop working the way it did before. Release rules are covered in another lesson.
- Tracked item
- A formal work record, such as an issue, that has an owner, a status, and a history.
- Response expectation
- A stated time window in which the team says it will reply.
What does a clear channel setup give you?
Fewer repeated questions
When answers live in one searchable place, a person can find an old answer before posting a new question. The same question then does not get answered ten times in ten different chats.
Support that people can see
When the team names a support channel and says who watches it, help becomes visible. Users stop guessing whether anyone is listening, and the team can show how much support it gives.
Trust between team and users
Users trust a system when they know where news will appear and when a serious problem will be announced. A quick, clear warning about a broken part protects the people who depend on it.
Trust is the hardest benefit to earn. A design system team that posts important news in a random place, and then goes quiet, teaches users to stop reading. A team that posts in the same place every time, and answers on a known schedule, teaches users to check that place first.
How do you choose channels by purpose?
The most common mistake is one big channel for everything. Questions, news, bug reports, and internal design debates end up mixed together, so important posts get buried. A better plan is to give each purpose its own place. Most design system teams need four.
Support questions
This is where users ask how a part works or why a screen looks wrong. On GitHub, a question-and-answer category lets the team mark one reply as the accepted answer, so later readers find it faster.
Announcements
This is one-way news: new releases, deprecations, and warnings. On GitHub, an announcement category can be set so that only maintainers start new posts, while everyone can still reply. This keeps the news easy to scan.
Feedback and requests
This is where people suggest improvements or new parts. An ideas category gives those suggestions one home, so they do not get lost among questions.
Contributor discussion
This is where people who build or change the system talk about how to do it. Keep it apart from user questions, so users are not forced to read internal debate.
Tip
Start with the fewest channels that cover the four purposes. Add more only when a real purpose has no home. Every extra channel is one more place a user has to check.
GitHub organizes its discussions in exactly this way. Each category has a format, such as open-ended discussion, question and answer, or announcement. People with maintain or admin permission on a repository decide the categories, and each new discussion must be placed in one of them.
Default categories
GitHub starts with an Announcements category for news from maintainers and a General category for anything relevant to the project.
Renaming and removing
Maintainers can rename, delete, or add categories as the community grows, so the setup can change over time.
Think of this as a design decision, not a tool setting. Write down what each category is for before you open it, then remove or merge any category that nobody uses.
Discussion boards and tracked work are not the same thing. The next sub-topic explains where each one belongs.
What is the difference between boards and tracked work?
A discussion board is built for open conversation. It is where a question can be explored, a proposal can be tested, and people can share opinions. GitHub describes its discussions as a place for open-ended talk.
Issues are different. When a conversation reveals a real bug or a missing part, the team should move it into an issue, so it is not lost in the chat history.
Tip
Ask one question before you move a post: does this need someone to own it, track it, and close it? If yes, it belongs in tracked work. If it is still a question or an idea, leave it in the discussion.
Who watches each channel and how fast do they reply?
A channel with no owner is a channel nobody checks. Each channel needs a named person or rota that watches it, and a plan for when that person is away. Before you open a channel, write down these three things.
The owner
The person or small group who reads new posts, sorts them, and answers or passes them on. Name a role, not just a person, so the job survives holidays and team changes.
The response window
The time within which the owner will reply. Support questions and urgent warnings need a shorter window than an idea post.
The backup
Who covers when the owner is unavailable. A channel with a backup is less likely to go silent for a week.
Owners need a clear purpose for each channel, because the right reply time depends on the purpose. A support channel and a general chat should not share one expectation.
Set the expectation in writing. A team that agrees on response norms helps everyone decide when to post now and when to wait.
Set Response Times on Purpose
Write the response window next to the purpose of each channel. A support window should be shorter than the window for an idea post, and the channel should say which one applies. If a channel has no fixed window, say so in plain words, so people do not wait for a reply that is not coming. A window you promise and then miss does more harm than an honest, looser one.
Name, Describe, and Clean Up Channels
A channel name should tell a stranger what the channel is for. Names like general or misc make people guess. Names that include the purpose, such as a support channel for one component family, help people choose the right place on the first try. Many teams use a short prefix, such as a word for support or a word for announcements, so channels group together in a list.
Avoid creating several channels for the same job. When one purpose is split across three names, users do not know which to use, and each channel gets only part of the traffic. Pick one name per purpose and stick to it.
Add a short description to every channel. The description should say what belongs there, who answers, and what to do first. Without it, the name alone has to carry the whole message.
Clean up once in a while. Archive channels nobody uses, merge duplicates, and update descriptions that are out of date. A stale description is worse than none, because it sends people to the wrong place with confidence.
Tip
Review your channel list on a fixed date each quarter. Ask three questions: Is this purpose still needed? Is the owner still active? Does the description still match what people post?
Keep Channels Healthy
Setting up a channel is the easy part. Keeping it useful takes steady habits. The four habits below matter most: visible rules, tidy threads, sorting requests, and moving real work into tracked places.
Pinned rules and onboarding
Pin the rules
Pin a short message that says what the channel is for, what to post, and how long replies take. People look at the top of a channel first, so the rules belong there.
Pin onboarding
Add a short welcome that points new members to the most useful starting places, such as the written guidelines and the support channel.
Keep the pins short
Long pinned text gets ignored. Three to six clear lines work better than a page of policy.
Threads and tidy conversation
Ask people to reply inside a thread when they answer a specific message. Threads keep each topic together, so a reply to one question does not interrupt a different topic. The team can then find the answer later without reading the whole channel.
Tagging and triage
Tags help the team sort posts. GitHub labels are one example, and GitHub says labels help maintainers triage and organize discussions. Use the same small set of tags every time, so the sort means the same thing to everyone.
- 1
Read each new post
The owner reads new posts within the response window and checks whether the post is a question, idea, bug, or news.
- 2
Apply one tag
Give the post one tag that matches its type and its part of the system, so it can be found later.
- 3
Answer or route
If the owner can answer, they reply in a thread and mark the answer. If not, they pass the post to the person who can.
- 4
Close the loop
The owner marks the post as answered, or says what happens next, so the poster is not left waiting.
Moving decisions and bugs into tracked places
A decision made in chat is easy to lose. Someone who joins a month later cannot find it, and the team may argue about it again. When a conversation ends in a decision or a bug, write a short summary in a tracked place and link back to the discussion. Keep the link both ways, so the chat post points to the record and the record points to the conversation.
Bugs
Open a tracked item with the steps to reproduce, the affected part, and an owner. Link it from the discussion where the bug was first reported.
Decisions
Write the decision in one short paragraph, with the date and the people who agreed. Put it where future readers will look for it.
Announcements
Post the news in the announcements channel, and do not rely on one notification setting to reach everyone.
Worked Example: A Confusing Button Variant on Polaris
Shopify's Polaris design system is a real example of a team that uses a public code repository with a discussion board. Its React library is an important caveat for this lesson. The React repository now says the library is deprecated and that it no longer takes contributions or feature requests. So the channel setup moved. Use this example to learn the pattern, and check the current team pages before you copy any step.
The archived React discussion board still shows the pattern clearly. Here is how a designer could use that pattern for a confusing Button variant.
- 1
Find the one place
The designer opens the Discussions tab of the repository. They do not search through chat or email. One known place is the whole point.
- 2
Search before posting
They search for the variant name. If someone already asked, they read the answer and any linked follow-up issue, and stop there.
- 3
Choose the right category
Because they want to know how the variant works, they choose the Q&A category, not Ideas. A question for help goes in a question category, and a change request goes in an ideas category.
- 4
Write a clear post
They name the Button, the variant, the screen where it appears, what they expected, and what they saw. A specific post gets a useful answer faster.
- 5
Read the answer and the follow-up
The team replies in the thread and marks the answer. If the answer reveals a real problem, the team opens a tracked issue and links it.
Tip
When you copy a channel pattern from a real team, write down the date you checked it. Public team setups change, and an old setup can send people to a page that no longer takes their posts.
Check Your Understanding
Quick check
Your team announces a breaking change to the Modal component in a busy company-wide chat. A week later, many product teams are confused and sending private messages to one designer. What was wrong with the channel setup, and what would you change?
Quick check
A product designer finds a bug in a Tag component. They post it in the general discussion category, a team member replies in a thread, and the bug is never logged. Which step would best keep the bug from getting lost?
Quick check
A team's support channel gets forty new posts a day, and for two days no one has replied. The channel has no description and no pinned rules. Which change would most improve it?
Key Takeaways
Give each purpose a home
Keep support, announcements, feedback, and contributor talk apart, and add a new channel only when a real purpose needs one.
Name an owner for every channel
Each channel needs a watcher, a backup, and a response window that users can read on the pinned message.
Move real work into tracked places
Bugs and decisions belong in a tracked record with an owner, linked back to the conversation so nothing is lost.
A good channel setup is quiet work. Users rarely notice it when it works. They notice it immediately when it does not, which is why it is worth designing with the same care as a button or a color.
Sources
- Shopify Polaris React repository (archived notice)
- Shopify polaris-react-archive Discussions page
- GitHub Docs: Managing categories for discussions
- GitHub Docs: About discussions
- GitHub Changelog: Discussions labels and announcements format
- GitHub community discussion #3951 on watching a single category
- Tutorials Dojo: GitHub Discussions overview
- Programming Line: GitHub Discussions setup and best practices
- Social Intents: Best practices for Slack channel organization
- Calamari: Best communication practices with Teams and Slack
- Salesforce: Building your Slack-first communication policy
- m.io: Slack best practices
- Brysa: Redesigning work around Slack, best practices
- EightShapes: Design system communications
- Pylon: How to use Slack for customer support
- DevActivity: GitHub Discussions setup guide
Last updated on 17 November 2026
Related lessons
- System designCommunication: How System Parts Talk, and When to Wait
- Design systemsDesign Editor: Set Up One Shared Design System File Your Team Can Trust
- Design systemsLoading Indicator: Show Users the System Is Working, Clearly and Consistently
- Design systemsRelease Strategy: How Design System Updates Reach Product Teams Safely
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.