Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

product-delivery

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.

YannickMaurice · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

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

About this skill


name: product-delivery description: 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. author: YannickMaurice version: 1.0.0 tags: product-management, delivery, metrics, gtm, launch

Product Delivery System

"The goal isn't shipping. The goal is learning whether your bet was right."

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.

Part of: Modern Product Operating Model — a collection of composable product skills.

Related skills: product-strategy, product-discovery, product-architecture, ai-native-product, product-leadership


When to Use This Skill

Use this skill when:

  • Planning how to roll out a new feature or product
  • Designing a metrics hierarchy for a bet or product
  • Running bet retrospectives after shipping
  • Executing GTM launches
  • Setting up dual-track development rhythm
  • Deciding when to scale, iterate, or kill a bet

Cadence: Continuous | Owner: Product Trio + GTM Team


The Problem This Solves

Most teams either:

  1. Ship features and never measure impact
  2. Measure vanity metrics that don't connect to outcomes
  3. Do "big bang" launches that create risk
  4. Never officially conclude bets—zombies live forever
  5. Treat GTM as marketing's problem after PM ships

The Delivery System ensures shipping is the beginning of learning, not the end.


Philosophy

Core Beliefs

  1. Discovery and delivery run in parallel — Don't pause discovery to deliver
  2. Staged rollouts are the default — Ship to 10% before 100%
  3. Metrics exist in hierarchy — Leading → Core → Lagging
  4. Every bet gets a retrospective — Explicit scale/iterate/kill decision
  5. GTM is a product responsibility — PM owns adoption, not just availability

What This Framework Rejects

  • Ship and forget (no measurement)
  • Big bang launches (maximum risk)
  • Vanity metrics (activity without outcome)
  • Zombie bets (never concluded, never killed)
  • Throwing features over the wall to marketing

Framework Components

1. Dual-Track Development

The Core Idea: Discovery and delivery happen simultaneously. While one bet is being built, the next bet is being shaped.

Week 1    Week 2    Week 3    Week 4    Week 5    Week 6
─────────────────────────────────────────────────────────
[  Discover Bet B  ][  Shape Bet B  ][  Discover Bet C  ]
         [    Build Bet A    ][   Build Bet B   ]
                    [ Ship A ]        [ Ship B ]

How It Works:

TrackActivitiesWho
Discovery TrackInterviews, OST updates, solution exploration, assumption testsFull trio (PM heavy)
Delivery TrackBuilding, testing, shipping, measuringFull trio (Eng heavy)

Time Allocation (Example):

RoleDiscoveryDelivery
PM60%40%
Designer50%50%
Tech Lead30%70%

Coordination Points:

  • Weekly sync: What's in flight on each track
  • Handoff moment: When a bet moves from "shaped" to "building"
  • Learning moment: When shipped bet results inform discovery

0→1 Mode: Tracks may blur. Everyone does everything. Speed > separation.

Scaling Mode: Clear separation. Dedicated discovery time. Research ops support.


2. Staged Rollout

The Core Idea: Never ship to everyone at once. Start small, learn, expand.

Default Rollout Stages:

StageAudienceDurationPurpose
Stage 0: InternalTeam dogfooding1-3 daysFind obvious bugs
Stage 1: Alpha5-10 friendly customers1 weekQualitative feedback
Stage 2: Beta10% of users1-2 weeksQuantitative signal
Stage 3: GA100% of usersOngoingFull measurement

Progression Criteria:

FromToCriteria
Internal → AlphaReady for externalNo P0 bugs, core flow works
Alpha → BetaValidated experiencePositive qualitative feedback, no major usability issues
Beta → GAMetrics acceptableLeading metrics trending right, no guardrail breaches

Feature Flags:

  • Every significant feature ships behind a flag
  • Flags enable instant rollback
  • Flags enable % rollout control
  • Flags are cleaned up after GA (don't accumulate debt)

Rollback Triggers:

  • Guardrail metric breached
  • Error rate > threshold
  • Customer-reported critical issue
  • Leading metrics trending wrong

0→1 Mode: Stages can be compressed. Alpha might be 3 customers for 2 days.

Scaling Mode: Formal stage gates. Release management. Beta programs.


3. Metrics Hierarchy

The Three-Tier Model:

┌─────────────────────────────────────────────────────┐
│                 LAGGING METRICS                     │
│         (Revenue, Retention, NPS)                   │
│         Move slowly, hard to attribute              │
├─────────────────────────────────────────────────────┤
│                  CORE METRICS                       │
│       (Activation, Engagement, Conversion)          │
│       The outcomes your bets target                 │
├─────────────────────────────────────────────────────┤
│                LEADING METRICS                      │
│         (Feature adoption, Task completion)         │
│         Move fast, early signal                     │
└─────────────────────────────────────────────────────┘

Metric Types:

TypeDefinitionExampleUse For
LeadingEarly signal, fast-moving, directly influenced by featureFeat
Read the complete source ↗