Defined MVP features for a start-up with user research
Defined MVP features for a start-up with user research
Brainstorming and Prioritizing features
Defined MVP features for a start-up with user research
Brainstorming and Prioritizing features
Scope:
Lived was an early stage startup building an employee benefits app. I explored how people use rewards and corporate perks by reviewing competitor apps and talking directly to potential users. Through 1:1 interviews, I uncovered key themes that shaped the MVP of the product.
My role:
I conducted 1:1 user interviews, contributed to affinity mapping, and collaborated with the design lead to shape insights into early MVP feature ideas.
Industry
Wellbeing
Team
Lead designer, Me, PM, CEO
Timeline
2 months
Website
Industry
Wellbeing
Team
Lead designer, Me, PM, CEO
Lead designer, Me, PM,
Timeline
2 months
Website
Founders wanted to find out what people expect from a benefits application before building it.
I used user research and prioritization frameworks to guide founders in defining MVP features.
Research Goals:
Some of the questions I asked from participants:
Does your employer have any employee recognition programs?
Is there a different way you'd like to get recognized?
Have you ever used rewards or points on an app like Aeroplan?
What has your experience been like?
What type of benefits would you like to use your points on?
What would make the worst possible app that you'd never use?
Some quotes from interviewees
Some quotes from interviewees
Some of the questions asked from participants:
Do you get any benefits from your employer?
Does your employer have any employee recognition programs?
Is there a different way you'd like to get recognized?
Have you ever used rewards or points on an app like Aeroplan?
What has your experience been like?
What type of benefits would you like to use your points on?
What would make the worst possible app that you'd never use?
Some quotes from interviewees
Discovered 4 themes from analyzing interviews
We used affinity mapping to synthesize information from the interviews. We came together in Figjam and synthesized the data and came up with the themes.
Affinity mapping and creating themes
Affinity mapping and creating themes
Affinity mapping and creating themes
Themes generated from interviews
Themes generated from interviews
01
Personalized
Users want to see offers that are personalized to their interests and lifestyles.
01
Personalized
Users want to see offers that are personalized to their interests and lifestyles.
02
Worthy
Users want offers to be clear and the process to be worth their time
02
Worthy
Users want offers to be clear and the process to be worth their time
02
Worthy
Users want offers to be clear and the process to be worth their time
03
Gift centric
Users feel seen when they receive gifts or get a token of thanks from their employers.
03
Gift centric
Users feel seen when they receive gifts or get a token of thanks from their employers.
04
Motivating
Users want to see their progress and have the possibility to receive extra points.
Brainstorming session and prioritization frameworks helped define MVP features.
This method helped us clearly define what the app Must have, Should have, Could have, and Won’t have at launch. It aligned the team around user value vs. effort.
SHOULD HAVE
Receiving additional points based on manager discretion
COULD HAVE
Topping off points with credit card when not enough
WONT HAVE
Employees to recognize eachother with points
Gamification
Conclusion and reflections
The startup founders needed a better sense of what users actually wanted so they could be sure they were building something people would use. I ran early user research to get that clarity and help shape a focused MVP. By talking directly with potential users and prioritizing real needs, I was able to avoid overbuilding and align the team around the features that mattered most.
From there, I turned those insights into designs, built the MVP, and launched the first version of the app.
Opportunity: How might we reduce cart drop offs
Founders wanted to find out what people expect from a benefits application before building it.
Observing user behavior showed us a common pattern:
Shoppers adding all their “maybe” options to the cart, then navigating back and forth between the cart and product pages to compare, delete, and rethink.
This back and forth created friction for users and led to high drop offs from the flow.
So we asked: how might we support decision-making earlier, without disrupting the shopping flow?
I used user research and prioritization frameworks to guide founders in defining MVP features.
Research Goals:
Heatmap of the old cart showing a high number of users going back to the shopping journey
Brainstorming session and prioritization frameworks helped define MVP features.
This method helped us clearly define what the app Must have, Should have, Could have, and Won’t have at launch. It aligned the team around user value vs. effort.
MUST HAVE (MVP)
SHOULD HAVE
Receiving additional points based on manager discretion
COULD HAVE
Topping off points with credit card when not enough
WONT HAVE
Gamification
Employees to recognize eachother with points
Conclusion and reflections
The startup team needed a better sense of what users actually wanted so they could be sure they were building something people would use. I ran early user research to get that clarity and help shape a focused MVP. By talking directly with potential users and prioritizing real needs, I was able to avoid overbuilding and align the team around the features that mattered most.
From there, I turned those insights into designs, built the MVP, and launched the first version of the app.
Conclusion and reflections
The startup team needed a better sense of what users actually wanted so they could be sure they were building something people would use. I ran early user research to get that clarity and help shape a focused MVP. By talking directly with potential users and prioritizing real needs, I was able to avoid overbuilding and align the team around the features that mattered most.
From there, I turned those insights into designs, built the MVP, and launched the first version of the app.
Brainstorming session and prioritization frameworks helped define MVP features.
This method helped us clearly define what the app Must have, Should have, Could have, and Won’t have at launch. It aligned the team around user value vs. effort.
MUST HAVE (MVP)
SHOULD HAVE
Receiving additional points based on manager discretion
COULD HAVE
Topping off points with credit card when not enough
WONT HAVE
Gamification
Employees to recognize eachother with points
View next project
New feature
E-commerce
Responsive web
Streamlined the checkout +29% conversion rate
Enabled users to view and edit their cart content by creating a side cart
Streamlined the checkout +29% conversion rate
Enabled users to view and edit their cart content by creating a side cart
New feature
E-commerce
Responsive web
Streamlined the checkout +29% completion rate
Enabled users to view and edit their cart content by creating a side cart
New feature
E-commerce
B2C
View Selected Work