A new software feature for tomorrow's workforce
Amazon: Data integration internal software project (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?
- Automation is needed by integrating audit data from external audit companies.
- This new feature will compare external audit data against Amazon's internal audit data, and will accept the new data or decline duplicative data.
- This will reduce errors from manual data entry since RB will be ingesting data from more reliable sources.
- The SR team also will not have to rely on sourcing managers to update key data fields like production status.
- Audit data is being integrated into RB software from external audit companies.
- With RB as the source of truth for SR data, this will also provide more accuracy to downstream systems.
My role
I was the only ux designer. Worked with the project manager and development team. I focused on:
- User research
- Low- and high-fidelity wireframes
- Design mock-ups
Problems that needed to be solved
- The SR team was manually entering data from internal and external sources. The redesigned feature will automate most of the data input to eliminate duplications and errors.
- In its current state, there was a lack of control to maintain data parity across internal systems. This often resulted in duplicate records, missing or delayed data entries.
- Updating and entering data in RB requires a sourcing manager to manually create a ticket. After receiving the ticket, the SR compliance operations (C-Ops) team manually enters the data that causes a scalability issue over time and is prone to error.
Platform
Internal web application
User research
Initially, there wasn’t any time allocated to conduct user research, so I worked from business requirement documents and case studies. Eventually, I was able to work with the SR C-Ops team in India that used the software.
Wireframes
With only a month allocated to complete the project, I worked closely with the team that uses the RB software every day. I presented my design concepts to the team for feedback and their input drove my design concepts moving forward.
Sketches
High-fidelity
Home page header, new notification alert icon
Tasks page
De-Duplication tab page
De-Duplication tab, filter dropdown page
De-Duplication matching page
De-Duplication matching - data consistent
A Successful Submit
An Error Issue Message
Design mock-ups
After I completed the low-fidelity wireframes, I moved to creating high-fidelity mock-ups. I was able to move in this direction after setting up conference calls with the team to gather the research I needed to finalize my designs. The designs were built to benefit the team’s workload and provide better accuracy in the downstream systems that rely on RB data.
New home page header
Tasks page
De-Duplication tab
De-Duplication tab, filter option dropdown
De-Duplication matching page
De-Duplication matching - data consistent
A successful Submit alert
An Error issue alert
Next steps
Once the final mock-ups were complete, I presented them to the stakeholders and development team for feedback on my designs. Impressed and satisfied with the work I delivered, they wanted to talk about the possibility of future iterations.
Once the high-fidelity color mock-ups were approved, I created redlines and sent my designs to the development team to build and implement.