Hayes and Jarvis Holiday Builder

Hayes and Jarvis Holiday Builder Design Sprint

The holiday builder is the beginning of a new direction for this brand – putting more focus on allowing customers to create their own bespoke itinerary online.

What we did

Internally within the organisation there was always the perception that bespoke multi-centres was always ‘too big to build’ but after a mixture of stakeholder persuasion and another project being put on hold the steering board decided to use a 6 week project gap to try out a Google Ventures style design sprint and build.

The Design Sprint

A multidisciplinary team was formed to work intensively on the problem for one week following The Sprint Book method. The goal was set, journey’s mapped and we picked a target. Stakeholders and specialists were interviewed and this all culminated in a series of ideas which were voted on and discussed.

The prototype

We hypothesised that we needed to meet two major needs here for multi-destination customers – there would be those who knew where they wanted to go (or start at least) and wanted to be able to put together their own itinerary (but using our expert knowledge in feasibility and practicality around destination pairings) and those who needed inspiration – wanted to see broadly what was we have to offer that suits their interests. Our winning idea catered for both of these – but we realised that given the time for build we would need to focus on one.

We decided to focus on the former because the latter was partly already met by our itinerary listings – something we could incorporate into the builder too. So we storyboarded the screen flow for a ‘holiday builder’ on whiteboards, trying to trash out all the details in sketch form before committing to a prototype.

Findings

The findings were positive – people understood the concepts and most interactions were understood. Where we saw struggles we agreed to iterate the design. But overall people were finding the new functionality in the overall journey – understanding how to use it and completing their task of requesting a quote.

Result

A final prototype was produced which formed the basis of the development and visual design work. We used existing components where possible only creating new code where absolutely necessary.

The final product went live on time and within 24 hours was generating requests which were converting into bookings. The business plan to use the Sprint method again for difficult problems.

Client

  • Hayes and Jarvis

Tags

  • Collaborative Design
  • Design Sprint
  • Prototype
  • Usability Testing