Police Body Camera
Android body camera system
Law enforcement officer
2015 – 2016
Wireframe, User Flow, Design Documentation
User Researchers, UX Designers, UI Designers
Motorola Solutions’ body camera system is an integrated speaker-mic, body camera and touchscreen content management device. It’s designed for law enforcement to capture, store, analyze and share crucial video evidence. As an UX consultant, I worked together with Motorola Solution’s design team to ideate, prototype and deliver designs to development teams.
Developed simple and efficient UX solutions for target scenarios and features.
Provided interaction designs, user flows, wireframes and UI requirements.
Collaborated with user researchers to capture and synthesize insights.
Generated design specifications, delivered and presented to development teams.
Design Goals and Collect Information
In this project, I was usually assigned a design task with basic function goals. Instead of providing ideas immediately, I would love to communicate with my team, UX researchers and research more to collect more information. This helped me to further develop my understandings for users’ needs and the core of problem.
“Five Ws and How” are my favorite start questions. The structure is great for information gathering and problem-solving. They help me to form a clear and comprehensive picture of design requirements. Detailed questions are vary based on different projects. Below are some generic questions:
What is this function about?
When does user use this function?
What is the frequency user interacts with this function?
How long does a user interacting with this function?
Where does this function belong to in the system?
What place does user need this feature?
Why does user need this function?
Who are the primary users?
Who are the secondary users?
Who are related with this function?
How does this function work?
Once I collected enough information and had a clear picture for the design task, it’s time for brainstorm solutions. Under the design requirements and design pattern, I enjoy thinking out of the box and approach the goals from different perspectives and paths. I wish to see all the possibilities. Then I would analyze the pros and cons of each version. I would also share with my team to collect feedback and then to further develop feasible solutions.
For example, when designing the status section I sketched dozens of ideas. Some promising ones were polished and developed into more detailed wireframes. Below are three examples:
Define A Screen: Details Matters
After rounds of discussions in ideation stage, a final design solution would be selected, polished and approved by the team. I need to define the designs in wireframe level with all detailed specifications. In this process, the keys are:
Each element and screen should be well described and defined
List all states and variations, such as different status, character limits, formats,
Interactions should be clearly defined
Create guidance and suggestions for UI design
User Flow: A Journey Beyond Screen
For this product, one challenge was complex using environment and various of interactions. User’s interaction includes screens, buttons, indicators, speaker, camera and other equipment connected with the device. When designing the user flow, it’s very important to consider all other factors and interactions.
Lessons Learned and Key Achievements
Details, Details & Details
I learned that a high-level wireframe and user flows are far away from desired solutions. It’s simple to think, “we need to show time here”. But what is the time format? Where is the time information retrieved from? Do we need to show time zone? What is users really looking? How to set up time? etc. It’s always a good idea to ask one more question and think one step further.
Every step/screen/element is “live”, because
They have various statuses based on different times and scenarios.
The relations with their contexts are always changing and developing.