Dear Sophie

Read the campaign story

Google Chrome’s Dear Sophie turned a browser advertisement into a story about a father preserving memories for his daughter. By early May 2011, contemporary coverage described the film’s emails, photographs and videos as a record of her growing up. The One Club archive credits BBH New York and Google Creative Lab. This case concerns that original film within The Web Is What You Make of It, rather than later local adaptations.

The Next Web reported the commercial on 4 May and identified Gmail, Picasa and YouTube among the services shown through Chrome. That distinction is essential: the emotional use case spans Google’s services, rather than demonstrating a browser-exclusive capability. The creators’ Supermarché portfolio also preserves the film. These records verify the execution and campaign context, not the family story as documentary fact or the film’s isolated contribution to browser downloads.

Editorial reading: The interface becomes a way to show care. Typing, attaching and saving are ordinary actions, but the father’s purpose gives them accumulated meaning. Each small action contributes to something a future recipient will experience. This is a useful alternative to a feature tour: a coherent personal goal can make otherwise separate functions understandable as parts of one activity, without requiring the audience to remember technical terminology.

The time structure is especially instructive. Most software demonstrations end when the task succeeds. Here the task’s value lies partly in a later moment, when someone can encounter what has been preserved. A team can use that principle for less intimate scenarios too: documenting a project, preparing a handover or collecting a shared history. The story should make the future benefit clear without promising that a service will exist unchanged forever.

A responsible adaptation must account for what the warm narrative leaves outside the frame. Digital memories involve access permissions, backups, export options and the wishes of the people represented. A historical advertisement is not current guidance on opening accounts for children or storing their information. For demonstration purposes, invented adult profiles and licensed or synthetic sample material can communicate the mechanism without exposing a real family’s private life.

A small team could show one meaningful goal completed through a short sequence of genuine product actions. Remove every interface detail that does not advance the goal, but retain enough to show which service supplies each capability. Test both emotional comprehension and accurate feature attribution. If people love the story but believe the product offers functions it does not provide, the demonstration needs repair. The transferable lesson is purposeful software storytelling, not sentiment detached from technical truth.

Give the workflow a recipient

Show who benefits from the completed activity and why that future moment matters.

Keep capability ownership clear

Distinguish the browser, connected services and storage features so the story does not create a misleading product promise.

Protect the memories behind the demo

Use fictional or properly licensed sample material and explain relevant access and retention limits.

A small test for another brief

Demonstrate a useful project archive using fictional adult profiles and sample material.

Assess goal recall, correct capability attribution and successful completion of a small trial workflow.

Stop if viewers infer unsupported features, permanent retention guarantees or permission to expose private family data.

• Choose one meaningful future recipient and a realistic task.
• Capture only genuine actions, identifying which connected service supplies each feature.
• Test the story and feature attribution with viewers unfamiliar with the product.