Deliver it
Lesson 24 of 24, level 01Index
Friday. The founder is in the room. You have one page and eight minutes.
Delivery is the last mile, and most of it is rehearsal
Lead with the ask
- Decision: Say the ask first
- Evidence: Show the strongest proof
- Action: Owner and next step
You are not performing. You are trying to get a decision made with the least friction possible, which means saying the ask first and then shutting up.
Record yourself once. It is uncomfortable and it is the highest return five minutes in this level.
Your final memo should let another person inspect how you reached a decision. It is the connecting thread across the work, not a scrapbook of every exercise you completed.
Use your chosen course project throughout. The additional examples below are fictional practice cases; transfer the method to your own evidence.
Build the evidence spine
Select the artifacts that support the recommendation: a source-linked observation, a flow, a measurement definition, and a bounded estimate. Show the chain between them. Remove impressive material that does not affect the decision. Clearly label synthetic data and untested hypotheses so the reader can judge the work on its actual merits.
Make the commitment bounded
State the user problem, smallest proposed change, scope exclusions, owner, and review plan. Include the strongest alternative and a reason to reverse the recommendation. A capstone can demonstrate good judgment without claiming a shipped result. Explain whether you researched, prototyped, tested, or launched, using those words accurately.
Invite a useful review
Ask the reviewer to identify an unsupported claim, a missing state, and a weak measurement assumption. Use that feedback to revise the memo, then keep a short change log. Reflect on one way AI accelerated your process and one output you rejected after checking it. Your judgment is part of the artifact.
Turn practice into a case
- Evidence: What you found
- Decision: What you recommend
- Artifact: What makes it inspectable
- Reflection: What changed your mind?
Doing it with AI, and where it breaks
Adversarial review: have a model attack your memo as a skeptical founder would, then fix what actually lands.
Discard the objections your document already answers. Only the new ones are the meeting.
Your AI workbench
Start with your own notes or clearly labelled practice data. Remove private details before sharing. Replace the placeholders, run the prompt in your chosen AI tool, and keep the output beside its source.
Review my capstone and linked artifact excerpts [paste] against this rubric: clear decision, traceable evidence, honest uncertainty, complete scope, measurable outcome, and credible review plan. Cite the exact passage behind each finding. Flag invented results and unsupported claims. Suggest the three highest-value revisions; do not rewrite the work as if you performed it.
Before you use the output
- Every result is observed or labelled hypothetical
- Artifacts support the recommendation
- AI assistance and human verification are disclosed
Stuck? Try this next
Ask AI to trace one claim all the way back to its source. If the chain breaks, weaken the claim or collect evidence before improving the prose.
Keep a brief AI log: input used, useful output, what you checked, and what you rejected. The decision remains yours.
Build it
A recorded five minute walkthrough of your memo.
From a product problem to a defensible decision
Publish a 700–1,000 word project case study. Link your Friday memo, show the strongest evidence, compare the option you chose with one you rejected, and explain what feedback changed your mind. State what you actually researched or built and what has not been tested.
Include: Your final memo plus two supporting artifacts and a short revision log.
- Write in your own voice for someone facing the same product problem.
- Use AI to critique the structure and find unsupported claims. Verify every source, number, and quotation yourself. Add a short note describing how you used AI.
- Remove private customer, company, and participant information. Label practice scenarios and synthetic data clearly.
- Publish on Medium, Substack, or a relevant Reddit community that permits project write-ups and links. Follow its posting rules; share a useful account of the work.
Include this plain attribution with a clickable link:
I developed this project while learning product management at pmcademy.com.
Checkpoint
If you did the build, these take two minutes. If you cannot answer one of them, that is the part to go back to.
Moving on marks this lesson complete. Finish the build first, it is the part that counts.