Enhancing the social responsibility workflow
Amazon: Rosebread audit trail and tracking internal software (2019)
Rosebread (RB) is a full-stack application for managing Amazon’s social risk in their supply chain and internal operations that consists of an intranet and underlying data storage for the management of suppliers, social responsibility audits and findings, and reviews for Amazon’s social responsibility (SR) team.
Why redesign?
- To enhance the SR team’s workflow, reliability, and transparency.
- Add the ability for RB users to investigate previous actions, including who made the last edit, what the values were, when the last change was made, and better understand updates made in the system.
My role
I was the only ux designer. Worked with the project manager and development team. I focused on:
- Improved and unified the Amazon style guide for the RB software
- User Research
- Low- and high-fidelity wireframes
- Design mock-ups
Problems that needed to be solved
- The SR team couldn’t track changes made in RB at the field level, which caused friction when facilitating appeals and resolving disputes.
- SR was processing all communication via email, which caused delays in follow-ups and led to errors.
- Improve and unify the customer experience for entity creation and editing. Eliminate unnecessary scrolling when saving entries; get rid of random refreshes and inconsistent messaging.
Platform
Internal web application
AUI (Amazon User Interface) Style Guide
Improved the AUI (Amazon User Interface) style guide for the existing Rosebread software. My improvements included consistent error alerts and messaging elements, form reconstruction for easy imputing of required and optional information and tab accessibility user flow.
User research
I worked from business requirement documents and case studies as there initially wasn’t time designated to user research for the three new features in RB. After submitting a request for user research to be successful in the redesign, I set up conference calls with the SR compliance operations (C-Ops) team in India that used the software. This research was essential to being able to finalize my designs that would benefit the team’s workload moving forward when they needed to investigate previous RB data edits or deletions.
Wireframes
I created low- and high-fidelity wireframe concepts that I presented to the SR C-Ops team. Their input helped to drive the next iteration of design concepts. My changes are noted below in my high-fidelity wireframes.
Sketches
High-fidelity
Site Information history tab, disabled
1. Site Information history tab, disabled
- Users are now able to open or close the history tab when needed, unlike the present history section.
Modified & deleted history (color coded)
2. Modified & deleted history (color coded)
- Users are now able to distinguish by color what fields or sections have been modified and/or deleted.
Added expanders
3. Added expanders
- Users will be able to research modified and/or deleted fields.
Added filters
4. Added filters
- Users are able to customize their search by fields, sections, user names and/or date ranges.
Added history tabs in Audits section, active & disabled
5. Added history tabs in Audits section, active & disabled
- Users are now able to review the history in the Audits, Findings & Review sections.
Added a Deleted Activity option in filters, disabled
6. Added a Deleted Activity option in filters, disabled
- Users now have the option to review the Deleted Activity in the Findings and Review sections.
Deleted Activity option, active
7. Deleted Activity option, active
- Provides users the option to see which sections (Findings and Reviews) were deleted, edited, when, why and by whom (including updates made by Rosebeard instead of a human user).
Deleted activitiy in original form fields & deleted identifier
8. Deleted activitiy in original form fields
- Provides users a faster and an organized layout to review the deleted findings and review history within each original form field.
9. Deleted activity identifier
- A visual of the deleted Reviews on the findings tab.
Design mock-ups
Once I made changes to the wireframes that incorporated the SR C-Ops team’s feedback. I worked with Amazon's user interface style guide in building the final screens.
Site Information history tab, disabled
Modified & deleted history (color coded)
Added expanders
Added filters
Added history tabs in Audits section, active & disabled
Added a Deleted Activity option in filters, disabled
Deleted Activity option, active
Deleted activitiy in original form fields & deleted identifier
Next steps
Once the high-fidelity color mock-ups were designed, I created redlines and sent my designs to the development team to build and implement.
