Project Overview
The mobile version of the Enterprise Document Upload (EDU) component introduced additional steps that risked slowing users down. Because EDU was an enterprise-wide, mandated solution, it had to be implemented, but its flow required adaptation.
My Contributions
I collaborated with engineers and the component team to reduce screens for single-document uploads, which represent ~90% of traffic, while exploring options to manage multi-document cases. The result was a streamlined, data-driven flow validated by stakeholders and documented for future rollout.
Single Upload Component (Standard)
- Required Screen S after upload.
- Intended to “summarize” uploaded files , but added friction in a single-file flow.
- Risked worsening drop-off rates, based on existing data.
Single Upload Component (My Version)
- Removed Screen S to reduce the number of steps.
- Used existing drop-off metrics for web(occurring right before upload) to prove that Screen S would not add value.
- Successfully negotiated approval to streamline the flow.
- Impact: A shorter, more efficient experience for ~90% of traffic.
Future Considerations: Multiple Document Upload
- The component team defended Screen S as necessary for tracking multiple files in progress.
- Alternatives were explored, such as reframing Screen S into a true summary view rather than a required step.
- Solution has not yet been implemented, but remains a point for future iteration.
Results
- Removed extra screen for single uploads(~90% traffic)
- Multi-doc flow unresolved; Screen S may serve as summary
- Balanced system rules with user needs