PM Frameworks 101

Customer Journey Frameworks

5-E Framework

1. Entice — What event triggers the user to enter into the UX?
2. Enter — What are the first few steps in UX Funnel?
3. Engage — What task(s) is the user trying to accomplish?
4. Exit — How does the user complete the task?
5. Extend — What follow-up actions occur after the user completes the task?

Source: https://www.lewis-lin.com/blog/2016/11/11/customer-journey-map-the-5es-framework

Prioritization Frameworks

1. RICE Framework

Reach — How many people will this feature effect within a given time?

Impact — How will this impact individual users? (3 = massive impact, 2 = high impact, 1 = medium impact, 0.5 = low impact, 0.25 = minimal impact)

Confidence — How confident are we about the impact and reach scores? How much data do we have to back up those estimates? (100% high confidence, 80% medium confidence, 50% low confidence)

Effort — How much time investment will this initiative require from product, design, and development? (Measured as persons per month)

RICE Score = (Reach X Impact X Confidence) / Effort

2. Value v/s Effort:

List of features and initiatives -> quantify them using value and effort scores

3. Kano Model

The horizontal axis has implementation at 3 levels:

1. Must-haves or basic features: If you do not have these features, your customers won’t even consider your product as a solution to their problem.
2. Performance features: The more you invest in these, the higher the level of customer satisfaction
3. Delighters or excitement features: These features are pleasant surprises that the customers don’t expect, but once provided, create a delighted response.

The way you get this customer insight is by developing a Kano questionnaire where you ask your customers how they’d feel with or without any given feature.

4. Story Mapping

Along a horizontal line, you create a series of sequential buckets or categories that represent each stage of the user’s journey through your product.

Along a vertical line, you then place these tasks in order of importance, from top to bottom.

Finally, you draw a line across all these stories to divide them into releases and sprints.

5. The MosCoW Method

Classifying features into four priority buckets:

1. Must-Have: These are the features that have to be present for the product to be functional at all. They’re non-negotiable and essential. If one of these requirements or features isn’t present, the product cannot be launched.
2. Should-Have: These requirements are important to deliver, but they’re not time-sensitive.
3. Could-Haves: This is a feature that’s neither essential nor important to deliver within a timeframe. They’re bonuses that would greatly improve customer satisfaction, but don’t have a great impact if they’re left out.
4. Won’t-Have: These are the least critical features, tasks or requirements (and the first to go when there are resource constraints). These are features that will be considered for future releases.

6. Opportunity Scoring

Opportunity scoring uses a Satisfaction and Importance graph to measure and rank opportunities. After you come up with a list of ideal outcomes, you then survey your customers to ask them the following questions:

How important is this outcome or feature? Ask your customers to rank them.

How satisfied is the customer with the existing solutions?

7. Cost of Delay

1. What would this feature be worth if the product had it right now?
2. How much would it be worth it if this feature gets made earlier?
3. How much would it cost if it was made later than planned?

The way you assign this monetary value to each feature is by calculating how much time and team effort they will take to build. You and the team can also assign value to the features in terms of how much they will be worth after they’re built.

8. Buy a feature

The game goes like this:

1. Choose a list of features, ideas, or updates and assign a monetary value to each one. This value isn’t arbitrary — it should be based on how much time, money, and effort each feature will cost you and the team.
2. Put together a group of people (up to 8 customers or your own internal team). Give them a set amount of money to “spend” on these features.
3. Ask your participants to buy the features they like. Some customers will put all of their money on only one feature they’re passionate about, others will spread their cash around multiple different features. Ask the participants to explain why they spent money on the feature they picked.
4. Then, reorganize that list of features in order of how much money your customers were willing to spend on them.

Source: https://roadmunk.com/guides/product-prioritization-techniques-product-managers/