← Portfolio
Product Thinking Portfolio · Case Study 01

Who Booked This?

A mobile app for extended family trips — built around the insight that group plans fall apart not from lack of enthusiasm, but from lack of a shared record of what was actually decided.

0→1 Consumer Mobile
Documents
📖
Case Study
Problem, users, key decisions, validation thinking, and success metrics.
 📋
Product Requirements Document
Full spec — v1.6. Core model, features, design principles, tradeoffs, monetization.
Wireframes
Wireframe 1
Itinerary day view
The primary screen — Active items, proposals, fork visibility, and urgent tasks in one view.
Wireframe 2
Item detail
Committed flags, per-item comments, inline audit trail, and state actions.
Wireframe 3
Proposals view
All open proposals with vote counts, comment signals, and promotion controls.
Wireframe 4
Task board
Urgent, unclaimed, claimed, and completed tasks — deadline urgency visible at a glance.
Wireframe 5
Fork detail
A parallel sub-group plan with its own items, committed flags, and rejoin point.
Wireframe 6
Create task
Noticing a gap — with the no-coercion principle built into the language and defaults.
Wireframe 7
Member list
All three access tiers, activity signals, and the never-joined section.
Wireframe 8
Child view
A completely different visual language — warmer, simpler, emoji-led, nothing to manage.
User Flows
Flow 1
Creating a trip
From opening the app through inviting the group and setting access tiers.
Flow 2
Proposal to Active
How a proposed item moves to Active — including the fork path when the group disagrees.
Flow 3
Forking the itinerary
Creating a fork, running it in parallel, and rejoining the main plan.
Flow 4
Task lifecycle
From noticing a gap through someone volunteering — and what happens when nobody does.
Who Booked This? — Rae Wree May 2026