# Case Study Design Decisions

> Explain and defend pivotal design decisions in a case study using stakeholder context, user and business evidence, alternatives, constraints, trade-offs, consequences, limitations, and follow-up. Use when a portfolio draft shows screens without rationale, lists activities instead of decisions, needs executive credibility, must explain rejected options, or must communicate complex enterprise, platform, system, or AI-agent design choices.

- Skill: `jpoindexter/case-study-design-decisions` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jpoindexter/case-study-design-decisions`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jpoindexter/case-study-design-decisions/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: jpoindexter (https://skillmd.com/u/jpoindexter)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jpoindexter/case-study-design-decisions

---


# Case Study Design Decisions

Make the decision legible to a skeptical non-designer. Read `references/decide-record.md`.

## Workflow

1. Identify the reader’s influence, priorities, vocabulary, and likely objection.
2. Select only decisions that changed user outcomes, system behavior, risk, cost, or delivery.
3. Complete a DECIDE record for each pivotal decision.
4. Connect design evidence, business consequences, technical constraints, and limitations.
5. Represent rejected alternatives fairly.
6. State what agreement enabled and what happened next.
7. Remove aesthetic rationale that does not affect use, comprehension, trust, or performance.

## Communication pattern

For each decision:

- set context before showing the artifact;
- name the problem and tension;
- explain the choice in the reader’s language;
- ground the rationale in users, business, research, and constraints;
- acknowledge limitations without weakening the argument;
- show the decision or learning that followed.

Do not hide uncertainty or pretend consensus existed. Distinguish the design recommendation from the final organizational decision.

## Output

Return a decision shortlist, completed DECIDE records, likely stakeholder questions, and recommended captions or callouts for the associated visuals.