Amanoba Logo
Back to Course

From Taste to System: Scaling Decisions

Day 2 of 30 · The Playbook 2026 – Masterclass for Designers

Turn subjective calls into explicit rules: Rule → Pattern → Doc.

Learning Goal

  • Write 3 design decisions as rules.
  • Apply the Rule → Pattern → Doc chain.
  • Create a Playbook outline for your product.

Why This Matters

  • Undocumented decisions get replayed.
  • Systematic decisions speed dev and reduce defects.
  • Without a playbook, quality variance explodes.

Explanation

Rule → Pattern → Doc

  • Rule: one-line decision (e.g., “Primary CTA: #FAB908 bg, #111827 text, 12x16 padding, no other CTA uses yellow.”).
  • Pattern: visual example (good/bad, states).
  • Doc: where it lives (Figma library, Notion page, repo).

Playbook Outline v1

  • Intent & Voice
  • Semantics (color, type, shape, motion, feedback)
  • Layout & Space
  • Components & Tokens
  • Governance (change, review, versioning)
  • Capstone & Examples

Examples

Bad: “If it looks nice, ship it.”

Good: “Primary CTA: rule + pattern + doc link; no other CTA uses yellow.”

Guided Exercise (10–15 minutes)

  1. Write 3 Rules for your product (CTA, card, form).
  2. Attach Pattern notes (good/bad, states).
  3. Add Doc location (Figma/Notion/repo) for each.
  4. Draft your Playbook outline with the 6 sections.

Independent Exercise (5–10 minutes)

Document one Rule in your real system (Figma/Notion), share with one developer, and ask for feedback.

Self-Check

  • 3 decisions rewritten as Rule → Pattern → Doc.
  • Playbook outline exists.
  • One rule published to the team.

Optional Deepening