Create and share
Design a Community Wheel With a Promise, Loop, and Content Map
Plan what the title promises, what happens after every spin, and which kinds of entries create real variety before writing a giant prompt bank.
Open the matching wheelBlueprint for the Bad Advice Hotline wheel
The promise is simple: players improvise a terrible but harmless answer to a ridiculous caller in ninety seconds. One person is the caller, one is the adviser, and the result supplies the problem.
- Loop: spin, read the caller problem, assign caller and adviser, improvise for ninety seconds, then switch roles.
- Lane one is tiny emergencies, such as “my sandwich is cut diagonally.” Lane two is impossible etiquette, such as “a ghost keeps arriving early.”
- Lane three is suspicious purchases, such as “my invisible chair is missing.” Lane four is social confusion, such as “my neighbor waves with both hands.”
- The rejection test is: can two players begin a scene from this line without another explanation? A phrase such as “banana chaos” fails even if it sounds funny.
- The creator writes three entries per lane, tests twelve total, and removes any prompt that repeatedly produces the same joke.
The blueprint creates an original game structure and a varied pilot bank. It does not replace the later checks for labels, phone layout, saving, or the recipient link.
Write the player promise in one sentence
Complete this sentence: this wheel helps people ___. “Improvise a ridiculous customer service call in under two minutes” is a promise. “Have fun with friends” is too broad to guide the entries. Name the audience only when it changes the design, such as a seated classroom round or a late night adult party. The promise is an editorial filter, not a slogan. Every proposed entry either helps deliver it or belongs in another idea.
Draw the loop from spin to finish
Write the repeated sequence as five verbs: spin, read, assign, play, reset. Define who acts, how long the turn lasts, and what changes before the next spin. If each result needs a different explanation, the loop is not stable yet. A stable loop lets varied content feel like one game. The creation guide handles the tool format; this blueprint handles the experience you are putting inside it.
Build content lanes before individual entries
Choose three or four kinds of result that express the promise in different ways. A fictional customer service wheel might use impossible returns, absurd complaints, suspicious product features, and overconfident solutions. Lanes prevent a bank of fifty entries from becoming the same joke with a different noun. Give each lane a purpose and a rejection test. “Does this create a playable scene, or is it merely a funny phrase?” is a useful question.
Pilot twelve entries, then study the repairs
Write three entries per lane and run two short rounds. Record where the host had to explain, where a turn ran too long, and which lane produced the same response every time. Repair the design before expanding the bank. The release test begins after the concept is stable and checks the actual artifact. Keeping concept feedback separate from technical testing makes it clear whether the idea failed or the link did.
Publish a truthful invitation
The title, description, and first visible entries should describe the same experience. Say whether people answer, perform, decide, or build a story. Mention a meaningful limit such as two minute turns or no equipment. Do not promise a live multiplayer experience if you are sharing an independently spun wheel. Use the sharing guide to match the invitation to the destination people will actually open.
A one page creator blueprint
- Player promise in one sentence
- Audience and setting only where they affect play
- Five verb round loop
- Turn length and ending
- Three or four content lanes
- One rejection test for weak entries
- Twelve entry pilot
- Truthful title, description, and invitation