Your case study gets written during the project, not six months later

Every call in the project leaves a trace of the decisions and their reason. This kit captures them as you go in a log, then turns that into the first draft of your case study.

Why

The most valuable part of a case study is the why, and it is the first thing you forget. Six months after shipping, you open your portfolio with the final mockups and a vague memory of the debates. You know what you did, no longer why you did it, nor what you dropped. The case study turns into a gallery of screens. The reasons did exist: they were spoken, in meetings, one by one. This kit catches them as they pass, in a decision log, so the case study gets written from what was settled, with the reason from the time. A recruiter does not read your screens, they read your trade-offs.

When

You build this kit at the start of a project you will want to show, when decisions get made in meetings. Audience: product designers first, PMs and POs who defend their choices. ✅ You know it's your kit when Your last portfolio took weeks to rebuild from memory You no longer know why a design direction was kept Your case studies show the result, never the reasoning ❌ Not for this kit The…

Tools included

View on Coeurdar