Three personas grown from research. Each is rooted in documented observations from strategy, competitive analysis, benchmarks, and live re-research in June 2026. Gaps are labeled. Hypothesis claims carry a ? badge. All three mood quotes on this page are illustrative, not sourced quotes - each is labeled accordingly.
16 observations were pulled from the six research files before building the personas. The six most structurally important are shown here. All 16 with sources are in user-research/docs/personas.md.
Alex owns two product areas and manages a backlog of 40+ active items. Feedback arrives from Intercom, Gong, Zendesk, app store reviews, and occasional user interviews. None of these tools talk to each other. Before each sprint planning session, Alex spends time manually reading through the sources, tagging items by theme in a Notion database or Jira epics, and trying to form a picture of what customers actually want.
That picture changes every time, because every PM has their own method. Alex's synthesis is not reproducible by a colleague.
Age 28-38 ? inferred from career progression, not validated. Source: strategy.md, Segment A profile; research.md Section 1.
Source: strategy.md, Segment A JTBD. Consistent with research.md Section 2.
Manual synthesis in Notion or Jira. Hours of reading across tools, tagging items, trying to spot patterns. The result is not traceable back to source items, not reproducible by the team, and hard to defend when challenged - "I think I saw this in several support tickets" is not evidence.
| Productboard | Feature-rich but complex to set up. Spark AI positions around workflow prompts (write a PRD, summarize) rather than traceable evidence. Trust mechanism unclear from public pages. High price point ($19-59/maker/month). |
| Canny | Vote-based prioritization. Autopilot AI captures and classifies. But Canny is customer-facing (public roadmap, changelog) - a different problem than internal PM synthesis. Using Canny means also managing customer expectations publicly. |
| Enterpret | Enterprise infrastructure, contact sales, not self-serve. Not accessible to a PM at a 150-person company without a procurement process. |
| Dovetail | Research-oriented (interviews, recordings, insight docs). Positioned as a research repository, not a synthesis-to-decision tool for PMs in sprint planning. |
| Jira Product Discovery | Attractive if already in Atlassian ecosystem. Scoring and backlog integration strong. But feedback ingestion and AI synthesis are weaker than purpose-built tools. |
| Notion DIY | Maximum flexibility, zero cost. But synthesis happens in Alex's head. Requires manual maintenance to keep evidence intact. When Alex leaves, the system collapses. Trust is in Alex, not a reproducible process. |
Source: competitors.md, benchmark.md.
Source: benchmark.md (Mechanisms 1-3, Anti-pattern). ux-patterns.md (B3). strategy.md, Riskiest Assumption (H1).
No real sourced quote was gathered in the research phase. Step 6 re-research was attempted (Reddit blocked, G2 blocked). Freeman C. (Senior PM, Capterra, Nov 2025) is the closest primary voice found. See live-research.md F5.
Morgan manages a team of four PMs and presents the roadmap to the board or leadership team quarterly. Each PM synthesizes feedback differently, and when Morgan assembles a quarterly strategy presentation, they are aggregating summaries of summaries - not traceable back to customer signal.
When leadership challenges a priority ("Why aren't we solving X? That's what I hear from every customer"), Morgan cannot point to systematic evidence. The answer is anecdote ("I believe our research shows...") rather than data.
Age 35-45 ? inferred from career progression, not validated. Source: strategy.md, Segment B profile.
Primary source: strategy.md, Segment B JTBD. Secondary job is a hypothesis - implied by the "no consistent evidence standard" pain but not stated explicitly in strategy.md.
Morgan-specific trust behaviors are a hypothesis. No primary source for this persona's trust behaviors was gathered in research.
Jordan speaks to customers daily - support tickets, onboarding calls, check-ins. Jordan sees patterns that product does not see: common complaints, feature requests from multiple accounts, recurring confusion in the same flow. Jordan logs these in Intercom or shares them in Slack, but they do not visibly move the roadmap.
Jordan has no closure loop: they share the feedback, and it disappears into a black box.
Age 26-35 ? inferred from career progression, not validated. Not the economic buyer. Adoption depends on Alex (Segment A) using the tool. Source: strategy.md, Segment C.
Source: strategy.md, Segment C JTBD.
Jordan-specific trust behaviors are a hypothesis. No primary source was gathered. This is the least-developed persona because research confirms CS/support as a later priority.