How to outline a case study from documented work
A case study explains a problem, the work undertaken and the outcome supported by evidence. An outline helps identify the missing material before a polished story is written.
Start with the right material.
- What you provide
- authorized customer project notes with documented outcomes.
- The intended result
- Save problem, approach and evidence sections without inventing quotes or performance numbers.
How the workflow works.
Organize the supplied facts around situation, approach, implementation and results. Distinguish measured outcomes from expectations and list the sources or permissions needed for quotes and customer details.
What to check in the result.
Review the link between the work and the reported result. A before-and-after change does not automatically establish causation, and an unsupported metric should remain a research question.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.