I’m a product designer at trivago, and would like to share some insights into one of our biggest projects we tackled in the last period. Well, from a product design perspective at least.
Pitching
I’m lucky enough to work in a company that appreciates initiatives to evolve the product, and not just on paper but we actually have a process in place for that. At that time it was called “pitching” — a trivago sort of version of sales client pitch. You create a prototype/flow/sketch whatever, pitch it to management and your colleagues with hypothetical improvements in business metrics and if you manage to create enough excitement and gather a team around your “pitch”, you’re good to go for a proper project. Check more regarding this process in our blog post. One of these projects, you guessed it, redesign the trivago app.
Changes
This new mechanism of proposing ideas coincided with the time the app’s team started to have more and more concerns regarding the state of the product: it seemed we were always catching up on the mobile web features, design and core function. At one point we asked ourselves:
What’s the point in downloading the app from the store when you can do the same thing in the browser?
So we decided to change that. All of us in the team: Engineers, Product Owners, Designers, Researchers and QA.
Following step was to propose our idea of the new app in a way that we: - Follow trivago’s business model. - Blend seamlessly with other trivago products and mediums. - Bring additional value to travellers. Remember the why download the app thingy?
And it was challenging I can tell you that, but super exciting as it seemed each of us took the role of a startup founder. The team came up with the following vision statement for the new app:
Empower users to discover and book their ideal hotels by providing a simple, innovative, and emotionally-engaging mobile experience.
Together
Then followed workshops, brainstorming sessions, design sprints all tailored to shape the new app proposal with the above statement in mind. We discussed features, flows and most importantly what are the traveller’s problems we want to solve as a trivago app. To increase efficiency we created “feature teams” (each had at least one designer, QA and engineer from Android and iOS) that worked in parallel.