A portfolio should help potential clients assess how a provider thinks. An attractive cover image draws attention, but does not explain why a particular solution was chosen. A strong case study answers specific questions: what needed to change, what constraints existed, which part of the work the team completed and what can be verified afterwards. Credibility comes from precision, not the number of impressive adjectives.
Distinguish work from a concept
A training example, an independent experiment and a completed client project can all be valuable, but they have different statuses. A concept should clearly be labelled as such. If a website is unpublished or the client has not permitted disclosure, the presentation must reflect that. Do not fill gaps with invented brands, testimonials or metrics. A small, honest portfolio provides stronger grounds for trust than a large gallery of uncertain provenance.
Explain the task in the client’s language
Instead of “creating a premium digital experience,” explain the actual problem. Perhaps visitors struggled to distinguish services, or the team spent too much time answering the same preliminary questions. If this is a hypothetical example, label it accordingly. Then describe constraints: existing content, the technical platform, integrations and language requirements. These details allow readers to assess the solution in context rather than comparing pictures disconnected from their purpose.
Show a few key decisions
There is no need to document every iteration. Choose two or three decisions that most affect how the website is used. These might include reorganising services, shortening an enquiry form or changing how a catalogue is presented. Explain the reasoning and trade-off behind each decision. If a large visual section was made more compact, show what information could then appear earlier. Readers see the logic, not only the final style.
Clarify authorship and permissions
In a collaborative project, distinguish your role from other contributors’ work. Strategy, design, writing, development and photography may belong to different people. Before publication, check permission to use the client’s name, images, logos and internal process details. Remove personal data and operational information from screenshots. Without permission, an anonymised explanation of the solution is preferable to exposing confidential information for the sake of a fuller case study.
Separate results from assumptions
Publish business metrics only when there is a source, a measurement period and a clear basis for comparison. More enquiries after launch do not prove that design alone caused the increase: advertising, pricing or seasonal demand may have changed simultaneously. Without data, describe verified outputs instead: the implemented structure, available user journeys and completed page templates. These are meaningful outcomes that do not require artificial success percentages.
Finish with an appropriate next step: invite a discussion about a similar challenge rather than promising to reproduce someone else’s result. A good portfolio demonstrates how you make decisions and helps potential clients decide whether that approach suits them.