Session Kit: Module 25: Portfolio, Feedback, and Final Project
Everything needed to run Module 25 as a taught session: prep, timing, materials, misconceptions, rubric.
Generated from modules/module25.md. Edit the module page, not this file.
At a glance
| Duration | 5-6 hours |
| Capability target | Submit a capstone portfolio that proves technical capability, communicates decision quality, and demonstrates iterative growth through feedback. Operationally: every artifact carries a caption naming the competency it proves and what a reviewer can check, the portfolio distinguishes what you did from what you were given, and at least one artifact shows a version that was wrong alongside the correction and the reason. |
| Learners leave with | Portfolio map (artifact -> competency) |
Before you walk in
- You can state the capability target in one sentence without reading it.
- You have one worked example you will narrate, including where you are unsure.
- Data access works — accounts, viewer, notebook — verified today, not last week.
- The rubric is visible to learners before they start, not after.
- You have decided what “uncertain” earns, and you will say so out loud.
Learners should arrive having covered:
- Completed artifacts from at least three technical modules
- One writing or presentation artifact
Materials
Run of show
| Time | Segment | Your note |
|---|---|---|
| 00:00-08:00 | Portfolio quality exemplar | |
| 08:00-20:00 | Competency-claim mapping | |
| 20:00-34:00 | Artifact curation and caption drafting | |
| 34:00-46:00 | Feedback exchange round | |
| 46:00-56:00 | Revision planning | |
| 56:00-60:00 | Final submission checklist |
The activity
Scenario: You are preparing your final portfolio for a competitive research opportunity. Assume the reviewer spends two minutes on the first pass and opens exactly one artifact.
- Select 6-10 artifacts and map each to one competency claim, cutting duplicates.
- Write four-line evidence captions and reflection notes, with line three naming something verifiable.
- Receive peer review against rubric criteria, having stated a decision, a criterion, and a deadline for each artifact.
- Produce a revision plan with priorities and deadlines, ordered by effect on what the portfolio proves.
What learners hand in
- Portfolio map (artifact -> competency)
- Reflection set
- Peer feedback log
- Final revision plan
- Permission and provenance check across all artifacts
Misconceptions to target
These are the errors this session exists to prevent. Surface them in the debrief rather than pre-empting them in the lecture — a misconception a learner has voiced is far easier to correct than one they are holding silently.
- They may believe: More artifacts make a stronger portfolio.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
- They may believe: Describing what you enjoyed about a project counts as reflection.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
- They may believe: A final version is stronger evidence when the earlier drafts are removed.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
- They may believe: A good artifact speaks for itself and needs no caption.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
- They may believe: Asking a narrow question wastes the reviewer’s expertise.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
- They may believe: Work you did yourself is automatically yours to publish.
- Surface it by asking: “What would have to be true for that to hold? What would change your mind?”
Naming the norm
Every session is a chance to make one piece of the hidden curriculum explicit. Pick a moment where you would normally just do the professional thing, and say out loud why you are doing it — then ask whether anyone was taught that.
For this session, the candidate is whichever norm the activity most depends on: stating an assumption in the same sentence as the claim, recording the version a number came from, or saying “uncertain” and having it count as a real answer. See the hidden curriculum for the collected set and why naming them is a fairness intervention rather than etiquette.
Assessment
- Minimum pass: portfolio claims are evidence-backed; reflection identifies at least one meaningful revision loop; feedback is incorporated with clear changes; contributions in group work are stated explicitly.
- Strong performance: demonstrates cross-module synthesis and transfer, highlights uncertainty and correction with technical maturity, communicates a future growth plan with concrete milestones, and includes at least one artifact whose earlier wrong version is shown alongside the correction and its reason.
- Common failure to flag: artifact dump with weak competency mapping, reflection limited to narrative without analytical depth, and minimal response to peer critique. Also flag portfolios where every caption line three is missing, since that is the difference between a folder and evidence.
Grade the reasoning, not the answer. A correct call with no evidence chain should not outscore a well-reasoned incorrect one — and saying so publicly changes behaviour within one session.
Exit prompt
Choose one artifact and write its four lines: one competency claim it supports, what you did versus what you were given, one thing a reviewer can verify and where, and one limitation with the revision you would make next.
If this session goes wrong
- Nobody talks in the debrief. You asked “any questions?” Ask instead: “Which cue would you drop first if the data got worse?”
- Everyone finishes early. They are pattern-matching, not judging. Give an ambiguous case where the answer is “uncertain” and see what happens.
- Nobody finishes. The scaffolding came off too fast. Work the next case together rather than pressing on.
- A learner is silently lost. The most likely cause is unstated vocabulary. Point them at the dictionary and check back.