The user was given two different choices of offers (2 cards) at the moment of making a direct booking in the hotel website.
Each card could be flipped: the front of each card was showing the claim and attracting the customer, the back was describing in detail the offer.
From our office in Barcelona I was managing a team of 3 designers and two developers remotely working from Madrid and Rome.
Also, it wasn’t attracting too many customers, the problem was that the whole process seemed a little bit confusing on desktop from the start.
Booklyng’s major asset is their exclusive tool board (called: “The Wizard”) that gives you the ability to create an offer pop-up with just a few clicks. That meant that this layout and its development had to be a “product”, ready to be reused by/for different clients as a ready-made template, so the HTML and CSS structure had to be solid and working everywhere.
this layout and its development had to be a “product”, ready to be reused...
This is one of the reasons why we were working with a Lean UX methodology.
Based on Lean-Agile methodologies this is a process that identifies a problem that should lead to some assumptions that create hypothesis, so you can quickly develop real solutions and/or amend them, ditch them or add new ones. An idea based work in progress process, more on this here.
Click on the offer to flip the card and see the back of it (More info >)
Click and return to the front.
Click on the offer to flip the card and see the back of it (More info >)
Click and return to the front.
In each of the four states the user could accept one of the offers as the main CTA was alway present.
We made 22 internal interviews with some of our customers (hoteliers and hotel staff, not real users) and asked them for some feedback about:
The task was quite simple: get to the end of the customer journey and receive an email with their offer/discount confirmation.
We added a second button below the main CTA that would point the user to Offer 2, we also made the back of the active card visible on the right.
So the user, instead of “click and flip” (desktop version) could do a left swipe on the mobile to see the back of the card and read more about it before accepting the offer. Hitting the See Offer # button at the bottom of each card shows the alternative offer, while the More Info button shows the back of the card the same way as the left swap does.
the user journey was repeatedly analysed and tested..."
Swipe the card to the LEFT and/or click on the card to see the back of it
(More info >).
Swipe the card to the RIGHT and/or click on the card to return to the front.
Swipe the card to the LEFT and/or click on the card to see the back of it
(More info >).
Swipe the card to the RIGHT and/or click on the card to return to the front.
Each state was showing a main CTA: Accept Offer # and a secondary CTA: See Offer #.
After the first layout was chosen and validated we proceeded to the development.
That means that each product could be viewed and tested (as it was) by anyone with that script. This kind of test was concentrating more on the actual User Experience, the user journey was repeatedly analysed and tested, amendments to the design and the development were made.
We also used Browserstack to test more technical details and be sure that the layout was working fine on most devices.
The final product ended up as one of the most successful at Booking.
Adobe Illustrator
Adobe XD
HTML5
CSS3
Bootstrap 4.0
Javascript