What a completed report actually looks like
Below is a full sample report, the same components and level of detail a real participant receives, built from entirely fabricated interview data so no real person’s assessment is shown here.
A report has four parts. The scorecard scores 16 dimensions, grouped into 4 competency families, and each dimension carries its own confidence level so you can see how firmly it is held. The evidence findings separate what was clearly demonstrated from what was claimed but never substantiated. Level fit states plainly what’s already proven at the target level and what still needs evidence. And strengths, risks, and development turn all of that into a short list of concrete next steps.
Readiness assessment
Competency profile
Demonstrated level
The sample report separates current role fit, highest demonstrated scope, target readiness, and confidence so a reader can see both the interpretation and how firmly the evidence supports it.
Evidence and confidence
Articulated a clear point of view on sequencing and why alternatives were rejected.
The enterprise-versus-self-serve tradeoff was specific, defensible, and revisited when challenged.
Examples of managing a difficult customer conversation were concrete and specific.
Peer- and leadership-level influence examples were vague when pressed for specifics.
Development priorities
Development Actions
- Seek out one initiative that requires aligning a peer team without formal authority, and track the specific tactics that work.
- Practice narrating decisions in terms of the tradeoff considered and rejected, not just the one chosen.
Suggested Next Experiences
- Own a cross-team or cross-functional initiative end to end, even a small one.
THE PRODUCT STRATEGIST, WITH AN EXECUTION DRIVER EDGE
Strong fit today. Developing toward the next level.
Based on 14 of 16 dimensions evaluated in this interview. 2 were not demonstrated in this interview, so they have no score and are left out of every average. 2 scores rest on thin evidence: they are included, flagged, and not a demonstrated weakness.
01 — Scorecard
Scorecard
Strategic Thinking
Average 7.0
2 of 4 dimensions evaluated
Articulated a clear point of view on sequencing and why alternatives were rejected.
Competitive positioning did not come up in this interview, so there is no evidence to judge either way.
Not demonstrated in this interview, so there is no score.
Not evaluated. Nothing here counts for or against the participant.
One clear example of proposing an unconventional approach that was later adopted.
AI-specific product judgment did not come up in this interview, so there is no evidence to judge either way.
Not demonstrated in this interview, so there is no score.
Not evaluated. Nothing here counts for or against the participant.
Execution & Judgment
Average 7.0
1 on thin evidence, included in the average and not a demonstrated weakness
The enterprise-versus-self-serve tradeoff was specific, defensible, and revisited when challenged.
Described consistent delivery against committed timelines across multiple examples.
Used specific usage metrics to support the central prioritization example.
Comfortable in technical tradeoff discussions but not deeply probed this session.
Thin evidence in this interview.
Limited technical-depth questions were asked; treat as directional.
Leadership & Influence
Average 5.5
1 on thin evidence, included in the average and not a demonstrated weakness
Explained a complex tradeoff clearly and concisely when asked to summarize it.
Examples of managing a difficult customer conversation were concrete and specific.
Peer- and leadership-level influence examples were vague when pressed for specifics.
Described specific coaching moments with a direct report tied to a real performance gap.
Described a working cadence with engineering and design that sounded consistent.
Thin evidence in this interview.
Commercial & Customer Judgment
Average 7.3
Reasoned clearly about churn risk and revenue tradeoffs in the enterprise-delay example.
Repeatedly grounded decisions in specific usage data rather than assumption.
Flagged a data-quality concern proactively rather than shipping around it.
Multiple specific examples of changing course quickly once new evidence appeared.
02 — Evidence
Evidence-Based Findings
Strongest Evidence
- Delayed a major enterprise request by a full quarter to protect a larger self-serve cohort, and could clearly articulate the usage data and churn-risk analysis behind that call.
- Described three separate instances of walking back a decision after new data contradicted the original plan, each with a specific detail about what changed their mind.
Role-Context Implications
- Operating in a fast-moving, resource-constrained environment where prioritization judgment carries more weight than process maturity.
Meaningful Gaps
- Examples of influencing peers or leaders outside direct reporting lines were vague when pressed for specifics on how agreement was actually reached.
Contradictions
None noted.
Unsupported Claims
- Described leading "cross-functional alignment" on a major initiative but could not name a specific disagreement that had to be resolved.
03 — Level Fit
Level Fit & Readiness
Current Level: Senior Product Manager
Consistently makes and defends difficult prioritization calls with real tradeoff reasoning, not just stated preference.
Target Level: Principal Product Manager
Not yet proven at the scope a principal role requires -- most examples were bounded to a single team or product area.
Already Proven
- Prioritization under real, conflicting stakeholder pressure
- Recovering from a wrong call once evidence changed
Not Yet Proven
- Influence across multiple teams without direct authority
- Operating with the ambiguity of a wider organizational mandate
Evidence Still Needed
- A specific example of changing a peer team's roadmap or priorities through influence alone
04 — Strengths, Risks & Development
Strengths, Risks & Development
Top Strengths
- Prioritization judgment under pressure
- Willingness to revisit a decision when evidence changes
- Clear, specific recall of actual events rather than general claims
Top Risks
- Limited demonstrated evidence of cross-functional influence
- Examples skew toward individual-team scope
Derailers
None noted.
Development Actions
- Seek out one initiative that requires aligning a peer team without formal authority, and track the specific tactics that work.
- Practice narrating decisions in terms of the tradeoff considered and rejected, not just the one chosen.
- Ask a skip-level peer for direct feedback on a recent disagreement, rather than a general check-in.
Suggested Next Experiences
- Own a cross-team or cross-functional initiative end to end, even a small one.
Strong at the current level, with real evidence of sound tradeoffs under pressure. The clearest path to the next level is building a track record of influence beyond your own team.