Show your process and collaboration
A brief look at your process can help readers: how you identified a need, which options you considered, and what you ultimately chose. You don’t need to share your entire working archive.
If you received feedback, explain how it influenced the next version. Choose one specific example of something you changed and why. This shows collaboration without empty claims.
For team projects, name other contributors as agreed and explain what you were responsible for. Don’t publish internal comments or work chats without the participants’ consent.
If the process didn’t go to plan, you can explain what you learned and how you changed your approach. Your portfolio doesn’t have to pretend every project went smoothly.
For sensitive projects, you can show your general approach without identifying details. Before publishing, check that the sample doesn’t reveal a client, partner, or internal information.
Ask a collaborator to review how their contribution is described. Accurate credit builds trust and can prevent misunderstandings after publication.
For each project, you could describe one instance when you discussed your approach with someone or changed a design in response to feedback. Explain what you heard, what you changed, and why. Don’t share names or conversations without consent. A specific example shows collaboration more naturally than a list of personal qualities.