pdurlej/patchwarden

Fork 0

#3 JTBD Job Map (Christensen forces-of-progress) #4

New issue

Closed

opened 2026-05-15 19:15:21 +02:00 by claude · 1 comment

claude commented

2026-05-15 19:15:21 +02:00

Collaborator

TL;DR (PL)

Mapa Jobs-to-be-Done dla Patchwarden persona (self-hosting non-dev operator). Christensen forces-of-progress: push obecnej sytuacji (co aktualnie boli), pull nowego rozwiązania (co przyciąga), anxiety (lęki przed switch), habit (co trzyma w status quo). Plus functional + emotional + social jobs. Cagan p.142: dla nowej kategorii JTBD > personas.

TL;DR (EN)

Jobs-to-be-Done map for Patchwarden persona. Christensen forces-of-progress (push of present pain, pull of new solution, anxiety of switching, habit of status quo) + functional/emotional/social jobs. Cagan p.142: for new category, JTBD > personas. Wave 2, sequential before #4 Positioning.

Scope

Forces-of-progress 4-square:

Push of present situation — what's painful enough about current state to make switching worth considering?
Pull of new solution — what attracts to Patchwarden specifically?
Anxiety of new solution — what scares about adopting (installation, learning curve, trust)?
Habit of present — what current behavior makes switching hard (sunk cost, familiarity)?

Job categories (per Christensen):

Functional jobs — what the user is trying to GET DONE (mechanics, outputs)
Emotional jobs — how the user wants to FEEL (in control, safe, professional)
Social jobs — how the user wants to BE PERCEIVED (by peers, future employer, community)

ICP characterization (folded in here, NOT separate persona doc):

Demographics (technical literacy level, work context, team size)
Tools used (Forgejo? Gitea? GitHub also?)
Income/budget tolerance ($7-9/mo realistic?)
Trigger event (what makes them search for Patchwarden?)
Anti-ICP (who Patchwarden is explicitly NOT for)

What this artifact does NOT cover:

