Starship
Slotter

I replaced a spreadsheet and learned the spreadsheet was the easy part

Forty-one students, one shared sheet, and three weeks of finding out why nobody wanted my replacement.

The networks lab has eleven workstations and about forty people who need them. Booking was a shared spreadsheet. Two people would write in the same cell, one of them would lose their slot, and whoever noticed last lost the argument.

I built the obvious thing: a booking page with real rows in a database, one slot per row, a unique constraint so two people cannot hold the same one.

The part that worked

The constraint. A booking is an insert that either succeeds or fails. There is no version where two people both think they have Tuesday at 14:00. That took an evening.

The part that did not

Nobody used it.

I asked seven people why. Six gave the same answer in different words: the spreadsheet is already open in another tab.

That is the whole thing. My tool was better at the task and worse at the moment. The spreadsheet was where they already were.

What I did about it

I stopped trying to replace the sheet and started writing to it. The booking page now pushes every confirmed slot into the same spreadsheet, read-only. People who like the sheet keep the sheet. People who kept losing slots use the page.

Bookings in the three weeks since: 96, of which 61 came from the page. Double bookings: 0, down from eleven in the previous month.

What I still do not know

Whether the page would survive if I removed the sheet. I suspect not, and I am not going to find out during exam season.

8 reactions

One project a week, in your inbox

What was built, the numbers it produced, and what did not work. No other email, and one click to leave.