Case study · 2024–26
Scheduling for marine service yards
This case study is sample content. Replace it with verified work before production deployment.
The schedule lived in several places at once: a whiteboard, a spreadsheet, and the heads of people who had worked at the yard for years. A booking could look valid in isolation while still asking too much of the lift, the tide window, or the available crew.
I started with the constraint model, not the calendar interface. We wrote down which conflicts were impossible, which were warnings, and which needed a human decision. The interface then exposed those rules in plain language instead of hiding them behind a generic red state.
The first release kept the whiteboard visible beside the screen. That made the transition reversible and gave us a clean way to compare the old plan with the new one during real work.
The shared schedule reduced double bookings and made capacity visible earlier. The useful outcome was not that the whiteboard disappeared. It was that the morning meeting stopped being an exercise in reconstructing yesterday.
A durable decision leaves enough context for the next person to understand the tradeoff, not merely the outcome.
