Week Four: The GV Sprint
Botify has set out on a journey to develop its first prototype, modelled by the GV Sprint approach.
5 days to map, sketch, decide, prototype and test! A very busy week in which Botify will merge its collective brain to create our first prototype.
Change the way people buy bundles
- Simple and intuitive
- Not overwhelmed
- Unintimidating [top goal]
- How can we narrow area of improvement?
- How can we overcome business constraints?
- How can we get real users?
- How can we make something that pleases everyone?
Note: After lunch, we revised our goals to be more specific. Here’s what we came up with:
- How can we make bundle building a more engaging online experience?
- How can we help customers process information and buying bundles more easily?
Beginning at the End – If We Were to Fail, Why?
Not what the customer/client wanted
It doesn’t improve on the current iteration of BB
It a a worse BB than the current BB
We’re obsessed with UI
Unfinished, we missed our delivery points (milestones)
Not responsive to user test results or client input
Our vision doesn’t align with the client vision
The Problem Statement
- Bundle Builder customers want to know the advantages of having bundles services / Telus.
- Customers want to easily search online for their options/services.
- Customers face a tedious, intimidating process of selecting and purchasing bundles
- Customers are unable to truly build their own bundle
- Customers want to easily find pricing and bundled services with options that suit their specific needs, understanding the advantages of having multiple services with Telus.
- Bundle Builder customers face multiple options and a selection process that is several steps and sometimes counter-intuitive, they are confounded with too many decisions and a breakdown in the decision tree process.
Problem statement keywords:
- Lack of clarity
Final (for now):
How can we help Telus customers purchase an affordable bundle that meets their needs without enduring tedious, unintuitive and untailored customer experience?
Mission Statement + Vision (to be narrowed):
We are building a bundle buying experience for new Telus customers, unlike our competitors, our product is simple, intuitive and tailored to the customer’s needs.
We focused on two personas, keeping in mind that the product needs to suit a general audience. For comparison sake, we looked at the following customer profiles, interviewing two individuals:
Ask the Experts / How Might We?
In order to discover how each team member is thinking about solving the problem statement. Each person gave their perspective, whether business, design or development, as to how the bundle builder dilemma.
With a 10 minute timebox for each, the other team members wrote down their inspirations in for form of a 3×5 post it with HMW (How Might We)….
Every time a perceived inspiration is heard, it is written down. All of these ideas and inspirations are put on the wall and then categorised by area.
At the end of this session, our wall was filled with ideas and inspirations which would help shape our thoughts, our imagination, and ultimately our visualisation of a solution through sketching.
With the HMW’s voted upon, the team had a wall filled with:
- The problem statement
- The mission statement
- The Key questions (to answer in the project)
- How might we/Ask the expert inspirations
Now it was time to do the fun stuff, sketching! Using time boxes, we did the following:
- 20 mins for rough notes
- 2o mins for doodling
- 20 mins for crazy 8s (rought draft)
- 20 mins to sketch a solution (on a single page)
At the end of this, all our questions, solutions, ideas and thoughts were articulated through the wonder of drawings. As they say, “a picture says a thousand words”.
The GV Sprint approach requires a tough decision to be made, pick one winner. Nonetheless, we found so many good concepts and much convergence, so the team elected to heat map the winning concepts from all solutions, creating a montage of ideas to build a prototype with. This ensured that no great idea that was voted on, was lost. It also united the team in their vision to create the first prototype.
Now it was time to divide the team into the prototype team and the testing team. Time to test our assumptions!
Images from the Sprint