Week 6 of 6
Proof portfolio
Present a coherent body of evidence an evaluator can inspect in five minutes.
You can present five weeks of work so an evaluator can judge your decisions in five minutes.
Watch and practise first
A public portfolio page, a 4–6 minute walkthrough, and your final report as a PDF.
- Notion or Carrd for the page — recommended
- Framer, a slide-based site, or a coded page
- Report as a PDF in Google Drive
These three links go on your public registry page, so a stranger will open them. Check all three in incognito, and check the page on your phone.
Everything the work must contain
- 01A short professional introduction, and the role or next step you are aiming at.
- 02Five case studies, one per week from 1 to 5.
- 03For each: the problem and user, your constraints, the decisions you made, the inspectable output, and what changed or failed.
- 04Direct links to every underlying public artifact.
- 05A capability summary grounded in that evidence.
- 06Contact details you are comfortable publishing.
- 07Do not claim employment, client work, partnerships, results, or metrics that did not happen.
Open every link in a private or incognito window before you submit. If it asks you to sign in or to request access, your reviewer will see exactly the same thing.
3 separate links
- Portfolio page URL
The public page holding all five case studies.
- Walkthrough URL
4–6 minutes explaining the work, not reading the page aloud.
- Final report PDF URL
Completed using the final-report handbook.
- Anything your reviewer should know
Optional.
What a reviewer checks
- 01Every artifact is accessible and explained with problem, process, and outcome context.
- 02The portfolio shows concrete decisions, revisions, and evidence of improved capability.
- 03The walkthrough and final report are complete, specific, and consistent with the published work.
How to build it
Week 6 - Publish a Proof-of-Work Portfolio
Capability
Present a coherent body of work so an evaluator can understand the problem, inspect the evidence, and judge your decisions in five minutes. This is not a gallery of screenshots and tool logos.
Curate the Story
Use the domain thread that connected your six weeks. For each artifact, explain:
- the problem and intended user;
- your role and constraints;
- the process and important decisions;
- the inspectable output;
- what failed, changed, or improved;
- what the work demonstrates.
Do not claim employment, client work, partnerships, results, or metrics that did not occur.
Build the Portfolio
Create a public page with:
- a concise professional introduction;
- your domain focus and intended role or next step;
- five project case studies from Weeks 1-5;
- direct links to the underlying public artifacts;
- a short capability summary grounded in evidence;
- contact details you are comfortable publishing.
Notion, Carrd, Framer, a slide-based site, or a coded page is acceptable. Accessibility and clarity matter more than animation.
Walkthrough and Final Report
Record a 4-6 minute walkthrough that explains the work rather than reading the page aloud. Complete the final report using the handbook in content/reference/final-report-handbook.md. Include specific changes in your judgment, process, or capability, supported by project examples.
Read your portfolio page on a phone before you hand it in. Most of the people you send it to will open it there first.
Reading is free and always will be. Applying gets you the review — a person who reads what you built against the rubric above.
Apply to the program