Travel Problem Solved

Read the campaign story

KAYAK used Travel Problem Solved in owned content by September 2015. Contemporary reporting describes Travel Hacks films by The Adventures Of that connected planning problems with tools such as Price Forecast and Explore. The creative contrasted unhelpful advice with a practical function rather than relying solely on scenic travel imagery.

Cut+Run documents a September 2016 continuation by The Martin Agency, directed by Benji Weinstein and edited by Frank Effron. It imagined the usefulness of travel-search capabilities in other everyday decisions. These related expressions remain one family. The sources establish activity by 2015, but not a definitive first launch date; the catalogue year is therefore unknown rather than inferred from a later agency appointment.

Editorial interpretation: a tool becomes more understandable when it is attached to a question someone already asks. A feature name alone may require prior category knowledge. A small comic problem gives the demonstration a purpose and helps the audience remember when the function might be useful. The creative should return to the actual tool quickly enough that viewers do not remember only the absurd advice or unrelated situation.

Editorial interpretation: solving a planning problem is narrower than guaranteeing a successful trip or the lowest possible price. Predictions depend on available information and can be wrong. A responsible adaptation should preserve that uncertainty while making the interface easier to understand. Confidence in using a tool is not the same as certainty about its output, and a campaign that blurs the distinction may create avoidable disappointment despite being entertaining.

Start from a decision rather than a feature list

Ask what the user needs to decide at a particular moment, then choose the feature that genuinely informs that decision. Limit each execution to one relationship so the explanation stays legible. A broad promise of making life easier is difficult to test, while a specific question can be followed through the interface. This also makes it easier to identify claims the tool cannot actually support.

Use analogy without importing false capabilities

An everyday analogy can make a technical function feel familiar, but it may also suggest powers the product does not have. Identify the exact similarity and the important differences before writing the joke. After the analogy, show the real interaction and explain its limits. Test whether people can distinguish a helpful estimate from a guaranteed answer rather than assuming the disclaimer corrects every impression.

Evaluate understanding before conversion

A click may indicate curiosity about the joke rather than comprehension of the feature. Ask participants to explain when they would use the tool, what information it needs and what uncertainty remains. Observe whether they can complete a relevant task in a prototype. This gives the team a stronger diagnostic than an isolated engagement rate and helps prevent an entertaining campaign from teaching the wrong mental model.

A small test for another brief

Proposed adaptation: storyboard a fictional timetable-comparison tool using one humorous planning dilemma, followed by a plain demonstration of the same function.

Measure correct task completion, understanding of uncertainty and inappropriate reliance on the estimate. Compare these with recall of the joke, and review whether the analogy helps people recognise the right use occasion without overstating the tool’s authority.

Stop if viewers infer guaranteed prices or outcomes, or if the test requires real travel documents, payment details or sensitive personal information.

• Use invented schedules and no real booking or payment.
• Explain assumptions and show an example where the estimate changes.
• Keep the comic and functional versions equivalent in factual content.