Frame the decision correctly
A screenshot shows your aesthetic preferences but doesn't explain how you solved the problem. A case study should make the initial conditions, the goal, your role, and the decisions made visible. Do not publish names, documents, or private data if you do not have the client's permission to share.
What should be considered during implementation?
Describe the work in a few meaningful sections: why a change was needed, which options were evaluated, and why this specific solution was chosen. Explain decisions that aren't immediately visible, such as mobile behavior or form flows. In projects involving multiple teams, do not claim sole credit for the entire outcome.
Verification and next steps
Do not fabricate sales growth percentages if you lack measurements. Distinguish between verifiable observations made before and after the launch. Presenting conceptual work with a clear label—such as "BCL Concepts"—is an honest way to showcase your design skills without creating the impression that it is a real client project.
Your quick checklist
- Obtain permission to share.
- Explain your own role.
- Do not produce unmeasured results.


