RADIO: driving a frontend design round

A speaker has one slot and an agenda slide.

At the talk	In the round
asking the organiser who will be in the room	requirements (step 2)
the agenda slide: sections, and how each leads to the next	architecture (step 3)
what each section carries	data model (step 4)
the hand-over line between two sections, written once the sections exist	interface (steps 5–6)
two live demos chosen for this audience, not one per feature	the deep dives (steps 8–9)
the timekeeper's card at each section's planned end	cumulative checkpoints (step 11)
the last five minutes are the audience's questions; a long opening costs demo time	lost minutes come out of the dives (step 12)

In real terms: the five phases are the outline, the clock protects the depth, and the candidate, not the interviewer, decides where the depth goes.

Breaks down when: an audience rarely interrupts. An interviewer may name an area to focus on; then that area is the dive, and the plan bends to it.

Contrasting case: a talk with one slide per feature and no demo. Every box is covered, and nothing is shown in depth.

4.1 ExamHall: a rehearsal that ran out of room

Requirements ran long, and at the Optimizations phase the candidate gave each of six areas two minutes. MR !1640 rehearses on the phase clock instead.

plan        Requirements 5 · Architecture 8 · Data model 5 · Interface 6 · deep dives 16 · closing 5 = 45
checkpoints Requirements 5 · Architecture 13 · Data model 18 · Interface 24 · dives end 40 · round ends 45
EXH-1440 Requirements ended at 11 vs checkpoint  5: 6 behind
EXH-1440 Architecture ended at 20 vs checkpoint 13: 7 behind
EXH-1440 Data model   ended at 24 vs checkpoint 18: 6 behind
EXH-1440 Interface    ended at 30 vs checkpoint 24: 6 behind
EXH-1440 six areas x 2 min = 12 min: ends at 42, 2 into the closing 5, no area in depth
MR !1640  deep dives get 40 - 30 = 10 min: two areas of 5, round ends on time

The candidate was behind from the first checkpoint, and a Data model one minute under budget won one minute back (step 11). Spreading the rest evenly overran the closing minutes and showed no depth (steps 8, 12). With the clock, the two dives shrink and the ending stays.

4.2 Proof domain, e-commerce catalog: one board for the search results page (worked, not executed)

The prompt is "Design the catalog's search results page". What each phase puts on the board:

Phase	On the board
Requirements	desktop and phone? which browsers? one language?
Architecture	SearchPage holding FacetPanel, ResultsGrid and ProductCard, plus a client-side query cache
Data model	products and facet counts from the server, by id; the shopper's picked facets and page, which never reach the database (where each lives is fsd-state-ownership)
Interface	GET /search?q&facets&cursor → { items, facets, nextCursor }; ResultsGrid props { items, onLoadMore }
Optimizations	performance (an image-heavy grid) and accessibility (facets used by keyboard), each named with its reason; offline and i18n set aside, since the shop is online-only and one-language

No box on this board is a server. The two dives are chosen from the product's facts, and the reasons are said aloud.