Prototyping (Apr 2018)
Scenario: Police Case Report Editor Enhancement
The South Sound 911 development team was gearing up to add a new feature to the police case report editor. This feature would make it easier to import person data from the computer-aided dispatch (CAD) system by grouping data and allowing the user to select multiple names at a time.
Goals
To make the best use of our time, we wanted to get user input on the design as soon as possible. The goal of the prototypes was to enable potential users to help us choose a design that was most intuitive for them.
Process
I collaborated with my project manager to create three high-fidelity prototypes (mine is "A"). We visited with field users to have them test out the prototypes and offer feedback.
- Option A used a simple list of tables, which was a pattern the users would be very familiar with from other applications. The default values were the system's "best guess" at good data, and the dropdown boxes allowed the user to select other options.
- Option B was the most visually similar to the user's existing (though less-featured) tool. It used more hierarchy by having the top-level list of names on the left and details for each name on the right.
- Option C gave users a glimpse of all the options at a glance when the top row was expanded.
Outcome
It was fascinating to observe the users' reactions to the prototypes. The users preferred the option which gave them the most control and ability to make accurate decisions up front, rather than the simplest or "minimalist" prototype.
With that knowledge, we built on the most popular prototype to create our minimum viable product. The new feature was released to beta and was received with enthusiasm by other users.