Team Check-In Question Wheel: 8 Work-Focused Prompts

What is a team check-in question Wheel?

A team check-in question Wheel is a small, reviewed list of meeting-opening prompts loaded into a random picker. The Wheel chooses one shared question; it does not choose who must answer. It works best in a recurring adult team meeting where several work-focused prompts are equally appropriate and the group wants a neutral way to vary the opening lens.

This page targets a different job from Randomly’s icebreaker and retrospective guides. An icebreaker invites a light, relationship-building response. A retrospective interprets evidence from a completed work cycle. A check-in surfaces the focus, change, dependency, risk, or support need that matters before today’s agenda proceeds.

The United Nations’ meeting material recommends questions that are quick and easy to answer, can relate to the meeting or the team’s work, and include an option to pass. Those constraints are more useful here than a catalogue of highly personal conversation starters. The prompt should help the room orient to the work without demanding disclosure.

Review the eight work-focused prompts

The quick-start Wheel contains eight questions covering outcomes, change, near-term focus, dependencies, clarification, risk, support, and continuity. Read all eight before the meeting and remove any prompt whose answer would require confidential details or duplicate an agenda item that already has a direct owner.

These prompts are intentionally operational rather than diagnostic. Do not add questions that ask people to reveal health information, family circumstances, protected characteristics, conflict details, customer identities, credentials, or performance concerns in front of the group. A public Wheel is not an employee survey, case-management system, or private feedback channel.

Choose the prompt before choosing the speaking order

Spin once to choose a shared question, then use the team’s normal voluntary response order. Do not spin again to select a person who must answer. Prompt selection and speaker selection are different decisions, and combining them can turn a low-pressure check-in into public pressure.

If the meeting also needs a random speaking order, complete the check-in first and use the separate speaking-order workflow afterward. Keeping the two lists separate prevents a person’s name from appearing beside a question that could be interpreted as an assignment or evaluation.

1. State the meeting purpose and what the check-in should help the group notice.
2. Show the eight prompt Entries, remove unsuitable options, and explain that one question will apply to the whole room.
3. Spin once, read the selected question aloud, and allow a short quiet pause before responses begin.
4. Invite brief spoken, chat, written, or pass responses in the team’s normal order.
5. Summarize the signal and say exactly whether it changes the agenda, creates a follow-up, or needs no action.

Keep a check-in distinct from a Daily Scrum

A check-in Wheel can support many recurring team meetings, but it should not redefine a formal Daily Scrum. The current Scrum Guide says Developers choose their own structure as long as the event focuses on progress toward the Sprint Goal and produces an actionable plan for the next day. Use the team’s agreed Scrum practice directly when that is the meeting you are running.

Do not create variety for its own sake. A stable recurring question may be better when the team compares the same signal over time. Use the Wheel only when any remaining prompt is genuinely useful today and a varied lens will help more than a consistent measure.

Run the round without turning it into surveillance

Tell participants what the answer will be used for, keep the round short, accept a pass without explanation, and avoid recording attributed responses unless the team already has an approved reason and system. A check-in should reveal what the meeting needs to handle, not create an informal performance record.

If someone raises a safety, people, legal, security, or other sensitive issue, stop the public round and route it through the qualified process. Random selection is not an escalation policy. Likewise, a participant’s decision to pass is not evidence of disengagement and should not be scored or interpreted in the room.

Make remote and hybrid participation equivalent

Display and read the selected question, allow quiet thinking time, and offer equivalent spoken and written response routes. Do not require cameras, fast typing, or a visible emotional reaction. Record the resulting agenda change in the same place for remote and in-room participants.

Randomly keeps Entries in the browser by default. A Shared Setup stores its configuration in the URL fragment, so the Randomly server does not receive the prompt list with the page request; anyone who receives the complete URL can still inspect it. Share only neutral prompts and keep actual team responses in the team’s approved communication system.

Presentation Mode removes setup distractions for a shared screen, but the facilitator should still read the Winner aloud and provide a text version. Animation is optional context, not the only way to understand what was selected.

Know when a random question is the wrong tool

Skip the Wheel when the meeting has an urgent known issue, only one suitable question, a formal reporting requirement, or a sensitive people matter. Ask the necessary question directly or use the documented process. Randomness is useful only when several reviewed prompts are interchangeable and the consequence is low stakes.

A manager should not use a random prompt to avoid a difficult conversation, gather hidden performance evidence, or pressure the group into public disclosure. A team should not use it to decide employment, disciplinary, medical, legal, financial, safeguarding, emergency, or regulated matters. The facilitator owns that boundary before the page is opened.