Program guide

How your Sensei works with you

What a Sensei does in the program: the weekly checkpoint, the questions they ask, how epic reviews run, and how to prepare so you learn the most.

  • Foundation
  • 30 min
  • 6 min read

After this lesson you can

  • Describe what happens at a weekly checkpoint, step by step.
  • Prepare for a checkpoint in 30 minutes.
  • Explain why the Sensei asks questions instead of giving answers.
  • Know what to do when you disagree with feedback.

Read these first

A Sensei is an experienced builder who coaches you through the program. Your Sensei is not a teacher who lectures and not a boss who approves. A Sensei is a person who looks at your work, asks hard questions, and helps you see what you missed. The word is also used for people who host live builds and review roadmaps in the community. You can read about that role on the Sensei page.

Why it matters

You can read about whole-product planning for a month and still not be able to defend a roadmap. Defending is a spoken skill. You learn it when someone asks “why this epic before that one?” and you have to answer without notes. The Sensei is that someone.

Key ideas

  • A checkpoint is short. About 30 minutes each week.
  • Honest and improving beats perfect. You are not graded for polish.
  • Questions, not answers. A Sensei asks so that you find the gap yourself.
  • Your work is in git. The Sensei reads your history before they meet you.
  • You explain without notes. If you cannot explain an epic aloud, it is not yet your epic.

What happens at a checkpoint (a suggested shape)

The program fixes only two things: the checkpoint is about 30 minutes, and you show your work while the Sensei asks questions. The split below is a shape that works well. Your Sensei may adjust it.

Step What happens Time
1. Walk You show this week’s output 10 min
2. Questions The Sensei asks about choices, evidence and risks 10 min
3. Gaps You both write down what is missing 5 min
4. Next You agree the one thing to fix before next week 5 min

The one-page map (Week 1), a persona and a journey (Week 2), the epic review (Week 3) and the roadmap defence (Week 4) are the four main checkpoints. Each has its own page.

The questions a Sensei asks

Topic A typical question What it checks
Evidence “Where did you learn that?” A persona or claim has a real source
Scope “What is out of scope, and why?” The epic has a line you chose
Order “Why does this epic come before that one?” The order is reasoned
Measure “How will you know it worked?” There is one number
Dependency “What does this wait for?” Cross-epic and cross-product links are known
Honesty “Did an agent help here? What did you check?” AI use is disclosed

How an epic review runs

  1. You read the epic aloud in your own words.
  2. The Sensei asks the questions above.
  3. You answer without notes. It is fine to say “I do not know yet. I will find out.”
  4. The Sensei writes the gaps as comments on the epic in git, so the record stays with the work.
  5. You change the epic, and the merge request shows what changed.

Steps to prepare (30 minutes)

  1. Open your work in git. Read the last week of history.
  2. Write the one-sentence goal of this week and check your output meets it.
  3. Choose the weakest part of your work and say what you are unsure about.
  4. Rehearse the walk aloud once, with a timer.
  5. Write your weekly note, including the line on AI use.

What a Sensei does not do

  • Write your epics or your roadmap.
  • Fill in your workbooks.
  • Decide your product’s order.
  • Approve work you cannot explain.

If a Sensei writes your epic, you lose the learning and they lose the chance to coach.

If you disagree

Disagreement is welcome. Say what evidence you have. If you still disagree, write both views in the epic comments and decide yourself. You own the roadmap. The Sensei owns the quality of the questions.

Working with AI agents

  • May: help you rehearse by asking you the questions above and listening to your answers. Summarise your own notes.
  • May not: answer the questions for you or write the epic you will defend.
  • A safe brief: “Ask me five hard questions about my epic, one at a time. Wait for my answer. Do not tell me the right answer.”

Common mistakes

  1. Arriving with a perfect-looking document and no understanding.
  2. Reading from notes. Practise without them.
  3. Hiding AI use. It is a bigger problem than the use.
  4. Taking questions as attacks. They are the point.
  5. Fixing everything at once. Fix the one thing you agreed.

Practice

  1. Pick one of your epics. Answer the six questions in the table aloud, with a timer.
  2. Ask a friend to ask you “why this order?” and answer in 30 seconds.
  3. Write your list of “I do not know yet” items.

Checklist

  • I read my git history before the checkpoint.
  • I can explain my output without notes.
  • I wrote down what I am unsure about.
  • My weekly note says how I used AI.

The 2030 Product Development Manager lens

  • You decide: what you bring, what you change and what you defend.
  • You delegate to agents: rehearsal questions, spelling checks, a summary of your own notes.
  • A sample brief: “Read my weekly notes and list the three things I wrote most about. Do not judge them.”
  • You verify by: answering the checkpoint questions without any agent in the room.
  • Disciplines involved: communication, product thinking and coaching.
  • On the agent ladder: a Sensei is part of how you govern: another person who checks what you and your agents did.

Further learning

Next: your work in git. Read Present and defend the roadmap to practise.

Go deeper

Further learning

Free or low-cost material from other publishers. We opened every link; check the cost label before you start.

Back to the library