Decide what can remain

Keep the operational problem, scope and process that make the case instructive. Review distinctive combinations of location, dates, images and metrics that could reveal the organisation. Avoid replacing specifics with exaggerated generalities. A reader should understand the type of challenge and the team’s contribution even if identifying details cannot be shared. Clearly explain that the case has been anonymised.

Preserve the evidence boundary

Maintain the original supporting records internally and obtain appropriate approval for the public version. Do not imply that a hypothetical example is an anonymised real client story. Those are different editorial formats and should be labelled differently. Where results are omitted, say what the case can still demonstrate, such as a workflow or delivery method. Offer additional context only through an approved process and within the agreed disclosure limits.

Put the guide to work

Have someone outside the project team review the anonymised version for recognisable clues. Internal colleagues can underestimate how distinctive a combination of details may be. Ask whether the operational lesson remains useful after any further changes, so the final case preserves value without exposing unnecessary context.

Imagine this

Hypothetical example

A service provider removes a client name but leaves a unique building photo and exact opening date. The revised case uses an approved generic diagram and broader timing while retaining the useful explanation of how the team coordinated a difficult operational handoff.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.