PMF Course Overview Flashcards

1
Q

What are the four PM pillars?

A
  1. Feature Opportunity Validation
    2.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Feature Opportunity Validation

A

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?”

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Feature Design

A

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?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Feature Development

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Feature Launch & Iteration

A
  • Iteration begins!
  • A/B testing
  • How do I improve the UX
  • How do I engage my community?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What to expect from the course

A
  1. Use dashboard
  2. Content segmented by dates (click through, read, absorb it)
    3.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Strategic Fit

A

It needs to align with the strategy and goals of the company

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

User Value

A

The opportunity needs to solve a relevant problem for a target user

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Business Value

A

Solving the user’s problem creates tangible value for the company, such as increased revenue or improved user retention

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Validating Strategic Fit

A

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?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Validating User Value

A

It’s my responsibility to curate a deep understanding of my users and represent their needs within my company

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Validating Business Value

A

Q: Can I solve a relevant user problem in a way that also captures some form of value for the business?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

The Opportunity Validation Process

A
  1. Conduct a manager briefing
  2. Refine the user value
  3. Refine the business value
  4. Validate & communicate the opportunity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Reasons to Understand Context

A
  1. Project Hypotheses
  2. Implicit Assumptions
  3. Alignment with Counterparts
  4. Alignment with Leadership
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Project Hypotheses

A

Provides you with a set of informed hypotheses about your users, their problem, and potential value

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Implicit Assumptions

A

Helps you surface the implicit assumptions your manager or leadership made

17
Q

Alignment with Counterparts

A

Allows you to get your design and engineering counterparts on board

18
Q

Alignment with Leadership

A

Enables you to build strategic alignment with your product leader and other members of the leadership team.

19
Q

Evaluating Strategic Fit

A
  1. Company mission and values: Understand your company’s reason for existing and long-term vision
  2. Company strategy:
    Grasp your company’s key objectives for the short and medium term
  3. Product strategy:
    Comprehend your product’s specific goals that ladder up to company strategy
  4. 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
20
Q

Evaluating User Value Hypothesis

A
  1. 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)
  2. What is the user problem?
    Understand the problem area and signals that indicate it exists.
  3. Why does this problem matter?
    Gauge severity (high / medium / low), number of impacted users, and current alternatives
  4. What does success look like, and how will we measure it?
    Define qualitative and quantitative goals, as well as non-goals
21
Q

Evaluating Business Value Hypothesis

A
  1. Who are the key stakeholders?
    Identify decision-makers and informed parties (such as customer service, sales, or marketing)
  2. What does success look like?
    Define qualitative and quantitative business goals
  3. How does this project ladder up?
    Explain how it fits into team, product, and company goals
22
Q

User Interview Steps

A
  1. Determine Audience
  2. Recruit Users to Interview
  3. Structure Interview
  4. Debrief and Synthesize
23
Q

Common mistake in determining users to interview?

A

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.

24
Q

How to define the right audience to interview?

A
  1. Define your company user profile, i.e., the target user for your company or product as a whole
  2. Identify how the target audience for your project differs from the company user profile
  3. Identify secondary attributes that add diversity to your project’s target audience
25
Q

The three S’s of User Recruitment

A
  1. Source - participants that match your target user profile
  2. Screen - reach out to possible participants and screen for fit
  3. Schedule - create an interview schedule to maximize insights
26
Q

Phases of user interview

A
  1. Warm Up
  2. Build
  3. Peak
27
Q

3 Main areas to understand from user’s perspective

A
  1. Is our hypothesized problem accurate?
  2. What alternatives do users leverage to solve the problem today?
  3. How severe is the problem based on the solutions they have available to them currently?
28
Q

Post-interview debrief steps

A
  1. User profile - verify who you spoke with, and the attributes they have from your target audience
  2. Document interview observations - jot down observations on the user problem and how the user experiences it
  3. Extrapolate - translate observations into something meaningful and specific to your project
  4. Evaluate interview - examine how the interview process is going, and adjust as needed to get the most out of the next one
29
Q

Synthesizing user interviews

A
  1. Cluster based on user problems
  2. Identify patterns across user profiles
  3. Identify patterns across alternatives and severity
30
Q

Funnel analysis

A

An approach to estimating impact that maps a series of steps your users take to get to a specific goals or endpoint, and then identifies where the biggest drop-off points are.

31
Q

Why validating business value matters

A
  1. Original assumptions could be inaccurate, too generous, or wrong
  2. Ensures you are working on a project that will deliver a positive business impact
  3. Impactful projects build cross-functional credibility
32
Q

Four key components of a well-constructed funnel

A
  1. Target Audience - This is the audience your feature or product is designed for. The audience is defined based on specific attributes or signals that identify them as potential users of your product or feature.
  2. Starting point - This is defined by a specific action that your target audience takes within your product. It signifies the beginning of the user’s journey.
  3. Endpoint - This is typically a quantitative signal or a user action that signifies that the user’s problem has been solved. It represents the culmination of the user’s journey.
  4. Intermediate steps - These are the specific user actions that connect the start and end points of the funnel.
33
Q

Three common types of funnels

A
  1. Sales funnels - These track the user’s journey from being a prospect or lead to becoming a converted customer.
  2. Feature funnels - These track the journey of a feature’s target audience from initial awareness to retention.
  3. Growth funnels - These break down the user journey into specific user states, such as acquisition, activation and engagement.
34
Q

Product Review Objectives

A
  1. Gather Feedback
  2. Identify Constraints
  3. Gain Approval
35
Q

Suggested engagement rules - product reviews

A
  1. Ask the audience to respect the order of the material and avoid skipping forward into other sections.
  2. Share that there will be time for questions and feedback at the end of each deep dive and for the overall project.
  3. Stress that leaders should focus their feedback on their areas of expertise. This is important because it helps you get the detailed feedback you need while avoiding moving the conversation in the wrong direction.
  4. Request that when giving feedback, they clarify whether it’s a blocker, a comment, or a suggestion.
36
Q
A