Product design
Scope
Review how users complete the work today, including the workarounds and decisions outside the current system.
Use prototypes to explore important flows and clarify behavior before implementation.
Define forms, permissions, empty states, errors and handoffs alongside the main screens. Keep design and development connected.
Selected work

ZMatic

ParkFly Geneva
For ParkFly Geneva, a customer’s reservation needed to connect to availability and the team carrying out the airport valet service. Staff also needed mobile access to booking information.
That changes the design questions. Who needs the information after booking? What can they update from a phone? Which state does the customer see? Read the ParkFly case.
Yes. We review the current tasks and constraints before choosing what to change. We keep the implementation team involved so the design accounts for existing data, permissions and integrations.
The agreed screens, interactions, components and specifications. Important empty, error and permission states need to be included, not left for developers to guess. The deliverable scope is agreed at the start.
Show us the flow that confuses people or sends them outside the application. We can explore the behavior before redesigning the screens.