Designing interfaces for vessel systems where a confusing screen isn't just bad UX. It's a safety question. This work sits under a non-disclosure agreement, so what follows is the context, my role, and what the domain demanded, not the screens themselves.
Kongsberg Maritime is the first truly global issuer of bridge systems, automation, and autonomous vessel technology, and the products I worked on are covered by a confidentiality agreement that doesn't expire when the contract does.
Kongsberg Maritime builds the systems that let vessels operate safely, efficiently, and increasingly remotely. Publicly, the company describes its work spanning bridge systems and control centres, vessel automation, and a growing portfolio of remote and autonomous ship technology, including Remote Operating Centres that let qualified personnel monitor or control vessels from anywhere with the right connectivity.
That public context matters because it explains the constraints I designed within, even though the specific interfaces stay confidential. Situational awareness systems fuse sensor data from 360 degrees around a vessel and must perform in poor weather and at night. Automation systems run engine rooms. A Remote Operating Centre might let a Chief Engineer's duties move from onboard a ship to a desk-based workstation onshore. None of that works if the interface is unclear, slow to read, or asks an operator to interpret ambiguity under pressure.
The description above draws on Kongsberg Maritime's own public materials on remote and autonomous ship technology, not on any confidential project detail. You can read more directly at kongsbergmaritime.com.
As UX/UI Designer, I worked on interfaces for complex maritime industry platforms, where usability and reliability weren't abstract design values but directly tied to how safely and confidently a vessel could be operated. The work spanned the full range from early research through shipped product.
"Every other project I've done, I get to show the thinking. Here, I had to learn how to talk about rigor without evidence on the page, which turned out to be its own design problem."
Working under NDA is its own kind of discipline. It means internalising design judgment well enough to defend it in a room without a screenshot to point to, and it means taking documentation, rationale, and process seriously even when no one outside the team will ever see the artifact. That habit carried over into every project I've done since.