jpoindexter Case Study Design Decisions
Make the decision legible to a skeptical non-designer. Read references/decide-record.md.
Workflow
- Identify the reader’s influence, priorities, vocabulary, and likely objection.
- Select only decisions that changed user outcomes, system behavior, risk, cost, or delivery.
- Complete a DECIDE record for each pivotal decision.
- Connect design evidence, business consequences, technical constraints, and limitations.
- Represent rejected alternatives fairly.
- State what agreement enabled and what happened next.
- 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.