Looking for a good dev-focused case study format?
People tell you to follow a classic Hero > Problem > Solution > Results.
They tell you to show numbers, talk value, etc.
And it is true. Great format.
But packaging this for devs is hard.
For example, putting numbers in there, and framing it in a "save 28min every week" is a recipe for losing trust with that dev reader.
That is if you can even get those numbers from your customers.
I like how @LaunchDarkly solves it.
- Change that customer saw (no numbers needed)
- Additional description of the use case (this seems to be optional for them)
- Before and After boxes with bullets (no numbers needed)
- Clear customer logo
Case study body:
- About: one paragraph about the company and use case
- Challenge: why they started looking for a solution
- Solution: why they chose their product
- Results: what they got from it
- They kept it short and focused on the team leader imho
They keep the content down to earth and devy but still frame it in a value-focused way.
I like that that they speak in the currency that devs care about.
Before: "Took 2-3 weeks to ship"
After: "Can ship experiments every day"
The cool thing is you could actually use this hero section format and then have a more technical user story below. By doing that you could speak to the why and how.
That depends on your target reader for this page of course.
Anyhow, I do like this format and I am planning to take it for a spin.