Delegated Decisions

If you do delegate a decision, e.g., snoozing a task, you could show clear context about how that choice changes the user's schedule before they confirm.

Example from

Planta

Try grouping data-losing settings into one clearly highlighted danger zone, so users see the stakes before making a delegated decision they can't undo.

Settings menu with sections listed left. Export data box with "Create new export" button top right. Danger Zone outlined red includes red "Delete" buttons for deleting post archive, changing subdomain, or deleting publication.

Example from

Substack

When delegating a setup choice like importing settings, you could remind users of the effort they'd face if they skip it, discouraging a short-sighted decision.

Split UI with black left panel titled "Get us up to speed" and a blue "Next" button; right panel with radio buttons for Edge, Safari, or manual password entry choices.

Example from

Possible impacts

Setting sensible defaults instead of delegating decisions could reduce churn, as new users aren't left tired or unmotivated trying to build an efficient setup.

As seen in:

Tiimo Helping you rearrange your day

Adding context to the decisions you do delegate might improve users' understanding of the trade-offs and consequences they're signing up for.

As seen in:

Delegating key setup decisions may decrease feature usage, as users can hide features they'd have valued but didn't fully understand when making the choice.

As seen in:

Arc Leveraging loss aversion

Limiting heavy delegation could raise the perceived value of your product, as users aren't left with a poorly configured setup that limits what they get from it.

As seen in:

Transit Showing travel options in a timeline

Google Google Docs removing an unnecessary decision

Removing unnecessary delegated decisions, e.g., naming or layout, may help users get work done faster, with fewer interruptions and less time spent configuring.

As seen in:

Arc Blocking mobile trackers

Fewer delegated decisions could reduce users' anxiety about making the wrong choice, an anxiety that might otherwise push them to abandon the product entirely.

As seen in:

Consultant to 100+ companies

Written by Peter Ramsey

Published: 25/10/2023

How to utilise this in your designs

Rather than delegating the naming decision, you could pre-fill a document title from its first line of text, highlighted so users can overwrite it in one keystroke.

Example from

Google

You could avoid delegating a privacy decision by blocking trackers by default, then letting users allow them temporarily if they run into usability issues.

Example from

If you do delegate a decision, e.g., snoozing a task, you could show clear context about how that choice changes the user's schedule before they confirm.

Example from

Planta

Try grouping data-losing settings into one clearly highlighted danger zone, so users see the stakes before making a delegated decision they can't undo.

Example from

Substack

When delegating a setup choice like importing settings, you could remind users of the effort they'd face if they skip it, discouraging a short-sighted decision.

Example from

Possible impacts

Setting sensible defaults instead of delegating decisions could reduce churn, as new users aren't left tired or unmotivated trying to build an efficient setup.

As seen in:

Tiimo Helping you rearrange your day

Adding context to the decisions you do delegate might improve users' understanding of the trade-offs and consequences they're signing up for.

As seen in:

Delegating key setup decisions may decrease feature usage, as users can hide features they'd have valued but didn't fully understand when making the choice.

As seen in:

Arc Leveraging loss aversion

Limiting heavy delegation could raise the perceived value of your product, as users aren't left with a poorly configured setup that limits what they get from it.

As seen in:

Transit Showing travel options in a timeline

Google Google Docs removing an unnecessary decision

Removing unnecessary delegated decisions, e.g., naming or layout, may help users get work done faster, with fewer interruptions and less time spent configuring.

As seen in:

Arc Blocking mobile trackers

Fewer delegated decisions could reduce users' anxiety about making the wrong choice, an anxiety that might otherwise push them to abandon the product entirely.

As seen in: