A user journey map of the package pickup scheduling experience on usps.com, surfacing friction in navigation, form design, and date selection, with recommendations grounded in UX research principles.
Overview
This project mapped the experience of scheduling a prelabeled package pickup through the USPS website. While the task itself is simple in concept, the process turned out to be more confusing than it needed to be due to navigation issues, unclear form fields, and a date selection experience that created unnecessary cognitive load.
Task Scenario
The scenario was straightforward: a user has a prelabeled package ready to go and wants to schedule a pickup through usps.com without having to call or go to a post office. I walked through the full flow step by step, capturing where the experience felt smooth and where it broke down.
What I Found
The homepage is cluttered with too many menu options and the Schedule a Pickup link is buried under Quick Tools rather than surfaced prominently. Users who are not already familiar with the site have to spend time hunting for the entry point.
The pickup address form auto-filled incorrect information and the field labels were vague enough that it was not clear what was being asked. When the auto-fill was wrong, fixing it was more confusing than it should have been.
There were multiple date pickers in the flow with no clear indication of which dates were actually available for pickup. The calendar was hard to read and the available dates were not visually distinct from unavailable ones.
Once submitted, the confirmation page was actually the strongest part of the experience. It showed all the relevant information clearly and felt like a satisfying endpoint to an otherwise frustrating process.
Recommendations
Schedule a Pickup should be prominently displayed on the USPS homepage rather than nested inside menus. Good design depends on discoverability — users should be able to see what actions are possible without having to search for them.
The pickup form could be significantly simplified. Grouping related fields, cutting unnecessary steps, and providing clear defaults would reduce the mental effort required to complete what is ultimately a simple task. As Whitenton (2013) noted, the total cognitive load of a site directly affects how easily users can find content and complete tasks.
Reflection
This project pushed me to think from the user's perspective in a structured way. Journey mapping made it easy to see not just where the friction was, but how the emotional experience shifted across each step. The contrast between the frustrating middle of the flow and the satisfying confirmation page was a good reminder that even one strong moment can affect how users feel about the whole experience.