01Foundations Days 1–10

You'll know what a product manager is for and how to judge value through the customer's eyes.

Team session guide →

  1. 01Build the right thing. Build it right. Build it on time.Three hats. One product.
  2. 02Know your stage. Pick your moves.Every product ages.
  3. 03Ship less. Change more.Shipped isn’t success.
  4. 04Nail the job. Features follow.People hire products to get a job done.
  5. 05Problem first. Solution second.Fall in love with the problem.
  6. 06Raise the gain. Cut the cost.Value lives in the customer’s eyes.
  7. 07Win the buyer. Keep the user.Who pays isn’t always who uses.
  8. 08Discover together. Decide together.Three minds. One decision.
  9. 09Reps beat talent.Product sense is a muscle.
  10. 10Protect the time that finds the truth.A PM’s week, honestly.

02Discovery Days 11–20

You'll talk to customers every week and test the riskiest idea before you build.

Team session guide →

  1. 11Talk to customers every week.Discovery is a habit, not a phase.
  2. 12Facts beat compliments.Ask about the past, not the future.
  3. 13Ask for a commitment.Look for real commitment.
  4. 14Test the scary one first.Find the assumption that could kill it.
  5. 15Outcome → need → idea → test.Connect every idea to an outcome.
  6. 16Prove the pain, then pitch the cure.Is the pain real?
  7. 17Cheapest test that answers the question.Fake it to learn it.
  8. 18Segment by need, not by label.Know who you’re building for.
  9. 19Map reality, not the brochure.See the whole journey.
  10. 20Decide. Ship. Keep learning.“Enough” is a decision.

03Strategy Days 21–30

You'll have a one-page strategy that says where you play, how you win, and what you won't do.

Team session guide →

  1. 21Strategy is choosing.Where, why and how to win.
  2. 22For everyone means for no one.Own a place in their mind.
  3. 23Know them. Be you.Study rivals. Don’t copy them.
  4. 24Features get copied. Moats compound.What stops them catching you?
  5. 25Build what makes you different.Build, buy or partner?
  6. 26Earn the right to be a platform.Products solve problems. Platforms let others do it.
  7. 27“Not now” is a strategy too.Every yes is a no to something else.
  8. 28If the team can’t say it, it isn’t real.It fits on a page, or it won’t fit in heads.
  9. 29Few goals. Checked weekly.Objectives inspire. Key results prove.
  10. 30Hold the vision. Flex the path.Plans break. Strategy adapts.

04Prioritisation Days 31–40

You'll prioritise with a method people trust and a roadmap without fake dates.

Team session guide →

  1. 31Score to debate, not to decide.A score is a conversation, not a verdict.
  2. 32Ask what waiting costs, not just what it’s worth.What does waiting cost?
  3. 33Fix the basics. Then delight.Not every feature delights.
  4. 34Commit to the near. Flex on the far.Roadmaps without fake dates.
  5. 35Promise outcomes. Discover features.Roadmap the problems, not the features.
  6. 36Respect the idea. Test the idea.When the boss has an idea.
  7. 37Debt has interest. Pay it on purpose.Tech debt is a product problem.
  8. 38Important + unhappy = opportunity.Find needs that are important and underserved.
  9. 39Same plan. Different story.One roadmap, many audiences.
  10. 40Kill it clearly. Keep the lessons.Stopping is a skill.

05Metrics Days 41–50

You'll track a handful of metrics that show whether customers are winning.

Team session guide →

  1. 41One star. Many paths to it.One number that means customers win.
  2. 42Manage inputs. Watch outputs.You can’t move outputs directly.
  3. 43Fix the leak before adding water.Find where people leak.
  4. 44Averages hide. Cohorts reveal.Group users by when they joined.
  5. 45Get them to value, fast.Find the aha moment.
  6. 46If it can’t change a decision, it’s decoration.Numbers that feel good and change nothing.
  7. 47Move the needle. Mind the fences.Win without breaking something.
  8. 48Lagging tells you. Leading warns you.See it coming.
  9. 49Measure the goal, not the game.When a measure becomes a target…
  10. 50Every metric should ladder up.Connect every metric to the top.

