Intelligent Parking Chair

Read the campaign story

The documented project translates an automotive feature into office choreography. Nissan’s announcement explains that cameras in the room helped establish chair positions and routes. The One Club describes the clap-triggered return and credits TBWA\HAKUHODO, TYO and BIRDMAN. This was a constructed demonstration inspired by vehicle parking assistance, not evidence that an office chair and a production car operate under identical conditions.

Editorial interpretation: changing the object makes the feature easier to notice. People have seen cars park, but chairs quietly arranging themselves violate an everyday expectation. The audience can understand the desired outcome immediately because it has experienced the minor inconvenience being solved. Surprise opens the explanation rather than substituting for one.

The demonstration also creates a risk of overgeneralisation. A controlled room has different obstacles, speeds and responsibilities from a road. An adaptation should explain what the installation demonstrates and what it cannot establish. The strongest lesson is to find an intuitive analogy for a technical benefit while preserving the boundary between showpiece, prototype and available product. View counts or press attention would not by themselves show that viewers understood this boundary or wanted the actual vehicle feature.

One useful editorial check is to remove the brand from the demonstration and ask what category viewers infer. If they think it advertises office furniture, the analogy needs a stronger bridge. Make that bridge explicit without turning the film into a technical manual or overstating similarity between the prototype and a vehicle.

Translate the benefit, not every component

Write the user benefit in ordinary language before looking for a surprising object. The analogy should retain the relevant relationship: something difficult to position becomes easier to place. It does not need to recreate the entire product. List the technical differences that could mislead viewers and decide which need explicit explanation. A short demonstration can be both entertaining and honest when it is precise about its scope. Avoid describing a creative prototype as a product launch unless the object is actually available with support and appropriate approvals.

Let a familiar task reveal the novelty

Choose a situation whose normal outcome the audience already understands. That reduces the time needed to explain what changed. Show enough of the starting state, trigger and result to make the demonstration readable. If the effect depends on hidden support systems, explain those systems in accompanying material rather than implying magic. Test the idea with non-specialists and ask them what they believe the technology does. Their errors reveal where the analogy is too broad, even if they enjoyed the film and can recall the brand.

Plan the proof behind the spectacle

Create a safe, repeatable demonstration protocol before inviting an audience. Document the environment, limitations and failure conditions. Give technical reviewers authority over promotional claims, and separate claims about the installation from claims about the commercial product. For live activations, provide supervision and a way to stop the system. A spectacular successful take is not a reliability study. The communication team should know what happens when the effect does not work, because that response often determines whether curiosity becomes trust or embarrassment.

A small test for another brief

Proposed adaptation: a software team could explain a scheduling feature with an original tabletop animation showing tasks moving into available slots. Use a clearly labelled visual model rather than pretending physical objects are controlled by the software. Pair it with a real screen recording of the feature under ordinary conditions. Ask viewers to describe which part was analogy and which part they could use today. Compare this combination with a conventional feature walkthrough. Keep the example narrow enough that the team can demonstrate exceptions, such as a task that cannot fit. No robotics, public-road tests or unapproved equipment are needed to test the communication principle.

Measure correct feature understanding, recognition of limitations, qualified product interest and recall of the real product rather than only the demonstration object.

Stop if the analogy implies unsupported autonomous capability, if prototype safety is uncertain or if audiences mistake a demonstration for an available product.