The geospatial data that the users manage in the ADP is either data they ordered, data they imported, data from the archives, or data from a url. Ordering data was the first priority because it was the primary revenue driver for awhile. As we learned more about our users and the ADP has matured we’ve discovered new monetization strategies. So the priorities shifted from ordering data to importing data because now we could charge by usage. Along with the proposed change in how we present data, we should also consider ways to make ordering/importing experience as smooth as possible because it is the start of our primary revenue drivers.
User Goal
Users want to use their ordered or imported geospatial data on the map
Business Goal
We want users to order and import more data.
How might we get our users to order and import more data?
It doesn’t matter whether the data was ordered or imported, it ultimately becomes a layer that they can add to the map. This isn’t properly reflected in the ordering or importing flow. The current order flow has some glaring UX issues which we discovered during a usability test. All this, along with the unclear services catalog, are all obstacles that prevent users from placing orders within the system. My understanding is that users prefer to email an Aerial Admin then to order directly from the site. It’s also important to note that the ordering flow and import flow are two very distinct experiences and I believe that there may be an opportunity to unify them.
If we rethink what it means to order or import data and redesign the experience so it’s more aligned with the outcome of that action, users will import and order data more frequently. We hope this will reduce the dependence on Aerial Admins and increase revenue from greater usage and more orders.
Solution 01
Let’s change the CTA to “New Layer.” This better reflects what the outcome of ordering or importing data is.
Level of Effort
Low
Possible Dependencies
Wireframe