Why Descriptions Matter
Work rarely explains itself. A viewer looking at an image, a video or a page of writing does not know what the brief was, what constraints you faced or what you personally contributed. A short description fills that gap. It turns a nice-looking object into evidence of how you think and solve problems.
Good descriptions are also an act of respect for the viewer’s time. They answer the questions people tend to have: What is this? Who was it for? What did you do? How did it turn out? If you answer those clearly, you make the work easier to understand and easier to trust.
A Simple Structure
Most project descriptions can follow the same outline, adapted to the size of the project.
The goal. Start with the problem or purpose in one or two sentences. Who was the project for, and what was it meant to do? “A short animated explainer for a neighborhood garden group, intended to help new volunteers understand the weekly schedule” is far more useful than “an animation project.”
Your role. State what you personally did. If you worked alone, say so. If you worked in a team, name your contribution precisely: writing, illustration, layout, editing, sound. Give credit to the others involved, as covered under source credit practices. Overstating your role is easy to spot and damages trust.
The process. Briefly describe how you approached the work: key decisions, tools or methods in general terms, and any difficulties. This is where you show judgment. You might mention that you tested two layouts, changed direction after feedback or simplified the design to keep it readable.
The outcome. Explain what happened. Finish with what was delivered, how it was used or what you learned. If you do not have measurable results, do not invent them; an honest “this was a personal project and has not been published” is better than a made-up claim.
For small pieces, two or three sentences covering these points is plenty. For major projects, a few short paragraphs may be appropriate.
Use Plain Language
Descriptions work best in clear, direct prose. Avoid vague, inflated phrases such as “innovative,” “cutting-edge” or “passionate about storytelling.” They take up space without telling the viewer anything. Replace them with concrete facts: what you made, for whom, and what choices you made.
Use plain language principles: short sentences, common words and a logical order. Write as if explaining the project to an intelligent friend who works in a different field. Technical terms are fine when your viewers will understand them; otherwise, explain them in a few words.
Keep a consistent tone across all descriptions. A consistent format, such as the same headings or order of information, lets viewers compare projects easily and find what they need. Applying a simple style guide to your own descriptions keeps spelling, tense and terminology tidy.
Be Honest About Context
Say what kind of project it was: client work, a class assignment, a personal experiment, a volunteer project or a collaborative piece. All are legitimate. Pretending that a practice exercise was a professional commission gains nothing and creates risk if someone asks follow-up questions.
Be careful with numbers. Only include figures you can support and that are relevant, and describe them accurately. If you say a project “increased engagement,” be ready to explain exactly what was measured and over what period. When in doubt, leave it out or describe the result qualitatively. Reading content metrics wisely applies to your own claims as much as to anyone else’s.
Respect Rights and Privacy
Before publishing a description, check that it does not reveal confidential information about a client, employer or collaborator. Obtain permission where needed, and avoid naming or showing identifiable people without their consent. If your project used materials from other sources, such as stock media or open-licensed images, mention it and follow any attribution requirements. These are general principles rather than legal advice; consult official guidance for your situation.
Keep It Readable
Place the description close to the work so the viewer does not have to hunt for it. Use short paragraphs, and consider a brief summary line at the top, so a person scanning the page can understand the project in a few seconds. A reader can then choose whether to continue into the detail.
Offer images with accessible descriptions, and avoid placing important information only inside an image. Proofread carefully. A typo in a description stands out, and the extra care you show signals care in the work itself.
Revise Over Time
Descriptions should be updated as your thinking changes. Read each one aloud and ask: Does it say something specific? Is anything exaggerated? Could someone unfamiliar with the project follow it? Ask a friend to read your descriptions and tell you what they understood. If they come away with the wrong idea, revise.
Re-read your older descriptions every so often. As you gain experience, you may see better ways of explaining decisions or notice claims that now seem too large. Honest, modest and specific wording tends to age better than hype, and it lets the work speak for itself.