Lay Out a Week on a Whiteboard Before Writing Code

Blog ZH

TanBlue Studio

Quiet notes from a small studio.

Blog Post

Lay Out a Week on a Whiteboard Before Writing Code

What a dental clinic booking system taught us

  • Research
  • Business systems
  • Scheduling
Show contents
  1. 1. One whiteboard session
  2. 2. The real requirement
  3. 3. Why not just ask?
  4. 4. What we do now

Before building the dental clinic booking system, we assumed the hard part was booking. It wasn't.

One whiteboard session

In week one we didn't open an editor. We borrowed a whiteboard at the clinic and asked the receptionist to put last week's appointment book on it, one sticky note per visit: which dentist, which chair, what time.

Halfway through, the picture was clear:

  • Nearly a third of the notes had been moved at some point;
  • Some had moved two or three times;
  • Follow-up visits for root canals were often only remembered after the patient had left.

The real requirement

The receptionist's biggest time sink was rescheduling, not booking. So in the system:

  • Rescheduling is a drag, with no form to open;
  • Every change is logged — who moved it, and how many times;
  • Multi-visit treatments use templates that book the later visits up front.

Why not just ask?

We did ask what the most annoying part was. The answer was "it's all fine". People rarely notice friction in what they do every day. You have to lay it out to see it.

What we do now

For every business system since, we start by laying out one real week of data on a whiteboard or paper. It's faster than writing a requirements document, and far more accurate.