Skip to content
Luxury TravelTailwind

Charlotte had it handled. The client couldn't see it.

Fifteen games and a travel app built around one finding: the care was exceptional and the evidence of it was invisible.

15Games
2/7Delight on entry
Tailwind journey screen
Tailwind seat screen
The brief

The care was exceptional. The evidence of it was invisible.

Tailwind has looked after private clients for eleven years, entirely through referral. Each one has a named travel partner who rebooks the connection before the delay is announced. None of that work reached a screen. The journey lived in a WhatsApp thread, a forty page PDF and a portal most clients had stopped opening. The brief was to find where the proof went missing, and how to show a tailwind without handing the load back.

01
A client of nine years stood in a hotel corridor in Zurich at 11.40pm, coat still on, scrolling through three sources. Charlotte had fixed everything twenty minutes earlier. "Charlotte had it completely under control. I just couldn't see that she did."
02
Delight scored 2 out of 7, and nearly all of it came from people. Trust in the artefacts stayed conditional, so clients quietly compensated by scanning, calling and checking. That vigilance was the thing the product existed to remove.
03
The right voice already existed. The portal said, "Important update: Your itinerary has been modified." Charlotte's midnight voice note said, "Go and have dinner." The product had never been asked to carry the second one.
The process

Four sessions. Fifteen games. One gap, seen from every side.

The First 60 Seconds and both Aspiration Gap sessions found the same reflex. Clients open the app already scanning, asking whether Charlotte knows. The Funeral Speech named the cost with one story from Zurich. The Heartbreak Scale put numbers against it, with delight at 2 out of 7.

Core PrinciplesThe Heartbreak Scale™75 min
DiscoveryThe First 60 Seconds™45 min
DiscoveryThe Aspiration Gap™60 min
DiscoveryThe Aspiration Gap™60 min
DiscoveryThe Identity Shift™30 min
Brand PersonalityThe Dinner Party™15 min
Brand PersonalityThe Rejection Letter™15 min
Brand PersonalityThe Funeral Speech™60 min
Design PrinciplesDesign Principles Builder™45 min
Design PrinciplesThe Anti-Principles™20 min
Tone & CopyThe Voice Sort™40 min
Tone & CopyWrite It Wrong™30 min
Tone & CopyThe Word Sort™15 min
Visual DirectionOpposite Ends™10 min
Visual DirectionMoodboard Speed Dating™15 min
"World class." "Concierge grade." "Seamless." "Stress free." "Premium." "Bespoke." Every one landed on the wrong pile. The words that belonged were plainer: confirmed, expected, usually, done.
Output 01: Strategy & Brand

From does Charlotte know to I have someone for that.

Three documents carried the strategy. The Feel Factor mapped how the app should feel across three layers, and why the first two seconds matter most. Tone and Copy turned a voice that already lived in Charlotte's midnight notes into rules a writer can follow. Interaction Principles set how the product behaves, so stillness reads as a promise.

The Feel Factor®
The Feel Factor

The Feel Factor®

Three layers: first impression, the journey and identity transformation. Mapped from the tired competence clients arrive with to the feeling of being accompanied.

The first screen answers the question every client arrives with. "Nothing needs you. Checked at 5.52." is a complete, valid first screen, and nothing else has to appear above it.
Every fact carries its own status and timestamp. A line without a time beside it is a claim. A line with one is evidence.
The shift isn't from worry to relief. It's from the person who holds everything to the person who has chosen, confidently, to put it down.
Download document →
Tone & Copy
Brand

Tone & Copy

Seven qualities held in tension, and seven registers the voice never enters. Specific without being clinical, calm without being detached, discreet without being opaque.

Use only what the client has told you. "We noticed you often travel on Thursdays" reads as care and lands as an alarm for a private client.
Certainty is earned sentence by sentence. Confirmed, expected, usually and next update by are in. Always, never, seamless and guaranteed are out.
Brief without being curt. "Flight cancelled, contact support" is short and alone. "Your 7.40 was cancelled. Charlotte has moved you to the 8.15, same seat." is four words longer, and completely different.
Download document →
Interaction Principles
Design

