The Headout Story
Headout is an incredible startup in Bangalore, doing some brilliant work in the space of travel experiences. As a designer, I have always enjoyed (and found myself most driven) when I work in areas that I personally find exciting and meaningful. In early 2018, I had the opportunity of working as a Product Designer with some of the most fun and passionate folks you could find.
This is a story about my contribution to Headout’s mission of helping people “Rediscover the Joy of Travelling”.
New York City. Berlin. London. Paris. Amsterdam. Singapore. Hong Kong. San Francisco. Naples. Rome. Las Vegas.
If you’re a traveller like me, you would have probably wondered what to do when you visited these amazing cities, full of stories and experiences. Our planning of ‘what to do’ in a city is often spontaneous and on-the-go, and involves the issues of unavailability, budget or standing in endless long lines. Headout simplifies this process by offering tickets on demand, on-device.
Headout: Experiences on Mobile Web and Desktop
January-April 2018
What was my role?
Product Designer
Who did I work with?
Varun Khona (CEO & Head of Product); Prateek Bhandari (AVP Growth; Parag Jain, AVP Operations); Kunal Khandelwal (Software Engineer); Amit Madnawat (Software Engineer)
What did I work on?
UX Design, UI Design, Motion Design, Prototyping, Research, Development
What did I learn?
Frameworks, Business Models, Product Execution, A/B Testing, (New tools!)
What tools did I use?
FullStory (for Research), Sketch (for UI Design), Invision and Principle (for Prototyping), Zeplin (for sharing assets and styleguides)
It was early 2018.
“According to our Data team’s report, our Checkout pages are facing major drop-off. We need to redesign our checkout experience to optimize our Conversion Rates across our range of product variants.”, Varun, the CEO announced.
As the lone designer on the team, this was a huge responsibility.
Jan 2018
Two Months Later:
Result: An overall, Massive 34% increase in CVR.
(*Feb-May 2018)
Let’s Headout!
Working here led to valuable learnings and a marked increase in my levels of skill, confidence and execution.
Some of the key questions that we asked ourselves before we started any project / sprint:
Business
What does this do for the company? How are we improving UX, revenue and scalability? Are we thinking about all stakeholders, factors and system constraints? How do our decisions consider future growth and expansion?
Product
How are we improving the overall experience for the customer? How do we achieve high quality content, visuals, interactions and storytelling? How are we delighting them in their every interaction with Headout?
Tech and Fulfilment
How are we building scaleable systems? How do we scale for future scenarios? How are we making product frameworks and development seamless and efficient? How are we aligning Product with Operations and Fulfilment?
Constraints
🤯 No direct access to users
🤥 And that means no prototype testing
🌎 Building for a world-audience
→ Used FullStory for session based research. Frequent syncs with Data team on CTRs and CVRs.
→ Execute quick A/Bs. Evaluate with Data. Fail. Learn. Repeat.
→ Inclusivity through multiple languages, scalable text length, accessibility considerations
1. Checkout on Mobile
January 2018
Design Goals
- What are the specific design patterns, flows and interactions through which we can maximise CTR (click-through rate) and CVR (conversion rate) across pages?
- What visual elements will aid in communicating product features, system status and make checkout an activity of seamlessness and confidence?
- How do we align the checkout framework to scale across inventories, and for responsiveness?
Deliverables
Variables
Developing the Checkout framework for Headout required a thorough understanding of the product inventory.
Date (D) | Time (T) | Variant (V) → [DTV]
The permutations that existed in the system: (Multi = m)
m D, m T, m V | m D, 1 T, m V | 1 D, 1 T, m V | m D, m T, 1 V
How might we design seamless checkout experiences that scale across Headout’s product inventory and platforms?
for instance:
Phantom of the Opera at Broadway, New York
— Single Variant
— Multiple Dates
— Multiple Showtimes
— Multiple Prices
— Seat Selection
The corresponding flow that would scale for desktop and mobile:
Burj Khalifa at the Top, Dubai
— Mutiple Variants
— Multiple Dates
— Multiple Times
— Guest Selection
Deliverables
- Product Card Redesign
- Visual + Interaction Framework
- Elements: Seats View, Selection (Date, Time, Guest), Tooltip, Filters
- Information Design + Content
- Checkout Flow (Mobile and Desktop)
- Prototyping and Development
Building the Framework
1.Awareness and System Status
to help ease of navigation through the flow
2. Contextual Action
by setting up previously made selections
3. Meaningful Organization of Information
through order and hierarchy
Explorations
The Product Card is a critical point of choice for the user in terms of key decision factors:
Variant Information | Duration | Time | Price | Availability
How can we make product cards readable, informative and compelling?
Apart from structuring content through levels of visual hierarchy, we came up with a visual framework of Boosters that inform the user about these factors.
These were organised based on Relevance, and Booster Type: Urgency, Value Proposition, Availability.
Experience Framework
A (Seatmaps)
1. Date + Time Selection | 2. Seat Selection | 3. Checkout
B (Multi Variants)
1. Date + Variant Selection | 2. Time Selection | 3. Guest Selection | 4. Checkout
Get Krishna Gautham’s stories in your inbox
Join Medium for free to get updates from this writer.
C (Single Variants)
1. Date + Time Selection | 2. Guest Selection | 3. Checkout
Building the Experience
We then laid out the experience through all possible states and interactions and defined the visual layers accordingly.
Steps: Contextual Information, Previous Selection
Filter States: All Selected, One Selected, Multiple Selected
Seat Selection: Available; Unavailable; Seat Unselected/Selected; Tooltip
Selection Status: Seats Selected; Price Information
Action Buttons: Active, Deactivated
Process and Deliverables
1. Constant collaboration, shareout and feedback with Product team
2. Rapid and iterative prototyping to aid Development efforts
New versions went live in a design-dev cycle of 3 weeks
3. Bi-weekly sync with Growth and Data team for result based evaluation
3. Checkout (Desktop)
Goals / Deliverables
- Task Flow and Interactions
- Task Sectioning, Selections, CTAs, Form Design
- Content Organisation, Visual Hierarchy
- Scalability: DTV + Device
- Consistent Visual + Structural Framework
Part I: Date, Time, Variant Selection
Few of the questions that we had to consider while building the Selection experience for Desktop:
Design Approach
- Desktop provides affordance for multiple selections. How can we situate the three major (DTV) selections in one field of view?
- How can we direct the user meaningfully through default selections?
- How best can we organise information, through hierarchy and visual structure?
- What are the states of selection, and how do we visualize them to afford interaction?
Explorations
- Integrating Headout’s Visual System
- App → Mobile → Desktop
- Consistent Content Organisation
- Fluid and Uniform Interactions
- Context of Selection
Framework Elements
Steps: Contextual Information, Previous Selection
Date Selection: Default selected; Calendar View
Time Selection: Available; Unavailable; Horizontal Tab View
Variant Selection → Action Buttons: Available; Sold Out; Boosters
Part II: Checkout
Design Goals:
1. Visual and informational Context
for efficient and confident selection
2. Clarity of Task and Action
through organized hierarchy, type and layout
3. Division of Tasks and Sections
for progress and flexible editing if required
Framework Elements
Steps
Contextual Information, Previous Selection
Selections
No. of Guests (Applicable Price, Resultant Value)
Cards
Selection Summary, Visuals, Price Details
Forms
Guest Details (Name, Phone No., Email ID); Card Details (Card No., Expiry Date, CVV)
Action Buttons
Confirmation
The page view of the Checkout page is meant to serve as a Summary of all the selections and inputs the user has made so far.
In this direction, we tested two specific models:
Hypothesis (on Desktop):
All visible actions as context vs Sequential actions
#1: All Checkout Actions in One Flow
#2: Sequencing Checkout Actions into Two Steps
*Ran an A/B Test on these two versions.
Why were we doing this?
- Gauging user confidence (Q)
- Ease of task completion (Q)
- Data based evaluation of resultant conversions (q)
(FullStory for session based research; Data team’s comprehensive results of CTRs + CVRs)
Results
#1 performed far better than #2.
Hypothesis (on Desktop):
All visible actions as context > Sequential actions ✅
Result: An overall, Massive 34% increase in CVR.
(*Feb-May 2018)
I consider this one of my biggest achievements as a professional designer. Working at Headout also revealed to me some of my best sides — my idea of life, growth and balance found new meaning when I worked on something I truly cared about and put my heart into.
Appendix: Other Projects
I believe that I did some of my best work while at Headout. There is so much to show and so much to write about, but I am scoping this article to the few important ones. What follows are glimpses of the final deliverables for some more work that I put my heart into.
Category Pages (Desktop)
Headout contains specific category pages that help users explore content and experiences. Featured here is an exploration from the Broadway Category Page, part of a massive redesign effort for targeted experiences on the platform.
5. Blog (Desktop)
The Blog is key to Headout’s Content and is the source of several great stories, recommendations and experiences. We redesigned the Blog from scratch to create a consistent and visually coherent experience that scored high on navigation and readability.
Live at: Headout Blog
6. Visual Systems and Updates
As part of one of the design sprints, I also reworked the visual system of Headout and defined an organised hierarchy of fonts, color and structure to aid sectioning and readability.
Let’s Headout!
I learned a lot, did a crazy amount of work — but most importantly had fun all the way through.
Here’s a picture from our weekend cricket sessions.











