Start with the shared project, then define your role
Team projects belong in a portfolio. They can show how you solve problems with other people, respond to feedback and carry work through to delivery. The challenge is giving a reader enough context to understand the project without implying that you completed every part yourself.
Open with a short description of the goal, the audience and the final deliverable. Then state your role in plain language. For example: “Our four-person student team designed a prototype for a campus event guide. I planned the user flows and created the interactive prototype.” If roles changed during the project, say so. A clear opening helps a reader interpret everything that follows.
Replace broad claims with specific actions
Words such as “led,” “built” and “managed” can mean different things to different readers. Explain the work behind them. Instead of “I led the redesign,” you might write: “I organized the initial planning session, drafted the page structure and coordinated feedback on two design options.” This gives a more useful picture of your contribution without diminishing anyone else’s.
Choose a few decisions that reveal your skills. A freelancer collaborating with a developer might explain how they prepared interface states and clarified handoff questions. A writer on a small team might describe how they turned a loose brief into an agreed content outline. You do not need a record of every task. Focus on actions that affected the direction, quality or completion of the work.
Show evidence and explain its limits
Support your description with artifacts you are permitted to share: an annotated sketch, a planning board excerpt, a draft alongside the final version, or a screenshot of the part you designed. Captions can connect each artifact to your work. For example: “I mapped these three onboarding paths before the team selected one for the prototype.” If an artifact represents several people’s work, identify your part rather than labeling the whole item as yours.
Not every useful contribution is visible in the final deliverable. You may have resolved an unclear requirement, documented a decision or helped the team prepare files for handoff. Describe what you did, why it mattered and what happened next. If client work is confidential or a school project has sharing restrictions, use an approved, simplified account instead of exposing private files or presenting reconstructed material as an original artifact.
Credit collaboration without losing your voice
Use “we” for shared decisions and outcomes, and “I” for work you personally completed. A sentence such as “We agreed to simplify the navigation; I revised the menu labels and tested them in the prototype” makes both levels clear. Name collaborators and their roles when you have permission, or credit them by function when names are unnecessary.
Be especially careful around decisions that emerged through discussion. You can say you proposed an idea, facilitated a review or incorporated feedback without claiming sole ownership of the result. Collaboration is part of the story: explaining how another person’s input changed your work shows judgment and adaptability.
Close with the outcome and what you learned
Describe the result at the level you can support. Was the project delivered, presented, published or left as a prototype? Did the team receive feedback that led to a revision? Avoid assigning a business impact to your contribution unless you have evidence and can explain the connection. A student project can end with a presentation; a freelance project can end with an approved handoff. Neither needs an invented success metric to be worthwhile.
Finish with one concrete reflection. For instance: “I learned to document interaction states earlier so the developer had fewer questions at handoff.” This tells a reader how you would approach similar work next time. Before publishing, ask a teammate to check whether your account fairly represents the division of work. A portfolio entry is strongest when its scope, evidence and credit all tell the same story.
