Skip to main content

Case Study Writing Lab

You are writing the full capstone case study in this lab. The deliverable is a 1,500-2,500 word document in your portfolio repo. This is a graduation artifact.

Retrieval Prompts​

  1. From memory, list the four load-bearing sections of a strong capstone case study.
  2. State the target length range and the order you write them in (not the order the reader sees).
  3. State the one-line summary word ceiling.
  4. What belongs in the "Tradeoffs" section that does not belong in "Outcome"?
  5. Why does "Outcome" get written before "Problem"?

Compare and Distinguish​

Separate these pairs clearly, in one sentence each:

  • case study vs README
  • case study vs demo script
  • case study vs résumé bullet
  • "what I'd do differently" vs "things that went wrong"
  • a load-bearing diagram vs a decorative diagram

Common Mistake Check​

For each statement, identify the error:

  1. "I'll open the case study with the architecture, because it's the most interesting part."
  2. "The more diagrams, the better -- I'll include six."
  3. "I'll mention every framework I used so nothing gets missed."
  4. "I don't need a 'tradeoffs' section because I made the right choices."

Mini Application​

Write the full case study in one sitting, following this exact sequence.

  1. One-line summary (≤ 25 words).
  2. Outcome paragraph with at least one measured fact.
  3. Problem section (2-3 paragraphs).
  4. Approach section (3-4 paragraphs, with one load-bearing architecture diagram).
  5. Implementation highlights (2-3 paragraphs covering the non-obvious technical moves only).
  6. Tradeoffs section (2-3 paragraphs).
  7. What I'd do differently (1-2 paragraphs).
  8. Optional appendix (diagrams, ADR links, runbook pointers).

Apply the margin-summary pass from Cluster 1 concept 02. Cut anything that reduces to "tools we used."

Then apply the three-pass edit from Cluster 3 concept 09:

  • structural pass (cut duplicated paragraphs)
  • sentence pass (replace abstract with specific)
  • word pass (kill adjectives and hedges)

Target final length: 1,500-2,500 words.

Evidence Check​

This practice page is complete only if:

  • a 1,500-2,500 word case study exists at library/raw/case-study.md in your capstone repo
  • the four load-bearing sections are clearly labeled
  • at least one diagram carries explicit edge labels (delivery semantics, consistency, failure boundary)
  • the document has been edited (visible diff between draft and final)
  • at least one peer has read it and given non-trivial feedback
  • a reader can state the problem, outcome, and one tradeoff in their own words after reading

Do not sign off on this page until all six are true.

Integrated Portfolio Evidence Package​

Add an evidence appendix to the case study.

Required structure:

  1. Problem and user outcome.
  2. Architecture diagram with labeled failure or consistency boundaries.
  3. Screenshots or terminal captures for the vertical slice, pipeline, deployment, dashboard, and rollback rehearsal.
  4. Testing evidence: unit, integration, end-to-end, and quality-gate summary.
  5. Security and ethics note: data handled, legal or professional responsibility, accountability boundaries, and communication choices.
  6. Tradeoff narrative: what you chose, what you rejected, what it cost, and what you would revisit.

Evidence check: a reviewer should be able to verify the capstone's claims from links, screenshots, diagrams, and command output without needing your verbal explanation.