Scheduled Gift Delivery
Design a thoughtful scheduling flow for sending flowers or gifts on future occasions without losing control of the final choice.
The brief
Understand the problem
Background
People remember important dates but still miss the ordering window. Automated gifting can help, yet substitutions, changing addresses, personal taste, and price shifts make fully automatic purchases risky.
User context
Elena wants to arrange birthday deliveries for three relatives over the next two months. She knows their preferences but wants to approve each final item before payment.
Product problem
The service must reduce repeated setup while keeping consent, budget, delivery details, and substitutions visible at the right time.
Objective
Design a future gift schedule with recommendation review, recipient details, approval, and delivery updates.
What to design
Define the experience
Required experience
- Occasion and recipient setup
- Gift recommendation review
- Scheduled order status
Screens and states
- Gift calendar
- Recommendation and customization
- Approval reminder
- Delivery tracking
Core user flow
Follow the critical path
- 01
Elena adds an occasion and budget
- 02
She records the recipient's preferences
- 03
The service proposes options before the order deadline
- 04
She approves a gift and tracks delivery
Product rules
Requirements and constraints
Requirements
- Make automatic purchase settings explicit
- Show cutoff dates and delivery windows
- Allow no-substitution preferences
- Support a private gift message and hidden price
Constraints
- Inventory can change before fulfillment
- Recipient addresses may be outdated
- Delivery dates cannot always be guaranteed
Reality check
States worth considering
Ready-to-use content
Mock data
Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.
Upcoming gifts
- Mum's birthday, 12 October, approval due 7 October
- Ari's graduation, 29 October, preferences incomplete
- Sam's birthday, 18 November, not started
Finish line
What to deliver
- Four responsive screens
- A clear approval and substitution policy component
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.