A case study can have immaculate mockups and still leave a basic question unanswered: what was the interface meant to help someone do? The strongest write-ups give readers a path from a user need to a screen-level decision. That path matters more than adding another glossy device frame.
Name the task before the layout
Begin with a concrete task, such as comparing subscription plans or finding a recent order. For a concept e-commerce flow, explain what a shopper needs to know before committing: product details, delivery information, or the next step in checkout. This gives the reader a reason to care about the screens that follow.
If the project has no research or real users behind it, say that plainly. You can still describe the assumptions that shaped the concept, but do not present them as research findings. A well-marked assumption is more useful than a confident claim with no evidence.
Connect choices to moments
Choose a few decisions that changed the user’s path. You might explain why filters sit beside a product grid, why a form asks for one piece of information at a time, or how an error message tells someone what to do next. Show the relevant screen beside the explanation so the reasoning is easy to verify.
Include the trade-off when there is one. A compact mobile header may save vertical space but leave fewer controls visible; a persistent navigation bar may improve access while taking up room. Naming that tension shows design judgment without pretending there is one perfect answer.
Separate intent from outcome
Use outcome language only when an outcome was actually observed or measured. If a project is conceptual, describe the intended behavior instead: the layout is designed to make plan differences easier to scan, for example. Do not turn an intention into a claim that conversion or usability improved.
A concise case study can follow a simple arc: task, important decisions, and what you would validate next. For concept work, that last step might be testing the flow with users or checking keyboard navigation. Readers leave with a clearer picture of both the interface and the designer’s process.