Case studies 101: The locksmith

This is my number one tip for producing a technical case study: the locksmith.
Picture the scene
You get home from work, you can't find your keys.
It's dark. Your bag's scraping grooves into your shoulders.
The key's not in that pocket.
You try the other. Not there.
Rummage in your bag. Not there either.
You're locked out.
Enter the locksmith
So you phone Lily the Locksmith. She’s easy to find online, seems happy to help.
She’s there in no time.
But she frowns when she sees your lock. It’s complicated, quite secure, with a rare type of key, and tricky to work with.
However, she reassures you it’s going to be fine, and it is! 👏
You get into your house, you pay Lily (a bit more than you wanted to) and all is well!
The case study
Now, imagine that you're writing a case study for Lily's website, based on the example we've just looked at.
Where do you start? With the customer problem, always. Call it the business problem if you prefer.
What’s the business problem here?
A complicated lock?
No.
A rare type of key?
No
The problem was: you were locked out of your house!
Why is this a useful way to think about case studies?
Because it’s a reminder that the business problem always comes first. For the customer, being locked out of their house is profoundly annoying and uncomfortable.
From the customer's perspective, the inconvenience of that experience trumps all other factors in this story.
This principle translates to all businesses.
It’s tempting to make the more ego-massaging bit of the story - the complexity of the job - into the headline problem.
But it isn’t.
If you’re struggling to find the initial business problem, try asking why:
Why did you deliver a data platform?
Because the client wanted a single view of the truth.
Why?
Because reporting was too slow and they were missing out on new business.
Aha!
You’ve found your business problem.
Need help?
If you need help with technical case studies, connect with me.


