# What Spreadsheets Can Teach Us About Maritime UX
In 30 seconds
Unofficial spreadsheets and WhatsApp groups aren’t security breaches—they’re user-generated prototypes of the product you should have built.
When a ship breaks down, Technical, Operations, and Accounts each run their own spreadsheet.
Workarounds show the path of least resistance—don’t pave over them with stern memos.
Build a single, trustworthy product so intuitive it makes the spreadsheet redundant.
If you’ve spent any time, like I have, immersed in the world of enterprise software, you will have seen the ritual. You’re sitting with a user, watching them work. They get to a certain point in their task, pause, and anxiously glance over their shoulder to check that no one is watching. And then, like a spy swapping secrets, they open it: the unofficial spreadsheet.
Because sometimes, manipulating data in that humble, illicit spreadsheet is just easier than grappling with the bespoke, multi-million-pound official system that doesn’t quite do what you need it to do.
In the hallowed halls of corporate IT, they call it 'Shadow IT.' What it actually means is 'people trying to do their jobs with tools that actually work.' Banning it is like a restaurant owner getting angry that customers keep using the salt shaker.
To give you a maritime example; There are few phrases in shipping more terrifying than "vessel off-hire." When a ship breaks down, a klaxon goes off on shore.
Needs to know what’s broken—and tracks their own version of the truth.
Needs to know when it will be fixed—with a second set of formulas and data.
Needs to know how much money they are losing every second—in a third spreadsheet.
The result is a weekly, soul-destroying reconciliation meeting where highly paid professionals argue for hours, not about how to fix the ship, but about whose spreadsheet is the "least wrong."
And why does this spreadsheet nightmare exist? Because the official system, the one they paid millions for, has failed them. It can't provide a single, trustworthy, real-time view of off-hire that serves all three departments at once. The data is fragmented and ambiguous, so our users simply cannot trust it. Each team has been forced to build their own "unofficial" source of truth just to do their job.
Now, the typical corporate response to this is to try and ban the spreadsheets. To send out a stern memo about "unapproved software." This is the thinking of a complete and utter blithering idiot.
Those competing spreadsheets aren't a security risk. They are a beautifully detailed, user-generated feature request. They are three different prototypes of the product we should have built. The intricate formulas, the specific data points each department cares about, the way they’ve structured their columns—every single element is a clue. It’s a treasure map that leads directly to a better product. The same goes for the flurry of WhatsApp messages between a Crewing Manager and a Port Agent. That isn’t a compliance breach; it's a desperate plea for a real-time, context-aware communication tool that the official channels have failed to provide.
These workarounds are the desire lines of the digital world. They show you the path of least resistance your users will always take. You can either pave over them and force everyone to use your horribly designed official walkway, or you can have the humility to see where people are actually going and build a proper path.
So, the job of a design leader isn't to stamp out Shadow IT. It's to hunt it down. To find every rogue spreadsheet, every unofficial WhatsApp group, and study them with the reverence of an archaeologist finding a lost scroll. Because in them, you will find the truth.
Build a product so good, so intuitive, and so damn trustworthy that it makes the workaround redundant. Build something better than the spreadsheet. It’s the hardest thing you’ll ever do.
What's the most ingenious spreadsheet you've ever seen someone build to do their job? I'm fascinated by the unofficial systems people create when official ones fail.