State the project’s team context, then identify the work and decisions you personally performed. Credit collaborators and distinguish your contribution from collective outcomes. Use artifacts and approval boundaries to explain responsibility, and avoid implying that a team result can be attributed entirely to one person.
Map responsibilities before writing the story
Create a private role map for the project. List the people or functions involved and the principal responsibilities each held. You may have drafted interview questions while a colleague recruited participants and another led the sessions. Include the people who approved important decisions, not only those who created visible artifacts. This map gives you a factual basis for describing the work without accidentally presenting a multi-person process as an individual achievement.
Identify your role at the relevant stage rather than relying only on a job title. Responsibilities may have changed during the engagement. Separate proposing, deciding, implementing and evaluating when different people performed those activities. If records are incomplete, use a narrower description you can support rather than filling gaps with assumptions. Confirm attribution with appropriate collaborators when needed, while respecting permission boundaries around names, internal roles and material that is not available for public disclosure.
Write at two levels deliberately
Use a short project-level account to explain the shared objective and context. Then move into first-person wording for your specific contribution. “The team delivered a revised help centre” and “I drafted the information structure and edited the agreed article set” communicate different levels of responsibility. Keep that distinction consistent in headings, captions and summaries. A broad “we” can obscure your contribution, while an unqualified “I” can assign you work performed by others.
Choose evidence that shows the boundary. An annotated outline may demonstrate your structural proposal, while the final site includes design and development work by colleagues. Explain which parts of a screenshot are relevant to your contribution instead of allowing the whole image to imply sole authorship. Credit reused systems and client-supplied content as appropriate. A polished final artifact often combines many kinds of work, so its appearance alone cannot establish who made each decision.
Handle results without individual over-attribution
If a team measured a result and you may report it, describe the measurement and collective context accurately. Do not claim that your contribution alone caused the change when other work and external conditions also mattered. When no measurement exists, describe observable milestones such as a handover or approved draft, keeping those separate from impact. A case study can show useful professional judgment without assigning causal credit that the evidence cannot support.
Read the final page as someone unfamiliar with the project. Could they identify what you did, who else contributed and what authority you held? Would a collaborator recognize the account? Check the project card and short biography too, because compressed summaries often lose attribution included on the full page. Update the record if a factual error is discovered, but do not broaden your role retrospectively as the team context becomes less visible over time.
Fictional example: an outline within a larger release
A fictional content designer, Nia, contributes to an invented help-centre release. Product specialists provide approved technical material, a designer develops the page components and engineers implement the site. Nia proposes the article hierarchy and edits a defined collection of pages. Her case study begins with the team objective, then shows a labelled outline and a sample edit as evidence of her own work.
The final screenshot credits the other functions and explains that Nia did not design or build the interface. The example concludes with the agreed content handover rather than claiming a support-volume reduction that was never measured. Readers can examine a meaningful contribution without being invited to attribute the whole fictional release to a single professional.
A checklist for your next step
- Map responsibilities and decision owners.
- Separate team context from personal work.
- Use evidence of your own contribution.
- Credit surrounding work.
- Check attribution in short summaries.
Common questions
Can I use “we” in a case study?
Yes, for shared work. Follow it with enough detail for readers to identify your own responsibilities and decisions.
Should I avoid mentioning team outcomes?
No. Describe them accurately and explain the limits of attributing them to your individual contribution.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.