user-psychology
User Psychology
Apply motivation, friction, and trust patterns to product decisions.
How to use
/user-psychologyApply behavioral constraints to this conversation.
Constraints
Motivation Patterns
- People act when the perceived benefit exceeds the perceived effort
- Reduce effort before increasing benefit (it's more effective)
- Loss aversion: people fear losing what they have more than gaining something new
- Social proof works because uncertainty triggers conformity
- Progress indicators motivate completion (the closer to done, the more motivated)
Friction Mapping
- Map every step in a flow. Each step is a potential exit point.
- For each step: what effort is required, and what value does the user receive?
- MUST reduce steps between intent and completion
- SHOULD front-load value and back-load commitment
- NEVER add friction for "engagement" purposes (dark pattern)
Trust Patterns
- Trust is built incrementally: small commitments before large ones
- Transparency about pricing, data usage, and limitations builds trust
- Admitting weaknesses builds more trust than claiming perfection
- MUST match expectations set in marketing with the actual product experience
- Broken trust is 10x harder to rebuild than to maintain
Cognitive Load
- MUST limit choices per screen (5-7 options max without grouping)
- SHOULD use progressive disclosure instead of showing everything at once
- Familiar patterns reduce cognitive load (don't reinvent standard UI conventions)
- NEVER rely on user memory between screens (show context, don't assume it)
Anti-Patterns
- Using psychological principles to manipulate rather than assist
- Dark patterns: hidden costs, trick questions, forced continuity, misdirection
- Artificial scarcity without real scarcity
- Guilt-based retention ("Are you sure? You'll lose everything!")
- Exploiting anxiety or FOMO for engagement
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1microcopy
The small words that shape big experiences. Button labels, tooltips, confirmations, placeholders, and the 3-word strings that determine whether a product feels polished or half-finished. Use during any copy audit pass.
1