Product for Designers

Decision Cards

Make interface decisions you can defend in any design review.

27 more cards are on the way. Get each one in your inbox as it unlocks.

Or install the deck for your AI tools

Product for Designers · Q1 2027

Learn to make these calls on your own.

These cards are the first of many. The course teaches the reasoning behind each one, with practice rounds and teardowns of real products.

Get new cards as they’re released, and early-bird pricing at launch.

Coming next

Flow & continuity

Autosave or Save

Is every edit safe to keep the moment it’s made?

Use Autosave when

Documents, notes, and canvases where each edit stands alone and losing work is the worst outcome.

Signs it fits

  • Continuous editing
  • Version history exists
  • Only the author is affected
  • People forget to save

Use Save button when

Settings and records where changes should land together, be validated first, or will reach other people.

Signs it fits

  • Several fields that must agree
  • Changes affect billing, access, or others
  • Server validation before applying
  • People expect to review, then commit

The numbers

Autosave if a half-finished edit is harmless and version history lets people go back. Save button if a half-finished state could break something or reach someone else. Never mix both models on one screen.

Say this in review

Changing the billing email affects invoices for the whole team, so changes on this screen wait for Save. A typo here shouldn’t reach anyone until it’s confirmed.

When it flips

The exception

With a Save button, closing the page loses work. Warn about unsaved changes, or keep a local draft.

See it work

Make the call

Card 13 of 15

A personal profile bio. Autosave or Save button?

Flow & continuity
The rule

Save automatically when every edit is safe to keep. Ask for Save when changes must land together or affect others.

From the lesson “Forgiveness”

ClickTap the card to turn it over

Install the deck

Bring every card into your AI tools, so they review screens and flows the way the cards do.

Agents can also read llms.txt, or any card as markdown by adding .md to its link.

15 of 42 cards