Setup Defaults

Give users a credible starting point they can understand, change, or skip.

What it is

Setup defaults are the preselected settings, templates, sample content, or starter configurations a product offers so a new user isn’t staring at an empty page deciding where to even begin. A CRM that opens with three example deals already in the pipeline, a design tool that starts a new file at a sensible canvas size, an app that pre-selects the most common notification schedule—all defaults, all doing the same job: turning “what should I do first” into “here’s a reasonable starting point, change what you don’t like.” It’s closely related to Momentum Bias but sits one level below it: setup defaults decide what the starting content or configuration actually is, while Momentum Bias is the broader sense of head-start and visible progress built from defaults, checklists, and partially completed work together.

Why it works

Friction names exactly what a default removes: not effort in the abstract, but a decision, and decisions are the most expensive kind of friction because a new user has the least context to make them well. Facing a blank workspace with no starting point forces someone to decide before they understand enough to decide confidently, which is precisely the moment self-doubt and abandonment are most likely. A credible default replaces that decision with a visible, editable answer—not a smaller decision hidden from view, but a real starting point the user can inspect, keep, or change—which lets them move straight to evaluating the product instead of configuring it.

The line between a helpful default and a sludgy one is the same test User Agency applies everywhere: would you still ship this default if it cost you conversions, or does it quietly serve the business at the user’s expense—a pre-checked marketing opt-in, a sharing setting nobody would choose on purpose. Skip defaults altogether and you get the failure this TTP exists to prevent: decision fatigue on an empty page, at exactly the moment someone has the least standing to decide well. Skew a default toward what’s convenient for you rather than likely for them, and you’ve turned a kindness into a manipulation wearing the same interface.

When to use it

• When configuration, content creation, or an Empty State would otherwise block first use
• When a template can demonstrate a useful workflow more clearly than a tour
• When Personalisation can safely tailor a starter path from declared intent

Do

• Provide a small set of clearly differentiated templates or starter configurations
• Make pre-filled values visible and easy to edit, remove, or replace
• Explain consequential defaults, especially those affecting sharing, notifications, cost, or data use

Don’t

• Treat a business-preferred choice as a neutral default
• Fill a workspace with example content that users may mistake for their own data
• Offer so many templates or branches that the default path creates a new decision burden

Founder Tip

A default should answer “where do I begin?”—not quietly answer “what should I choose?” for the user.

Make It Yours

1. To identify the blank moment:
   • Where does a new user face an empty page or a high-effort first decision?
   • What starter state would let them do something useful immediately?
2. To make the default relevant:
   • Which stated goal, role, or use case can safely shape the starting point?
   • What is the smallest set of options that covers meaningful differences?
3. To preserve agency:
   • Can a user see what was chosen for them and change it quickly?
   • Which defaults need an explicit choice because their consequences matter?
4. To show real value:
   • Does the template demonstrate a core workflow rather than decorative activity?
   • Is example content clearly marked and easy to delete?
5. To learn and improve:
   • Which defaults do users keep, replace, or abandon?
   • Does the default reduce time to a meaningful outcome without causing later confusion?

Related concepts

• Friction
• User Agency
• Mental Models and Affordances

Further reading

• Default Settings in UX — Nielsen Norman Group on choosing and communicating defaults responsibly.
• Settings — Apple guidance on organising preferences and respecting user control.
• Ten Usability Heuristics — especially user control, error prevention, and recognition over recall.
• Data protection by design and default — useful guardrails for consequential data defaults.

Agent skill

• Primary command: /productfeeling friction — provide credible editable starters that reduce blank-page effort
• Related commands: /productfeeling states, /productfeeling persona, /productfeeling jobs
• When the agent should load this TTP: “default template”, “starter configuration”, “pre-filled workspace”, “example content”, “sensible defaults”
• Companion handoff: Impeccable — template selection, editable pre-fills, and consequential-default disclosure
• Feeling north star this TTP serves: a credible beginning users can change or skip
• Anti-goals: business-preferred defaults as neutral, mistaken example data, decision-heavy template sprawl
• Reference path: skill/reference/friction.md