Explore - A web application for uploading, styling, analyzing, and sharing spatial data.

End-to-end UX and UI Design
Project Overview
The visualization of spatial data is critical for radio frequency engineers working at a telecommunications company to accurately and efficiently monitor and improve coverage throughout the network. When we started this project each engineering team was using different software tools to visualize data from their local devices, resulting in data silos, inefficiencies and costly subscriptions. To address this, we developed a web-based application that gives teams a centralized repository for spatial data, allows users to combine their data with other teams' data, and facilitates the creation and sharing of custom maps and dashboards.
My Contributions
I was the lead designer on this application throughout multiple phases of work from inception through MVP and continued releases (2019-2022).  I worked on the end-to-end research and design of the application. I created all key MVP workflows and developed an MVP design system. I worked with a product manager and a team of five developers. In late 2022 the team scaled to include an additional designer and three more developers.
Initial Research and Buy In
Phase 1 - Q3 2019
Goals:
Establish which tools are being used throughout the organization for visualizing spatial data and determine users' satisfaction with their current tools/identify pain points.
‍
Method:
Survey - The process started with a survey to better understand which tools were being used, the types of data being viewed, and engineers' pain points with their current processes. I wrote a survey that received 93 responses, and synthesized the results.
Interviews - As a follow up to the survey, I conducted 12 contextual inquiry interviews to observe the engineers' processes to identify ways to improve efficiency.
Brainstorm - I then presented insights from the research to the product development team and we discussed ways in which our team could help improve data access and visualization for RF engineers.
Buy-in - We met with various stakeholders (executives and senior engineers throughout the organization) to present the vision and get their feedback and buy-in on the idea of creating a new application for RF engineers.

Outcomes:
Vision - We decided to build an application and data repository that combines all of the spatial data that RF engineers rely on in one place, and provides them with access to the most up-to-date data available.  
MVP planning - We created an MVP backlog for the application.
MVP Design
Phase 2 - Q4 2019 - Q4 2020
MVP goals:
Central data repository - RF engineers found it difficult to find relevant and current data, so we decided to build a data repository where individuals and teams could upload their data.
Custom map creation and sharing - Users were frustrated that they needed to go to multiple applications in order to view the data they needed to analyze for day-to-day work, so we added a feature that allows users to create custom maps with any combination of datasets in the repository.

Methods:
Low fidelity ideation/mockups - I started the process by creating flows and low fidelity mockups.
User feedback - Based on previous research, the team was able to identify some potential super users for the application. These super users provided rapid feedback as I iterated through various low-fidelity mockups. After approval from the super users, I sought out feedback from other potential users to further validate the designs.
High fidelity mockups - Mockups were validated with users and then provided to the development team using Zeplin for handoff.
Agile development - Our product development team worked in two week sprints with designs created ahead of development. Throughout the implementation, I was in close contact with the dev team to ensure that the designs met technical specs and that the UI was implemented as intended.
‍
Outcomes:
Successful launch - feedback form users was overwhelmingly positive. The product team started hosting informational sessions to showcase the tool and within a couple of months we were seeing between 700 and 900 logins each month.
Product backlog created - Through the informational sessions the product team was able to identify additional features that would be beneficial to our user group. We added these to the application backlog and began to develop a roadmap for continuous improvements.