Success Case Method
Investigate cases with strong and limited outcomes in depth to identify enabling conditions and barriers. Its purpose differs from estimating representative average effects. [1]
- Difficulty
- Intermediate
- Cost
- Low
- Duration
- Illustrative estimate (adjust for scale and staffing): 2–6 weeks overall; 1 week for the survey, 1–2 weeks for interviews and 1–2 weeks for analysis and reporting
How it works at a glance
The success case method defines expected success, uses surveys or other means to identify cases with high and low success, then examines them through interviews and evidence. It describes concretely how outcomes occurred. [1]
Because exceptional cases are deliberately selected, their results cannot be treated as the average for all participants. Organize verified outcomes and enabling and inhibiting conditions to inform improvement. [1]
- Set the evaluation focus
- Identify success and failure through a survey
- Select interviewees
- Conduct in-depth interviews
- Develop success and failure stories
- Prepare recommendations and dissemination plans
When to use it and when it is unsuitable
When to use it
- Quickly examining workplace transfer after training (Behavior, Level 3) at low cost
- Diagnosing why well-received training is not used at work
- Obtaining concrete barriers and success factors for redesigning training quickly
- Exploratory research to generate hypotheses before a large evaluation study
When it is unsuitable
- When statistically demonstrating average training effects is the objective; a few in-depth cases are not representative
- Small training programs expecting uniform outcomes without successful or unsuccessful cases
Participants, roles, and deliverables
Participants and roles
Evaluation officers, participants with contrasting outcomes or use, and supervisors or others able to verify circumstances as needed. Determine numbers by case diversity and depth of examination.
Main deliverables
- Participant survey findings for case identification
- Success stories (number determined by the subject)
- Failure stories (number determined by the subject)
- Analysis and recommendations on enabling and inhibiting transfer factors
Implementation steps
- Set the evaluation focusAgree with training officers on expected work behavior changes and their organizational value. Define success clearly in advance.
- Identify success and failure through a surveyUse a short survey or similar approach to identify cases where expected behavior or results did and did not occur. Set question numbers based on selection needs and response burden.
- Select intervieweesPurposively select cases with high and low outcomes. Rather than fixing numbers or percentiles, choose cases illuminating success and non-use conditions and explain selection reasons.
- Conduct in-depth interviewsAsk about outcome situations and conditions enabling or preventing use. Adapt duration to interviewees and check corroborating records and third-party information.
- Develop success and failure storiesUse interviews to describe success and failure stories. Protect identifying information while concretely communicating circumstances, actions, outcomes and factors.
- Prepare recommendations and dissemination plansAnalyze success factors and recommend which to strengthen to increase overall transfer rates. Also plan to disseminate success stories within the organization.
Strengths and limitations
Strengths
- Offers unparalleled practicality as a low-cost, rapid method for evaluating training transfer
- Contrasting success and failure clearly identifies improvement directions
- Concrete stories communicate well to senior managers and can demonstrate training investment value
Limitations
- Focusing on extremes prevents understanding the overall distribution of effects
- Small case numbers provide no statistical basis for representativeness
- Survey and interview design and implementation require appropriate skills
Common pitfalls
- Too many questions aimed at detailed effect measurement reduce response rates; SCM surveys are for identifying cases
- Collecting successes alone and omitting failures; interviews on failure contain the most important improvement information
- Interviewers try to attribute success to training and overlook workplace or managerial factors
Conditions of use and evidence
- Examines the most successful and unsuccessful cases; selection is not intended to represent average outcomes. [1]
Cases that did and did not use training plans in meetings
The following fictional example selects 2 people with contrasting conditions for use from 12 evaluation planning trainees.
Scroll horizontally to view the table
| Participant ID (anonymous) | Success / failure group | Selection rationale (survey response features) | Interview date and time |
|---|---|---|---|
| A01 | Success group | Used it in a meeting and decided items and responsibilities | October 15, 2026 (fictional) |
| A02 | Failure group (non-use) | Prepared a draft but had no meeting opportunity | October 16, 2026 (fictional) |
Common errors in judgment
Selecting only successful cases for publicity
How to revise
Examine non-use cases and explain conditions and barriers
ReasonThis identifies support needed to reproduce success.
Presenting the proportion of selected successes as the overall effect
How to revise
Explain selection methods and examine overall proportions separately
ReasonExtreme cases have been selected.
References and checked sections
- Success case methodBetterEvaluation
- Section consulted
- Main text; five key steps; Advice
- How it relates to the text
- Examines the most successful and unsuccessful cases; selection is not intended to represent average outcomes.
Editorial and checking information
How to cite this page
Change history
- — Corrected statements and procedures identified during content checks (U03). Preserved the order, number and labels of input fields and the section structure.
- — Updated explanations to correspond to the sources and added method-specific fictional completed examples, judgment examples and a change log.


