PMF Course Overview Flashcards
(36 cards)
What are the four PM pillars?
- Feature Opportunity Validation
2.
Feature Opportunity Validation
Thinking through:
“what is our user problem?”
“is there value in solving that problem for our users?”
“Is there a strategic fit with what my company is building?”
“does solving this problem translate into dollar value?”
Feature Design
Out of all possibilities, how do I know that this is the best one?
- Constraint focused brainstorming
- Prototyping with users
Qs: (Figjam example)
1. What types of reactions do users want to provide?
2. Where do they want to provide them?
3. How do they want to be notified?
Feature Development
Found a solution that you believe will work well
Involves stakeholders:
1. Engineering team
2. Design
3. CS
4. Marketing
5. Sales team
6. Data teams
Feature Launch & Iteration
- Iteration begins!
- A/B testing
- How do I improve the UX
- How do I engage my community?
What to expect from the course
- Use dashboard
- Content segmented by dates (click through, read, absorb it)
3.
Strategic Fit
It needs to align with the strategy and goals of the company
User Value
The opportunity needs to solve a relevant problem for a target user
Business Value
Solving the user’s problem creates tangible value for the company, such as increased revenue or improved user retention
Validating Strategic Fit
Q: Does this feature contribute to the goals of my team, the product, and the company?
Q: Does this feature drive the company forward in a meaningful way?
Validating User Value
It’s my responsibility to curate a deep understanding of my users and represent their needs within my company
Validating Business Value
Q: Can I solve a relevant user problem in a way that also captures some form of value for the business?
The Opportunity Validation Process
- Conduct a manager briefing
- Refine the user value
- Refine the business value
- Validate & communicate the opportunity
Reasons to Understand Context
- Project Hypotheses
- Implicit Assumptions
- Alignment with Counterparts
- Alignment with Leadership
Project Hypotheses
Provides you with a set of informed hypotheses about your users, their problem, and potential value
Implicit Assumptions
Helps you surface the implicit assumptions your manager or leadership made
Alignment with Counterparts
Allows you to get your design and engineering counterparts on board
Alignment with Leadership
Enables you to build strategic alignment with your product leader and other members of the leadership team.
Evaluating Strategic Fit
- Company mission and values: Understand your company’s reason for existing and long-term vision
- Company strategy:
Grasp your company’s key objectives for the short and medium term - Product strategy:
Comprehend your product’s specific goals that ladder up to company strategy - Team goals:
Confirm how your project fits into your team’s objectives. Your project should directly support one or more of your team’s goals, and you should be able to understand the level of impact your project will have towards those specific goals
Evaluating User Value Hypothesis
- Who is the user?
Get initial hypothesis on who the target user is. You can start with a few categories: demographics (B2C), firmographics (B2B), and product behaviors (both B2B and B2C) - What is the user problem?
Understand the problem area and signals that indicate it exists. - Why does this problem matter?
Gauge severity (high / medium / low), number of impacted users, and current alternatives - What does success look like, and how will we measure it?
Define qualitative and quantitative goals, as well as non-goals
Evaluating Business Value Hypothesis
- Who are the key stakeholders?
Identify decision-makers and informed parties (such as customer service, sales, or marketing) - What does success look like?
Define qualitative and quantitative business goals - How does this project ladder up?
Explain how it fits into team, product, and company goals
User Interview Steps
- Determine Audience
- Recruit Users to Interview
- Structure Interview
- Debrief and Synthesize
Common mistake in determining users to interview?
Interviewing users who are most active, have participated in user interview panels in the past, or users who have submitted tickets instead of interviewing users who are experiencing the problem I’m trying to solve.
How to define the right audience to interview?
- Define your company user profile, i.e., the target user for your company or product as a whole
- Identify how the target audience for your project differs from the company user profile
- Identify secondary attributes that add diversity to your project’s target audience