Product launches

One night. You do not get to run it again.

A launch is the least repeatable event you will run all year. Everyone in the room is taking photos, and the difference between a good archive and a thin one is decided in the six hours it is happening.

The night

The stakes are concentrated into one evening.

A season of activations forgives a bad night. A launch does not. The room is full of the people you most want photographed, most of them are being photographed by colleagues rather than by the photographer you hired, and those are frequently the better pictures — less posed, closer, actually showing the room. They are also the ones that never arrive.

Where it goes wrong

  1. The photographer covers a fraction of it.

    One person cannot be at the door, the demo and the toast. Your team can, and is, on their phones.

  2. The best picture surfaces three weeks later.

    Usually in a chat, usually compressed, usually long after the moment it would have been worth posting.

  3. Nobody wants to be chased on launch night.

    Asking twenty colleagues to send you files is the worst possible use of the day after, and it is the reason half of them never get sent.

How it runs

  1. 01

    The week before

    Make the album and send the join code round with the run sheet. Anyone joining the workspace for the first time installs it once.

  2. 02

    On the night

    Nobody is asked to do anything except pick the photos they already took. Seconds, not a task.

  3. 03

    The morning after

    The whole night in one album at full resolution, from every phone in the room, without a single message asking for it.

The best photo of the night is on somebody’s phone and I will never see it.

Get the whole launch, not the photographer’s slice of it.

Related

What teams like this look at next