The current path, without Sift, which does not exist yet. As-Is is research, not invention: every emotion and every barrier stands on a real, sourced public quote. Strength of evidence is marked, a single mention is a signal, a repeat across sources is a pattern. Where the path is not covered by data, the gap is marked [?]. As-Is is a mirror, not a cure: no solutions live here, they belong to To-Be.
01
Focus
One persona, one job. This map follows a single path: how the Overloaded PM does the roadmap-prep job today. Segment B (Product Lead) runs a lighter variant of the last three phases, aggregating the team's syntheses and presenting to the board, not a fundamentally different path.
A
The Overloaded PMPrimary
Alex - Product Manager, B2B SaaS, 150 employees
Main Job
"When I am preparing for a roadmap planning session and I have customer feedback spread across multiple tools I haven't had time to read, I want to feel certain I know what our customers actually need most, with the evidence behind it, so that I can walk into the session with a call I'll stand behind and defend if anyone pushes back."
Focus persona: personas.md (Persona A). Main job: jtbd.md (Main Job of the Product).
02
The As-Is Path
Six phases, derived from the real path of this job, not a generic funnel. Each card carries the phase goal (job link), what Alex actually does, the touchpoints, the live thought, and the barrier. Every barrier stands on a sourced quote shown in the Emotional Curve section below.
Phase 1Signal
The session looms
Emotion: negative, intensity 4
Goal (job link)
Register that a planning session is coming and that arriving without a defensible view is not an option. (Main Job; E2)
Actions today
Sees the planning session on the calendar; mentally braces; blocks time to "do the feedback review" before the meeting.
Touchpoints
Calendar; Jira / Linear sprint board
Thought
"What priorities do I have from product?" "Am I doing enough? Am I focusing on the right thing?"
Barrier
No synthesized point of view ready when planning arrives; fear that admitting this looks like incompetence, so the PM does not even ask for help.
Phase 2Pattern
Gather the scattered signal
Emotion: negative, intensity 4
Goal (job link)
Get the recent customer feedback in one place to work from. (J2, make sense of the incoming pile)
Actions today
Opens each source in turn and pulls recent items: support tickets, call recordings, helpdesk, reviews, interview notes; reads across many tabs.
Touchpoints
Intercom (support), Gong (sales calls), Zendesk (helpdesk), app store reviews, interview docs
Thought
"The information is all over the place and completely siloed." "There's gotta be a good way to get through the noise."
Barrier
Feedback is siloed across many disconnected channels; volume and noise make collection cumbersome before any thinking starts.
Phase 3Pattern
Read and tag / cluster
Emotion: negative, intensity 4
Goal (job link)
Turn raw items into themes and spot the real patterns, not just the loudest voices. (J2)
Actions today
Reads each item; tags by theme in a Notion database or Jira epics; hours of reading; tries to hold the emerging picture in memory.
Touchpoints
Notion database / Jira epics
Thought
"This is wayyyy too much for a human to go through." "I get sick of sifting through stuff."
Barrier
Manual reading and tagging is hours of low-leverage labor; volume exceeds human capacity; the output is often not even usable afterward.
Phase 4Pattern
Synthesize and decide priority
Emotion: neutral to negative, intensity 3
Goal (job link)
Reach a confident sense of the top customer problems and judge how strong the evidence is. (Main Job; J3, know how much to trust)
Actions today
Forms themes from memory; ranks them; decides what goes on the roadmap; privately wonders how solid each conclusion is.
Touchpoints
Notion / Jira; the PM's own judgement
Thought
"Any system that summarizes feedback will gloss over the key insights." "Plenty of things get missed."
Barrier
Summarizing flattens nuance; you cannot review everything so things get missed; hard to know whether the theme you land on is actually strong evidence, so the PM re-reads the raw data or refuses to act.
Phase 5Signal
The planning session
Emotion: negative, intensity 3
Goal (job link)
Walk in and present a call worth standing behind. (Main Job; E2, certain, not defensive)
Actions today
Presents priorities to the team; references "what customers are saying" to justify the ranking.
Touchpoints
Planning meeting (room / Zoom); slides or the Jira / Linear roadmap
Thought
"They were uninterested." "They just did not understand anything I was saying."
Barrier
The prioritization rationale does not translate to the room; the audience questions or disengages; the PM cannot make the reasoning stick.
Phase 6Pattern (strong)
Defend under challenge
Emotion: negative, intensity 5, the floor
Goal (job link)
Hold the position with real evidence when pushed, not opinion. (J1, stakeholder defense; S1)
Actions today
A stakeholder pushes back ("my customer said X"); Alex tries to recall where they saw the signal; often "I think I saw this in several tickets"; may back down or scramble back to the source.
Touchpoints
The meeting; scrambling back into Intercom / Notion mid-conversation
Thought
"Customer says x but we believe y is better, with no data and no evidence." "Evidence is nothing in the face of a hippo."
Barrier
Stakeholder or executive opinion outweighs the evidence; the "my customer said X" anecdote trumps synthesized data; the PM has no leverage even when the data is on their side. The deepest point of the As-Is curve.
Scroll horizontally to follow all six phases. [?] Phase 3 tool split (how many PMs tag in Notion vs Jira vs a spreadsheet, and how long it takes) is unsourced: the activity is sourced, the distribution and duration are not. [?] Phases 5 and 6 in-room texture is sourced from the job statement and the "roadmap challenged by sales" pain, firmed up by mining below.
03
Emotional Curve
Sentiment by phase on a -5 (worst) to +5 (best) axis. Each point rests on a real, sourced emotion. Point weight encodes evidence strength: pattern-backed points are full filled dots, signal-backed points are smaller hollow dots, so a single mention is never shown as strong as a confirmed pattern. No point sits on a [?], nothing is interpolated.
Shape: a flat, entirely negative trough. The journey opens at -4, never rises above -3, and drops to its floor of -5 at the end. There is no positive point anywhere in the As-Is journey. The absence of any relief is itself the finding.
Bottom (deepest negative): Phase 6, defending the call under stakeholder challenge, strongest evidence and lowest sentiment. Peaks: none. Weakest-evidence points: Phases 1 and 5 (signals), the first candidates for firming up in interviews. Phase 4 was promoted to a pattern in Step 6 re-research.
Supporting voices, grouped by phase
Every quote below is verbatim public feedback with its source URL. Screenshots of the source pages are saved in research/screens/ as durable evidence. Reddit is read via old.reddit.com.
Phase 1, The session loomsSignalNegative, intensity 4, anticipatory dread and self-doubt
Thoughts: "What priorities do I have from product?" "Am I doing enough? Am I focusing on the right thing?" "Is project A more important than project B?"
"I was working on roadmap items (discovery, PRD, planning, etc.), then came the Spring Planning and EM asked me 'what priorities you've from product?' I drew blank and felt I should be on top of every sprint and should have product priorities clearly aligned so I can get product work done. But I didn't have any."
"Asking for help openly feels like I'm showing the company I don't know my shit."
u/lefarche, GPM at a Series C AI SaaS startup - Reddit source - Screenshot: research/screens/reddit-overwhelmed-drew-blank-planning.png
Phase 2, Gather the scattered signalPatternNegative, intensity 4, overwhelm and fatigue
Barrier: feedback is siloed across many disconnected channels; volume and noise make collection cumbersome before any thinking starts.
"when it comes down to qualitative data, the information is all over the place, and completely siloed. I try to leverage data from zendesk tickets, user interviews and transcripts, feedback widget pop ups, sitting in sales calls, even whatsapp groups with the field teams etc. By having so many different channels where customer feedback is collected, it can be cumbersome to take all of this qualitative data and synthesize it."
"This shit sucks. Man, there's so many random people sending BS feedback to our email and other feedback channels, there's gotta be a good way to get through the noise."
"I receive a lot of different input across many channels. With Product Board, I can use my Chrome extension and send everything there. Once a week a specific time is designated to search across all input and find the most valuable insights."
Productboard reviewer, tool-specific, the same reality framed positively - Capterra source - Screenshot: research/screens/capterra-productboard-1.png
Phase 3, Read and tag / clusterPatternNegative, intensity 4, tedium and exhaustion
Barrier: manual reading and tagging is hours of low-leverage labor; volume exceeds human capacity; the output is often not even usable afterward.
"This process is often incredibly messy, tedious and highly intensive (in terms of labor). You're often living in sticky note hell and it's even more challenging to do this as a remote team."
Sherif M., "Distinguished Product Manager," describing the general manual workflow before any tool - Capterra source - Screenshot: research/screens/capterra-dovetail-tagging.png
"I spent 8+ hours 'tagging' nearly 20 research interviews, come to find out I can't generate any meaningful reports with the data I just transcribed and tagged. No easy way to show who answered what. In all, an entire waste of time and money."
Andrew E., 1.0 star, Dovetail-specific, but the 8+ hours of tagging labor is the general pain - Capterra source - Screenshot: research/screens/capterra-dovetail-tagging.png
"wayyyy too much for a human to go through." ... "There's so many random requests that I get sick of sifting through stuff."
Phase 4, Synthesize and decide priorityPatternNeutral to negative, intensity 3, low trust in the synthesis
Barrier: summarizing flattens nuance; you cannot review everything so things get missed; hard to know whether the theme you land on is actually strong evidence, so the PM re-reads the raw data or refuses to act. This is the J3 "how much to trust a conclusion" gap, observed in the wild.
Original thread
"The devil is in the details. Any system that will summarize feedback will gloss over the key insights coming from customers."
"half the time our team isn't consistently reviewing all the transcripts so plenty of things get missed just from our laziness."
u/kashin-k0ji, same thread - Reddit source - Screenshot: research/screens/reddit-analyzing-feedback-at-scale.png
Corroboration, Step 6 re-research, June 2026, promotes this phase to a pattern
"Surface-level summaries often miss nuance. I still need to go back to the source material to really trust the insight. Traceability is a big deal. If I cannot point to a verbatim quote to back up a theme, I am not using it in a decision. Biggest blocker: Trust. Execs (rightfully) want to know where insights came from. Any AI workflow that obscures the data trail is a non-starter."
u/bo-peep-206, bullseye: restates the whole claim and names traceability as the trust condition, direct support for GZ1, GZ2 and H1 - Reddit source - Screenshot: research/screens/reddit-ai-summary-distrust-1.png
"AI summarizes 50 interviews and offers a label: 'pricing concerns'. ..but usually, AI does not reference specific interviews and times to note the specific quotes about pricing concerns."
u/learning_more, the summary hides which evidence sits behind a theme - Reddit source
"For interviews, I've tried using AI for summaries but like you said, they miss stuff. Still gotta do the manual tagging for themes."
"I also get nervous about the focus they're putting on AI. ... the AI features are annoying, unreliable, inaccurate."
Olivia H., Principal User Researcher, cross-site Capterra Dovetail review, researcher role adjacent to PM - Capterra source - Screenshot: research/screens/capterra-dovetail-ai-unreliable.png
"pick out the themes so you can bring those up to your team and stakeholders. you will be able to speak more confidently and feel more comfortable in your decisions over time."
u/drteacherman, names the phase goal, confidence, aspirational not delivered by the current path - Reddit source - Screenshot: research/screens/reddit-overloaded-qualitative-data.png
Phase 5, The planning sessionSignalNegative, intensity 3, deflation, not landing
Barrier: the prioritization rationale does not translate to the room; the audience questions or disengages; the PM cannot make the reasoning stick.
"I tried to explain some really basic stuff.. RICE, GIST, Kano. They were uninterested."
"I presented a Now/Next/Later roadmap and explicitly state 'This does not correspond with a literal timeline.' The next question I got was 'Okay, but when is Next?'"
"I really don't know how to communicate to them that we need to be able to pivot. They just did not understand anything I was saying."
Phase 6, Defend under challengePattern (strong)Negative, intensity 5, powerlessness and resignation, the floor
Barrier: stakeholder or executive opinion outweighs the evidence; the "my customer said X" anecdote trumps synthesized data; the PM has no leverage even when the data is on their side. The deepest point of the As-Is curve and the sharpest argument for Sift.
"Because usually stakeholder agendas and egos are more heavily weighted than feedback from users"
"This ends up being one of the hardest things to manage - customer says x but we believe y is better ... With no data and no evidence. You need to have success metrics and show why this doesn't work to make better data-driven decision"
u/OkExpression8287, same thread - Reddit source - Screenshot: research/screens/reddit-feedback-challenge-hippo.png
"Evidence is nothing in the face of a hippo."
u/Facelotion, same thread - Reddit source - Screenshot: research/screens/reddit-feedback-challenge-hippo.png
"Executive leadership thinks their gut fEeLiNgS are more accurate than quantitative data."
u/plot_twist7, same thread - Reddit source - Screenshot: research/screens/reddit-feedback-challenge-hippo.png
"I'm a Junior PM. Almost broke down today due to getting into so many conflicts this week with multiple other PMs/stakeholders." ... "This is my first time dealing with so many conflicting opinions coming at me in all directions."
"It can be difficult to say 'no' to a HiPPO, especially if the executive, investor, or another stakeholder behind it is of particularly high-authority."
19 verbatim quotes, 10 public pages read, 8 screenshots saved as evidence. Every phase stands on a real quote; no phase is left on a drawn-in emotion. Strength split: Phases 2, 3, 4, 6 are patterns; Phases 1 and 5 remain signals (one strong voice with partial corroboration) and are the weaker points to firm up. Phase 6 is the deepest and strongest, Phase 4 is the second pillar, so both differentiator growth zones (GZ1, GZ2) stand on pattern-strength evidence.
04
Growth Zones
Five places where today's experience hurts most and where Sift can win. Each is tied to a Step 4 barrier and, where one exists, a research gap. Zones backed by a pattern are prioritized over single signals. No solution is written here, that is To-Be. This is where it hurts and where the opening is, not how we fill it. "Differentiator vs table-stakes" is flagged because pattern-strength in the mining is not the same as a competitive opening. GZ1 and GZ2, the two differentiators, are emphasized.
GZ1
Evidence that actually outweighs the anecdote
DifferentiatorPriority 1
From Phase 6, strong pattern, -5, the floor
Today the "my customer said X" anecdote plus executive ego beats synthesized data, because the PM's evidence is unciteable ("I think I saw this in several tickets"). The opening is the PM's total lack of leverage in the room even when the data is on their side. This is the deepest trough and the clearest unclaimed position, the safest ground for the MVP.
BarrierPhase 6, strong pattern, the floor of the curve at -5.
Research gapNo competitor owns the PM "defend your roadmap with evidence" story (competitors.md O14; research.md gap "PM-specific positioning"). Jobs J1, S1, E2.
GZ2
Trust the synthesis without re-reading everything
DifferentiatorPriority 2
From Phase 4, pattern (promoted in Step 6 re-research)
PMs distrust summaries they cannot trace: "surface-level summaries often miss nuance, I still need to go back to the source material to really trust the insight" (bo-peep-206). The opening is that the PM cannot trust a summary whose evidence trail is hidden, so they either re-read the raw data or refuse to act on it. Mining and research now agree, top-tier priority.
BarrierPhase 4, now a pattern: 5+ independent PM and researcher voices across three Reddit threads plus Capterra (Step 6 re-research).
Research gapJ3 "know how much to trust a conclusion" is the clearest unclosed gap across all five competitors (jtbd matrix; research.md gap "honest confidence display"). This is also the riskiest assumption H1.
GZ3
Kill the hours of manual tagging
Partly table-stakesPriority 3
From Phase 3, pattern
"Sticky note hell", "8+ hours tagging", "wayyyy too much for a human to go through." The opening is the low-leverage manual labor between raw signal and a usable picture. Competitors already auto-classify, so automating the labor alone is table-stakes here, not an edge.
BarrierPhase 3, pattern.
Research gapMVP AI synthesis; Objective 2 (time to decision); the core time-saving value. Necessary but partly served by competitors.
GZ4
One home for siloed signal
Table-stakesPriority 4
From Phase 2, pattern
Feedback lives "all over the place, completely siloed" across Zendesk, Gong, interviews, widgets, WhatsApp, email; collection is cumbersome before any thinking starts. The opening is the fragmentation itself. Necessary but not differentiating, every competitor aggregates; this is the price of entry, not the edge.
BarrierPhase 2, pattern.
Research gapMVP ingestion (CSV + Intercom first, D3); aarrr Activation.
GZ5
Walk in ready, and make the reasoning land
SupportingPriority 5
From Phases 1 and 5, signals
"I drew blank" when asked for priorities; "they did not understand anything I was saying." The opening is arriving with a synthesized point of view and a form of it the room can engage with. Lowest priority, rests on single signals, but it is the same evidence-brief artifact that GZ1 needs, so it comes largely for free.
BarrierPhases 1 and 5, signals.
Research gapS1 (give stakeholders something to engage with); the shareable evidence brief.
Ordering logic: GZ1 and GZ2 are both deepest-pain and unclaimed-position, so they lead. GZ3 and GZ4 are real pattern pains but partly served by competitors, so they are necessary table-stakes rather than the edge. GZ5 supports GZ1 through the same artifact. To-Be must close GZ1 to GZ4 for the path to hold; GZ5 improves it.
Still open [?]
Exact per-planning-cycle synthesis duration is [?]: the "8+ hours to tag ~20 interviews" anchor is tool-specific, not per-cycle. Order of magnitude (hours to days) holds; the precise number stays [?] pending user interviews. Phases 1 and 5 remain signals and are the first candidates to firm up. Whether the evidence brief is used before (persuade) or after (defend) the decision is still open, deferred to beta observation.