Name the outcome you delivered, not the work you did
This case study is a draft. The structure is in place; the writing is not. Nothing on this page should be read as a claim yet.
Problem
What kept breaking, and why the fix never held. Documentation case studies live or die on this section: without a regression to point at, the docs read as housekeeping.
Process
What you wrote, who you wrote it for, and how it got into the build. Say where the docs sit - in the repo, in the design file, in the ticket template - because that is what decides whether anyone reads them.
Outcome
What stopped regressing. If you have a before and after count of issues, this is where it goes.
-
fill in
-
fill in
-
fill in