product-delivery

Name: product-delivery
Author: yannickYamo

9installs4forks

How to install product-delivery?

yannickyamo/skills/product-delivery

$npx -y skills add yannickYamo/skills --skill product-delivery

Installs into the current project.

Summary

Ship, measure, and learn effectively. Use when planning staged rollouts, setting up metrics hierarchies, running bet retrospectives, or executing GTM launches. Part of the Modern Product Operating Model collection.

Files · 1

View on GitHub

SKILL.md

1	# Product Delivery System
2
3	> "The goal isn't shipping. The goal is learning whether your bet was right."
4
5	This skill covers the Delivery System — how we ship, measure, and learn. It runs discovery and delivery in parallel (dual-track), ships with staged rollouts, measures with a clear hierarchy, reflects through retrospectives, and executes GTM with precision.
6
7	Part of: [Modern Product Operating Model](https://github.com/yannickYamo/skills) — a collection of composable product skills.
8
9	Related skills: `product-strategy`, `product-discovery`, `product-architecture`, `ai-native-product`, `product-leadership`
10
11	---
12
13	## When to Use This Skill
14
15	Use this skill when:
16	- Planning how to roll out a new feature or product
17	- Designing a metrics hierarchy for a bet or product
18	- Running bet retrospectives after shipping
19	- Executing GTM launches
20	- Setting up dual-track development rhythm
21	- Deciding when to scale, iterate, or kill a bet
22
23	Cadence: Continuous \| Owner: Product Trio + GTM Team
24
25	---
26
27	## The Problem This Solves
28
29	Most teams either:
30	1. Ship features and never measure impact
31	2. Measure vanity metrics that don't connect to outcomes
32	3. Do "big bang" launches that create risk
33	4. Never officially conclude bets—zombies live forever
34	5. Treat GTM as marketing's problem after PM ships
35
36	The Delivery System ensures shipping is the beginning of learning, not the end.
37
38	---
39
40	## Philosophy
41
42	### Core Beliefs
43
44	1. Discovery and delivery run in parallel — Don't pause discovery to deliver
45	2. Staged rollouts are the default — Ship to 10% before 100%
46	3. Metrics exist in hierarchy — Leading → Core → Lagging
47	4. Every bet gets a retrospective — Explicit scale/iterate/kill decision
48	5. GTM is a product responsibility — PM owns adoption, not just availability
49
50	### What This Framework Rejects
51
52	- Ship and forget (no measurement)
53	- Big bang launches (maximum risk)
54	- Vanity metrics (activity without outcome)
55	- Zombie bets (never concluded, never killed)
56	- Throwing features over the wall to marketing
57
58	---
59
60	## Framework Components
61
62	### 1. Dual-Track Development
63
64	The Core Idea:
65	Discovery and delivery happen simultaneously. While one bet is being built, the next bet is being shaped.
66
67	```
68	Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
69	─────────────────────────────────────────────────────────
70	[ Discover Bet B ][ Shape Bet B ][ Discover Bet C ]
71	[ Build Bet A ][ Build Bet B ]
72	[ Ship A ] [ Ship B ]
73	```
74
75	How It Works:
76
77	\| Track \| Activities \| Who \|
78	\|-------\|------------\|-----\|
79	\| Discovery Track \| Interviews, OST updates, solution exploration, assumption tests \| Full trio (PM heavy) \|
80	\| Delivery Track \| Building, testing, shipping, measuring \| Full trio (Eng heavy) \|
81
82	Time Allocation (Example):
83
84	\| Role \| Discovery \| Delivery \|
85	\|------\|-----------\|----------\|
86	\| PM \| 60% \| 40% \|
87	\| Designer \| 50% \| 50% \|
88	\| Tech Lead \| 30% \| 70% \|
89
90	Coordination Points:
91	- Weekly sync: What's in flight on each track
92	- Handoff moment: When a bet moves from "shaped" to "building"
93	- Learning moment: When shipped bet results inform discovery
94
95	0→1 Mode: Tracks may blur. Everyone does everything. Speed > separation.
96
97	Scaling Mode: Clear separation. Dedicated discovery time. Research ops support.
98
99	---
100
101	### 2. Staged Rollout
102
103	The Core Idea:
104	Never ship to everyone at once. Start small, learn, expand.
105
106	Default Rollout Stages:
107
108	\| Stage \| Audience \| Duration \| Purpose \|
109	\|-------\|----------\|----------\|---------\|
110	\| Stage 0: Internal \| Team dogfooding \| 1-3 days \| Find obvious bugs \|
111	\| Stage 1: Alpha \| 5-10 friendly customers \| 1 week \| Qualitative feedback \|
112	\| Stage 2: Beta \| 10% of users \| 1-2 weeks \| Quantitative signal \|
113	\| Stage 3: GA \| 100% of users \| Ongoing \| Full measurement \|
114
115	Progression Criteria:
116
117	\| From \| To \| Criteria \|
118	\|------\|----\|----------\|
119	\| Internal → Alpha \| Ready for external \| No P0 bugs, core flow works \|
120	\| Alpha → Beta \| Validated experience \| Positive qualitative feedback, no major usability issues \|
121	\| Beta → GA \| Metrics acceptable \| Leading metrics trending right, no guardrail breaches \|
122
123	Feature Flags:
124	- Every significant feature ships behind a flag
125	- Flags enable instant rollback
126	- Flags enable % rollout control
127	- Flags are cleaned up after GA (don't accumulate debt)
128
129	Rollback Triggers:
130	- Guardrail metric breached
131	- Error rate > threshold
132	- Customer-reported critical issue
133	- Leading metrics trending wrong
134
135	0→1 Mode: Stages can be compressed. Alpha might be 3 customers for 2 days.
136
137	Scaling Mode: Formal stage gates. Release manage

People who liked this also viewed

6 picks

Type

product-delivery

9installs4forks

View on GitHub

How to install product-delivery?

yannickyamo/skills/product-delivery

$npx -y skills add yannickYamo/skills --skill product-delivery

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Product Delivery System
2
3	> "The goal isn't shipping. The goal is learning whether your bet was right."
4
5	This skill covers the Delivery System — how we ship, measure, and learn. It runs discovery and delivery in parallel (dual-track), ships with staged rollouts, measures with a clear hierarchy, reflects through retrospectives, and executes GTM with precision.
6
7	Part of: [Modern Product Operating Model](https://github.com/yannickYamo/skills) — a collection of composable product skills.
8
9	Related skills: `product-strategy`, `product-discovery`, `product-architecture`, `ai-native-product`, `product-leadership`
10
11	---
12
13	## When to Use This Skill
14
15	Use this skill when:
16	- Planning how to roll out a new feature or product
17	- Designing a metrics hierarchy for a bet or product
18	- Running bet retrospectives after shipping
19	- Executing GTM launches
20	- Setting up dual-track development rhythm
21	- Deciding when to scale, iterate, or kill a bet
22
23	Cadence: Continuous \| Owner: Product Trio + GTM Team
24
25	---
26
27	## The Problem This Solves
28
29	Most teams either:
30	1. Ship features and never measure impact
31	2. Measure vanity metrics that don't connect to outcomes
32	3. Do "big bang" launches that create risk
33	4. Never officially conclude bets—zombies live forever
34	5. Treat GTM as marketing's problem after PM ships
35
36	The Delivery System ensures shipping is the beginning of learning, not the end.
37
38	---
39
40	## Philosophy
41
42	### Core Beliefs
43
44	1. Discovery and delivery run in parallel — Don't pause discovery to deliver
45	2. Staged rollouts are the default — Ship to 10% before 100%
46	3. Metrics exist in hierarchy — Leading → Core → Lagging
47	4. Every bet gets a retrospective — Explicit scale/iterate/kill decision
48	5. GTM is a product responsibility — PM owns adoption, not just availability
49
50	### What This Framework Rejects
51
52	- Ship and forget (no measurement)
53	- Big bang launches (maximum risk)
54	- Vanity metrics (activity without outcome)
55	- Zombie bets (never concluded, never killed)
56	- Throwing features over the wall to marketing
57
58	---
59
60	## Framework Components
61
62	### 1. Dual-Track Development
63
64	The Core Idea:
65	Discovery and delivery happen simultaneously. While one bet is being built, the next bet is being shaped.
66
67	```
68	Week 1 Week 2 Week 3 Week 4 Week 5 Week 6
69	─────────────────────────────────────────────────────────
70	[ Discover Bet B ][ Shape Bet B ][ Discover Bet C ]
71	[ Build Bet A ][ Build Bet B ]
72	[ Ship A ] [ Ship B ]
73	```
74
75	How It Works:
76
77	\| Track \| Activities \| Who \|
78	\|-------\|------------\|-----\|
79	\| Discovery Track \| Interviews, OST updates, solution exploration, assumption tests \| Full trio (PM heavy) \|
80	\| Delivery Track \| Building, testing, shipping, measuring \| Full trio (Eng heavy) \|
81
82	Time Allocation (Example):
83
84	\| Role \| Discovery \| Delivery \|
85	\|------\|-----------\|----------\|
86	\| PM \| 60% \| 40% \|
87	\| Designer \| 50% \| 50% \|
88	\| Tech Lead \| 30% \| 70% \|
89
90	Coordination Points:
91	- Weekly sync: What's in flight on each track
92	- Handoff moment: When a bet moves from "shaped" to "building"
93	- Learning moment: When shipped bet results inform discovery
94
95	0→1 Mode: Tracks may blur. Everyone does everything. Speed > separation.
96
97	Scaling Mode: Clear separation. Dedicated discovery time. Research ops support.
98
99	---
100
101	### 2. Staged Rollout
102
103	The Core Idea:
104	Never ship to everyone at once. Start small, learn, expand.
105
106	Default Rollout Stages:
107
108	\| Stage \| Audience \| Duration \| Purpose \|
109	\|-------\|----------\|----------\|---------\|
110	\| Stage 0: Internal \| Team dogfooding \| 1-3 days \| Find obvious bugs \|
111	\| Stage 1: Alpha \| 5-10 friendly customers \| 1 week \| Qualitative feedback \|
112	\| Stage 2: Beta \| 10% of users \| 1-2 weeks \| Quantitative signal \|
113	\| Stage 3: GA \| 100% of users \| Ongoing \| Full measurement \|
114
115	Progression Criteria:
116
117	\| From \| To \| Criteria \|
118	\|------\|----\|----------\|
119	\| Internal → Alpha \| Ready for external \| No P0 bugs, core flow works \|
120	\| Alpha → Beta \| Validated experience \| Positive qualitative feedback, no major usability issues \|
121	\| Beta → GA \| Metrics acceptable \| Leading metrics trending right, no guardrail breaches \|
122
123	Feature Flags:
124	- Every significant feature ships behind a flag
125	- Flags enable instant rollback
126	- Flags enable % rollout control
127	- Flags are cleaned up after GA (don't accumulate debt)
128
129	Rollback Triggers:
130	- Guardrail metric breached
131	- Error rate > threshold
132	- Customer-reported critical issue
133	- Leading metrics trending wrong
134
135	0→1 Mode: Stages can be compressed. Alpha might be 3 customers for 2 days.
136
137	Scaling Mode: Formal stage gates. Release manage

People who liked this also viewed

6 picks

Type