Briefing
Episode 32 · Primer and discussion · About 13 minutes
Download the MP3 · Linda and Leonard, AI voices, read a script written from the sources below.
Download the MP3 · Linda and Leonard, AI voices, read a script written from the sources below.
Written from the episode and public sources, checked on 10 November 2026. The use cases are the host's suggestions, not case studies, and the Google figures are Google's own. Check the originals before quoting.
Before we record, every claim the hosts make is checked against the sources (this table was last updated 10 November 2026). Confirmed means a primary source or two independent reports; Reported means one party says so; Partly right, Disputed, Unverified and Not yet known mean what they say, and the hosts say so on air. This is the table as we left it.
Sign up for our podcast at agile-insights.com.au.
Linda Here is the idea for today. Making a short, edited video at work has become cheap enough to be worth doing, because the same AI agents that write code can now edit footage and build animation. That changes who makes video, and it means a video pipeline should be governed like any other piece of software. By the end of this primer you will know what has changed, when a video beats a document, and the few controls that keep a cheap video honest.
Leonard So this comes from an episode of The AI Daily Brief on the eighth of November. The host, Nathaniel Whittemore, makes a comparison that a lot of people in technology will recognise. About a year ago, a coding model got good enough that people who could not code started building working software. He thinks the newest models are doing the same thing for video. What actually changed, though? Video editing has had clever tools for years.
Linda He lists eight changes, and three of them do most of the work. The first is that editing became a conversation. You can ask an agent to find the best takes, trim the pauses, place some supporting footage and assemble a first cut, inside the coding tools people already use. The second is that a model can now watch footage. Google published a feature in September where the model decides which parts of a long video to look at, and at what speed. Google says it uses up to eighty eight per cent fewer tokens and is up to seven per cent more accurate, with the biggest gains on recordings that run for hours. Those are Google's own figures, and nobody has tested them independently yet.
Leonard And the third?
Linda The third is animation. A coding agent can now write an animated video as code, using a library called Remotion, and render it to a file. That matters because animation explains dense information well, and because code can be re-run. The host says that on his own projects, animation has worked much better than video generated from a text prompt, which can still look slightly wrong. So the cheap, reliable kind of AI video is not a model inventing footage. It is real recordings, real voices and real data, with the agent doing the editing and the graphics.
Leonard That is a useful line to draw. But cheap does not mean wanted. Nobody needs more video in their week. How does he decide when a video is actually the right format?
Linda He gives six signs, and they make a good test. Video beats a document when showing beats telling, like a new screen or a number changing between quarters. When the audience will not read the document. When you keep giving the same explanation. When it has to work in several languages. When the recordings already exist. And when you need conviction to land without being in the room yourself. His sharpest point is about the audience. Busy executives, frontline teams and customers will not read a wall of text, and that is a fair reading of their week, not a judgement about them. If none of the six signs apply, write the document.
Leonard Fair enough.
Leonard Then here is where it gets interesting for anyone who looks after AI in an organisation. He describes three levels. At level one, the agent edits footage you already have, like a highlight reel from a long meeting. At level two, it makes something new, like last quarter's results as an animated chart. At level three, it runs a pipeline, say a two minute update every Friday built from metrics and tickets. And he puts it neatly himself: a video is a video, but a pipeline is an application that makes videos. That is the governance moment, isn't it?
Linda It is. Once something publishes on a schedule without a person pressing the button, it is software, and it needs what software needs. A named owner. A check on what it says, especially the numbers, because a video is believed faster and checked less than a document. People skim a report twice, but almost nobody re-watches a video to check a figure. So the numbers should come from a fixed set of data, and the run should stop if the script says something different. Every frame should carry the date the data was taken. And there should be a record of which version said what, so that if the figures are restated, you can find the old videos and pull them.
Leonard Mm. That is the bit that matters.
Leonard And people. A lot of these use cases put real faces and voices on screen, and some of them are copies of people rather than the people themselves. Where does consent come in?
Linda That is the second control. If you make an avatar or a voice copy of a staff member, get recorded consent, say what it can be used for, and decide what happens when that person leaves. Microsoft already requires a recorded consent statement before it will build a custom avatar. If you cut a heated meeting into a short video for people who missed it, tell the people in it before it travels. And put a short line at the end saying the video was made with AI and who reviewed it. In Europe, rules on disclosing lifelike AI content have applied since August this year, so the habit will be expected anyway.
Leonard So the practical starting point is small...
Linda Very small. Pick one explanation you keep giving, and try level one or two on material that is not confidential. Use the six signs to decide whether it should be a video at all. Before anything reaches level three, give it an owner, a number check, consent for every face and voice, and a date to be remade or retired. In part two, we look at the use cases themselves, and where the risk really sits.
Linda The idea again, briefly. AI agents can now edit footage, watch recordings and animate data, so a short video at work costs very little to make. The risk moves from making the video to trusting it. In this part we take the use cases from The AI Daily Brief on the eighth of November and ask which ones to try first, and which ones need a decision before anyone builds them.
Leonard A quick recap for anyone who skipped part one. The host's three levels are: the agent edits footage you already have; it makes something new, like an animated chart; or it runs a pipeline that publishes on a schedule. His six signs say when video beats a document, and the strongest is simply that the audience will not read the document. The controls we described were an owner, a number check, consent for faces and voices, a disclosure line, and a date to remake or retire the video.
Linda So let me start with the use cases I would try first, because they are low risk and they teach you the tools. The how-to video for a new screen or a new process is the obvious one. It is the same explanation, given again and again, which is one of the six signs, and nothing in it is confidential. Then the explainer for something hard, like a pricing model. The host suggests talking it through with the AI, asking for a better structure, then animating that. And the handoff video, when someone is leaving or going on leave. Talking for twenty minutes is faster than writing a handover document, and the successor gets the reasons, not just the steps.
Leonard I agree with all three, and the handoff one is quietly important. Knowledge walks out the door at every transition, usually because the person leaving is overloaded until their last day. But I would put the meeting video in a different bucket. The host's example is a meeting where a decision was argued hard, and he says a short cut of the actual exchanges serves the people who missed it better than minutes. I can see that. But a cut is an edit, and an edit is a point of view. Choose which ninety seconds of an hour to show and you have chosen whose argument sounds stronger. Minutes get agreed. A clip just travels...
Linda That is fair, and I would not drop the use case, I would change who signs it off. The chair of the meeting, or whoever owns the decision, approves the cut before it goes anywhere, and the people in it know it exists. That is the same rule you would apply to minutes, just made explicit because the format feels more like evidence. Video carries a kind of authority that text does not. When you see someone say it, you believe that is what happened, even when the edit left out the reply.
Leonard Then the exec pre-read. The host's line is that it assumes nobody reads the pre-read, which got a laugh from me. A strategy paper or business case turned into a short video for leaders who have to get up to speed fast. My worry there is different. A video is linear. You cannot skim back to the assumptions table, and a board member who would have spotted the weak number on page six now hears a confident voice go straight past it. So I would only do it as a companion. The video gets people into the paper. It never replaces the paper, and the numbers in it come from the paper, word for word.
Linda Always page six.
Linda Agreed. Two use cases I would hold back until there is a governance decision. The first is personalised sales video. The host's example is one base video turned into twenty or thirty versions, each with the prospect's own name and numbers. Each is a separate claim to a customer. If one carries the wrong figure, that is a misstatement with your logo on it. So every version goes through the same number check as the base, and someone owns the template. The second is the avatar. The host says avatars and dubbing already pay off inside companies, especially for translation, and I believe that. But a lifelike copy of a real employee needs recorded consent, a written scope, and a rule for what happens when they leave.
Leonard The last one is my favourite and the riskiest: the video that updates itself. How-to videos and process guides rarely got made because footage goes stale in three to six months. The host says an agent can now re-gather the material, update the script and re-render on a schedule. That turns a stale video into a maintained one, which is genuinely good. It also turns it into a system nobody is watching. A process video that quietly updates itself after a policy change, with a small error, will be followed by everyone who trusts it.
Linda That one worries me too.
Linda So where does the evidence settle? The capabilities are real. The model watching video comes from Google's own announcement, with its own figures, and the animation tools are documented by their makers. What is not known is how often these pipelines get things wrong once they run unattended, because nobody has published that yet. The use cases are the host's suggestions, not case studies. So treat this as an invitation to experiment, not a proven method.
Leonard Which gives us the to-do list. Use the six signs as an intake test, so video only gets made where it beats the document. Start at level one or two on material that is not confidential. Before anything runs as a pipeline, put it on your list of AI systems with an owner, and make the run stop if a number in the script does not match the source. Stamp the date of the data on every frame, and keep a record of which version said what. For any real face or voice, get recorded consent and an exit rule. And end every video with a line saying it was made with AI and who reviewed it.
Linda If you'd like to know more, sign up for our podcast at agile-insights.com.au.
Leonard Thanks for listening.
Every episode tagged #oversight
All of the briefings (38) · Follow Briefing in Apple Podcasts or any podcast app
Everything from Agile Insights: briefings, Making You Think and the reference series