Describe each project in context
Add a short description to each work sample: what the goal was, who it was for, what constraints applied, and what your role was. Context helps readers understand the result without having to guess.
Name your specific contribution: research, design, writing, coordination, or implementation. If a team created the result, say who was involved and what you were responsible for.
Explain one decision you made and why. You can briefly mention an alternative you considered, too. This shows your professional judgement, not just the finished work.
If the project wasn’t launched or you don’t know its impact, say so. Don’t make up numbers or results. Describe what you completed, what you learned, and what you’d change next time.
Use plain language and short paragraphs. If readers need an explanation of a technical term, provide one. Your portfolio should present your work, not test your audience’s attention span.
Avoid unnecessary jargon when describing a project. Imagine a reader outside your field and explain why the decision mattered. A little context is more helpful than a long list of tools.
Try writing the description in four short sentences first: the brief, your role, an important decision, and the result. Then remove repetition and replace vague words with specific actions. If you can’t verify the result, name the completed deliverable or what you learned. That keeps the description accurate without marketing promises.