The To-Be journey

The ideal path: how the same PM does the same job, inside Sift. Every step and every feature closes a specific As-Is barrier or serves a specific job, and the trace is shown. A feature with no parent pain or job is cut.

A
The Overloaded PM Focus persona
Alex - Product Manager, B2B SaaS, 150 employees
Main job
Primary
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. As-Is source: cjm-as-is.html.

Design rule - To-Be = design
The future must be designed, so "don't invent" does not apply here. It is replaced by tracing: every step and every feature closes a specific As-Is barrier or serves a specific JTBD job, with a link to it. A feature with no parent pain or job is cut. The To-Be map sharpens the existing MVP core, it does not fork a second parallel backlog.

01

The To-Be path

The same PM doing the same job, inside Sift. Each step traces to a concrete As-Is barrier or a job (the Closes line). A step that closes nothing is an orphan and is cut. Target emotions are designed goals contrasted against the As-Is emotion on that phase, not measured. Steps 3, 4, and 6 are the differentiators.

Scroll horizontally to move through the six steps.

1

Connect the signal (once)

PM connects CSV import and/or Intercom; feedback ingests and normalizes; PII scrubbed by default.

Goal (job)J2 - make sense of the incoming pile
ClosesAs-Is P2 siloed channels / GZ4
CapabilityIngestion and normalization pipeline (CSV + Intercom MVP; Zendesk, Gong follow the same pattern)
Target emotion"It is all in one place" (vs -4 overwhelm). Table-stakes.
2

Open to a synthesis already done

When the session looms, PM opens Sift and sees feedback already clustered into themes with volume, recency, and evidence count; no manual reading or tagging.

Goal (job)Main job; J2
ClosesAs-Is P1 no POV / GZ5 + P3 tagging / GZ3
CapabilityAI theme synthesis, kept current (new signal since last session digest)
Target emotionPrepared, calm (vs -4 dread and -4 exhaustion)
3Differentiator

See how strong each theme is

Each theme shows item count (n=X) and a low-signal badge when thin; strong themes are visibly distinct from thin ones.

Goal (job)J3 - know how much to trust
ClosesAs-Is P4 cannot gauge strength / GZ2
CapabilityHonest confidence display (n=X plus low-signal badge)
Target emotionCalibrated trust (vs -3 distrust)
4Differentiator

Spot-check the evidence, then commit

PM clicks a theme, sees its supporting items (n=X), clicks any item to the raw original text; verifies a theme they already know is real, then trusts the novel ones; sets priority.

Goal (job)Main job; J3; E1 - feel I actually understood it
ClosesAs-Is P4 distrust and re-reading / GZ2
CapabilityProgressive drill-down (theme, evidence items, raw source) with inline citation
Target emotion"I understood it, and I can prove it" (vs -3 distrust)
5

Walk in with a brief the room can read

PM shares an evidence brief (top themes, evidence per theme, source quotes, recommended priority) as a link before the session, so the reasoning is legible without Sift access.

Goal (job)S1 - give stakeholders something to engage with; J4; Main job
ClosesAs-Is P5 rationale does not land / GZ5
CapabilityShareable public evidence brief (no login to view)
Target emotionIt lands, it is legible (vs -3 deflation)
6Differentiator

Defend with one click

Challenged in the room ("my customer said X"), the PM pulls the theme live and shows n=X items and the verbatim quotes on the spot; the anecdote meets traceable evidence.

Goal (job)J1 - stakeholder defense; E2 - certain not defensive; S1
ClosesAs-Is P6 opinion outweighs evidence / GZ1
CapabilityLive traceable evidence chain (theme, items, verbatim quote), citable in the moment
Target emotionGrounded, certain (vs -5 powerlessness). The deepest win.

Orphan check: none. All six steps close a named As-Is barrier and serve a job. All five growth zones are covered: GZ1 to Phase 6, GZ2 to Phases 3 and 4, GZ3 to Phase 2, GZ4 to Phase 1, GZ5 to Phases 2 and 5.

D3 - First integration set (locked)
CSV + Intercom for MVP. CSV gives zero-friction day-one activation (any PM can upload existing feedback and reach a first synthesis within 20 minutes); Intercom is the source named in the Segment A stack. Email-forwarding rejected: lower signal quality and messy source attribution undermine the traceability the whole product rests on.
D2 - Confidence display (locked)
Item count n=X plus a low-signal badge for MVP day-one scope. Source diversity and time range are real but are v2. A single opaque confidence score is rejected outright: a confident number with no visible basis is exactly the anti-pattern benchmark.md warns against, and would undermine trust rather than build it.

02

Emotional curve - As-Is vs To-Be

The To-Be projected target overlaid on the As-Is evidence curve. The entirely-negative As-Is trough is designed to invert into a steady positive line, rising to its peak exactly where As-Is hit its floor. Phase 6 is the largest lift (-5 to +4), the deepest, best-evidenced As-Is pain becoming the moment the PM is most in control.

+5 0 -5 +9 lift P1 Connect P2 Synthesis P3 Strength P4 Spot-check P5 Brief P6 Defend
As-Is: evidence-backed (solid)
To-Be: projected target, not measured (dashed)

The dashed To-Be line is a designed goal, not measured data. Phase 6 (the amber band) is the biggest inversion: from -5 powerlessness, the As-Is floor and its strongest-evidenced pain, to +4 control. That single inversion is the product's core promise, aimed at a real, confirmed pain.


03

Backlog and MVP

