SynthMock
A strong cover creates a clear first impression. The case study still needs to explain the problem, the decisions and what was learned. Keep the mockup's role specific so visual polish supports the work rather than replacing it.
Try it in SynthMock
Start with a Duo scene.
Use a reusable template as your starting point, then apply the choices in this article.
A paid plan is required to use templates and export.
Use the cover as an invitation
Choose a Duo source state that represents the central task in the project. A beautiful but unrelated dashboard can mislead a reader about the work that follows. If the project is a concept, identify it as one near the beginning instead of letting a realistic device imply a released product.
The cover can establish visual direction, interface character and the intended device context. It cannot show that research happened, that users completed tasks successfully, or that a redesign improved a business outcome. Those claims require their own real evidence in the case study.
Separate presentation from proof
A useful portfolio structure gives different artifacts different responsibilities. The following is an editorial outline, not a fixed case-study template.
| Artifact | What it can communicate | What belongs elsewhere |
|---|---|---|
| Duo hero | The product's visual character and selected task | Research findings and outcome claims |
| Interface detail | A specific design decision | Evidence of behavior without a prototype or test |
| Process material | The actual alternatives and reasoning | Invented polish-only narratives |
| Verified results | What was measured or observed | Unsupported causal conclusions |
Keep the narrative proportional to the work
If you explored a layout independently, explain the constraints you chose and the tradeoffs you noticed. That can be worthwhile work without a fictional client, invented participants or fabricated metrics. A clearly labeled concept is more credible than a polished story that suggests evidence it does not contain.
For the cover itself, favor the view that makes the selected interface understandable. Use a closer companion image when small controls matter, and keep the lighting consistent with the rest of the presentation. End the visual review by checking whether the hero, title and opening paragraph all describe the same project. The reader should know what they are about to learn before the device's reflections become the main topic.
Final pass
Before you call it finished
- Label concept work clearly.
- Make the cover represent the case study's central task.
- Support research and outcome claims with actual evidence.
Make the next version yours.
Explore Duo templates ↗