**Disclaimer: Some details of this project will not appear in this case study because they are intellectual property. You may gain access to the full case study upon request at the discretion of the author. Please email lkanaventi1020@gmail.com to get the password.
Developing the Journey of Branch
A competitive audit was done to discover what current the current mental models of customers were, and what opportunities there were for Branch to meet the customer’s needs.
from the company’s perspective
To further understand the company’s successes and their vision moving forward, an interview with the stakeholders was conducted. Based off the interview, a focus area was determined.
The journey
To understand the customer’s journey, a journey map was created. It identified pain points and opportunities to improve the user’s journey.
The intellectual property has been redacted by the gray boxes.
tech scoping
A senior engineer came to scope out how long each idea would take to implement. The project was given 30-40 points, which would translate to 4-6 weeks of time.
User input
To determine what ideas were most valuable to our users, the team used the dot voting strategy to send the top 10-12 ideas to the Kano Analysis Survey to get user input. The Kano survey allowed us to take user input and extrapolate it into numbers to identify: what was needed, what would be neat to have, what would be tolerated, and what users absolutely don’t want.
The final 6
Based off the company’s goals, the technical limitations, and the user input, I chose six features that would fit the limitations, help the company build upon their vision, and make the users happy. I sketched out some low-fidelity wireframes before I digitized them in Sketch, and annotated them in a presentation. The annotations in the presentation documented how these features would work, and why I chose them. Following that I took one user flow of the wireframes and created an interactive prototype in Axure so that the client could see how the features would interact and flow together. They could also use the interactive prototype for usability testing in the future if they decided to move forward on the feature set.
The above is an example of the low-fidelity wireframe of a feature without the notes about what the feature is (due to intellectual property).