APX Radio, Si500 Body Camera and SmartTouch Interface

THE ASK

To innovate the existing portfolio of products to better fit the new demographic of first responders. Bringing the physical buttons to a touch screen with the addition of voice commands which would allow enhanced usability throughout our users shift. The mission was to update for the “new school” users while maintaining the legacy platform enough that the “old school” users would remain comfortable and confident. All of this while taking a step back and creating a unified system that allows all Motorola Solutions devices to collaborate seamlessly.

Mission Statement:  “To protect your greatest resource, your focus”.

SI500 - BODY CAMERA & MICROPHONE

APX NEXT - SMART RADIO

RESEARCH

Discovery and Empathy workshops where designers, stakeholders and users would work together to think outside the box and dream up the best possible solution. From this I would be able to determine the direction our designs and innovations need to go.

Human Factors and the start of our Framework guidelines. Collaborating with our Human Factors team, I would dive into the intricacies of switching from physical to digital buttons. This consisted of color for day/night, size of touch targets along with backend processing time. Many other factors would be taken into consideration as existing and new features were brought into the new devices UI as this would bring to build our rules and behaviors.

User Specific research included interviews to identify the endless number of critical scenarios.

Stakeholder MVP Meetings would provide us with the list of existing features that would need to be translated to our UI first and foremost as an effort to develop our initial MVP. Pre-innovation ;)

Research & Design Workshops would create an open forum of innovation to determine not only how I can create a better experience for our users but also become the cutting edge device in the market place. As you will learn, a lot of this is built through out portfolio of devices maintaining a beautiful collaboration with each other.

DESIGN

Our Interface when viewed by the outside world seems basic and “nothing special”. What often gets lost in our field is how critical the UX is and the fact that the UI is following the experience. Designing an interface for critical and high velocity environments required a keen focus on every little detail within the UI. This meant taking user disabilities such as color blindness into account, This meant making sure our user spent less time looking at our device and more time focused on their task (eyes up to stay safe), This meant creating patterns our user could memorize and perfect.

Android became our operating system of choice to fit the human factors requirements for specific processing time. I could not afford our devices to lag or fail in the field so all designs were developed with backup systems running on android.

To maintain our mission statement of protecting our users focus in high velocity environments our interfaces contained guidelines which dictated that our interfaces would have little depth and allow quick actions with very minimal cognitive load. Our rule was no further than 3 layers deep which would ultimately minimize button clicks.

ViQi was implemented which was our voice command platform. Similar to your at home smart devices like Google and Alexa however our AI would run license plates and alert officers of nearby threats. This would minimize work for dispatchers and allow them to focus on more critical emergencies.

Framework of components was built with all Human Factors rules taken into consideration. This would allow all future UI to maintain the critical rules around our UI uncovered through research.

Initial Designs where developed for our MVP features. Later I would begin to innovate to create a cutting edge device for our users.

Seamless fit into our portfolio was a priority. This would require collaboration with our global teams at Motorola Solutions to update existing dispatching portals, evidence management systems, onboarding platforms and other existing devices to now function along side these new members of the portfolio.

MVP RELEASE

Initial release was only legacy features from previous radios.

ENHANCEMENT RELEASE

This would include new features that made our radio cutting edge in technology

A few items:

Cellular Backup

Voice Command Complex Demands

GPS Tracking

DAY SHIFT USERS

NIGHT SHIFT USERS

Quick Channel Change

VALIDATION

Pre-MVP Completion Stakeholder review using Invision prototypes would allow the consistent check in with all parties to make sure we stay on schedule and all requirements are met.

Pre-MVP User feedback using Axure prototypes would allow a more in depth exploration into the user experience. Together with our human factors team we would meet with members of Motorola Solutions partnered agencies to run Wizard of Oz testing on the existing UX to make sure our work is meeting expectations.

Story time! During the Agile process our development teams fell behind to a level that posed a threat to our launch date. Being the only designer capable of more complex prototyping I was tasked to build a prototype in Axure that would replicate a true experience. This meant every button was functional and dynamic. This would prove to senior leadership that the design work was completed and cover my team while proving that there was a lack of resources on the development end. This prototype I created was SO realistic our CEO got his hands on a radio we hacked with android to run this prototype and was upset that it wasn’t able to actually make a radio transmission. It took some explaining to help him understand this was a very realistic prototype and unfortunately Axure prototype telecommunication :)

Post-MVP User feedback would occur as we worked on MVP 2 thanks to an Agile workflow. We would continue to fly out to meet with agencies and review our initial MVP through in-field testing such as ride alongs where we would partner with an officer for their shift and monitor their use of the new device.

DEVELOP

As we created features we would type up what we refer to as a User Behavior Spec. This was our documentation that consisted of rules and behaviors for our interface designs. This would then be passed off to development as each feature was completed (Agile workflow style). We maintained development support working with massive teams of developers all over the globe to make sure the designs met our specification.

I believe one of my skills in the UX field is my ability to build friendly relationships with my stake holders. When we are all happy the process is smooth sailing. My lead developers and I were on a friendly basis which allowed for painless corrections and positive ideation and innovation from both parties.