SV350 In Vehicle Interface

Interface that manages multiple Cameras, Microphones, and Sensors throughout an officers vehicle and on-body equipment.

THE ASK

Our mission was to fill a gap in the Motorola Solutions portfolio. My task was to build a cutting edge interface that managed multiple Cameras, Microphones, and Sensors throughout an officers vehicle and on-body equipment. I was tasked with innovating to make this product superior in the market.

RESEARCH

Research & Design Workshops would create an open forum of innovation to ideate how this system would seamlessly interact with the rest of our device portfolio. Not only how it would interact but what opportunities this device brings to the overall system. An example being the ability to store and transfer information back to the proper authorities without draining a smaller devices battery by relaying through the vehicle.

Stakeholder Meetings would create requirements to determine the MVP for this launch. This would identify the features I would include in the design of this interface.

Discovery and Empathy workshops where stakeholders, users and myself would work together to understand the complexities behind designing for in the vehicle use. To better understand the critical scenarios that these interfaces are being used in.

Collaborating with our Human Factors team, I would dive into the intricacies of in-vehicle interfaces. This included safety guidelines by setting rules such as a maximum of 6 seconds for any user to complete a task.

Through interviewing our users I could identify content hierarchy. An example of this was when an officer demonstrated how he would interact with a physical screen while driving. Since the left hand is on the steering wheel, they would grab the screen with their right hand. This made the top right corner the optimal place for the record button since the user would grab the screen and their thumb would press the button with precision at any speed.

DESIGN

Since this product was a gap in the portfolio I began from scratch, only taking inspiration from existing Motorola style guides. I would have to make those patterns and components fit a new format for in-vehicle.

Starting with pen and paper I would ideate on the red route, also known as the primary flows. Once I felt the designs were in a good place I digitized them into wireframes that I could share with stakeholders for their thoughts on the user experience. Since the components were retro fitted for in-vehicle interfaces which contained specific touch target guidelines I used wireframes for touch target sizing as well. Developers would use wireframes for touch target placement and my high fidelity mock ups for digital asset placement. Button components would be much smaller than the actual touch target to allow room for error.

WIREFRAMES

Initial wire flows were created to map out each feature and gain approval from all stakeholders. They were then recycled to serve as touch target mapping for the development team.

HIGH FIDELITY

The MSI style guide was applied to the wireframes bringing this platform into alignment with the MSI portfolio.

VALIDATION

In field usability testing would allow our users to test the MVP of this product. I was missing cloud capabilities at the time, however the full interface was accessible to monitor performance.

This in field testing led to user feedback which would enhance the interface for the next iteration.


DEVELOP

As mentioned earlier, developers would use wireframes for touch target placement and my high fidelity mock ups for digital asset placement. These mockups were provided with proper documentation defining the rules and behaviors behind the interface.