Client
EIVA A/S
Role
Product Design Lead
Year
2025-2026
The central design challenge was:
How might EIVA make the next generation of NaviSuite feel like one coherent product experience while preserving the expert power, flexibility, safety and data-quality control that maritime users depend on?
Key areas of focus
Fragmentation across NaviPac, NaviScan, Helmsman, Kuda, Mobula, VSLAM and related tools.
Similar tasks appearing in different programs with different interaction patterns.
Steep learning curves for newer users.
Configuration concepts that were necessary but difficult to reason about visually.
Need for clearer system readiness, recording, sensor health and data-quality feedback.
Emerging autonomy workflows that required supervision, trust and override capability.
5 UX workstreams
Unifying acquisition workflows and future platform direction.
Making technical setup easier to understand and recover from.
Translating computer-vision workflows into readable system states and controls.
Supporting planning, monitoring, intervention and post-mission review.
Creating shared foundations for Figma, components, variables, handoff and governance.
5 UX workstreams
Unifying acquisition workflows and future platform direction.
Making technical setup easier to understand and recover from.
Translating computer-vision workflows into readable system states and controls.
Supporting planning, monitoring, intervention and post-mission review.
Creating shared foundations for Figma, components, variables, handoff and governance.
MOST OF MY WORK IS NDA!!! So you won’t be able to see much of any UI work.
LEGACY UI:
WIP UI:
Power was not the problem. Clarity was.
Users valued the depth of EIVA’s software. The problem was that capability was distributed across too many products, views, settings and inconsistent pathways.
Acquisition needed a shared product model.
NaviSuite Acquisition could be understood as a family of connected workflows, not just separate applications.
Different roles needed different depth.
A surveyor, ROV pilot, client representative and data processor do not need identical interfaces. They need role-appropriate visibility, control and detail.
Configuration was a core UX problem.
Vessel definitions, sensors, offsets, reference points, geodesy and calibration all shaped whether users could trust the data they collected.
Maritime UX happens under pressure.
Users may work on moving vessels, in sunlight, with small screens, limited attention and real operational consequences.
Autonomy changes the interaction model.
Users need to plan, simulate, supervise, intervene and evaluate autonomous missions — not simply control a vehicle directly.
A design system needed governance, not just components.
Consistency required shared naming, variables, Figma practices, interaction rules, theme support and implementation handoff.
Outcome
The work helped EIVA move from a fragmented product landscape toward a clearer, more coherent and user-centered NaviSuite direction.
It contributed by:
Turning scattered user feedback into a clearer product narrative.
Identifying fragmentation and unclear information architecture as recurring UX problems.
Framing role-based access and task-based workflows as a way to support different user types.
Translating configuration and sensor setup into readiness, guidance and recovery concepts.
Making VSLAM and Discovery workflows more understandable through status, controls and feedback states.
Connecting autonomy strategy to mission planning, monitoring, override and review.
5
UX workstreams connected into one product story
9
Primary user groups considered across maritime operations
8
Workflow stages mapped from mobilization to delivery
Next Project
