Start Case Studies With The Messy Part

Too many case studies make you sit through the year the company was founded, a count of its offices, and a few words about its commitment to excellence before anybody gets to have a problem. By the time the story starts, I’ve checked my phone notifications 3 times.

The person reading your case study probably has their own mess. Give them a chance to recognize it. Start with somebody trying to get an ordinary job done. Then show us the little thing that turned it into an afternoon.

Put the mess before the logo

Here is a made-up opening: "Every Friday, Maya checks three sheets to find which invoices are late. Two sheets disagree. The third one was last edited 5 months ago."

You know her job, the problem she's facing, and the cost in effort. No need to announce a "complex business challenge." It seems messy enough.

Now compare: "Maya works at Crestfield Technologies, a leading provider of tailored solutions."

We have learned almost nothing. Even the solutions appear to need a tailor.

In a real case study, use real details and make them human. Do not add three sheets because this example had three sheets.

Ask what was on the customer's screen, desk, or list when the problem showed up. Be clear about the stakes. Then show how it got solved and how life got better.

Find the detail that carries the stakes

Nielsen Norman Group's guide to user stories puts the user, their goal, and their setting at the center. The point is to show an experience from the user's side. That is a useful check for a customer story too.

Who was stuck? What were they trying to do? What got in the way? What did that cost them? Answer those before you give the brand a speech.

For a real example, look at NNG's case study of Marketade's work for Baileigh Industrial (which sells machinery). Customers kept calling sales staff because they could not find what they needed on the site.

The article gives a sharp detail... A sales rep might spend 20 minutes on questions about a $716 hand bender instead of helping with a possible $130,000 laser table sale.

That contrast gives the problem weight. We can see why the wrong calls mattered. It is more useful than "the client needed a better digital experience."

Note the limit: The article presents what a rep might face. It does not report a named rep losing a $130,000 sale. A good detail does not need a bigger claim stapled to it.

Show the work between before and after

A weak case study jumps from "things were bad" to "then they hired us." It is a fairy tale with a billing address.

The Baileigh story shows the steps. Marketade spoke with sales staff, watched people try the site, and tested whether they could find products through its menu structure.

Then the team changed the groups and labels in the menu. Broader groups gave people a clearer first choice. That links the change to the problem. We can follow the work.

Your story needs that link too. What did the customer try? Why was it not enough? What changed? Which part of the change helped with the original snag?

Ask those questions in an interview. Then ask for one example. "The process was much smoother" is a start. "What did you no longer have to do?" gets you closer to a useful sentence.

Let the result keep its real size

In the Baileigh tests, the overall score rose from 4.0 to 7.4 out of 10 across eight tasks. NN/g reported that as an 85 percent increase in product findability: how well people could find the products.

That is a test score. It is not an 85 percent rise in sales. Keep the label attached to the number. Numbers wander into strange places when nobody watches them.

The article also reports later growth in revenue and leads. But Marketade's principal said they could not isolate the menu changes' share of that growth. That limit belongs with the result.

Use the same care in your case study. Name what changed, how it was measured, and over what period. If other changes took place, say so. Do not give your work credit for the weather.

No clean number? Use a specific, approved customer quote about a real change. Do not invent a score. Keep enough context for the reader to judge what the quote means.

The reader does not need a perfect hero. They need a fair view of the problem, the work, and the result. That is how they judge whether your help could fit their own mess.

Build your next case study from these notes

Open at the snag.
Use a real moment that shows someone trying to get a job done. Put the company bio later.

Name what was at stake.
Show the lost time, extra work, cost, or risk. Get the detail from the customer, not your wish list.

Get the customer's words.
Ask what happened on one real day. Keep their wording, and have them check the quote rather than writing praise for them.

Show the change.
Connect each key step to the problem it helped solve. Give the customer a role in the work.

Keep the proof in bounds.
Name the measure and time frame. Check quotes, results, and permission before you use them.

End with the fit.
Explain who might face the same problem and when this approach makes sense. Skip the victory lap.

Start with the mess. Show the work. Let the proof stay human-sized. Your logo can wait until the story has earned it a seat.