P7 · Program

Product Management

The science and art of the product lifecycle. Consult, validate market fit and scale — with people who have run product for global platforms rather than described it.

X = Feature backlog —[Δ Discovery · Δ Definition · Δ Experience · Δ Scale]→ Y = Product-market fit

The hook

A roadmap built from requests is a queue. A roadmap built from driver logic is a strategy.

Intent · Move product from opinion-led delivery to evidence-led value: discovery that finds real pain, definition that frames it, and scale mechanics that hold past the first thousand users.

3

phases: discover, create, scale

1000→1M

the scale problem

10X

value match target

The movement

X · today

A roadmap driven by requests and opinion

Y · destination

A roadmap driven by driver logic and evidence

Product work has three distinct problems and most teams collapse them into one. Discovery finds the pain. Creation frames and validates a solution. Scale makes the same value reach a thousand times more people.

Each phase has its own methods, its own evidence and its own failure mode.

Value discovery

  • Discover pain and match 10X value
  • Research and ethnography per segment
  • Jobs, pains and gains mapping
  • Design thinking and problem reframing
  • Product-market fit grid positioning

Value creation

  • Define, validate and execute the offer
  • UX and human-centred design
  • Gamification and adoption loops
  • Backlog, roadmap and release sequencing
  • Pricing and packaging tied to value delivered

Value scale

  • Got your first 1,000 — now scale to a million
  • Onboarding, activation and time-to-value
  • Retention, expansion and churn diagnosis
  • Platform extensibility and ecosystem
  • Support and reliability as product features

Why it matters · impact

Feature volume is not value

Most shipped features are never adopted. Every one of them adds permanent maintenance cost and interface complexity.

Activation decides retention

Retention curves are set in the first session, not in month three. Time-to-value is the most under-instrumented number in early product.

Scale breaks different things

What gets you to a thousand users — founder-led onboarding, manual support, bespoke configuration — is exactly what blocks a million.

How it runs · deep dive

01

Discover · Find the pain worth solving

Structured discovery replaces the request backlog as the source of roadmap truth.

  • Jobs, pains and gains mapped per segment with frequency and intensity
  • Opportunity solution tree from the outcome down to bets
  • Behavioural data joined to qualitative evidence, not quoted separately
  • Explicit anti-roadmap: what we are choosing not to build, and why
02

Define · Frame and validate before build

Each bet carries a value hypothesis and a falsifiable test.

  • Value hypothesis with the metric it should move and by how much
  • Prototype, concierge or fake-door validation before engineering spend
  • Design system and accessibility baseline so speed does not cost quality
  • AI features held to the same evidence bar: measurable task success, not novelty
03

Scale · Make value reach everyone

The systems that turn a working product into a compounding one.

  • Onboarding and activation redesign against time-to-value
  • Retention and churn diagnosis by cohort, segment and behaviour
  • Self-serve and expansion loops replacing manual touch
  • Platform extensibility, API surface and integration strategy
  • Reliability, support and performance treated as product features

Measured on · KPIs

Time-to-value

Signup to first meaningful outcome

< 1 session

Activation rate

New users reaching the activation event in 7 days

> 40%

Feature adoption

Target segment using a shipped feature within 30 days

> 30%

Day-30 retention

Cohort still active after 30 days

+10 pts

Discovery hit rate

Validated bets that move their stated metric

> 50%

Roadmap traceability

Roadmap items linked to a value driver and metric

100%

What you walk away with

  • →Opportunity solution tree with evidence attached
  • →Validated value hypotheses and test results
  • →Activation and retention instrumentation
  • →Roadmap traceable to drivers, plus the anti-roadmap

Other programs