Reference · Cross-cutting

Source Quality, Stakeholder Alignment & Implementation Handoff

Load when source hierarchy, data confidence, triangulation, stakeholder alignment, implementation handoff, 30/60/90.

Part of the Product Strategy skill · loaded on demand from SKILL.md

Part of the product-strategy skill. See SKILL.md for the workflow spine and when to load this file.

XXI. Source Quality & Assumption Management

Purpose

Ensure the strategy is evidence-based, transparent, and robust to uncertainty.

Source Hierarchy

Prioritize sources in the following order:

Internal customer, usage, and financial data
Primary customer research
Expert interviews
Regulatory or official sources
Credible market datasets
Competitor disclosures
Analyst reports
Press and secondary sources
Proxy benchmarks
Team assumptions

Data Confidence Rating

For each major input, assign confidence:

Rating	Meaning
High	Direct, recent, reliable source
Medium	Credible source, but partial or requires interpretation
Low	Proxy, outdated, incomplete, or assumption-based

Assumption Log Template

Assumption	Source	Confidence	Sensitivity	Owner	Validation Plan

Triangulation Rules

Use at least two independent sources for important assumptions where possible.

Triangulate:

Market size
Growth rate
Customer adoption
Pricing
Conversion
CAC
Cost-to-serve
Churn
Margin
Regulatory requirements
Partner fees

Common Data Pitfalls

Watch for:

Confusing TAM with reachable market
Overestimating conversion
Ignoring cannibalization
Underestimating CAC
Underestimating cost-to-serve
Assuming competitor pricing reflects willingness to pay
Using global benchmarks for local markets
Ignoring regulatory differences
Treating one customer segment as representative of all customers
Overlooking operational complexity
Building a base case that is actually an upside case

XXII. Stakeholder Alignment Plan

Purpose

Ensure decision-makers align on strategic ambition, investment appetite, risk tolerance, and execution model.

Key Stakeholder Groups

Executive sponsor
Product leadership
Commercial leadership
Technology leadership
Operations
Risk
Compliance
Legal
Finance
Data / analytics
Customer support
Sales
Marketing
Partner management
Regional or market leaders

Alignment Questions

What decision needs to be made?
What level of ambition is expected?
What time horizon matters?
What investment level is acceptable?
What risks are unacceptable?
What capabilities must remain internal?
What can be outsourced or partnered?
What are the non-negotiables?
What does success look like?

Stakeholder Outputs

Stakeholder map
Interview guide
Workshop plan
Decision log
Open issue tracker
Alignment summary
Steering committee materials

XXIII. Implementation Handoff

Purpose

Translate strategy into execution-ready workstreams.

Handoff Components

A strong strategy handoff should include:

Product requirements
MVP scope
Prioritized backlog
Business case
KPI targets
Roadmap
Capability requirements
Partner requirements
Regulatory requirements
Risk register
Operating model
RACI
Launch plan
Validation plan
Decision gates

First 30 / 60 / 90 Days

First 30 Days

Focus:

Confirm executive decisions
Assign owners
Finalize MVP scope
Begin vendor or partner outreach
Define product requirements
Confirm regulatory path
Set up governance
Launch customer validation or pilot design

First 60 Days

Focus:

Complete partner selection
Finalize operating model
Start build or integration
Finalize pricing and packaging
Build launch funnel
Prepare risk and compliance controls
Define analytics and KPI dashboard
Recruit pilot customers

First 90 Days

Focus:

Launch pilot or beta
Measure early adoption
Test onboarding and activation
Validate unit economics
Identify operational issues
Refine roadmap
Prepare scale decision

Handoff Outputs

Execution roadmap
Workstream plan
Product backlog
Partner RFP
Pilot plan
KPI dashboard
Governance cadence
Decision gate calendar
Launch readiness checklist