alectivism Template skill. Fill in the [BRACKETED] placeholders with your organization's details — or paste your org context and ask Claude to populate them for you.
Case Study Generator — [YOUR ORGANIZATION]
Case Study Structure
Standard Format
Title: [Client/Company] + [Key Result] + [Program or Context] Example: "Acme Co Achieves 3x ROI Through [YOUR PROGRAM]"
The Challenge
- 2-3 sentences on what the organization was trying to solve
- Industry context — why is this a common challenge?
- What had they tried before?
The Approach
- Which [YOUR ORGANIZATION] program, tool, or framework was used
- Methodology (brief, accessible — avoid jargon)
- Timeline and scope
- Partner involvement (if any)
The Results
- Lead with the headline number — bold and prominent
- Supporting metrics in bullets
- Comparison to industry benchmarks or prior baseline (if available)
- Statistical confidence or sample details (if relevant)
Key Takeaways
- 2-3 actionable insights others can apply
- What made this work (conditions for success)
- What surprised the team
About [Client/Company]
- 1-2 sentence company description
About [YOUR ORGANIZATION]'s [Program Name]
- 1-2 sentence program description
- How to participate or learn more
- Contact or CTA
Quick-Hit Format (for newsletters, social, sales)
Length: 150-200 words Structure:
- Challenge (1 sentence)
- Solution (1 sentence)
- Result (1 sentence with headline number)
- CTA (1 sentence)
Data Sources for Case Studies
- [YOUR PROGRAM/LAB] experiment or pilot results
- [CLIENT/MEMBER] testimonials from events or surveys
- [INITIATIVE] outcomes and assessments
- Certification or training program metrics
- [Add your organization's relevant data sources]
Key Results to Reference
Populate this table with your organization's documented results:
| Program | Organization | Result |
|---|---|---|
| [YOUR PROGRAM 1] | [Organization name] | [Key metric — e.g., X% lift] |
| [YOUR PROGRAM 2] | [Organization name] | [Key metric] |
| [YOUR PROGRAM 3 / Cross-study] | [Aggregate] | [Cross-study finding] |
Guidelines
- Get approval before using a client/member's name in a case study
- Verify all numbers against source data
- Don't fabricate quotes — use real ones or omit
- Frame results honestly — include context (sample size, conditions, timeline)
- Make it useful, not just promotional — readers should learn something
Process
- Identify the subject (which organization, program, result)
- Gather data from internal sources ([YOUR DOCUMENT STORAGE], program reports, meeting notes)
- Draft in the appropriate format
- Flag any numbers that need verification
- Note if client/member approval is needed before publication
- Present for review