Skip to content
Product Alignment Framework: How Miro navigated explosive growth to 20 million users
Share
Explore

PAD Template

Fill out this page to create your product alignment document.
Duplicate this page for each project that requires a PAD. Then, delete these instructions and the button below before filling out the rest of the page.

Duplicate PAD

Project Info

Owner:
type @ to tag people
Team:
type a team name
Status:
In development

Step 1: Problem/opportunity framing

Problem statement

What problem are we solving?
What is the opportunity that we are addressing?

Audience

For whom are we solving this problem?

Rationale

How do we know this is the right problem to solve? Why this opportunity and not others?
Does this relate to current OKRs and if yes, which ones? Or is this a proposal for future OKRs (based on business strategy)?
Will this neutralize competition? Differentiate Miro? Delight prospective users?
Any links to customer research, conversations, or observation from data?


Example: Type
/Miro
to embed Miro boards that frame the problem/opportunity.

Success metrics

How do we know if we solved this problem?

Competitive research: (if
neutralizing
competition)

How did others capture this opportunity / solve this problem?

Potential solutions directions

What are some high-level solution directions to explore to capture this opportunity / solve this problem?
Describe potential solutions through short descriptions or high-level sketches / low-fi prototypes (no implementation details at this stage).
Compare the high-level solution directions (e.g. through impact vs. complexity using high-level T-shirt sizing estimates in days, weeks, months).


Step 2: Solution framing

Proposed solution

What is the scope of the proposed solution?
What are the key features?
How difficult will it be to realize the solution?

Why proposed solutions were rejected

Provide context for why this solution was chosen over the others.
Include links to user research, customer data, etc.

Out of scope

What is not in the scope of the proposed solution?

Dependencies, risks, and mitigating factors

What are the dependencies?
What are the risks associated with the solution (e.g. compliance, legal, privacy, security, strategic risk, operational, infrastructure stability/scaling risk, etc.) and the mitigating factors?

Add a known risk
Reset
Risk
Severity
Mitigation
1
Compliance
Red
Blocked
2
Legal
Yellow
Work around
3
Privacy
Green
N/A
4
Security
Red
Blocked
5
Strategic
Green
N/A
6
Operational
Green
N/A
7
Infrastructure stability/scaling
Yellow
Work around
There are no rows in this table

Severity options

GTM strategy

What is the release plan? List the key milestones (e.g. dev complete, alpha, beta, general accessibility, etc.).
What is the marketing and operational support needed for this launch?
What are the pricing and packaging strategies?

Dev complete
Alpha
Beta
General accessibility
Q2 2019
Q3 2019
Q4 2019
Q1 2020
Q2 2020
Dev complete
Alpha
Beta
General accessibility



Step 3: Post-launch recap

Success reflection

How successful were we in achieving our goals (relative to our success metrics)?

Lessons

What have we learned? How will this help us improve?

Done reading?
FS
JH

Click the button above to let the author know you’ve read this far.


Appendix

Any extra materials e.g. clarifying documents related to the problem or solution, user research, data, etc..


Next up:
Run a product alignment meeting with the
.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.