← Back to projects

Reservations for airport & event parking

Goal

A new business opportunity for the company. Initial work had already stalled two years before I joined. The challenge was influencing a shift in behaviour: getting people to reserve a parking spot before leaving the house, using only the app.

Outcome

Reservations were seen as important by the business, and I led the UX end to end. The first release let people reserve a garage entirely in-app, but feedback we should have gathered earlier showed low traffic and no real market fit. We went back to the drawing board, re-ideated, and relaunched with a narrower, airport-focused scope. The next iteration is already in development.

6+ months, brief to first release
11k reservations last month
Row of app screens for the initial reservation flow: searching for a location, selecting arrival and leave dates, a list of nearby garages, and the confirm reservation summary with price breakdown

My contribution

My role covered usability testing, ideation, visual design, documentation, and dev support, working closely with the head of design and the product manager. I wasn’t part of early discovery; it had already been decided that this would all happen in-app only.

Task flow diagram mapping how a user reserves a parking spot, from the map or the dedicated reservations tab, through search, results, and payment, to a confirmation screen

Re-started from the basics, focusing on tasks, to get stakeholders aligned, all based on initial research findings. I included flows that are often missed besides the happy path, like what happens when someone overstays a reservation.

The head of design and I went through existing wireframes and adjusted them based on the newly clarified flows. Then we decided to jump straight to high fidelity, using the new design system. The main assumption was that once released as its own tab, reservations would get a high amount of traffic and usage.

Phone screen showing a garage's location details with amenities and entry instructions, next to two usability testing quotes about the difficulty of finding an elevator and wanting to know what to expect before arriving

I set up two usability studies to discuss parking habits, and to check people’s interaction with the flow.

People’s entry point was different from the design: 7 of 9 participants tried pressing the search bar first when starting a reservation. They said that first, it’s about finding the location, then reserving a spot.

The numbers made it clearer still: a 75% conversion rate on the booking flow, but low traffic, under 75,000 users a year. Doing everything in-app simply didn’t work. It also highlighted the need to stop maintaining reservations as its own mini-app inside one tab; the next release moved to a single, shared code base.

Photographed notebook pages sketching map icons, search entry points, time and date selection, and simplified reservation cards

Definitely not pretty, but useful for quick explorations. Previous findings clearly showed a need to re-think reservations: how do I show people they can use this app for reservations, within their current interactions?

App screens showing the pivoted reservation flow limited to Amsterdam Schiphol and Rotterdam airports, with date and time selection and a resulting garage option near Schiphol

Instead of around 170 garages, only a couple of airports were made available at first. The main flow had to change, quickly.

Tested this again in a moderated session. Going to the airport turned out to be part of a longer, more stressful journey than expected. Specific location maps and shuttle instructions were added after this second study, and the pivoted flow was released as a first version.

Five screens of the relaunched flow: an expanded map of the Schiphol quickparking location, entry and shuttle instructions, the reservation overview, a payment success screen, and the confirmed reservation with barcode

The relaunched flow, scoped to Schiphol Airport reservations.

Things I learned