JTBD Synthesis Deliverable For Product & Growth teams

JTBD Interview Synthesis: Four Forces, Job Clusters & Product Opportunities

A finished illustrative synthesis plus a reusable structure for demand-side interview rounds, organized around Four Forces, buying timeline, real competitive set, contradictions, job clusters, and opportunity scoring.

Product context: Cadence · Method: Bob Moesta demand-side JTBD · Evidence status: illustrative only
SOURCE TRAIL

Where this framework comes from

Framework source: JTBD Strategist prompt by @alex_verem, derived from Bob Moesta’s demand-side method.

Original X post: https://x.com/alex_verem/status/2044375991867318680

Framework elements used here — Four Forces, six-phase buying timeline, job clustering by pushes + pulls, real competitive set, contradictions, and recommendations — come from that post and were not substituted.

Core belief preserved: “Bitching ain’t switching” — study people who DID switch.

Product ContextIllustrative

Illustrative product context: Cadence

ProductCadence — a hypothetical async standup / team-check-in SaaS.
Switch event — what do people STOP doing when they hire Cadence?Stop running daily live video standups.
1 · ProductCadence, a hypothetical async standup and team-check-in SaaS.
2 · Switch to understandTeams who stopped daily live video standups and moved status sharing into async check-ins.
3 · Customer stories basisIllustrative fabricated synthesis based on invented switch stories; not real interviews.
4 · Current assumption about why people buyTeams buy because live standups interrupt maker time and no longer create alignment in distributed teams.

Evidence status: fabricated example only. Source: Illustrative fabricated synthesis dataset; framework source linked above.

Section 1 · Timeline Map

Six-phase buying timeline

Illustrative

Illustrative six-phase timeline. Each trigger and blocker is invented to demonstrate the synthesis structure.

Section 2 · Four Forces Diagram

Push, Pull, Anxiety, Habit

Illustrative

F1 · Push

  • Standups fragment maker time
  • Remote members repeat updates across timezones
  • Status meetings hide real blockers
  • Meeting load makes managers feel busy but not informed

F2 · Pull

  • FunctionalFewer synchronous interruptions
  • FunctionalSearchable status history
  • EmotionalLess performative meeting anxiety
  • SocialLooks like a disciplined distributed team

F3 · Anxiety of the New

  • Will people actually write useful updates?
  • Can managers trust async accountability?
  • Will important blockers be missed?
  • Will this become yet another tool?

F4 · Habit of the Present

  • Daily standup is a ritual everyone recognizes
  • Leaders equate live presence with control
  • Slack pings are already where work happens
  • Teams know how to cancel a meeting, not redesign coordination

Force balance

Driving F1 + F2 = 78
Restraining F3 + F4 = 61
Gap: +17 toward switching. Verdict: Switch likely when Cadence proves accountability without adding another meeting.

Illustrative score, not measured evidence.

Source: Illustrative fabricated synthesis dataset; framework source linked above.

Section 3 · Switching Moments

What made today the day

Illustrative
MADE TODAY THE DAY

Two missed standups in one sprint made the ritual feel optional but still costly.

MADE TODAY THE DAY

A timezone expansion turned a 9:30 meeting into a 6:30 meeting for the new engineer.

MADE TODAY THE DAY

A release blocker appeared in Slack after standup, proving the meeting was not the real coordination layer.

MADE TODAY THE DAY

A senior IC calculated that daily standups consumed the equivalent of one full workday per sprint.

MADE TODAY THE DAY

A manager was asked for a written status summary anyway after every live standup.

Source: Illustrative fabricated synthesis dataset; framework source linked above.

Section 4 · Real Competitive Set

What Cadence is really hired against

Illustrative

When customers are in distributed product teams with recurring status uncertainty and want alignment without interrupting maker time, they choose between: Cadence, a shared Google Doc, Slack threads, doing nothing / keeping the live standup.

Competitive comparison matrix
OptionWhy it gets hiredWhy it losesHidden appeal
CadenceStructured async check-insLoses if prompts feel roboticManagers get a written artifact
Shared Google DocFree and familiarOwnership decaysZero procurement
Slack threadsDiscussion already lives thereUpdates disappearNo behavior change
Doing nothing / live standupPreserves the ritualBurns focus timeLeaders feel in control

Source: Illustrative fabricated synthesis dataset; framework source linked above.

Section 5 · Job Clusters

Hiring pathways (by pushes + pulls)

Illustrative

Job 1 — When a distributed product team keeps repeating status across meetings and Slack, help them preserve alignment without sacrificing maker mornings.

Push cluster: meeting repetition, timezone drag, status theater.

Pull cluster: single async artifact, searchable blockers, less interruption.

Conflict: serving this job with strict prompts may hurt teams that need emotional check-in rituals.

Job 2 — When managers cannot see blockers until it is too late, help them create accountability without adding surveillance.

Push cluster: late surprises, vague ownership, stakeholder pressure.

Pull cluster: blocker visibility, follow-up trails, calmer escalation.

Conflict: too much manager visibility may hurt IC trust and adoption.

Job 3 — When senior ICs lose deep-work continuity to ritual meetings, help them communicate progress without performing availability.

Push cluster: fragmented focus, performative updates, calendar resentment.

Pull cluster: concise check-ins, autonomy, fewer context switches.

Conflict: minimizing participation may hurt managers who need richer context.

Job 4 — When a growing remote team onboards new members, help them learn norms without reviving daily live status meetings.

Push cluster: new-hire uncertainty, undocumented process, ritual drift.

Pull cluster: templates, examples, persistent team memory.

Conflict: template guidance may feel bureaucratic to mature teams.
Section 6 · Irrational Contradictions

Dining-room-table & say/do gaps

Illustrative
Dining room table insight

Managers say they want fewer meetings, but the daily standup is where they reassure themselves the team still exists.

Invented quote / not customer evidence
People say X but do Y

People say “Slack is enough,” but still ask for a recurring meeting because Slack has no closure ritual.

Invented quote / not customer evidence
People say X but do Y

ICs say they hate status updates, but adopt Cadence when the prompt lets them protect uninterrupted work.

Invented quote / not customer evidence
Painkiller layer vs real cause

“We need better standup notes.”

Invented quote / not customer evidence

Real cause: The team lacks a trustworthy async accountability ritual.

Painkiller layer vs real cause

“We need everyone on camera.”

Invented quote / not customer evidence

Real cause: Leaders are using presence as a proxy for progress.

Source: Illustrative fabricated synthesis dataset; framework source linked above.

Section 7 · Opportunity Scoring

Prioritized opportunities

Illustrative

Priority score = (Reach × Impact × Confidence) ÷ Effort

Sortable — click a column header. Default sort: Priority descending.

Scores are illustrative and fabricated; replace with real synthesis judgment after interviews. Source: Illustrative fabricated synthesis dataset; framework source linked above.

Section 8 · Prioritized Recommendations

Per job cluster

Illustrative