TAP TAP GO
Define the starting condition
Describe the original problem using observable information. State the relevant period and the scope of the work. Avoid dramatic before language that cannot be supported. If a measurement was not captured at the start, say so and use a qualitative account instead of inventing precision. Keep the client’s goal separate from the result eventually observed.
Explain the contribution
Show what the team actually did and what else may have influenced the outcome. A case study can describe a useful improvement without claiming sole causation. Use the same definitions for the before and after measures. Include limitations and permission to publish the information. A reader should be able to understand the result and decide which parts of the approach might transfer to their own situation, rather than simply admiring a large percentage.
Put the guide to work
Ask the client-facing team which part of the result they can substantiate if challenged. That question often reveals where a case study moves from observation into interpretation. Keep the compelling story, but make the supporting measurement and the team’s actual contribution clear enough to discuss without improvisation.
Hypothetical example
A supplier says its process doubled enquiry quality but has no baseline definition. It revises the case study to show the new qualification criteria, a dated sample and the observed change in follow-up conversations. The result is narrower, but more useful to a prospective buyer.
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.
