MyDPD for SME
A shipping tool for small companies that need business features with the ease of use of a consumer app. The people using it run real operations, but they have no IT department and no appetite for enterprise software.
This product has not been released. This page is shared with permission on scope, and the screens below are here to show design decisions, not product plans.
Who my users are
I work at headquarters, so my direct users are the business units in each country, not the people who ship parcels. The business units carry the customer knowledge and the market requirements, and they are the ones I design with.
I ran a workshop with the business unit in Italy, the pilot market. They brought very specific requirements. My job was to find designs that worked for them and still worked across the rest of Europe, which meant most decisions had to stay flexible. They shaped the product heavily, and that is how a pilot is supposed to work.
The hard part comes later, when a workflow has to change in a way nobody planned for at the start.
Requirements I pushed back on, and one I accepted
I cannot go into specifics while the product is unreleased. What I can describe is the shape of the calls. Marketing and the business units bring requirements that do not always survive contact with interaction design, and the work is finding the version that satisfies both sides.
Rejected a requirement: a registration page presenting the app's benefits as text set over a corporate photograph. It came from the business and it failed on accessibility, so it did not ship in that form.
Rejected a requirement: payment flows that were not unified, which would have broken the logic the user had already learned elsewhere in the product.
Accepted a constraint: parts of the navigation had already been built before the design work started. Miscommunication between managers, and no time or budget to undo it. I designed around it.