5Maps Analytics Application

I was asked to create a mapping application that combined the features of Forecast5's existing mapping application and that of an acquired company. The intent was to modernize the application to appeal to both sets of customers while retaining the functionality that each set found most useful.

I held a kickoff meeting with the new product owner, lead developer, and subject matter experts from both products to understand the needs of each client base. We reviewed functionality and came up with a list of features that either needed to be added to 5Maps, or existed in 5Maps and needed to be updated. We also discussed pain points for current users in both products. Based on that initial discussion, we identified a workflow and the pages needed to accomplish the most popular tasks.

The core group (lead developer, the product owner, and myself) met twice weekly to review ideas and iterations, with a SME present for the topic being discussed as well. Because these meetings were held online over Zoom and sketching and sharing could be time-consuming, the product owner or SME would typically have either sketched out an idea for discussion or brought an example from a competitor. We would discuss those as a group to ask questions related to our clients needs, determine feasibility, and discuss what it might look like in 5Maps.

I created wireframes based on our discussions that we would review at the next meeting. When we had completed a workflow for a particular task, I would add it to our prototype and test internally with users familiar with our clients and their tasks. They would work through real-world examples and provide feedback for continued iteration.

Because we went through our topics systematically, beginning with the most important functionality and pages, I was able to deliver annotated wireframes to development regularly so they could work as we continued to design. Additionally, by involving the lead developer in the design discussions, we headed off most potential issues with development time and feasibility, resulting in a quicker development overall.

We released the MVP version of the new 5Maps to a select group of clients from both customer bases, and continued to iterate on the nice-to-have features. By showcasing this improved version of the software at our yearly conference, we exceeded our business plan for client migrations to the new software (which had a higher price point), and increased year-over-year client retention as well.