Case Story

Case Stories allow the sharing of experiences and practices in the implementation of programs and
projects. It can be a five to ten-page description of a particular approach, process, or activity related to the
program or project. More specifically, case stories:
 describe experiences encountered and lessons learned and therefore can be used as a learning tool
by other organizations and stakeholders;

 include pending questions and challenges identified by the organization.

Ideally, case stories are developed and drafted in close collaboration with an outside partner, such as an
academic institution or a civil society organization.
(Source: http://www.unglobalcompact.org/cop/Case_Story/index.html)

A case story provides a distinct example of how an organization (i) implements its principles in its
operations, (ii) interacts with its key stakeholders (iii) and/or promotes partnerships or supports
broader organizational goals.

It showcases a good practice, which could serve as an example for other participants facing similar
challenges.

The case story does not present company policies in a comprehensive way, nor does it define boundaries
or a company’s scope of operations. Instead, it illustrates how a specific policy is implemented at the
operational level, or describes an isolated activity or good practice in a given area.

The case story should include the following elements or structure:

Elements Description
An outline of the situation or challenge
encountered.

An identification of the main “drivers” or the Why did the company focus on this problem, and
motivation for the company to address this issue why at a given time?

An identification of the key players involved in The nature of the different players and their
addressing the problem, both inside and outside the interests/histories with the issue at hand should be
company. presented.

A (chronological) description of action taken - by

whom, in what order, and how.

A description of how managers perceived potential What were the benefits of the approach selected to
risks and reasons why a particular decision or action resolve the case? How did parties find a common
was chosen. ground to solve the issue at stake?
Outcomes and impacts What were the measurable outcomes or impacts of
the action taken? What were the non-quantifiable
but seemingly relevant impacts of the action taken?
What was considered a success? Which elements
were considered a failure? In addition, it is important
to assess both short and long term impacts and
unanticipated outcomes, positive as well as
negative.
Finally, the case story should include remaining
unanswered questions as identified by the
company.

(Source:
http://www.unglobalcompact.org/docs/communication_on_progress/Case_Story/Case_Stories_Guidelines.
pdf)

Case stories provide respondents with an opportunity to highlight their work, their successes and
lessons learned. Furthermore, respondents can increase visibility of the problems and challenges
they face.

Case stories are potentially a very useful tool in facilitating dialogue between ministries,
stakeholders, partners and donors about what works and what does not work.

Outcome and impacts can be described at the level of individual projects or programmes.

Alternatively, or in tandem, impacts at the macro-level or the impact of an individual project or

programme or the combined effect of (several or all) projects or programmes can be elaborated.

Case Story Template

Executive Summary
1. Issues Addressed
2. Objectives Pursued
3. (For projects and programmes: Design and Implementation)
4. Problems Encountered
5. Factors for Success/Failure
6. Results Achieved
7. Lessons Learned
8. Conclusion (applicability to other programs)
Annexes and/or References

(Source: http://www.wto.org/english/tratop_e/devel_e/a4t_e/call_case_stories_e.pdf)