How to Show Your Contribution in a Team Project

The real problem

Team projects are common, but they often create unclear case studies. If everything is written as “we,” hiring teams may not understand what you personally shaped. The goal is not to take credit for everything. The goal is to make your contribution legible.

This is where many portfolio pages lose strength. They show activity, but not reasoning. They show artifacts, but not the thinking behind them. For a hiring team, mentor, or reviewer, that missing reasoning can make even good work feel hard to evaluate.

What to focus on instead

A stronger case study does not need to sound dramatic. It needs to make the work easier to understand. The reader should be able to see what problem you worked on, what your role was, what choices you made, why those choices made sense, and what changed because of the work.

Key principles:

• Separate team context from your personal responsibility.
• Name the decisions or artifacts you directly shaped.
• Mention collaboration without hiding behind it.
• Explain where you influenced the direction.
• Use “I led,” “I contributed,” or “I supported” accurately.

A practical structure

Use this simple flow:

1. Context: What was the product, team, or situation?
2. Problem: What needed to change or become clearer?
3. Role: What were you responsible for?
4. Decision: What important choices did you make?
5. Reasoning: What evidence, constraint, or trade-off shaped those choices?
6. Outcome: What changed, what was learned, or what became easier?

This structure keeps the case study readable without turning it into a shallow template. The goal is not to fill sections. The goal is to help someone understand your thinking.

Example framing

Weak framing:

I redesigned the flow and improved the user experience.

Stronger framing:

I focused on the onboarding step where users were unsure what to do next. Instead of adding more explanation, I simplified the sequence and made the next action more visible. This helped the team align around a clearer first-use experience.

The stronger version does not depend on exaggerated claims. It explains the situation, the decision, and the reasoning.

What to avoid

• Do not turn the case study into a gallery of screens.
• Do not hide your role behind vague “we” language.
• Do not overclaim impact if you do not have evidence.
• Do not describe every step equally; highlight the decisions that mattered.
• Do not copy another designer’s case study structure without adapting it to your own project.

Final thought

A strong UX case study is not just proof that you worked on a product. It is proof that you can think through a problem and explain your choices clearly.

More case study guides

• what hiring managers look for in UX case studies
• writing a UX case study without metrics
• preparing your UX case study for a design interview