06Evidence Days 51–60

You'll turn opinions into small tests and know when the evidence is good enough.

Team session guide →

  1. 51If it can’t fail, it isn’t a test.Turn opinions into testable bets.
  2. 52Randomise. Wait. Then decide.Let customers vote with their behaviour.
  3. 53Small samples tell tall tales.Is it real, or just noise?
  4. 54Right question, right method.Not every question needs an experiment.
  5. 55Write the exit before the entrance.Decide when to stop before you start.
  6. 56Fix the system, not the symptom.Keep asking why.
  7. 57Listen for the silence.Who’s missing from your data?
  8. 58Spot with numbers. Understand with people.Numbers say what. People say why.
  9. 59Test interest with honesty.Measure demand before you build.
  10. 60Trust, but verify the pipeline.Question the data before you trust it.

07Engineering Days 61–70

You'll work with engineers on specs, slices and releases that land safely.

Team session guide →

  1. 61Short, living, and clear on why.Write specs people actually read.
  2. 62If you can’t test it, it isn’t done.Define done before you build.
  3. 63Thin slices. Real value. Often.Ship the thinnest slice that works.
  4. 64Ask about the one-way doors.Some tech decisions are product decisions.
  5. 65Quality is a requirement.How well, not just what.
  6. 66Deploy anytime. Release on purpose.Release to some before you release to all.
  7. 67Calm comms. Real follow-through.When it breaks, what’s your job?
  8. 68Treat your API like a product.Developers are users too.
  9. 69Launch with them, not at them.The front line knows first.
  10. 70Same team. Same outcomes.Speak both languages.

08Launch Days 71–80

You'll launch, price and follow up so people actually use what you built.

Team session guide →

  1. 71Plan the launch while you build.Building it is half the job.
  2. 72Match the noise to the news.Not every launch needs a parade.
  3. 73Value first. Features later.The first week decides everything.
  4. 74Lower the wall they have to climb.Better isn’t enough.
  5. 75Price reflects value delivered.Price the value, not the cost.
  6. 76Three clear choices beat twelve clever ones.Good plans make choosing easy.
  7. 77Announced isn’t adopted.They know about it. Why don’t they use it?
  8. 78Lead with what’s better for them.Write about them, not you.
  9. 79Enable early. Listen always.Sales can’t sell what they don’t understand.
  10. 80Launch is the start of learning.Did it work?

09Stakeholders Days 81–90

You'll lead without the title and get decisions made.

Team session guide →

  1. 81Earn trust before you need it.Lead without the title.
  2. 82Map them before they surprise you.Know who matters, and how.
  3. 83One decider. Everyone knows who.Who decides?
  4. 84Make the trade-off visible. Let them choose.No, but here’s what we can do.
  5. 85Partners early. Not gatekeepers late.Bring Legal in early.
  6. 86No decision? No meeting.Every meeting needs a decision.
  7. 87Clear writing is clear thinking.Write it down to think it through.
  8. 88Separate the people from the problem.Conflict is about goals, not people.
  9. 89No surprises. Bring options.Make your boss’s job easier.
  10. 90Your product is also your people.Grow people, not just products.

10AI features Days 91–100

You'll know where AI features help, where they fail, and how to launch them in stages.

Team session guide →

  1. 91Right tool. Not the shiny tool.Use AI where uncertainty is OK.
  2. 92Design the failure before it happens.AI will be wrong. Plan for it.
  3. 93Assist the work. Don’t hijack it.Good AI feels like a helpful colleague.
  4. 94No evals, no confidence.Test AI like you test code.
  5. 95Cheap per call can be expensive per result.Measure cost per success, not per call.
  6. 96Match autonomy to risk.Decide where humans stay in charge.
  7. 97Transparency builds trust.Tell people when it’s AI.
  8. 98Prove value before you build the engine.Own the difference. Rent the rest.
  9. 99Impressive demos aren’t evidence.Launch AI in stages.
  10. 100Ideas are cheap. Judgement isn’t.The craft changes. The job doesn’t.