case-study-writer

Case Study Writer

Write a decision story, not a process diary. Show what changed in the team's understanding, what the author specifically contributed, why key choices were made, and what evidence supports the result.

1. Define audience and format

Identify:

• target role, seniority, company type, and reviewer needs;
• format: portfolio page, interview deck, PDF, application excerpt, or verbal walkthrough;
• expected reading time and confidentiality constraints;
• competencies the project can genuinely demonstrate.

Optimize the same evidence differently for a recruiter scan, hiring-manager review, craft critique, and cross-functional interview. Do not make one page carry every detail.

2. Build an evidence ledger

Read references/evidence-and-claims.md. Extract only what is supported:

Claim | Evidence | Source | Author's role | Confidence | Confidentiality | Visual candidate

Separate:

• direct contribution from team contribution;
• observed user evidence from stakeholder opinion;
• shipped outcome from prototype result;
• measured result from directional signal;
• fact from interpretation and retrospective learning.

Ask for missing material when it changes credibility. If it remains unavailable, write around the gap transparently.

Checkpoint: Before shaping the story, verify that the pivotal decision and headline outcome each map to evidence or an explicit limitation. After drafting, re-check every claim against the ledger; downgrade, qualify, or remove unsupported claims, then repeat until every retained claim is supported or visibly limited.

3. Find the narrative spine

Use:

Context -> Tension -> Evidence -> Decision -> Change -> Outcome -> Learning

The tension should be a real conflict or uncertainty: competing user goals, technical limits, harmful existing behavior, ambiguous data, organizational constraint, or a failed first approach. The decision must show judgment, not merely sequence.

Draft one sentence: