What problem were you solving?Required Who needed this work? What was happening before the project? Why did it matter?
Who worked on it? Team size, collaborators, supervisor, and how the work was divided. Avoid private contact details.
What did YOU personally own?Required Separate your decisions and deliverables from the team’s. Be specific enough that we can write in your voice without claiming someone else’s work.
Who used, evaluated, or benefited from it? Describe the real audience and what success meant to them.
What did success need to look like? Functional requirements, quality targets, user needs, deadlines, or acceptance criteria.
What made the problem difficult? Budget, materials, time, safety, access, software, people, missing data, or organizational rules. Include the constraints that changed your decisions.
What did you start with? Existing design, research, inherited files, a blank page, or an unfinished attempt. What was already done before you joined?
Walk us through the work in order.Required Discovery → first attempt → feedback or testing → changes → final deliverable. Rough bullets are enough.
What other approaches did you consider? Compare at least two if possible. What were their advantages, disadvantages, and reasons for rejection?
What was your most important decision? What evidence informed it? What trade-off did you accept? What would have happened if you chose differently?
What tools and methods did you actually use? Name the tool, then explain what you did with it. For example: used CAD configurations to compare three arm sections.
What failed, surprised you, or needed rework? What did you notice, how did you diagnose it, and what changed afterward?
How did you know whether it worked? Test setup, review method, research participants, acceptance check, or inspection process. If no validation happened, say so.
What changed, and what is the evidence?Required Give the baseline, final value, units, sample size/time period, and source for any metric. Distinguish measured, calculated, estimated, and not yet known.
What exists at the end? Prototype, report, deployed system, drawing pack, campaign, process guide, or another artifact. What can a reader actually inspect?
What should we NOT claim? Unverified results, work you did not own, a project not yet built, confidential outcomes, or unresolved problems.
What did you learn—and what would you do next? A specific lesson and how you would apply it, not just “teamwork” or “communication.”
What media supports this story? List each filename/link, what it shows, where it belongs in the story, who made it, and a short caption. Mention before/after pairs and video timestamps.
May we publish this project and the media you explicitly name for it? Only select yes if you have permission. We will still check for visibly sensitive information.
Discuss permission or redactions first Yes, I am authorized to publish the named material No, keep this project private Where should this project appear? You can feature your strongest work. Every authorized project remains available.
Recommend based on my target and evidence Feature this project Include in the complete project directory What can we publish from this project?Required Who owns the work? What permission exists? List redactions, restricted names, faces, dimensions, or files that must stay private.
