Product design · Dreamable

Designing a platform for
meaningful gifts

Letters To is a platform where users create personalised, time-released letters as lifelong gift experiences. I led the full product design — from user research through to high-fidelity screens — working remotely with a distributed team across San Francisco, Europe, and the Philippines.

End-to-endProduct design

RemoteDistributed team

AgileDelivery

Role: UX / UI Designer
Company: Dreamable · San Francisco
Year: 2016
Focus: Product design · UX Research

Read the case study

Context

The challenge

The product concept was emotionally strong. The risk was that the design would undercut it — too much friction in the flow, too little trust at checkout, no clear way for multiple contributors to coordinate. My job was to design an experience that lived up to what the product was promising people.

Working across three time zones forced a discipline I hadn't fully applied before: every design decision had to be self-explanatory without a call to explain it. If a wireframe could be misread, it would be. That constraint made the work more precise — and the handoffs cleaner than anything I'd shipped with a co-located team.

Emotional product, clear UX

The platform carries emotional weight — gifts and personal letters. The UX had to feel warm and trustworthy without becoming sentimental or unclear.

Multi-participant journeys

Letters could involve multiple contributors writing to a single recipient — requiring clear flows for invitation, coordination, and contribution tracking.

Time-release mechanics

Users needed to schedule letter delivery — selecting dates, setting milestones, and understanding when and how their recipient would receive each message.

Trust at every step

Users were creating something personal and permanent. Any friction or confusion in the flow risked breaking confidence in the platform entirely.

Research

Understanding users

The research question wasn't "what do users want from a gifting app." It was "what makes a gift feel permanent and personal — and what kills that feeling." The answers shifted the design priorities significantly before a single screen was drawn.

People don't remember what they received — they remember how it made them feel

Every interviewee described their most meaningful gifts in emotional terms, not material ones. "It showed they really knew me." "I still read it when I have a bad day." The writing and the timing mattered more than anything physical.

The emotional weight of the moment must be present in the onboarding — not after signup.

Group coordination kills participation

When asked to contribute to shared gifts, people dropped out the moment it felt like admin. Chasing others, unclear deadlines, no visibility of progress — every friction point reduced the chance of completion. Several described abandoning group gifts entirely after one bad experience.

Contributors need a focused, minimal view — only their own task, clearly scoped.

Digital gifts feel disposable unless they feel permanent

Scepticism about digital gifts came down to one thing: "Will it still be there in five years?" Users needed to believe the delivery was reliable and the content was preserved. Trust signals and clear confirmation states were non-negotiable at checkout.

Checkout had to feel like a moment of completion, not a transaction.

The Thoughtful Giver

Values meaning over material — wants gifts that last and feel personal

Goals

Create something genuinely personal for someone they care about
Involve others without the coordination becoming a burden
Trust that delivery will happen at the right moment

Frustrations

Generic gifts that don't reflect the relationship
Coordinating group contributions is complicated
Uncertainty about whether digital gifts feel "real"

Design priorities

Warm, simple onboarding that explains the concept immediately
Clear contribution flow for multiple authors
Visible scheduling — user controls when it's received

Key user flows defined

Create

Onboarding→ Choose recipient→ Select occasion→ Write letter→ Set delivery date

Collaborate

Invite contributors→ Contributors write→ Owner reviews→ Final book compiled

Deliver

Checkout→ Confirmation→ Time-released delivery→ Recipient receives

Process

From wireframes to high fidelity

Structure before warmth. The wireframing phase resolved every flow decision — who sees what, when, and in what sequence — before any visual language was introduced. An emotional product with confused UX would undermine the whole premise.

The biggest wireframe debate was the onboarding: whether to explain the concept up front (longer, educational) or drop users straight into creation (shorter, learn-by-doing). We tested both. The educational path won — users who understood what a "letter book" was before starting completed it at a significantly higher rate than those who discovered the concept mid-flow.

The visual language had one job: get out of the way of the content. These were personal letters — the most emotionally significant thing on the screen. Any decoration that competed with the text was wrong. Restraint wasn't an aesthetic preference here; it was a product decision.

Wireframes

User journey mapped from onboarding through to checkout before any visual design began

High fidelity

Five screens, one seamless journey

Each screen was designed to remove friction and keep focus on what matters — the letters themselves.

Onboarding

One job: make the concept immediately clear. Users needed to understand what a letter book was and feel confident enough to start — without a paragraph of explanation.

Select date

Choosing when a letter arrives is central to the product. The design surfaced occasion prompts to connect the date to a real moment — not just a calendar field.

Layout

Users personalise how their book looks — text-only to photo-heavy. Keeping options clear without overwhelming was the core challenge here.

Composer

Distractions stripped to zero. The writing is the focus. For group books, contributors see only their section until the owner compiles the final version.

05 — Checkout

Completing the gift

The checkout needed to feel like a moment of completion — not a transactional dead-end. A summary of what the recipient would receive, when and how, gave users confidence that something meaningful was about to happen.

Outcomes

What the design achieved

Shipped on time. Usability testing passed. Stakeholder reviews approved first-time. For a distributed team running async across three time zones, those outcomes came directly from decisions made before coding started — documented handoffs, clear specs, and flows precise enough that developers in another timezone never had to ask.

5 / 5

Core flows passed moderated usability testing

On time

Shipped on schedule across three time zones

100%

Management reviews approved first-time

Design quality

High task completion across all five core flows

Onboarding, date selection, layout, composer, and checkout all passed moderated testing — new users completed each without prompting.

Group flows

Multi-contributor flow tested clean

The owner/contributor role separation — one of the hardest flows to design — was understood immediately in testing, with no tooltips or explanation.

Delivery

Parallel development with no sync bottleneck

The documented agile process and detailed handoffs let development in the Philippines proceed without a sync call for every decision.

Stakeholder alignment

Approved first-time in every review

Over-documented rationale removed the back-and-forth with the San Francisco team — every decision arrived with its reasoning attached.

Reflection

Key learnings

Emotional products need extra clarity

The more meaningful a product feels, the less tolerance users have for confusion. Warm design aesthetics don't substitute for clear flows — they amplify them.

Remote teams need over-documented design

Working across time zones and languages meant every design decision had to be self-explanatory. Annotations, rationale notes, and clear handoff specs became part of the design — not an afterthought.

Multi-author flows are complex to simplify

Designing for multiple contributors required clear role separation without making the experience feel fragmented. The key was giving each contributor a focused view — no one saw more than they needed to at any moment.

Agile works if the process is honest

The distributed agile workflow surfaced issues early and kept the team aligned. Regular check-ins and a clear backlog made a complex product manageable across a team that rarely worked in the same timezone.

What Letters To taught me

This was my first full end-to-end product design role — concept to launch, across a distributed team. The experience built discipline in documentation, clarity in remote communication, and a deeper respect for the emotional contracts that personal digital products make with their users.

Designing a platform formeaningful gifts