Home ยท Whiteboard Challenge Starter Kit
30-minute whiteboard challenge framework
A repeatable way to run a product or UX whiteboard round in 30 minutes. Interviewers score your reasoning and how clearly you communicate it, not how polished the boxes look.
Clarify the challenge
Turn a vague prompt into a bounded problem you can solve in this room.
- Restate the prompt in your own words before you ask anything.
- Cover users, constraints, success, platform, and what is out of scope.
- Confirm one problem statement, then move on.
See also: Clarifying-questions cheat sheet.
Identify users and usage context
Name who you are designing for and where the product shows up in their life.
- Pick a primary user. Mention secondary users only if they change the design.
- Note the setting: device, frequency, time pressure, and who else is involved.
- State the job the user is trying to get done.
Define and prioritize user needs
Show you can rank, not that you can list everything.
- Write 3 to 5 needs or pain points.
- Rank them. Circle the one or two you will solve now.
- Say which need you are deferring and why.
Generate multiple ideas
Diverge before you commit, so the later choice looks considered.
- Name 3 directions, not 3 shades of the same app.
- Vary the product type, platform, or interaction model.
- Keep each idea to a label and one line. Do not draw screens yet.
See also: 10 realistic practice prompts.
Select a direction and explain tradeoffs
Choose in public, with reasons the interviewer can follow.
- Pick one idea and say what you are giving up.
- Tie the choice back to the top user need and a real constraint.
- Name what would make you switch.
Create a user flow
Show the path from intent to outcome before you draw interface.
- Map the happy path in 4 to 7 steps.
- Mark the entry point, the key decision, and the success state.
- Note one error, empty, or edge state if time allows.
Sketch the proposed experience
Make the flow legible. This is not a visual design critique.
- Draw the 2 or 3 key moments as simple frames.
- Label what matters. Use words if drawing is slow.
- Show hierarchy: what is primary and what is secondary.
- Skip color, alignment, and component polish.
Define success metrics
Say how you would know the solution worked.
- Pick 1 primary success metric and 1 guardrail.
- Make them observable. Avoid "users are happy."
- Connect them to the need you prioritized.
Summarize the solution and next steps
Leave a crisp story and a next step the interviewer can remember.
- Restate the problem, the user, the choice, and why.
- Recap the flow in one breath.
- Name what you would prototype, research, or cut next.
- Stop while you still have the room.
See also: Self-evaluation rubric.
Related resources
- 10 realistic practice prompts: Ambiguous, interview-style prompts you can run on your own or in a WiBo session. Built to feel like the real whiteboard, not a portfolio tutorial.
- Self-evaluation rubric: A 1-to-5 self-score for a finished round: framing, questions, product thinking, communication, and close. Practice only, not a hiring prediction.
- Clarifying-questions cheat sheet: The questions interviewers expect early: users, constraints, success, platform, and what is in scope. Use it so you do not freeze on a vague brief.