How to sketch fast when you can’t draw

The purpose of sketching in a whiteboard challenge is to make your logic visible — to you, as part of your thinking process and a way of making sense of the problem through visual thinking, and to the interviewer, so they can follow. Before you start, clarify the problem and the user needs, since sketching is a functional tool for organising thoughts. A rough box labelled “home screen” communicates everything a beautifully rendered mockup would, in two seconds instead of two minutes, because the point is to explain your design process rather than to make art. Every second you spend making a sketch pretty is a second not spent thinking, and the interviewer would rather watch you think.

You can express almost any product idea with a tiny kit:

• Rectangle — a screen, a component, a container.
• Rounded rectangle — a button or an input.
• Circle — a user, an avatar, a state.
• Arrow — a flow, a transition, a cause.
• Line + label — a relationship or annotation.
• Stick figure or a box marked “user” — a person in the system.

That is the whole alphabet. A user flow is boxes and arrows. A screen is a rectangle with a few labelled rectangles inside. A system is circles connected by lines. These are standard wireframing conventions, so the moment you use them the mockup is recognisable — and visual hierarchy does the rest: bigger boxes, deliberate spacing, and labels keep the focus on the most important thing. Nothing here requires drawing ability.

Briefly explore a couple of directions first, then commit. Draw: the one or two critical screens where your key decision lives; the user flow as a chain of boxes; a table when you are comparing options or mapping frequency against severity. These carry your argument, and it is worth noting edge cases and trade-offs directly on the sketch. If a better direction appears, revise rather than defend the first concept.

Skip: icons, realistic imagery, colour, pixel alignment, every screen in a flow (draw the two that matter and say “and the rest follow the same pattern”). Time spent here is pure loss.

Label everything. An unlabelled box is a puzzle; a box labelled “insufficient-funds screen” explains why the concept works, not just what it looks like. Labels do more work than lines.

The fastest sketch is one you narrate as you make it: “I’ll put the amount buttons here, big, because this user is standing in a queue and can’t fumble.” Narration means the sketch never has to stand alone — the interviewer understands it as it appears, so it can be rough. It also keeps the room with you during the seconds your hand is moving, which is when candidates most often lose the thread. If the interviewer gives feedback, iterate live rather than defending the first version — adapting on the spot reads as senior. Timed practice runs out loud, on a real board, build exactly this habit, and after a handful of them the drawing stops being the scary part.