Reflection: Feature flows & Proto Pitch 2

Company Traction

This week, we focused on developing our MVP and gaining more customers for our customer side. Developing our main feature is our priority before we can continue to acquire more customers. As a team, we decided that a better MVP flow would attract more users. Alongside developing our MVP, we continued to improve the website design for customers before we send out another recruiting email.

Web Advertising

AvB Testing

We had two feature flows that we wanted to test. The first flow included a singular invite, and the second flow included multiple restaurant suggestions and a voting system. We featured tested with two groups of people and learned that the singular flow was much better.

My teammate and I split up into two different groups. I had brought two target users who I was able to contact to help with the user testing. One was an industrial designer and the other was a UX designer in a small startup. I quickly learned that a Flow isn’t a Flow, if it doesn’t flow well.

After closely examining the lo-fi wireframes, there was still a lot of fidelity issues. The informational gaps left the user searching for information interrupting the flow. We started wanting to do AvB testing, but for me, it ended it being a usability study. There is a slight change in the behavior of inviting people out to eat. As pointed out by one of the prototype testers, it’s just adding extra “Candy” to the main feature. Instead of testing out two different flows, it was essentially the same flow with extra candy. Presenting this issue to the group was difficult to communicate with my group because we framed it as AvB.

I recruited two design professionals to help with feature testing. I felt having a more professional eye for design would help our overall process. Just learning more about “Candy” was a great insight into understanding what an MVP flow is all about. We need to understand the core mechanics of our feature and what information we need to provide so the user does not get confused during the flow.

Quotes & Opportunities

From the script, I found it useful to have the app screen in a presentation slide format to communicate all feedback. I used different colors to represent the two people when I communicated their insights. I found this effective to communicate design compared to reading off a script. After my synthesis, I was able to have insights to create design opportunities for the group. Showing everyone my research process made my conclusions more logical.

Proto-Pitching

Our group has a unique challenge of presenting a two-sided business model. Compared to other groups, that means we have half as much time to fit in all the content required. We need to unite the two models into one design and precisely deliver every word. If we can begin simplifying what is relevant, considering the whole instead of explaining the facets of each part. We have more time to practice but we are dividing the tasks up well so that we could be more efficient with our time. Every week we practice the same parts allowing us to get better at delivery. In the closing weeks are are going to continue the invitation flow, recruit more users and refine our proto-pitch.