Helping traffic engineers make more informed
traffic safety decisions
Starting in February of 2019, while working for FordLabs (a software incubation firm internal to Ford Motor Company), I began working on RoadCode, a safety visualization tool designed to help traffic and safety engineers make more data-informed safety decisions. The project originally kicked off for the US Department of Transportation’s “Solve for Safety” competition but, due to the success of our team and project, RoadCode is now in the process of being a fully commercialized product. RoadCode was selected as one of two finalists for the competition (out of a field of over 50 entrants including Uber and Allstate Insurance) and still awaits the final results of the competition.
ROLE: Product Designer
TEAM: Product Manager, Product Owner, Engineers (4), Data Scientist, Safety Analyst
TIME: Feb - Mid June (3.5 months)
METHODS: Interviews, Personas, Design Studios, Sketching, Hi-Fidelity Comps
When making decisions regarding traffic safety, engineers at local, county, and state road agencies are limited by the use of only one data set: crash data. Crash data only gives information about what happened a year prior. In addition, the tools they currently use are often old, clunky and hard to use.
Thus, the question my team and I set out to answer was:
How might we help traffic and safety engineers (TSEs) make better, more well-rounded decisions by allowing them to visualize and use various types of data (crash data, connected vehicle data from Ford cars, and cell phone data) all in one beautifully designed interface?
Because of the competition, we were on a tight deadline: to design and develop a MVP version of RoadCode in approximately three months. In addition, the high-level concept of what RoadCode would do was somewhat pre-defined since the team that kicked it off had applied for the competition six months prior.