Amazon
Amazon
Amazon
Streamlining Law Enforcment
Streamlining Law Enforcment
Streamlining Law Enforcment
requests on campus.
requests on campus.
requests on campus.
UX Design
Content Strategy
Consulting
UX Design
Content Strategy
Consulting
UX Design
Content Strategy
Consulting
Overview
An internal tool for Law Enforcement Agencies to use when there’s an emergent issue, where there is an imminent danger of death or serious injury.
In collaboration with Seven2, a Spokane-based Interactive Agency, I had the opportunity to fly to Amazon’s Seattle HQ to work with Amazon on an internal tool to streamline Law Enforcement Requests.
User Stories
User Stories help create a shared understanding, with both the product team and the stakeholders, of the features that make up the application. This cross-disciplinary deliverable is essential. It opens up the channels of communication, making collaboration paramount.
Wireframes
Tabular data and responsive web design don’t go well together. Users are conditioned to scroll vertically but are less likely to scroll horizontally. We could display a truncated column, which would indicate that there was more content off-screen, but is there a better way?
The solution: a card based layout. With a card based layout, we can choose which information is most important to the user at a glance. If the user finds the case they are looking for, they can view the case details via accordion, or a deeper dive by viewing the case detail page.
Card Layout and Responsive Web Design
No matter what the width, the case data within each card is visible at a glance. Users can quickly identify the case they are looking for.
Create an Emergency Request — Unauthenticated User
If there is an emergency, Users still have the ability to Create an Emergency Request without the need for signing in to their account. The only difference between an authenticated user and an unauthenticated user creating an emergency request is that unauthenticated users are required to complete a ReCaptcha. All of the mandatory data needed for a request is still collected.
The internal team at Amazon requested that the form be a single page and that all fields are required. In an emergency situation, you need to fill out this entire form to formally Create an Emergency Request.
Proposed Form Solution
Long forms can be daunting. Rather than overwhelm the user, I propose that we create shorter, digestible sections of the form for data collection. Steps provide a clear breakdown of the process as a whole. Users are aware of how much more form there is to complete.
If I were to revisit this project, I would like to test to see which form execution would have a higher completion rate: “The long and lengthy” form OR “The Step-by-Step” form.
Case Detail
Users can see all of the information related to the case through the metadata that was collected during the Emergency Request creation, any associated documents, and historical correspondence with other internal team members involved in the case.
Overview
An internal tool for Law Enforcement Agencies to use when there’s an emergent issue, where there is an imminent danger of death or serious injury.
In collaboration with Seven2, a Spokane-based Interactive Agency, I had the opportunity to fly to Amazon’s Seattle HQ to work with Amazon on an internal tool to streamline Law Enforcement Requests.
User Stories
User Stories help create a shared understanding, with both the product team and the stakeholders, of the features that make up the application. This cross-disciplinary deliverable is essential. It opens up the channels of communication, making collaboration paramount.
Wireframes
Tabular data and responsive web design don’t go well together. Users are conditioned to scroll vertically but are less likely to scroll horizontally. We could display a truncated column, which would indicate that there was more content off-screen, but is there a better way?
The solution: a card based layout. With a card based layout, we can choose which information is most important to the user at a glance. If the user finds the case they are looking for, they can view the case details via accordion, or a deeper dive by viewing the case detail page.
Card Layout and Responsive Web Design
No matter what the width, the case data within each card is visible at a glance. Users can quickly identify the case they are looking for.
Create an Emergency Request — Unauthenticated User
If there is an emergency, Users still have the ability to Create an Emergency Request without the need for signing in to their account. The only difference between an authenticated user and an unauthenticated user creating an emergency request is that unauthenticated users are required to complete a ReCaptcha. All of the mandatory data needed for a request is still collected.
The internal team at Amazon requested that the form be a single page and that all fields are required. In an emergency situation, you need to fill out this entire form to formally Create an Emergency Request.
Proposed Form Solution
Long forms can be daunting. Rather than overwhelm the user, I propose that we create shorter, digestible sections of the form for data collection. Steps provide a clear breakdown of the process as a whole. Users are aware of how much more form there is to complete.
If I were to revisit this project, I would like to test to see which form execution would have a higher completion rate: “The long and lengthy” form OR “The Step-by-Step” form.
Case Detail
Users can see all of the information related to the case through the metadata that was collected during the Emergency Request creation, any associated documents, and historical correspondence with other internal team members involved in the case.
Overview
An internal tool for Law Enforcement Agencies to use when there’s an emergent issue, where there is an imminent danger of death or serious injury.
In collaboration with Seven2, a Spokane-based Interactive Agency, I had the opportunity to fly to Amazon’s Seattle HQ to work with Amazon on an internal tool to streamline Law Enforcement Requests.
User Stories
User Stories help create a shared understanding, with both the product team and the stakeholders, of the features that make up the application. This cross-disciplinary deliverable is essential. It opens up the channels of communication, making collaboration paramount.
Wireframes
Tabular data and responsive web design don’t go well together. Users are conditioned to scroll vertically but are less likely to scroll horizontally. We could display a truncated column, which would indicate that there was more content off-screen, but is there a better way?
The solution: a card based layout. With a card based layout, we can choose which information is most important to the user at a glance. If the user finds the case they are looking for, they can view the case details via accordion, or a deeper dive by viewing the case detail page.
Card Layout and Responsive Web Design
No matter what the width, the case data within each card is visible at a glance. Users can quickly identify the case they are looking for.
Create an Emergency Request — Unauthenticated User
If there is an emergency, Users still have the ability to Create an Emergency Request without the need for signing in to their account. The only difference between an authenticated user and an unauthenticated user creating an emergency request is that unauthenticated users are required to complete a ReCaptcha. All of the mandatory data needed for a request is still collected.
The internal team at Amazon requested that the form be a single page and that all fields are required. In an emergency situation, you need to fill out this entire form to formally Create an Emergency Request.
Proposed Form Solution
Long forms can be daunting. Rather than overwhelm the user, I propose that we create shorter, digestible sections of the form for data collection. Steps provide a clear breakdown of the process as a whole. Users are aware of how much more form there is to complete.
If I were to revisit this project, I would like to test to see which form execution would have a higher completion rate: “The long and lengthy” form OR “The Step-by-Step” form.
Case Detail
Users can see all of the information related to the case through the metadata that was collected during the Emergency Request creation, any associated documents, and historical correspondence with other internal team members involved in the case.
Conclusion
Services
UX Design
Content Strategy
Consulting
Tools
Sketch
Trello
Procreate
team
Senior UX Designer
Tyreil Poosri
Creative Director
Jesse Pierpoint
Account Executive
Allison Roskelley
Lights on·off