You are watching this as an architect
An operator watches to learn what to do with an item. You are watching to decide where gates belong and who stands behind them.
See the approval mechanism from the governance side: what the gate is, what it records, and what you are deciding when you place one.
This video also appears in the Launchpad track, where the question is what to do when an item arrives in front of you. Here the question is different: where should gates exist at all, who should stand behind each one, and what does the system record when a decision is made.
Watch for the evidence trail specifically. A recorded decision carries who decided what, when, and against what supporting material, and that record is what makes governance in this model demonstrable rather than assumed. It is what you would show someone asking how a decision was reached.
As an architect you need one more thing the video does not dwell on: which decisions the platform records. Completing work, ignoring it with one of five reasons and escalating it to a named person are all durable. So is sign-off. A drafted campaign, a new version of a play, a new analyst question and a drafted artifact each arrive as a review card with three answers (Approve, Request changes and Reject), and the two that are not an approval require a reason, which is stored with the decision. That makes sign-off a control you can design around rather than a step you record somewhere else.
Who can give each answer is a permission, and placing it is part of the design. Campaign sign-off needs marketing:write, play publishing needs revplays:publish, analyst questions need ai_agents:write and artifact reviews need artifacts:write. Decide which roles hold each before you decide where the gates go, because a gate nobody on the team is allowed to answer is a queue that never clears.
The framing to carry into the next lesson is that review capacity is finite and every gate spends some of it. This is not an argument for fewer gates; it is an argument for placing them deliberately, because the alternative is spending the budget uniformly across consequential and inconsequential work alike.
That is what a blanket approval policy does. It looks maximally cautious and produces the opposite: a queue where everything requires a decision is a queue people clear rather than read, so the items that genuinely needed scrutiny received the same three seconds as everything else. The next lesson is about spending the budget on purpose.

Now watch the video
This lesson is the orientation. The material itself lives on its own page, kept in one place so it stays current everywhere it is referenced.
You should be able to answer each of these from memory before opening it. Recalling the answer is what makes it stick; recognizing it when you read it does not.
A record of who decided what, when, and against what evidence. That trail is what makes the governance demonstrable rather than assumed, and it is what you would show someone asking how a decision was reached.
It spends finite review capacity. Gating everything spends that budget uniformly across consequential and inconsequential work, which buys less scrutiny where it mattered, not more.
An operator watches to learn what to do with an item. You are watching to decide where gates belong and who stands behind them.
Who approved what, when, and on what evidence. That trail is the governance artefact. It is what makes the model auditable rather than merely careful.
The next lesson is about spending that budget deliberately — mapping severity to the people who should hold each level.
Explore how agents prepare work across your revenue teams, and how people review it, guide it and decide what happens next. Fictional data. Real product.
Explore the demo