Scaling Decisions: Turning Subjective Calls into Explicit Rules

Learning Goal

To turn subjective calls into explicit rules, we'll explore the Rule → Pattern → Doc chain.

Who

Designers, product managers, and anyone looking to enhance their decision-making processes.

What

We'll cover three key design decisions and how to transform them into systematic rules.

Where

In this lesson, we'll focus on scaling decisions from subjective to systematic.

When

This lesson is ideal for you if you're looking to enhance your design decision-making processes.

Why it matters

Without a playbook, quality variance explodes, and systematic decisions speed up development and reduce defects.

How

1. Write 3 Design Decisions as Rules: Start by identifying three subjective design decisions you've made recently and rewrite them as one-line rules (e.g., “Primary CTA: #FAB908 bg, #111827 text, 12x16 padding, no other CTA uses yellow.”).

2. Apply the Rule → Pattern → Doc chain: For each rule, provide a visual example (good/bad, states) and document where it lives (Figma library, Notion page, repo).

3. Create a Playbook Outline for your Product: Draft a high-level outline with the 6 sections (Intent & Voice, Semantics, Layout & Space, Components & Tokens, Governance, Capstone & Examples) to guide your playbook creation.

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

1. 3 decisions rewritten as Rule → Pattern → Doc.

2. Playbook outline exists.

3. One rule published to the team.

Optional Deepening

• Polaris (Shopify): https://polaris.shopify.com

• Atlassian Design System: https://atlassian.design