Guidebook empowers hosts to help attendees make the most of where they’re at.
The Guidebook app provides a library of guides for events, organizations, and places. Each guide is created by an event organizer or host and is composed of schedules, tools, and useful information. In the past Guidebook focused on simply providing these mobile guides for events like PAX or Pycon. However over the past few years, the types of guides have expanded from events to places, weddings, community centers, and more. The newest version of the Guidebook app aims to showcase these other guide types in a relevant way to our users everywhere.
From Prescription to Exploration.
Up until the release of this redesign. Users would be given direction by the event hosts to download the guide for the event they were attending. This meant that our user experience revolved around getting users to download the guide for their event as quickly as possible.
According to our metrics, we observed that the most popular way for people to find and download the guide they wanted was through search. If they knew the name of their event, they would just type that in. Despite the fact that we knew this, we thought we could shift user’s mentality to include exploration with an on boarding process. However after only one user test, it was clear that the on boarding process was in and of itself and obstacle to finding and downloading a guide. So we got rid of it.
Another approach, getting rid of Downloads
Initially our app distinguished between downloaded and non-downloaded guides. This was presented as a “My Guides” section, and a “Guidebook Library” section. However this in and of itself was not a helpful distinction. In fact it created unnecessary overhead in explaining to users how the guidebook app worked.
We had originally put this schema in place because technically, guides were downloaded before they could be viewed. But in doing so, we separated the “Guidebook library of guides” from “Your Guides” and out of those two screens, we could only emphasize one. By emphasizing Your Guides we obscured the Guidebook Library, and vice versa.
By getting rid of the “downloaded guide” distinction, we were able to combine the two concepts into one screen. Users didn’t care about the distinction so why force it on them? Now, instead of two places where guides could reside, we had just one.
A faster and simpler experience
Over the many weeks we worked on this project, we went from a multiple screen on-boarding process with a two screen app, to a single screen experience. At the end of the day we were left with an app that optimized finding and viewing guides while simultaneously encouraging exploration of other guides.