How can product managers, designers measure stakeholders' happiness — quantitatively?

The What

The Partnership Happiness Framework (1):

The Why

Product Managers have it tough — especially when it comes to Stakeholder Engagement.

Marketplace, Platform, and Ecosystem Product Managers can have 10x more stakeholders to partner with all other Product Managers.

Image source: https://segment.com/blog/how-segment-models-growth-for-two-sided-marketplaces/

Often times, stakeholders also have stakeholders too!

Given such a Complex, Ecosystem environment,

How can Product Managers, Designers measure Stakeholders’ Happiness — Quantitatively?

And use the data to:
- Identify, Frame, and Solve The Right Problem?
- Pinpoint Success Factors and Pain Points?
- Choose the Right metrics?

NPS flag problems…but lacks the precision needed for action and analysis

Fortunately, the Partnership Happiness Framework (1) solves this problem.

The How

The Partnership Happiness Framework:

Step 1

Step 2

Step 3

Here’s an example:

Identify + Collect Data:

Example 1

Example 2

Example 3

Analyze and Visualize:

How to Prioritize?
Who gets What resources?

Why?

1. High Level Analysis

Step 1

Step 2

2. Granular Deep Dive (Root Cause Analysis)

Tabulate + Visualize for Insights

Identify Patterns

Root Cause Analysis

The Takeaway

Product Managers now have a powerful quantitative tool to surface stakeholders’ pain points and turbocharge Discovery and Problem Solving.

The tool is flexible enough to meet your needs.

For example, this tool can feed into prioritization frameworks such as:

• RICE
• MoSCoW
• Kano
• Carver

How will your Product team use this tool?

Please comment and let me know your thoughts! :)

References

1. Customer satisfaction measurement: a conceptual framework