What Should We Eat? Decision Wheel Ideas
Build a useful meal wheel by filtering allergies, budget and travel distance first.
Published · Reviewed
What Should We Eat? Decision Wheel Ideas
Build a useful meal wheel by filtering allergies, dietary needs, budget, opening hours and travel distance first. The wheel should settle a tie among viable choices, not decide whether an unsafe or unavailable option is acceptable.
Recommended process
- Remove options that fail dietary or allergy requirements.
- Check current availability and delivery range.
- Use equal weights unless the group agrees otherwise.
- Save rejected ideas for a different context instead of forcing them into the draw.
Worked example
A group removes a closed restaurant and two options that cannot handle an allergy. The remaining choices—noodles, curry and sandwiches—are equally weighted for the final low-stakes selection.
What to check before using the result
- Never randomize around a serious allergy.
- Confirm prices and hours outside the wheel.
- Let participants opt out of an unsuitable result.
How the random step is handled
Random Picker Tools uses window.crypto.getRandomValues() for browser-based selection. Integer results use rejection sampling to avoid modulo bias, and complete list orders use a Fisher–Yates shuffle. This addresses the software selection step; the organizer still controls eligibility, duplicate rules, consent, accessibility and any legal requirements.
Privacy note
Normal picking and shuffling happen in the browser. Use initials or non-sensitive identifiers when possible, avoid storing unnecessary source data, and create a share link only when temporary server storage is appropriate for the people represented in the list.