The existing MVP core, sharpened. This is the same list as the lean UX canvas Solutions, the JTBD matrix MVP core, and the CLAUDE.md MVP scope, reordered by priority with a parent and a success signal on each. One list, not a second parallel backlog. Every item has a parent barrier or job; an item with no parent is not added. The five MVP-spine rows are highlighted.

# Feature / capability Parent (As-Is barrier / job) Priority Success signal (hypothesis)
1 Feedback ingestion - CSV + Intercom As-Is P2 siloed (GZ4); J2 MVP 40% of signups reach a first synthesis on their own data within 7 days (aarrr.md Activation)
2 AI theme synthesis - transparent clusters with volume, recency, evidence count; basic ranking by signal As-Is P1 no POV (GZ5) + P3 tagging (GZ3); Main job; J2 MVP First synthesis in under 20 minutes with at least one theme the PM recognizes as real (aarrr.md Activation)
3 Honest confidence display - item count n=X + low-signal badge As-Is P4 cannot gauge strength (GZ2); J3 MVPD2, mandatory Activated users act on the synthesis; leading H1 condition. Objective 1: 60% cite Sift as primary roadmap input at 90 days
4 Evidence drill-down + inline citation - theme, evidence items (n=X), raw source text As-Is P4 distrust (GZ2) + P6 unciteable evidence (GZ1); Main job; J3; E1 MVP Activated users open the drill-down at least once in the first session (the trust behavior named in live-research.md)
5 Shareable public evidence brief - no login to view As-Is P5 does not land (GZ5) + P6 defend (GZ1); S1; J4 MVP 25% of signups attributed to referral / brief sharing (aarrr.md Referral)
6 Prioritization scoring - multi-factor (customer segment, revenue impact) Main job (rank and interrogate) Later PM interrogates a ranked list rather than accepting a black-box order (basic volume/recency ranking already ships inside item 2)
7 "New signal since last session" digest Weak parent: retention loop (aarrr.md) + H-J1 continuous sensing, which jtbd.md marks as an UNCONFIRMED hypothesis job. Not an As-Is barrier. Laterheld with caveat Week-4 retention 50% for activated users (aarrr.md Retention)
8 Roadmap link - native lightweight or Jira / Linear sync J4 (get the team to the same why); the decision-theme-signal chain Later Roadmap items linked back to their themes; serves Segment B more than the core Segment A journey
MVP spine = items 1 to 5
Remove any one and the To-Be path breaks: no ingestion (no signal), no synthesis (back to manual reading), no confidence display (no trust, H1 fails), no drill-down (the differentiator is gone), no brief (Phases 5 to 6 have nothing to carry). Items 6 to 8 improve the path but it holds without them.

04

Critique and risks

Adversarial check of the To-Be map and backlog: does every feature have a parent, does the backlog sharpen rather than fork the MVP core, and is "MVP" no broader than the riskiest assumption (H1).

Parent audit - result: no orphans
Every To-Be step and backlog item traces to a parent. Each of the five MVP-spine items (1 to 5) has at least one pattern-strength parent, so no MVP feature rests on a single-source signal alone. One weak parent found and flagged: item 7 (new-signal digest) is parented by the retention loop plus H-J1, which jtbd.md marks as an unconfirmed hypothesis job. It stays LATER, held only with that caveat, and does not earn a slot until H-J1 is confirmed.
Sharpen, not fork
The lean UX canvas prioritization view is narrowed: basic ranking by signal ships inside the AI synthesis item (MVP); multi-factor scoring (segment, revenue) moves to LATER. A narrowing, not a contradiction. The jtbd.md matrix (3 MVP jobs: Main, J3, S1) is consistent; ingestion and drill-down are the enablers of those jobs, not new scope.
Action for Step 11 - fork risk to close
CLAUDE.md MVP scope lists 7 features, including roadmap link and full prioritization, as MVP. This CJM narrows MVP to the 5-item spine and moves roadmap link and multi-factor scoring to LATER. Until CLAUDE.md is updated, two MVP definitions coexist. Step 11 must narrow CLAUDE.md to the 5-item spine so the repo holds one MVP definition.
Brief in MVP - decision recorded
Item 5 (shareable brief) is the one MVP item broader than H1: it tests H3 (viral loop) and serves S1 (stakeholder engagement), not the PM's own trust. Decision: keep the brief in MVP. It closes the Phase 5 barrier, it is the go-to-market and referral artifact, and "evidence as a social object" (job S1) is a confirmed behavior. But it is explicitly the first candidate to move to a fast-follow if a leaner, H1-only first test is wanted later. A conscious scope choice: MVP tests H1 (items 1 to 4) plus the deepest-pain defend-and-share value (item 5).
Dangerous / open items
MVP vs H1: items 1 to 4 are the pure H1 test, the transparency-and-traceability mechanism H1 requires. Remove any one and the To-Be path is dead.
Item 7 (digest): no confirmed parent; held in LATER, gated on confirming H-J1.
Forked MVP definition: the CLAUDE.md 7-feature MVP vs the 5-item spine is the open fork risk, actioned for Step 11.

Orphans cut: none new. The map confirms the earlier cuts, which correctly map to no To-Be step: J5 signal-loop / contribution tracker (D1, Segment C), real-time monitoring (anti-pattern per ux-patterns.md), team synthesis reproduction (unconfirmed job). The free/paid split is untouched: the drill-down (item 4) stays the paid differentiator, consistent with gating the trust mechanism as the paid value.