Programs

Sales · Facilitator-led

Customer Discovery for Product Teams

Five rooms from the first customer interview to the build decision, run weekly, measured over time.

A five-week program for product managers validating a roadmap item before it is built, assigned by a head of product or product lead, built on Renatus. Two simulation rooms, one research room and two guided documents · Five weeks, one room a week, real customer conversations between them · Unlimited attempts · Ongoing thereafter.

5 weeks · 5 rooms · Total time 2 hours 25 min

Sign up to continue
Who it's for
Product managers with a roadmap item to validate, founders at idea or pre-product stage, and product marketers who own positioning.
Cadence
5 weeks
Format
Facilitator-led
Program sessions
5

Who it's for

Product managers with a roadmap item to validate, founders at idea or pre-product stage, and product marketers who own positioning.

Output

  • A scored report after each simulation, with the moment that earned each score, one recommended focus and a trajectory across every attempt
  • A sourced report on the market's customers with a confidence rating on every section, and an evidence log of real interviews written up as evidence and opinion
  • A problem statement with a recommended path and next steps, and a positioning statement with a verdict, both built from what the product manager states and ready for an engineering lead
  • Scored against published frameworks: Behaviour-Grounded Discovery, Underlying-Job Framing, the Minto Pyramid Principle and Aristotelian rhetoric; the documents are built on 5 Whys, the Weighted Decision Matrix, Five-Step Positioning and Category Choice; the report rests on named, cited sources

Program contents

  1. Interview discipline — Customer Discovery
  2. Market evidence — Customer Intelligence
  3. Problem definition — Problem Analysis
  4. Positioning the offer — Product Positioning
  5. Making the build case — Presentation Under Pressure

How the program works

A five-week program for product managers validating a roadmap item before it is built, assigned by a head of product or product lead, built on Renatus. Two simulation rooms, one research room and two guided documents · Five weeks, one room a week, real customer conversations between them · Unlimited attempts · Ongoing thereafter.

The rooms

Why this program exists

A product manager with a roadmap item in mind asks a customer whether they would use it, and the customer, being polite, says yes. The feature is built on that yes, ships to silence, and a quarter of engineering is gone. This program prepares product managers to find out what is true before the build starts. Ren plays the customer in a discovery interview built for the product's stage, researches who the market's real customers are from named sources, guides the product manager through a problem statement and a positioning built from their own evidence, and then plays the senior audience that tests the build case.

What you'll achieve

  1. A scored report after each simulation with the moment that earned each score, and unlimited attempts, each a new customer or a new audience, charted against every attempt before it
  2. A sourced report on the market's customers with a confidence rating on every section, and an evidence log of real interviews written up as evidence and opinion
  3. A problem statement with a recommended path and next steps, and a positioning statement with a verdict on whether it holds, both ready for an engineering lead

At a glance

Who it's for
Product managers with a roadmap item they want to validate, founders at idea or pre-product stage, and product marketers who own positioning. It is assigned by a head of product, a product lead or a founder running the team. Customer Discovery calibrates to the product's stage, so one cohort can hold a first-year product manager and a founder. It assumes participants can get three customers or prospects on a call across two weeks, and nothing else.
Cadence
5 weeks
1
Interview discipline · Customer Discovery · Read Question Openness and Hypothesis Discipline; read the three rewritten questions
2
Market evidence · Customer Intelligence · Read the gap and what drives the decision, with their confidence ratings; read the three hypotheses and the first write-up
3
Problem definition · Problem Analysis · Read Why It's Happening and Recommended Path against the original two sentences; read the evidence log
4
Positioning the offer · Product Positioning · Read Best-Fit Segment and the verdict; read the one-page case; read the Ren summary across four rooms
5
Making the build case · Presentation Under Pressure · Read Evidence Handling and Question Response; make the build decision; read the team report; set the ongoing plan

Session by session

1

Week 1: Interview discipline

Find out how much the product manager leads a customer today, and rewrite the questions that do it before the first real conversation.

2

Week 2: Market evidence

Get a sourced picture of the market's customers before interviewing three of them, and turn it into hypotheses a real conversation can test.

3

Week 3: Problem definition

Name the real problem, what it is costing and why it is happening, from the evidence log and the report, and choose a path.

4

Week 4: Positioning the offer

Land a positioning that names the alternatives, the segment and the category to claim, and get a verdict on whether it holds.

5

Week 5: Making the build case

Put the build case to a senior audience that challenges it, hold the argument on evidence, and take the question the product manager did not prepare for

Five rooms from the first customer interview to the build decision, run weekly, measured over time.

Sign up to continue
Meet Ren
Your AI strategist
We use essential cookies to keep you logged in and protect your session. Our only optional cookies remember your language preference — we don't track you or collect unnecessary data. Cookie Policy · Privacy Policy

Cookie Settings

Choose which cookies you'd like to allow. Essential cookies cannot be disabled as they are required for the platform to function.

Essential Cookies Always Active
Login sessions, security tokens, and consent preferences. Required for the platform to work.
Functional Cookies
Language preferences, display settings, and last accessed report. Disabling may affect personalisation.
Analytics Cookies
Aggregated, anonymised usage data to help improve the platform. Never used to identify you personally.