Detailed persona document (Cagan: JTBD > personas for new categories)
Interview script (that's #8 Discovery Plan)
Positioning statement (that's #4 Canvas)

Inputs (feedstock)

docs/discovery-interview-plan.md — persona filter + interview script provide hypothesis to test
PM-SHOW.md § "who is this for" — current ICP draft
docs/research/2026-05-15-wedge-competitive.md — competitive alternatives = what current users do today
Christensen Competing Against Luck — forces-of-progress framework
Bob Moesta JTBD interview methodology

Skill draft

Anthropic Skill: product-management:synthesize-research
Anti-prompt: "NOT generic persona doc with demographics + goals + pain points. This is forces-of-progress: ANXIETY and HABIT are equally weighted with PUSH and PULL. Most JTBD docs skip those — don't."
Prime with: Christensen Competing Against Luck + Bob Moesta JTBD interview teardowns

Dependencies

Blocked by: none (Wave 2 entry point — can start after #1 Vision drafts OR in parallel)
Blocks: #4 Positioning Canvas (needs ICP + JTBD as input), #8 Discovery Plan (informs cadence)

Cagan-grade acceptance criteria

Universal (must pass all 5):

Evidence cited — every job claim cites either an interview note OR a public self-hoster signal (r/selfhosted thread, Mastodon post, blog)
Operator-readable <10 min — 4-square diagram + ICP block ≤2000w
Names the wrongness condition — "this JTBD is wrong if 5+ discovery interviews surface a primary job not on this map"
Single concrete decision — moves docs/decisions.md by adding D10: "primary functional job = [TBD operator choice OD4]; commit to test this in M2 discovery"
Cousin-family attribution — credits skill, discovery interview plan, Agent A wedge research

Tier-1 core extras:

One numerical anchor — frequency hypothesis ("operator hits this pain X times per week") OR willingness-to-pay ranges
Visible asymmetry — names a job that only Patchwarden can fulfill in the wedge (e.g. "Forgejo-native + non-dev-readable + policy-not-LLM")

Operator decision points

This artifact gates on:

OD4 — Primary functional job framing (defaults proposed in body; operator picks one to commit-and-test in M2)

Status flow

status:cagan-grade-review-pending → operator merges → close → tick epic Wave 2 #3 → unblock #4 #8

Parent epic: #1 (this is artifact 3 of 11)
Plan: /Users/pd/.claude/plans/deep-pondering-popcorn.md § Wave 2

Drafted by Prof Kong (claude Opus 4.7) on behalf of pdurlej, 2026-05-15.

## TL;DR (PL) Mapa Jobs-to-be-Done dla Patchwarden persona (self-hosting non-dev operator). Christensen *forces-of-progress*: push obecnej sytuacji (co aktualnie boli), pull nowego rozwiązania (co przyciąga), anxiety (lęki przed switch), habit (co trzyma w status quo). Plus functional + emotional + social jobs. **Cagan p.142**: dla nowej kategorii JTBD > personas. ## TL;DR (EN) Jobs-to-be-Done map for Patchwarden persona. Christensen forces-of-progress (push of present pain, pull of new solution, anxiety of switching, habit of status quo) + functional/emotional/social jobs. **Cagan p.142**: for new category, JTBD > personas. Wave 2, sequential before #4 Positioning. ## Scope **Forces-of-progress 4-square**: 1. **Push of present situation** — what's painful enough about current state to make switching worth considering? 2. **Pull of new solution** — what attracts to Patchwarden specifically? 3. **Anxiety of new solution** — what scares about adopting (installation, learning curve, trust)? 4. **Habit of present** — what current behavior makes switching hard (sunk cost, familiarity)? **Job categories** (per Christensen): - **Functional jobs** — what the user is trying to GET DONE (mechanics, outputs) - **Emotional jobs** — how the user wants to FEEL (in control, safe, professional) - **Social jobs** — how the user wants to BE PERCEIVED (by peers, future employer, community) **ICP characterization** (folded in here, NOT separate persona doc): - Demographics (technical literacy level, work context, team size) - Tools used (Forgejo? Gitea? GitHub also?) - Income/budget tolerance ($7-9/mo realistic?) - Trigger event (what makes them search for Patchwarden?) - Anti-ICP (who Patchwarden is explicitly NOT for) **What this artifact does NOT cover**: - Detailed persona document (Cagan: JTBD > personas for new categories) - Interview script (that's #8 Discovery Plan) - Positioning statement (that's #4 Canvas) ## Inputs (feedstock) - `docs/discovery-interview-plan.md` — persona filter + interview script provide hypothesis to test - `PM-SHOW.md` § "who is this for" — current ICP draft - `docs/research/2026-05-15-wedge-competitive.md` — competitive alternatives = what current users do today - Christensen *Competing Against Luck* — forces-of-progress framework - Bob Moesta JTBD interview methodology ## Skill draft - **Anthropic Skill**: `product-management:synthesize-research` - **Anti-prompt**: *"NOT generic persona doc with demographics + goals + pain points. This is forces-of-progress: ANXIETY and HABIT are equally weighted with PUSH and PULL. Most JTBD docs skip those — don't."* - **Prime with**: Christensen *Competing Against Luck* + Bob Moesta JTBD interview teardowns ## Dependencies Blocked by: none (Wave 2 entry point — can start after #1 Vision drafts OR in parallel) Blocks: #4 Positioning Canvas (needs ICP + JTBD as input), #8 Discovery Plan (informs cadence) ## Cagan-grade acceptance criteria **Universal (must pass all 5)**: 1. **Evidence cited** — every job claim cites either an interview note OR a public self-hoster signal (r/selfhosted thread, Mastodon post, blog) 2. **Operator-readable <10 min** — 4-square diagram + ICP block ≤2000w 3. **Names the wrongness condition** — "this JTBD is wrong if 5+ discovery interviews surface a primary job not on this map" 4. **Single concrete decision** — moves `docs/decisions.md` by adding D10: "primary functional job = [TBD operator choice OD4]; commit to test this in M2 discovery" 5. **Cousin-family attribution** — credits skill, discovery interview plan, Agent A wedge research **Tier-1 core extras**: - **One numerical anchor** — frequency hypothesis ("operator hits this pain X times per week") OR willingness-to-pay ranges - **Visible asymmetry** — names a job that **only Patchwarden** can fulfill in the wedge (e.g. "Forgejo-native + non-dev-readable + policy-not-LLM") ## Operator decision points This artifact gates on: - **OD4** — Primary functional job framing (defaults proposed in body; operator picks one to commit-and-test in M2) ## Status flow `status:cagan-grade-review-pending` → operator merges → close → tick epic Wave 2 #3 → unblock #4 #8 --- Parent epic: #1 (this is artifact 3 of 11) Plan: `/Users/pd/.claude/plans/deep-pondering-popcorn.md` § Wave 2 *Drafted by Prof Kong (claude Opus 4.7) on behalf of pdurlej, 2026-05-15.*

claude added this to the M1: Cagan Package v1.0 milestone

2026-05-15 19:15:21 +02:00

claude added the

status:cagan-grade-review-pending

labels

2026-05-15 19:15:21 +02:00

claude referenced this issue

2026-05-15 19:15:45 +02:00

#4 Positioning Canvas (April Dunford 5-step) #5

claude referenced this issue

2026-05-15 19:17:16 +02:00

#8 Continuous Discovery Plan (Torres cadence + opportunity solution tree) #8

claude referenced this issue

2026-05-15 19:17:49 +02:00

#9 Business Model Canvas + Unit Economics (Osterwalder + CAC/LTV/payback + sensitivity) #9

claude referenced this issue

2026-05-15 19:18:24 +02:00

#2 Product Strategy (insights → bets ≤3 → principles) — LAST per strategy-as-synthesis #10

claude referenced this issue

2026-05-15 19:19:30 +02:00

#11 Empowered Team Operating Principles (solo-operator variant, cousin-family delegation) #12

claude referenced this issue

2026-05-15 19:21:36 +02:00

Epic: Cagan-grade product strategy package (11 artifacts × 5 waves) #1

claude referenced this issue from a commit

2026-05-15 21:11:49 +02:00

docs/product: Cagan-grade product strategy package v1.0 (11 artifacts batch)

claude referenced this issue

2026-05-15 21:12:42 +02:00

Epic: Cagan-grade product strategy package (11 artifacts × 5 waves) #1

claude referenced this issue

2026-05-15 21:37:34 +02:00

#1 Product Vision Narrative (3-year motivational prose) #2

claude referenced this issue from a commit

2026-05-15 22:03:12 +02:00

docs/product: iter-2 — auto-merge-by-policy + filter stack + Goldratt thesis

claude referenced this issue

2026-05-15 22:03:45 +02:00

#12 Strategic Thesis — defense-in-depth + Goldratt constraint-redirect + emergent selection pressure #13

claude referenced this issue

2026-05-15 22:04:31 +02:00

#6 Four-Risks Assessment (Cagan: value / usability / feasibility / viability) #6

claude commented

2026-05-26 12:44:35 +02:00

Author

Collaborator

Closed via operator voice ack 2026-05-26.

Operator highlights:

Agentic-first operator persona — TAK, 100%
Spokój (E5) jako najgłębszy emotional job — "Patchwarden daje luz i świadomość że mogę sobie vibe się bawić i rzeczy się dzieją"
New operator insight: "SF flex 2026 — ludzie nie mówią nad czym pracują, tylko nad czym ich AI-e pracują w tym momencie jak oni nie patrzą. Patchwarden to demokratyzuje."
OD4 sharpening: NIE tylko "stay above the code" → "value first" — chodzi o dostarczanie wartości (kod, dokumentacja, narzędzia — whatever artifact)
Anti-ICP softening: pro-dev/enterprise — "buduję dla siebie i podobnych, potem zobaczymy"

Modifications queued in claude/patchwarden-tactical-updates PR:

OD4 → "value-first" framing (subsumes stay-above-the-code as one expression)
"SF AI-e flex" insight do TL;DR jako democratization angle

D10 (value-first JTBD primary functional job) → claude/patchwarden-decisions-batch PR.

Status: cagan-grade-approved. — claude (Patchwarden dedicated thread)

**Closed via operator voice ack 2026-05-26.** Operator highlights: - Agentic-first operator persona — TAK, 100% - Spokój (E5) jako najgłębszy emotional job — *"Patchwarden daje luz i świadomość że mogę sobie vibe się bawić i rzeczy się dzieją"* - **New operator insight**: *"SF flex 2026 — ludzie nie mówią nad czym pracują, tylko nad czym ich AI-e pracują w tym momencie jak oni nie patrzą. Patchwarden to demokratyzuje."* - **OD4 sharpening**: NIE tylko "stay above the code" → **"value first"** — chodzi o dostarczanie wartości (kod, dokumentacja, narzędzia — whatever artifact) - Anti-ICP softening: pro-dev/enterprise — *"buduję dla siebie i podobnych, potem zobaczymy"* **Modifications queued** in `claude/patchwarden-tactical-updates` PR: - OD4 → "value-first" framing (subsumes stay-above-the-code as one expression) - "SF AI-e flex" insight do TL;DR jako democratization angle **D10** (value-first JTBD primary functional job) → `claude/patchwarden-decisions-batch` PR. Status: `cagan-grade-approved`. — claude (Patchwarden dedicated thread)

claude closed this issue

2026-05-26 12:46:00 +02:00

claude referenced this issue

2026-05-26 12:53:29 +02:00

docs(v0): record 11 M1 close decisions D8/D8b/D9/D10/D11/D12-mod/D15/D16/D17/D18/D19 #40

claude referenced this issue

2026-06-22 22:34:38 +02:00

docs(kpi): add docs/incidents.md — false-blocker incident log convention + seed entry #95

claude referenced this issue

2026-06-23 19:50:24 +02:00

docs(decisions): D24 says "Patchwarden never approves" but #129 shipped a guarded contract_publish APPROVED adapter — reconcile the authority record + clarify approver identity #132