What a whiteboard session is
A whiteboard session is a structured hour where a small group works on one question. Ideas go on sticky notes, notes go on the board, the group sorts and votes, and the session ends with two or three actions that each have an owner and a date. A photo of the board becomes the record.
It works because the people closest to the problem usually know the most about it. A line cook knows why tickets back up at 7:30, and a host knows exactly where the waitlist breaks down. A structured session gets that knowledge out without turning into a complaint meeting.
Before the session
Write one question. Make it specific and positive: "How do we get every Saturday ticket out in under 15 minutes?" works better than "Why is the kitchen so slow?" Write it on the board before anyone arrives.
Invite the right people. Mix front and back of house if the problem crosses the pass. Include at least one newer employee; they notice things everyone else has stopped seeing.
Set the limits. Decide ahead of time what can't change, such as pay rates, staffing budget or the menu concept, and say so at the start.
Gather supplies. A whiteboard or a wall, sticky notes, markers for everyone, small dot stickers for voting, and a phone to take a photo. Schedule it during paid time and bring food.
The whiteboard session plan puts all of this on one page.
Running the session
1. Frame the question (5 minutes)
Read the question aloud. Explain why it matters, with a fact if you have one, such as average Saturday ticket time or a recent guest comment. State the limits. Tell people that every idea is welcome and nobody will be blamed for the current situation.
2. Silent ideas (8 minutes)
Everyone writes ideas on sticky notes, one idea per note, without talking. Silent writing gives quieter people the same chance as the loudest person in the room, and it stops the group from following the first idea mentioned. Aim for at least three notes per person.
3. Post and cluster (10 minutes)
People put their notes on the board and read them aloud quickly. Then the group moves similar notes together into clusters and gives each cluster a short name, like "prep levels," "printer placement" or "who calls the order." Don't debate ideas yet; just group them.
4. Vote (5 minutes)
Give each person three dots to put on the clusters they think would make the biggest difference. Managers and owners vote last. Count the dots.
5. Pick and plan (15 minutes)
Take the top one or two clusters. For each, agree on:
- what exactly will change,
- who owns making it happen (a name, not "the kitchen"),
- by when,
- how you'll know it worked.
Keep it small enough to start this week. "Set Saturday prep pars for the sauté station by Thursday; Maria owns it; we'll check ticket times for the next two Saturdays" is a good plan. "Improve kitchen efficiency" is not.
6. Photo and close (2 minutes)
Take a photo of the board. Thank people. Tell them when you'll follow up.
After the session
Send the photo and the action list to everyone within 24 hours. Then do what you promised: check in with each owner before the deadline, and share the result at a pre-shift. If an action didn't work, say so and try the next idea from the board.
Follow-up is the part that makes the next session work. A team that sees its ideas tried will bring better ideas next time. A team that never hears back will stop offering any.
Mistakes to avoid
Don't use a session to announce a decision you've already made; people will notice and trust the method less. Don't let it turn into a list of complaints about specific coworkers; steer back to systems and steps. And don't try to solve three problems in one hour. One question, one hour, two or three actions.
Where whiteboard sessions fit
Use pre-shift meetings for one focus per shift, one-on-ones for individual coaching, and whiteboard sessions for recurring problems that need the whole team. The shift meetings and trainings guide covers the other two, and our self-coaching program shows how they fit into a weekly rhythm.
Frequently asked questions
How many people should be in a whiteboard session?
Five to nine works best. Fewer than five gives you too few ideas; more than nine means some people won't speak. For a larger team, run two sessions on the same question and combine the results.
Should the owner attend?
Yes, but the owner should speak and vote last. When the boss gives an opinion first, many people quietly agree instead of offering their own ideas.
What if the team suggests something we can't afford?
Say at the start what's off the table, such as a pay raise or a new hire, and stick to it. If a suggestion is out of reach, say so honestly and ask what a smaller version would look like.
What kinds of problems work best?
Practical, recurring problems where the team has first-hand knowledge: ticket times on Saturdays, a messy close, a slow host stand, a confusing to-go process, a station that's always short of prep.