Challenge Overview
For the next release of the MPS-MTR platform (read about the MVP design here), our client asked us to build out the reporting feature for “operator” users of the MPS platform, and a corresponding notifications feature for “admin” users, as this is a crucial part of the product’s value proposition in streamlining Material Test Report touch points and ensuring pipeline components meet all safety requirements.
My Role & Responsibilities
Product manager and UX Designer:
Collaborate with client to understand the challenge, workflow, and requirements
Design and validate UI
Result
Shipped features in 2 weeks. Requirements set by stakeholders were met.
Challenge: Build reporting feature for operator users
Objective 1: Reporting non-conforming components
Field workers/inspectors (operator users) must be able to report components that are non-conforming for safety and compliance purposes
Users create lists based on the shipment/purchase order, and add components and their corresponding MTRs to it so all parties involved in the project can review the list to ensure all MTRs are attached.
If a component is damaged or incorrect, the user can now “flag” the component to report the problem and deal with it accordingly.
Objective 2: Obtaining a missing Material Test Report
A component without an MTR cannot pass the safety inspection. Field workers/inspectors (operator users) must be able to obtain a copy of the missing MTR.
After inputting the component details, the user is shown the MTRs in the system that match the inputs (ideally, only one). If the MTR is not in the database, users can still add the component to the list and also request an MTR.
Challenge: Build notifications feature for admin users
Objective 1: View and upload requested Material Test Reports
Admin users must be notified when an MTR request is submitted, and be able to view and upload the requested Material Test Reports to keep the project moving.
With the team, I ideated ways to deliver notifications to the user including sending a text or email to a designated user, or building out a notifications feature. We determined we had the capacity to build a notifications feature, which alerts users on the platform when an item has been flagged or an MTR requested.
Objective 2: Review and resolve reported components
Admin users should be notified when a component is flagged so they can implement next steps and stay up-to-date with the project.
Similarly, admin users should be able to review components that have been flagged so they know which components from which project need to be re-purchased/replaced.
