The Problem

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.

‍

Progression

Single Document Upload: Enterprise Version
No items found.

In the enterprise version of the upload experience, users were required to pass through an additional screen after submitting a document. This screen aimed to summarize uploaded content, but was applied universally across both single- and multi-file workflows.

For single-document uploads, this step provided little value while interrupting task completion. Instead of reinforcing user confidence, it introduced friction in what should be a straightforward flow.

Given existing drop-off trends in similar interactions, this design decision likely increased abandonment risk rather than improving clarity.

Single Document Upload: My Version
No items found.

The enterprise upload experience introduced an additional screen after file submission, intended to summarize uploaded content. While useful in multi-file scenarios, this step created unnecessary friction in single-document workflows.

For users uploading a single file, the extra step interrupted momentum and added cognitive load without delivering meaningful value. Given existing drop-off trends in similar flows, this introduced a measurable risk to completion rates.

‍

Future Considerations: Multiple Document Upload
No items found.

The component team maintained that Screen S was necessary for tracking multiple files in progress, particularly in more complex enterprise workflows. This highlighted a valid system requirement: giving users visibility and control when managing multiple documents.

However, applying this pattern universally introduced friction in simpler scenarios. Rather than removing the step entirely, alternative approaches were explored—such as reframing Screen S into a true summary view that supports multi-document uploads without interrupting single-file flows.

While this solution has not yet been implemented, it remains a key area for future iteration and validation.

‍

Conclusion

The redesigned flow removes the unnecessary summary step for single-document uploads, which account for the majority of user traffic (~90%). This streamlines the experience for the most common use case, reducing friction and preserving task momentum.

Multi-document workflows remain an open area for refinement. Screen S may be repositioned as a contextual summary view to support these more complex scenarios without impacting simpler flows.

You must balance system requirements with user needs by removing friction where it was unncessary, while preserving flexibility for more complex use cases.