Reactance

Try grouping several permission requests into one checklist, with the reason for each, so people decide for themselves instead of pushing back against pressure.

Onboarding permissions screen. Each request explains its purpose: microphone "app to listen", notifications "For chat summaries". Microphone access shows as granted with a tick, while notifications still await enabling.

Example from

Cue

Rather than forcing onboarding on everyone upfront, consider offering guidance only once someone sends several negative prompts in a row, so help feels offered, not imposed.

Chat screen for an AI app builder. Above the prompt box, a dismissible tooltip says "Feeling stuck?" and "Use chat mode to create a plan.", nudging users towards the "Chat" mode button.

Example from

Lovable

When someone enters their first password by hand, one option is to suggest importing existing passwords from another browser, framed as an offer, not a required step.

Log-in page in a web browser. While signing in, a modal offers to import saved passwords from another browser, with "No Thanks" and "Import" buttons that show their Esc and Enter keyboard shortcuts.

Example from

Possible impacts

Forced onboarding, trials or sign-up can provoke reactance and push users to cancel, so offering choices like a skip or shorter trial could help reduce churn.

As seen in:

Duolingo Sharing your checkmate

Pressuring people to invite friends may trigger reactance, whereas making sharing an optional offer with a clear reason might lead to more genuine referrals.

As seen in:

Spotify A well-timed nudge

Pushy flows can make users feel their freedom is under threat; a visible way out, e.g., skip, undo or cancel, could lessen their frustration.

As seen in:

Cue Permission to do list

Small concessions of control, like letting users choose when or whether to act, may soften reactance and leave people feeling happier using the product.

As seen in:

Consultant to 100+ companies

Written by Peter Ramsey

Published: 31/08/2023

How to utilise this in your designs

Next to a big commitment, e.g., setting a default, you could offer a lower-commitment 'try for one week' option, so saying yes doesn't feel like giving up their freedom.

Example from

Try grouping several permission requests into one checklist, with the reason for each, so people decide for themselves instead of pushing back against pressure.

Example from

Cue

Rather than forcing onboarding on everyone upfront, consider offering guidance only once someone sends several negative prompts in a row, so help feels offered, not imposed.

Example from

Lovable

When someone enters their first password by hand, one option is to suggest importing existing passwords from another browser, framed as an offer, not a required step.

Example from

Possible impacts

Forced onboarding, trials or sign-up can provoke reactance and push users to cancel, so offering choices like a skip or shorter trial could help reduce churn.

As seen in:

Duolingo Sharing your checkmate

Pressuring people to invite friends may trigger reactance, whereas making sharing an optional offer with a clear reason might lead to more genuine referrals.

As seen in:

Spotify A well-timed nudge

Pushy flows can make users feel their freedom is under threat; a visible way out, e.g., skip, undo or cancel, could lessen their frustration.

As seen in:

Cue Permission to do list

Small concessions of control, like letting users choose when or whether to act, may soften reactance and leave people feeling happier using the product.

As seen in: