Ask for Encouragement Without Chasing Engagement
Design a peer-support space where people can request a specific kind of encouragement and control how others respond.
The brief
Understand the problem
Background
Motivational feeds can become performative, overly positive, or dependent on likes. People may need quiet acknowledgment, practical accountability, or space without unsolicited advice.
User context
Elena is returning to study after a difficult semester. She wants gentle check-ins from a small group but does not want productivity comparisons or public reactions.
Product problem
Support is personal. The interface must respect response preferences, protect vulnerable disclosures, and avoid mechanics that turn difficult moments into engagement content.
Objective
Create a bounded support request, response, and check-in experience without public popularity metrics.
What to design
Define the experience
Required experience
- Support preference and audience setup
- Focused request composer
- Response options matched to stated needs
- Private check-in and boundary controls
Screens and states
- Support settings
- Request composer
- Support thread
- Check-in
- Safety action
Core user flow
Follow the critical path
- 01
Elena chooses a small trusted group and preferred response types
- 02
She asks for a check-in before an upcoming study session
- 03
Friends respond with acknowledgment and one agreed reminder
- 04
Elena marks the request complete without publishing a success update
- 05
She adjusts her boundaries for future requests
Product rules
Requirements and constraints
Requirements
- Let people request listening, encouragement, advice, or accountability
- Hide follower counts, public rankings, and reaction totals
- Respect audience and reply boundaries on every request
- Provide quiet ways to acknowledge support
- Offer reporting and appropriate external help information for concerning content
- Avoid streak penalties and emotionally manipulative notifications
Constraints
- The service is not a substitute for professional or emergency support
- Members may be in different time zones
- A user may change audience access after replies exist
Reality check
States worth considering
Finish line
What to deliver
- Design five mobile screens showing consent-based support, boundary controls, and a safety escalation.
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.