The best time to write a case study is before you need one.

■ Memory loses the useful parts first

Most people wait until they are job hunting, pitching, or rebuilding their site before they write about their work. By then, the easy parts remain and the important parts are blurry.

You remember the final screen. You remember the project name. You may remember the team. But you forget the tense meeting, the rejected option, the constraint that shaped the solution, the comment that changed your mind, and the small sign that the work actually helped.

Those details are often the proof.

■ Capture decisions, not diary entries

You do not need to journal every day. You need to catch the moments that will matter later.

When something changes direction, write it down. When a constraint forces a tradeoff, write it down. When a user quote clarifies the problem, write it down. When a teammate adopts your artifact, write it down. When the work ships, stalls, or gets cut, write down why.

The goal is not to create a perfect record. The goal is to keep the evidence from evaporating.

■ Use a five-line capture

After a meaningful project moment, write five lines.

Context: what was happening? Decision: what choice was made? Constraint: what made it hard? Evidence: what supported the choice? Consequence: what changed afterward?

That is enough. You can turn five honest lines into a case study later. You cannot recover them from memory six months after the work has moved on.

■ Save raw proof safely

Keep safe screenshots, notes, sanitized diagrams, meeting summaries, test findings, pull quotes, before and after structures, and links to shipped work where appropriate.

If the work is confidential, capture a private note about what can be shown later and what must stay hidden. Future you will not remember the boundary clearly unless present you records it.

■ Make the habit small enough to survive

A huge documentation habit will die. A two-minute capture can survive.

At the end of a project, a sprint, a launch, or a major decision, add one note. Not for the company. Not for the performance review. For your future ability to explain your work truthfully.

A strong portfolio is not built in one heroic rewrite. It is built by saving the evidence while it is still warm.