Interaction Principles

Six principles for how the product behaves: pace, feedback, transitions and stillness. Interaction is where brand intent either holds or quietly collapses.

Status lines arrive already resolved. Loading that performs effort asks the client to watch, when the whole promise is that they can stop.
Motion carries meaning or it stays still. When "Charlotte is rebooking you now" becomes "Done. You're on the 9.15, same seat," the new line arrives in place. Nothing sweeps or bounces.
An alert that changes nothing trains the client to check every alert. The rarer the buzz, the more it means.
Download document →
Plus 8 more documents in the full engagement
04
Research & Strategy
Research & Insights Report
05
Research & Strategy
The Aspiration Gap
06
Research & Strategy
User Personas
07
Research & Strategy
Emotional Journey Maps
08
Design
Design Principles
09
Brand
Visual Direction
10
Brand
Copy Handbook
11
Design
Animation and Interaction Guide
Output 02: The Design

Five screens, one named partner.

From the first open, to the journey card that says Charlotte has this, to a seat held on a client's usual preference. Tap through the screens below.

Original
WAA
Output 03: Technology

A build that proves the screen is honest before anything else.

Native on both platforms, chosen so the lock screen never gives anything away. Twenty six weeks across four phases, sequenced by emotional dependency, with the confidence model first. The handoff keeps the design intent intact once the build team starts solving local problems.

Tech Stack Recommendations
Technical

Tech Stack Recommendations

Native Swift and Kotlin, NestJS on Node.js, PostgreSQL and Redis, with the trade-offs named. Every choice was held against the product, the team and long term maintenance.

Native over cross platform for one reason: the lock screen. A notification extension strips each payload to "Your car is ready" before it displays. No name, destination or companion ever appears in a preview.
The iOS client renders a finished, attributed status object and never assembles its own view of the journey. "Confirmed by Michael at 5.40" has to have been confirmed by Michael at 5.40.
PostgreSQL over a document store. Household privacy is a relational problem, and a schema that can hold anything tends to drift towards holding everything.
Download document →
Developer Handoff
Delivery

Developer Handoff

Not a functional specification. It holds the emotional intent behind decisions that might look arbitrary, the constraints that cannot be traded away under deadline, and the criteria the build is judged against.

A disruption status line reaches the client within three minutes, naming the person dealing with it and the time of the next update. Charlotte sends it in a single tap, because honesty has to be cheaper to produce than silence.
Every fact shows its confidence and its age. "Michael is at Terminal 5" when he is at Terminal 3 is worse than showing nothing, because the product gave the client false permission to stop checking.
Acceptance criteria are emotional as well as functional. A reviewer who did not build the product must know within two seconds whether anything needs them, and feel that a person is holding the journey.
Download document →
Plus 3 more documents in the full engagement
03
Technical
Technical Blueprint
04
Delivery
Implementation Roadmap
05
Delivery
Build Cost Reference Guide
The result

A product judged on whether a client can stop checking, not just whether the itinerary is right.

Delight at 2 out of 7 and a client in a Zurich corridor pointed at the same root cause. The care was real and the evidence of it was invisible. The response was a set of rules specific enough to survive a disruption at midnight, in the design and in the twenty six week build plan that protects it.

Evidence before a request
The app opens on Charlotte's name and photograph, with one plain line stating where the journey stands. No menu, no dashboard and no sign in screen between the client and the answer.
Every fact shows how sure we are
Confirmed, expected, pending or stale, each with a time beside it. A client who sees Tailwind admit what it doesn't yet know will believe it on the days it says it does.
Nothing handed back
Handled problems are written in the past tense, with no task for the client. Small asks get the same tone as large ones, and a standing instruction can be given in a sentence and withdrawn in a line.
A build order that protects trust before features
The confidence model first, then disruption and the living itinerary, then the personal touches. The roadmap makes that order a constraint, not a suggestion.
More work

Other case studies