waitingroom
waitingroom is a prototype that fills the gap between Figma and implementation, where the behaviour of a component is decided and currently written down nowhere.
A room for behaviour rules and independent design iteration. The step between a specification and a built component, a waiting room.
Built with
- Static HTML, CSS and JavaScript, no build step
What it is for
A component library gives you a radio group and a select. A colour system tells you what they look like. Neither tells you when to use which.
That from five options on, a radio group becomes a select. That a person's surname is never truncated. That a single option is not a choice at all. Those decisions are project-specific and usually made silently — in a Figma file, in an implementation, in a chat message.
In numbers
2026 1 Day
How it works
- Gap after the spec
- One rule, executable
- Control panel
- Stated and justified
A rule becomes executable: a prototype that actually applies it, with a control panel to drive it past its own thresholds.
And readable: stated, justified, with its edge cases — and with what it does not answer.
What it is not
It is not production code! Nothing here is meant to be shipped or held to production standards; if it looks like a delivery, that is a bug in the presentation.
It is not a component library either. Four of the eight steps in the workflow are marked as the team's own. The point is to slot into their process, not to replace it.
What's next
Awaiting stakeholder review
What can Iget out ofyour way?
Reach out