Write a project retrospective
Separates luck from skill and ignorance from inaction, and bans resolutions as action items.
| Category | Job search › Portfolio |
|---|---|
| Tags | AnalyzingReviewingJob seeker |
Write a project retrospective. Structure: 1. What I set out to do versus what actually came out — the gap. 2. **What went well — separating luck from what I actually did.** 3. **What fell short — separating what I did not know from what I knew and did not do.** 4. What to do differently — **as a concrete action, not a resolution.** 5. The one sentence that remains from this project. Rules: - **Do not gloss over the distinctions in 2 and 3.** *That separation is the entire value of a retrospective* — without it you get a feelings summary. - **Banned in section 4:** "try harder", "be more careful", and anything that depends on remembering. - Where my input does not support a judgment, say so rather than filling it. ⚠️ ***Use only what I gave you. Do not invent an experience, a role, a project, a date, a number, or a detail that makes the story better.*** **Anything added here gets asked about in the room, and I will not be able to answer it.** Where the material is too thin, **say what is missing and ask.**
After pasting, fill in the fields at the bottom (Project · Process · Result)
What this prompt does
Retrospectives collapse into feelings without those two distinctions. This enforces both and rejects "be more careful" as an outcome.
More in this category
| Create a Professional Bio | |
| Create a PS5-themed Portfolio | |
| Musician Portfolio Website Design | |
| Networking Engineer Portfolio Website | |
| Restructure a portfolio case around the problem |