​

INRIX does traffic data. In fact, INRIX supplies much of the traffic data that mobile navigation apps use to display congestion and incidents. INRIX leverages vehicle connectivity, advanced parking management, dynamic data for city planning and traffic flow optimization.

​

With the approach of autonomous vehicles, INRIX wanted to expand its offerings into this new area. The Autonomous Vehicles RoadRules (AVRR) project set out to provide an archive for municipalities and transportation authorities to record their rules of the road, namely speed limits, turn and lane restrictions, and the like.

​

INRIX had created a POC more than 6 months earlier. Most of the work had gone into the back-end, and the UX was produced quickly with little user input. Alpha users complained it was too hard to use without hand-holding from INRIX. The original designer left and was contracted to redesign and complete the UX.

​

With no artifacts other than the POC available, my first steps were to identify a feature we could walk through end-to-end. This would build our design muscle while I onboarded. Because of its necessity and apparent straight-forwardness, assigning a speed zone was selected. 

​

INRIX had staffed the dev team before I came aboard. To load their queue, I was asked to design several setup features first. This was a good idea in that it helped me explore the visual design space, the design aptitude of the team, and the capabilities and work style of the dev team. 

​

Having not worked with interactive maps before, I started by reviewing other mapping applications, including Google Maps and Bing Maps, and geospatial applications, like the ones a city would use to show its infrastructure.

​

These mockups show the process and interaction I designed for selecting a roadway and placing a speed limit on it.