wefindvenues

What if you could make finding event space better?

This is a story about a how we ran a Design Sprint 2.0. If you’ve never heard of that, you can learn more here or read the book — I highly recommend it!


The challenge

wefindvenues wanted help to identify how they needed to improve their digital product with real user feedback.

Long term goal: To be the tool for businesses to find event space for medium to large events

The approach

Considering the innovation required, the Design Sprint was a perfect methodology to collect problems, work-up solutions and test with users.

Monday

We had just one day together, so it was vital to maximise the value and identify problems, work-up solutions and decide on where to focus effort.

Identifying questions to answer

There was a big opportunity to increase customer success with the product, as we identified some key areas to improve.

To get inspired and to see how other companies had solved the problem, we went around the room for the Lightning Demos round. Each person shared a digital product that they thought we should learn from. This helped when identifying solutions later in the sprint.

Lightning demos

We left the team at wefindvenues and had a long-term goal, some sprint questions and inspiration to take on to the next day — sketch day.

Tuesday

Our second day is all about sketching solutions, before looking at what we could design in the user interface. What we needed was a sketch of exactly what we needed to build on Wednesday, with all the decisions made.

We sketched up solutions, voted on them, with the most voted featuring in our storyboard.

Crazy eights
Voted crazy eights

We ran video calls with our partners to share what we had done so far and ask questions that had arisen.

In the afternoon, we proceeded to sketch the Storyboard. We made decisions on what each page should do on the whiteboard, what should be communicated and how we should word questions within the data capturing flow.

Creating the storyboard
Storyboarding

At the end of Tuesday, we had everything we needed to take into sketching day.

Wednesday

Wednesday is the day were we can open our laptops and start building the high-quality prototype. This is about getting to high-quality quick and dirty. We don’t have time to create pattern libraries or ensure consistency — this is all about making a convincing prototype for real people to feedback on our decisions made so far.

Building the pages
Homepage
Enquiry pages

Thursday

With the prototype built, we went to user testing with a scenario in mind. We wanted to learn from users finding a location for an upcoming product launch.

For this project, we used the remote testing platform What users do to recruit users and run them through the test.

The outcomes

We delivered a human-tested prototype, a product backlog and a set of decisions within four days. Using time as an asset, we were able to provide value and fast-forward the product into the future to learn before committing to further design and development.

“We ran a four-day Design Sprint with wefindvenues. From understanding their key problems, to building a prototype to test, we gave them a clear direction on where to innovate with evidence from real people giving them confidence before investing in production“ — Ross Chapman, product designer at Etch
“We restructured the whole way our proposal making team works with the sprint. It’s been that valuable” — Paul Moynihan, wefindvenues

Results

Once the team at wefindvenues finished making the changes in production following the design sprint, early indications show a good (+100%) increase in enquiries. We’re now talking about what happens next!


Want to see our how our Design Sprints look? There’s more on this awesome website!