The work is under NDA, so the visuals are altered.
In short
Eptura’s desk screen is a small display fixed to a desk in the office. Version 1 did one job: it let you check in to the desk you’d booked.
Research showed people wanted more from it, so I designed version 2 to deal with the problems people actually hit at a desk, on a screen 640 pixels wide, in the few seconds they spend looking at it. It tested well [TEST: headline result]. It was never released.
How it was: A clock that checked you in
Version 1 showed an analogue clock face and a check-in button. That’s useful once a day and decorative the rest of the time.
The research told a fuller story. People arrived at broken desks with nowhere obvious to go. They rebooked the same desk every day in the app. They had no way to report a fault or say whether a desk was any good. The screen wasn’t failing. It was being asked to do very little.
The ask: Earn every pixel
I carried out audits, a competitor review, interviews and tree tests to find out what people needed at the desk itself, rather than in the app.
The constraint was severe. A 640 by 360 pixel screen, read by someone putting their bag down. Every feature had to justify its space, and anything that could wait for the app had to.
What I did: Three jobs, in order of need
Make the normal case quick
Four booking types cover how people actually work: all day, morning or afternoon, by the hour, and by shift. You check in with your staff badge, a PIN or a QR code, with a countdown that shows how long you have. Extending a booking takes one tap.
Help when things go wrong
If the desk is broken, you can swap to another from the screen and report the fault to facilities in the same visit. Nobody has to go looking for a free desk or a person to tell.
Make the good desk yours again
You can book the same desk for another day, rate it and add it to your favourites, without opening the app.
Setup in one scan
Setting up a screen takes one QR scan. I looked at setup that needed no action at all, and recommended against it: the engineering cost didn’t match the number of screens being sold. The packaging follows the same thinking. Rip it open, plug it in, scan, move to the next desk.
Where it stands: Tested, not released
[TEST block – see 00-testing-framework.md]
Method
Unmoderated Maze test, [n] participants; moderated sessions with [n] [CHECK who]
Task
[TEST]
Task success
[TEST]
Time on task
[TEST]
Ease rating
[TEST]
What people said
[TEST: one real quote]
These are results from testing before release, not from use in offices. Version 2 was not released.
Then and now: From weeks to days
When I designed version 2, I couldn’t test an idea until engineering built a prototype. Each round took weeks. While I waited, decisions stayed unproven and changes queued behind sprint work.
For this case study I rebuilt both versions in code with Claude. The two screens near the top of this page aren’t pictures. They run the version 2 booking flow in your browser.
That changes how I work. I can try an idea, test it and refine it in the same week, then hand engineering working code instead of a description of it. Engineering still owns the build. They now start from something already tested, and I no longer wait on them to find out whether an idea works.
In hindsight: Small screens, hard choices
Most of the design work on this project was saying no. A screen this small has room for a handful of things, and the hard part was deciding which ones mattered most to someone standing at a desk with a coffee in one hand.
It never reached an office. The thinking did reach the rest of my work: decide what someone needs in the moment, put that first and leave the rest to somewhere with more room.