Navigation System
Designed the UX for a vehicle positioning system operating in low-light and GPS-denied environments, built for reliability under demanding field conditions.
Context
The client needed a new navigation system for a range of vehicles, from cars to submarines, operating in environments where standard GPS either fails or cannot be relied upon. The system had to function in low-light conditions and without network connectivity.
The constraint was unusual: we couldn't see the deployment context or the other tools the system would be used alongside, and we couldn't test with real end users. Timeline was tight.
Team
Two UX designers and one UI designer on the design side. The client team consisted of the product manager and his development team.
Methodology
Given the time constraints, we started with a detailed brief to identify the core functionalities. From there, we ran five co-conception workshops over six weeks, with wireframe iterations between each session.
After the wireframes were validated, we handed off to the UI designer who applied visual style and color. In parallel, we produced a UX guide explaining how each screen worked, so the development team could understand the design rationale and implement it correctly.
The Problem
[TODO: Add the specific challenges the positioning system needed to solve. What made GPS-denied environments difficult for existing navigation solutions?]
Project Goals
[TODO: Add four to six specific, measurable project goals tied to system reliability, usability in low-light/offline conditions, or device type coverage.]
Research & Strategy
[TODO: Describe research methods (given the constraints of not accessing deployment context or real users), key findings about the core use cases, and how you validated assumptions through co-conception workshops.]
Solution & Design Decisions
[TODO: Outline the key UX decisions made around navigation flows, reliability feedback, low-light readability, and offline-first interaction patterns.]
Outcome & Impact
[TODO: Add what shipped, feedback from the development team during implementation, or field testing results if available.]
Learnings
[TODO: Add two to four paragraphs reflecting on designing for constrained environments, designing without user access, or working with embedded systems teams.]