Open Hours: Drop-In Help Times From Your Design System Team
Learn how a design system team can offer regular, live help sessions, and how to turn each session into lasting fixes for everyone.
In short
Open hours are regular live drop-in help sessions run by a design system team, with each session turned into lasting fixes for everyone.
10 min readFree
What You Will Learn
This lesson explains Open Hours. Open Hours are regular, scheduled time slots when a design system team is free for live help. Anyone who uses the system can come in with a question, a blocker, or an idea and get an answer while the problem is still fresh.
You will learn why teams hold Open Hours, how to run them well, and how to turn what you hear into better guidance. You do not need to write any code for this lesson. The focus is on people, schedules, and habits.
Key words
- Design system
- A shared set of parts, rules, and guidance that product teams use to build their screens.
- Design system team
- The small group that builds, looks after, and supports the system.
- Adoption
- How many people actually use the system in their everyday work.
- Drop-in
- A session where people can join at any point during a set time, without booking a slot first.
- Blocker
- A problem that stops someone from finishing their work.
- Pain point
- A part of the work that frustrates people or causes the same mistake again and again.
- Host
- The named person who runs the session and keeps it moving.
- Agenda
- A short plan of the topics to cover in a session.
- Docs
- The written guidance that explains how to use each part of the system.
- Backlog
- The list of planned changes and requests the team has not finished yet.
What are open hours?
Think of Open Hours as an open door at set times. A member of the design system team waits in a video call or a room. A designer or developer drops in, asks the question, and leaves when the answer is clear. Nobody has to write a long message and wait days for a reply.
<cite index="5-3">A design system leader can use the same model to schedule open time that keeps the team in touch with the people it supports.</cite> The same approach works without a physical office, since <cite index="5-4">the sessions can run remotely over video.</cite>
Open Hours are not a formal meeting with a fixed program. They feel closer to a live help desk. The format matters less than the promise: a regular time, a known place, and a real person who will answer.
Why do open hours exist?
Teams hold Open Hours for three main reasons. Each reason solves a problem that is hard to solve with tickets or long chat threads.
Lower the barrier to adoption
Adoption gets easier when a user can get a question answered in minutes. <cite index="13-5,13-6">Compared with formal meetings, these sessions feel relaxed, so small problems get solved on the spot, which makes people more confident about using the system.</cite> The advice is also to bring questions that fit in about ten minutes, and to move bigger talks into private meetings.
Surface pain points early
A session shows where people are stuck before the problem spreads. <cite index="1-6">Teams can gain insight into what other teams are working on or struggling with.</cite> <cite index="10-7">When a team cannot adopt a part, the reason often exposes a weak spot that the system team can fix.</cite>
Build trust
Users trust a system more when its builders listen. Trust also grows for people who work alone. <cite index="15-8">At IBM, some teams have only one designer, who can use the weekly slot for design feedback and skill growth.</cite>
How do you run open hours well?
Good Open Hours are easy to join and hard to forget. Five parts do most of the work.
- 1
Keep a fixed, recurring schedule
Choose one time each week and keep it. <cite index="9-8">Send a recurring calendar invite so people can block the time, even if they only stay for a few minutes.</cite> <cite index="8-10">Nucleus advises running the session weekly and avoiding cancellations, so regular visitors build a habit.</cite>
- 2
Give one clear channel or link
Put the way in to the session in places people already check. The Acorn team uses a shared calendar and a sign-up form. <cite index="1-10">The same sign-up form is also saved in the channel's bookmarks bar.</cite>
- 3
Name a host
Choose one person to be online for the whole slot. At Acorn, <cite index="1-15">a dedicated systems team member stays in the Zoom for the allotted time, so anyone can drop in.</cite>
- 4
Use a light agenda
Keep a short list of topics, and leave room for anything else. Some teams take topics in the order people signed up. Others use no agenda at all. <cite index="19-1,19-2">One design system lead runs weekly sessions with an open video link and no agenda required.</cite>
- 5
Capture questions and outcomes
A session helps more people if its content lasts past the call. <cite index="5-13">Follow-up messages in chat can summarize what was discussed.</cite>
Tip
Write the link, the time, and the host's name on the same page. If a new visitor needs more than one click to find the session, many will give up before they join.
Worked Example: Acorn's Weekly Office Hours
The lesson plan suggested the Shopify Polaris team as an example. We could not find public details of a Polaris drop-in call, so this walk-through uses a public page from the Acorn Design System, which serves the Firefox community. The team <cite index="1-3">hosts weekly recurring office hours for that community.</cite> The steps below follow the published process. The sample user, Sam, is imagined to show how the steps fit together.
- 1
Sign up ahead
Sam has a question about a form. The text fields and the dropdown menus look mixed up, and Sam is not sure which part to use for a choice. Sam fills in the sign-up form and names the topic. <cite index="1-11">A confirmation email then arrives with the event details and instructions for joining.</cite>
- 2
Choose the time that fits
The team meets once a week and <cite index="1-6">alternates between a time that suits American time zones and one that suits European time zones.</cite> Sam joins the slot that fits the day.
- 3
Join and wait your turn
<cite index="1-13">Topics are usually taken in the order people signed up.</cite> Sam waits until the topic is reached. Anyone without a sign-up can still join the drop-in call, because the host stays on the line for them.
- 4
Walk through the screen together
Sam shares the form on screen. The host asks what the user should do and explains which part fits which job. The team talks through the choice, so Sam sees the idea used on a real screen.
- 5
Turn the answer into guidance
The lesson does not stop when the call ends. The host notes that the same confusion came up in chat and adds a short rule to the docs about when to use each part.
The example shows the full loop. A user brings a real problem, the host answers it on a real screen, and the answer ends up in writing where the next person can find it.
How do you turn sessions into improvements?
A session that helps one person is good. A session that helps the whole community is better. The goal is to capture what you hear and spread it. Three habits make this work.
Log recurring questions
Keep a simple running list of the questions you hear. <cite index="8-7">Design system teams often hear the same questions again and again.</cite> A list makes the pattern visible. When one question appears three times, it is a sign that the docs or the part itself needs work.
Feed docs and the backlog
Some answers belong in docs, and some reveal a real change to the system. <cite index="7-11">Some teams find that new requests come up during these sessions, and then they help the person ask for the change.</cite> <cite index="15-11">A common pattern is that one team's question matches a request another team has already filed, so the two can be joined.</cite>
Share takeaways with everyone
A fix that only the attendees know about helps very few people. <cite index="8-7">A shared channel lets everyone see the questions and the answers, which spreads the help beyond the call.</cite> Short written summaries help too.
Tip
After each session, ask three questions. Which question came up twice? Where should the answer live? Who else needs to see it? Write the answer once, in the place people already look.
Keep the loop short. Do not let a good answer sit in a notebook for months. A one-line update in the shared channel is often enough for the next visitor to find the answer.
Common Mistakes to Avoid
Cancelling too often
A slot that is cancelled often never becomes a habit. Keep the time, and if you must move it, tell people early.
Making it feel like a formal meeting
Open Hours work best when people feel free to ask small questions. A long agenda of updates can scare away the very people the session is for.
Leaving no record
If the answers stay in the call, the same questions return next month. A short written note after each session stops that cycle.
Keeping the host hidden
If nobody knows who will answer, people will not come. Name the host in the invite and in the channel.
Check Your Understanding
Try these two short scenarios. Each one needs the ideas from this lesson.
Quick check
Your team's Open Hours slot has been empty for three weeks. Meanwhile, the chat channel keeps getting the same questions about modals. What should you change, and why?
Quick check
A product designer asks in Open Hours when to use a text Input versus a Select. Two weeks later, three other designers ask the same thing in chat. What is the best next step for the design system team?
Key Takeaways
Open Hours are a fixed, live time when design system users can get help. They lower the barrier to adoption, reveal pain points early, and build trust. To run them well, keep a regular time, give one clear link, name a host, use a light agenda, and record the outcomes. To make them pay off for everyone, log the repeated questions, improve the docs and the requests, and share what you learned with the whole community.
Sources
- Office hours - Acorn Design System (Firefox)
- How to conduct office hours for your design system and help with adoption (zeroheight)
- The drop-in clinique sessions (Nucleus Design blog)
- Design System Adoption in the Enterprise (Medium, Meridian team)
- The power to serve. Lessons learned on design system team operation (Carbon for IBM.com, Medium)
- Best Practices for Creating Collaborative Adoption in Design Systems (Supernova)
- How to maintain a design system that teams actually use (Headway)
- Office hours: the powerful design tool you aren't using (yet) (Silver Spider, Alex Jones)
- Building Design Systems That Teams Actually Use (Timothy Graf)
- Planning the Perfect Creative Workshop for Your Office (Hoop and Fred)
- Office Hours with Shopify SEO Expert Kyle Risley (Shopify Community)
- Designing design systems: Supporting implementation and adoption (Adobe Design)
Last updated on 17 November 2026
Related lessons
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.