How to Plan a Video With a Client in the Room

Key Takeaways

• Build live, do not present. A plan assembled in front of the client is a plan they own.
• Agree the single objective before any structure. Sessions fail on unstated disagreement about what the video is for.
• Establish what is fixed early, especially budget band and deadline, or you will design something impossible.
• Work in blocks, not shots. Structure is the right altitude for a client conversation.
• Write the scope decision in the room, before anyone leaves.
• Have someone other than the facilitator drive the canvas. Facilitating and typing at once does both badly.

Why a Presented Plan Invites Notes

The instinct is to prepare thoroughly and bring a plan. It backfires for a structural reason.

A finished artifact asks for a verdict. When you present a completed plan, the only role available to the client is critic, so they criticise. This is not obstruction; it is the role the format handed them.

A plan built in front of them offers a different role. They become a participant, and people do not send notes on things they helped make. The same client who would have returned two pages of comments on a document will spend ninety minutes building something with you and approve it at the end.

The second reason is speed of correction. In a live session a misunderstanding is caught in thirty seconds. In the present-then-notes cycle, the same misunderstanding costs a week: you build on it, present, they flag it, you rework.

The trap is the fake workshop. Arriving with a prepared plan and asking for input on it. Clients see through this immediately, and it is worse than an honest presentation because it wastes their time and yours while pretending to be collaborative.

A useful diagnostic: if you could send the artifact instead of holding the meeting, you are presenting, not planning.

Prepare Structure, Not Content

You should still prepare. Prepare the frame, not the answers.

Set up the canvas with empty regions labelled for what the session will produce: objective, audience, constraints, structure, look, next steps. Empty regions do most of the facilitation for you, because a visible gap is an invitation.

Prepare three or four examples of formats or approaches that might fit. Not proposals: reference points, to give the conversation vocabulary. Clients often cannot describe what they want and can reliably point at something and say more like that.

Write your own questions in advance. The ones you need answered to make the video: who is this for, what do they currently believe, what do we want them to do, where will it play, what has been tried before. Having them written means you get through them even when the conversation wanders.

Know your constraints. What you can deliver in the time and money likely available. You will need this in the room, and looking it up mid-session cedes control of the conversation.

The Session

Ninety minutes to two hours. Longer and the client's attention degrades and decisions get made badly at the end.

The one thing (15 minutes)

Agree, in one sentence, what the video must achieve. Write it at the top and leave it there.

Push for specificity. "Raise awareness" is not an objective. "Get finance directors at mid-size firms to believe this is not a six-month implementation" is.

This is where the session earns most of its value, because it is common for two people on the client side to want different things and to have never said so out loud. Surfacing that in minute ten saves the project. Discovering it at the first cut costs a reshoot.

If the room cannot agree the objective, stop. Do not proceed to structure. An unresolved objective produces a video that fails for reasons nobody can articulate.

What is fixed (15 minutes)

Deadline, budget band, mandatory inclusions, brand rules, who must approve, anything already promised to someone.

Ask about budget explicitly. People avoid this and then design something unaffordable, which means a second session to take things away, and taking things away permanently frames you as the person removing the good ideas.

You do not need a number. A band is enough: is this a one-day shoot or a three-day shoot.

Build the structure (45 minutes)

Now build, in blocks.

A block is a chunk of the video with a job: the hook, the problem, the demonstration, the proof, the ask. Five to eight blocks for most videos. Write each as a card with its job, and arrange them.

Blocks, not shots. Shot-level conversation with a client is the wrong altitude: it invites opinions about details before the shape is agreed, and it takes far longer. Structure is a conversation a client can genuinely contribute to.

Move them around. This is the part that only works live, and it is the part that makes the session feel collaborative. Try the proof before the demonstration. Try opening on the customer instead of the product. The client sees the alternatives and chooses, which is a completely different experience from being shown one order.

Attach the references as you go. When someone says they want it to feel a particular way, put the reference on the board next to the block it applies to.

Mark the unknowns. Anything the room cannot decide gets written as an open question with an owner and a date, rather than being resolved by whoever is most confident.

Scope and next steps (20 minutes)

Convert the structure into a scope decision while everyone is present.

Say what this means in days. "This structure is a two-day shoot with two locations, or one day if we lose the customer segment." Real numbers, in the room, while the trade-off is still live.

Get the decision now. Which version are we making. A scope decision deferred to email takes a week and arrives without the context that made it easy.

Write the next steps with owners and dates. Who provides the customer contact, who confirms the location, when the script draft lands.

Running It Well

Two people from your side. One facilitates, one drives the canvas. Doing both means the facilitator is looking at a screen instead of at the room, and the conversation dies.

Do not defend. If the client proposes a structure you think is weaker, build it on the board next to yours and compare. Seeing both is more persuasive than arguing for one, and if theirs is better you have learned something.

Watch for the quiet person with authority. Frequently the most senior person speaks least and approves later. Ask them directly for their view before the session ends.

Send the board, not a write-up. Within the hour, while it is fresh. The board they helped build is the record. A tidied document reintroduces the present-then-notes cycle you just avoided.

What Goes Wrong

Arriving with a finished plan. The client becomes a critic and behaves like one.

Skipping the objective. Or accepting a vague one, so the disagreement surfaces at the first cut.

Not asking about budget. Designing something that has to be dismantled later.

Working at shot level. Slow, and it invites detail opinions before the shape exists.

One person facilitating and typing. Both done badly, and the room disengages.

No decision in the room. The session's value evaporates over the following week.

Sending a polished document afterwards. Turns a co-owned plan back into a deliverable to be reviewed.

The Bottom Line

Build the plan in front of the client instead of bringing one. Agree the single objective first, establish what is fixed including the budget band, then assemble the structure in blocks and move them around until the shape is right.

Convert it to a scope decision before anyone leaves, and send the board rather than a write-up. A client who watched the plan get built does not send notes on it.