How to Make a Case Study Without Sharing Private Details

A good case study shows what you did, why it mattered, and what changed for the client. The difficulty is that the most convincing details are often the most sensitive, such as names, figures, locations, and internal problems. You can write a useful case study without exposing a client, but it takes deliberate effort. You need permission, a clear lesson, careful editing, and a check for details that identify people indirectly. This guide describes a practical way to do that.

A practical example

Which detail teaches the lesson: the client’s name, or the fact that two people thought the other one had approved the proof? In a case study about missed approvals, you can often leave out the name. That alone does not make the story safe to publish.

A before-and-after edit

Too revealing: “Two days before the town’s only winter festival, its printer had to rerun the sponsor posters.” Even without a name, the date, event, and supplier may identify the people involved.

More useful, if approved: “The working proof and the approved proof lived in different email threads. I moved the approval to one shared record and named the person responsible for releasing the file.” This version explains the change without repeating the client’s predicament. It does not claim that all reprints stopped.

Ask the client to approve the proposed wording, audience, and publication location in writing. Check the underlying agreement and the rights of anyone else whose words, images, or work appear. Approval from one contact is not blanket permission to use every detail. Keep a private record of what supports each result; omit a number if you cannot substantiate it or share it safely.

If the combination of facts still gives the client away, or permission is withheld, leave the case unpublished. You can build a new, clearly labeled fictional demonstration of the approval method without presenting it as a client result.

Get permission in writing

Before you draft anything, ask the client for permission to write about the project. Explain what you plan to publish, where it will appear, and whether you will name them or describe them generically. Ask them to review the final version before it goes live. Keep the permission in writing, even if it is a short email. A verbal yes is easy to forget or misremember, and a written record protects both of you. If the client says no, respect that decision and write about a different project, or write a general lesson without any project details.

Identify the lesson first

A case study needs a point. Start by writing one sentence that describes what the project taught you or what other people could learn from it. For example, “Setting a single approval contact at the start prevented three rounds of conflicting feedback.” The lesson shapes which details matter and which can be left out. If you cannot state the lesson clearly, the story is not ready, and a longer story will not fix that. Focus on the decision or practice that made the difference.

Use sources and numbers you can stand behind

Readers trust specific numbers, but only when they are accurate and can be explained. Use figures that you recorded during the project, such as hours saved, response times, or the number of revisions. Be clear about what was measured and over what period. Avoid rounding in ways that make results look larger than they were. If a number came from the client, confirm that they are comfortable sharing it, and consider showing a range instead of an exact figure when that protects them.

Remove identifying combinations of facts

Removing a name is not always enough. A combination of details can identify a client even when no name appears. A specific industry, a small city, a unique product, a rare job title, and an exact start date together may point to one organization. Read your draft from the point of view of someone who knows the client’s field. Generalize where you can. Replace “a family-owned bakery in a town of 4,000 people” with “a local food business,” and drop details that do not support the lesson. The story should still be concrete, but the concrete parts should belong to the lesson, not to the identity.

Agree on the level of detail

Before writing, talk with the client about how much detail is acceptable. Some clients are happy to be named with a full description, others want only a general industry label, and some want a story without any numbers. Write down the agreed level and keep it with the permission record. If you later want to add a detail, ask again. This conversation takes a few minutes and prevents a difficult request to remove a published story later.

Tell the story in order

Structure the case study around the situation, the challenge, the approach, and the result. Keep each section short and specific. Describe what the client needed, what made the situation difficult, what you did and why, and what changed afterward. Use plain language and avoid jargon the reader would not recognize. Include a quote from the client only if they have approved the exact wording. A calm, honest account of a partial success is often more useful than an account that claims everything went perfectly.