Accessibility Navigation Platform
This case study reflects work completed in a consultancy environment. Client names, internal terminology, and visual artifacts have been removed or generalized due to confidentiality agreements. Because this platform was internal to the organization, original UI screens and workflow diagrams are not included. The structural challenges, leadership decisions, and measurable outcomes are accurately represented.
Overview
This indoor navigation system was designed to help blind and low-vision people navigate buildings. A mobile application provided navigation assistance, while a web application allowed facilities teams to configure the building information and routes behind that experience.
I joined to lead product design for the web application. Early designs were in place, but important interactions remained unresolved. As the team explored additional requirements, those designs became difficult to extend.
The work focused on making the mapping workspace easier to use and establishing an interaction model that design and engineering could develop together.
My role
I led product design, UX design, and design strategy for the web application.
I reviewed the existing designs, researched facilities managers’ responsibilities, and worked with engineering to rethink the mapping and editing experience. Much of my contribution involved low-fidelity exploration: making proposed behavior tangible, identifying technical constraints, and resolving questions before investing in detailed interface design.
The challenge
Facilities teams needed to upload floor plans, define locations, and connect them into navigable routes. They also needed to maintain that information as buildings changed.
The existing designs approached much of this work through mobile-style interactions. Frequently used tools were hidden behind menus and a floating action button. Some edits required leaving the mapping workspace, and contextual menus could obscure nearby map elements.
There were also unresolved questions about how the system would support more complex buildings and connections between floors. We needed to work through those behaviors without treating the existing screen designs as fixed constraints.
Approach
I began by reviewing the designs with the development team and identifying where interaction decisions were creating usability or implementation problems.
Access to representative users was limited. I researched facilities managers’ day-to-day responsibilities and used the client’s input and discussions with our own facilities manager to inform the work. This helped us consider how mapping tasks would fit around their other responsibilities, while recognizing the limits of what we had validated.
I advocated returning to low-fidelity wireframes. Working at that level made it easier to explore alternatives, invite engineering input, and change direction as we learned more.
The work
Keeping the map at the center
The map was the main workspace, but several interactions took users away from it.
I proposed keeping floor controls directly within the mapping interface so people could move between levels without leaving their work. A supporting list of map elements also provided another way to find and select items.
The aim was to keep the information needed for an editing decision visible together.
Making frequently used tools visible
Creating map elements required accessing tools through a floating action button.
For this desktop workspace, I proposed a visible toolbar above the map. This gave frequently used tools a consistent location and reduced the need to open a menu before beginning an action.
Editing without covering the workspace
Contextual editing menus could cover other elements on the map, making it harder to understand the surrounding layout.
I proposed moving editing controls into an inspector beside the map. Its contents changed with the selected element, bringing the relevant information and controls into one place.
This let users inspect an item’s properties while retaining a view of the map around it.
Working through connections between floors
A building’s navigation network needed to extend beyond a single floor plan.
I worked with engineering on how users would connect locations across levels. We explored selection-based controls that presented likely connections alongside alternatives, giving users a starting point while allowing them to correct the choice.
This was one example of why we needed to define behavior together before refining the interface.
Results
Internal testing with our facilities manager provided encouraging feedback on the revised interactions.
The low-fidelity approach also gave design and engineering a more productive way to work through unresolved requirements. We could compare alternatives and discuss implementation constraints before committing to detailed screens.
Development was later paused because of funding constraints. The project did not reach a broader release during my involvement, so the available feedback reflects internal evaluation rather than demonstrated outcomes for the wider user population.