Create a Team Jar
Set up a Social Jar named 'Team Lunch'. Set custom categories like 'Fast Food', 'Sit Down', 'Pub'.
Share the Link
Post the invite code in your team Slack or Teams channel. Anyone can join and contribute.
Build the Menu
Add all the local haunts. Tag them by price ($ or $$) and distance/walking time.
Spin Before You Starve
At 11:55 AM, someone hits spin. No arguments, just go. If it picks the salad place again, so be it!
The Slack Channel Death Spiral
It starts every day around 11:30 AM. Someone types "Lunch?" in the team Slack channel. Three people reply "Sure, where?" Then nothing. For 20 minutes, no one commits to a suggestion because no one wants to be the person who picks the place everyone secretly hates. Eventually, someone suggests the same sandwich shop you went to yesterday, everyone reluctantly agrees, and another unremarkable lunch passes.
This is a coordination failure, not a preference failure. Everyone has places they'd love to try — they just don't want to be the one to suggest them and risk rejection.
How a Team Jar Ends the Debate
A Team Lunch Jar removes the social friction entirely. Everyone adds their favorite local spots asynchronously — tag by price ($, $$), distance (walking, driving), and cuisine type. When 11:55 hits, one person opens the jar, applies any needed filters, and spins. The entire decision takes 3 seconds. No discussion, no committee, just go.
Over time, the jar builds a collective intelligence of your team's dining preferences. New team members instantly get the curated "greatest hits" list instead of eating at the same three places for their first month. It's the smallest culture improvement that makes the biggest daily difference.
Pro tip: Set up a Recurring Event for "Friday Team Lunch" so the reminder appears automatically each week. Use RSVP to know the headcount before booking a table, and post the week's pick via Announcements so even remote teammates can coordinate.