A picker wheel is really just a blank canvas until you decide what goes on it, and the entries you choose are what turn a generic tool into something built specifically for your activity. This guide covers how to think through building a custom wheel from scratch, whatever you're actually trying to decide.
Start with the actual decision, not the format
Before typing anything in, get specific about what you're actually deciding — not "something fun for the party" but "which of these six party games we'll play first." A vague starting point tends to produce a vague, less useful wheel; a specific one makes it obvious exactly which entries belong on it and which don't.
Choosing the right entries
Good wheel entries are mutually exclusive and roughly comparable in scope — all names, all game options, all discussion topics, rather than a mix of different kinds of things lumped together. Mixing categories (a few names, a few tasks, a few prizes) on one wheel usually signals that you actually need two or three separate wheels, one per category, rather than a single combined list.
Deciding how many entries to include
There's no fixed right number, but very short lists (2-3 entries) can feel like they don't need a wheel at all, while very long lists (50+) make individual slices hard to read and the spin itself less satisfying to watch. Somewhere between 4 and 20 entries tends to hit a comfortable middle ground for most everyday uses, readable and meaningfully random at the same time.
Building category or theme wheels
For activities like trivia, icebreakers, or challenge formats, a wheel of categories or themes (rather than specific outcomes) adds a layer of structure: spin once for the category, then decide or spin again within it. This two-step approach works well whenever an activity naturally breaks into a general type plus a specific instance, since it lets you reuse the same category wheel across many sessions while swapping out what's inside each category.
Designing wheels for recurring activities
If an activity repeats — a weekly meeting, a regular game night, a recurring classroom routine — it's worth building the wheel once, thoughtfully, and saving it rather than rebuilding it from scratch each time. A well-built recurring wheel should need only small edits between uses, like removing someone who's left the group or adding a new option, rather than a full rewrite.
Structuring wheels for elimination or bracket formats
For a tournament-style or elimination activity, "remove winner after each spin" turns a single wheel into a bracket-generating tool: each spin removes the previous pick, gradually narrowing the field. This is a simple way to seed a bracket or determine an elimination order without needing separate bracket software for something that's really just a sequence of fair, random draws.
Adapting a wheel for different group sizes
A wheel built for a small group of five doesn't need much adjustment to scale up to fifteen — the entries change, but the underlying approach doesn't. What does change at scale is readability: very large groups may benefit from splitting into two or three smaller wheels covering sub-groups, rather than one wheel so packed with entries that individual slices become hard to make out.
Testing a wheel before using it for real
Before running a custom wheel in front of a group for something that matters, it's worth spinning it privately a few times first to check that every entry is spelled correctly, nothing important was left off, and the overall list still makes sense as a set. This small step avoids the awkward moment of noticing a typo or a missing name only after the group is already watching.
Naming entries clearly for a shared audience
When a wheel will be read by other people, not just you, entries need to make sense to someone without your full context. A shorthand that's perfectly clear to you (initials, an inside reference) can leave a group squinting at the screen trying to work out what a slice actually means. Writing entries the way you'd explain them out loud to a stranger keeps a shared wheel legible to everyone watching it spin.
Reusing one wheel structure across different activities
Many custom wheels share the same underlying shape even when the content is completely different — a "pick one of these options" structure works identically whether the options are games, meals, or discussion topics. Once you've built one wheel that works well for a given format, it's often faster to duplicate that structure and swap in new entries than to rethink the whole approach from scratch for a similar but distinct activity.
Handling entries that need different odds
Not every custom wheel should treat all entries as equally likely. If one option genuinely should be more likely than the others — a house favorite in a meal wheel, a more central topic in a discussion wheel — duplicating that entry a couple of times shifts the odds proportionally while keeping every other option's relative chances intact among themselves.
Iterating on a wheel after its first real use
The first time a custom wheel gets used for real is often the best moment to improve it — you'll notice which entries got laughs or engagement, which felt out of place, and whether the overall list still made sense once people saw it in action. Treating a wheel as a first draft rather than a finished product, and refining it after each real use, tends to produce noticeably better versions by the third or fourth time you run it, especially once you've saved it and can compare notes across sessions.
Practical setup for a custom wheel
- Nail down the exact decision first, then build entries specific to that decision.
- Keep entries in the same category and roughly the same scope on a single wheel.
- Save any wheel you'll reuse, and test it privately before using it live with a group.