As part of my Master’s in Human-Computer Interaction at Carnegie Mellon University, I worked on a team to research and develop a solution in the law enforcement domain.

We spent 4 months conducting contextual research among various stakeholders. From our findings, we designed and developed Vivid, a mobile application that enables police officers and detectives to gather rich contextual and multimedia evidence in the field.


5 people

8 months


Project Manager

User Researcher


Contextual inquiry

Affinity diagrams


Speed dating


User testing


“I’m a big proponent of getting things down as quickly as possible [because] scenes change in an instant… there’s a lot lost.”

Detective & Former Patrol Officer
Allegheny County Police

In most agencies around the U.S., officers and detectives respond to multiple calls a day and are often pressed for time when responding to events. They count on limited time - often just minutes - to gather all the relevant information to solve cases.

The current tools that officers have access to in the field lead to several issues when capturing information in the field, including:

  1. Gathering people’s information in the field is tedious and error-prone
  2. Language barriers obstruct understanding
  3. Handwritten notes lose detail
  4. Taking notes is painful but essential
  5. Officers dread writing reports


“I see this having a place in our existing system, especially for new cops.”

Detective & Former Patrol Officer
Allegheny County Police

We utilized insights from months of in-depth research to design Vivid, a concept for a mobile application to enable police officers to capture information on a scene with greater speed, accuracy, and detail.

Vivid has 5 key features, each of which addresses a specific need:

  1. Collect witness and victim information by scanning important documents
  2. Support interactions with non-English speakers
  3. Capture scene details as multimedia information
  4. Take notes digitally
  5. Speed up reporting process

Go here to see how each feature works.


We spent 4 months applying user-centered design principles to understand the domain of law enforcement and identify opportunities. We applied our research insights to prototype and iteratively test concepts.

Project Kickoff

At the beginning of our project, we met with our client to understand what they already know about law enforcement and identify interesting opportunities to focus on.

We conducted various exercises with the client, including question storming, stakeholder mapping, and territory mapping.

We used question storming to identify what both the team and the client were interested in learning about law enforcement.

We used stakeholder mapping and territory mapping to share our existing knowledge of the law enforcement domain and identify gaps in knowledge.

Scope Definition

Based off of what we learned from our kickoff meeting, we identified two key themes for our initial research: understanding how law enforcement operates in the field and interacts with members of the public.

We used these two themes to define the hunt statement to guide our initial research.


We are going to research the day in the life of a police officer, focusing on touchpoints with members of the public, so that we can identify opportunities to improve law enforcements’ effectiveness and make situations safer for officers and citizens alike.

Interviews & Interpretation

To understand how law enforcement operates today, we interviewed a broad range of stakeholders, including police, emergency responders, and members of the public.


local law enforcement agents
emergency planning officials
criminal data analyst
federal law enforcement agents
community policing officer
criminal justice expert

We interviewed participants in the context of their work environment to better understand their attitudes and behaviors.

We used the rose-bud-thorn method to draw out important insights from each interview.

In order to identify common themes from our interviews and literature research, we created an affinity wall.

We brainstormed several more specific design directions based off of the overarching themes from our affinity wall.

Insights & Opportunities

We compiled the key research insights and design opportunities from our research and presented them to our client.


1 – Reliance on community relationship

Increased transparency from law enforcement could help communities gain a better understanding of the police and build trust and rapport.

2 – Influence of social media

While social media can be a valuable information source and platform to strengthen connections with the community, it has also increased public scrutiny of police.

3 – Necessity of soft skills

Officers regularly rely on their soft skills to comfort victims, collect information, and de-escalate intense situations. However, police training does not focus on developing these essential skills.

4 – Inefficiencies of field technology

Officers need quick access to reliable information in order to accurately appraise situations and make split-second decisions. Unreliable information, in- efficient communication channels, and cumbersome tools can make fieldwork difficult and dangerous.


1 – Community Rapport

Law enforcement relies heavily on the support and cooperation of local communities to effectively perform their duties. Members of the community provide information to help law enforcement solve cases and they help law enforcement devise solutions to local crime and disorder problems.
Public trust in law enforcement is recovering from an all-time low in 2015 and as a result, officers have difficulty getting members of the community to trust and work with them. This makes us wonder: how might we design a solution to improve rapport between law enforcement and local communities?

2 – Field Work

A significant amount of law enforcement work occurs out in the field – patrolling local areas, interacting with the community, interviewing witnesses, and tracking down leads. This work in the field requires officers to make split-second decisions in unpredictable situations, which can escalate dangerously for both officers and members of the public. This made us wonder: how might we better support law enforcement officers in the field to improve safety and effectiveness?

Visioning Session

After presenting our research findings to our client, we conducted a visioning session to kick off our prototyping phase.

We split out into two groups, each brainstorming ideas around a different design direction.

We shared the ideas from each group and voted on the ones that are the most desirable, feasible, wild, and dystopian.

Storyboarding & Speed Dating

Having generated a wide range of designs around our two design directions, our next step was to find which ones resonated most both with law enforcement and members of the public.

We conducted speed dating sessions with both members of the public and law enforcement to identify ideas that were desirable for both.

The idea of being able to capture case information in a collaborative digital format strongly resonated with both federal and local law enforcement.


To get a better understanding of how law enforcement captures information on the scene today, we participated in ride-alongs with the Pittsburgh Police.

Officers spend a significant amount of time filling out paperwork for incidents. This requires them to fill out information they have already recorded in their notebooks.

Most officers we observed used a small notepad to capture information on the scene.

Fun fact: I spent 15 hours riding along with patrol officers across 2 different policing zones in Pittsburgh. I also got to eat Mexican food with patrol officers… twice.

Guiding Design Principles

Based on all of the research and feedback we received, we developed five principles to guide the design of our application (or any other application for law enforcement).


1 – Support maximum flexibility

Officers have highly variable approaches and techniques for capturing information at a scene. To be successfully adopted, a solution should enable officers to capture information in a way that makes sense to them.

2 – Continue to support the current way of working

Officers already have their techniques and methods for capturing and remembering scene information. For a solution to be successful, it should enable officers to do the same things they can do today (e.g. write down information).

3 – Prioritize speed and simplicity

When officers arrive at the scene, they need to quickly collect information in a highly chaotic environment. A solution should enable them to capture better information without distracting them.

4 – Support mobility and portability

Because situations that they respond to are unpredictable and could escalate dangerously, officers need gear that enables them to be mobile and have their hands free. We chose to make Vivid a mobile application for this reason: phones are small and as easy to carry around as a notepad.

5 – Be durable

Both the hardware and software should be robust. For hardware, this means that it should not break if an officer suddenly needs to drop it. For software, this means that it should have redundancies in place to prevent errors or information loss.

Design Iterations & Validation

In parallel with our summer research, we designed and prototyped a mobile information capture system.

We went from low-fidelity wireframes all the way to a high-fidelity prototype.

We tested with both patrol officers and detectives. Detectives saw value in the collaborative features while patrol officers emphasized the need for quick access to features.