Key Facts
- A stage name should describe an observable state.
- A card moves when its exit condition is met.
- Blocked work needs a reason and an owner.
- Count accepted outputs separately from generated drafts.
What Is Wrong With “Nearly Done”?
A batch can look nearly finished while nothing is ready to leave production. One video lacks a permission record, another needs narration and a third has never been watched as an export. A percentage hides those different problems.
Name the next handoff instead. “Ready for edit” is useful when the script and required assets are available. “Ninety per cent complete” tells the editor little about the decision that remains.
Use the board to find where work stops moving and choose the action that will unblock it. A busy-looking board is not the same as a finished batch.
Which Stages Are Worth Having?
Example board: a channel explaining everyday packaging.
Scroll this table sideways to see every column.
| Stage | Entry Condition | Exit Condition |
|---|---|---|
| Ready to research | Viewer question and scope are clear | Evidence sufficient for the planned explanation |
| Ready to write | Research notes identify supported claims | Script accepted for production |
| Ready to assemble | Script and necessary assets available | Complete reviewable edit exists |
| In review | Export and metadata available together | Required corrections resolved and version accepted |
| Ready for delivery | Accepted package and route identified | Destination outcome recorded |
| Outcome checked | Intended result inspected | Learning or follow-up assigned if needed |
Use fewer stages when you work alone. Research and writing may form one handoff. Keep review distinct from assembly, though: producing an edit and deciding whether it works are different jobs.
How Does A Filled Batch Expose The Bottleneck?
Here is the example batch in progress:
Scroll this table sideways to see every column.
| Card | Current Stage | Blocker | Next Action |
|---|---|---|---|
| Why a carton has folding flaps | In review | One diagram reverses the fold direction | Replace the diagram before approval |
| How a resealable strip closes | Ready to assemble | None; required close-up supplied | Editor assembles the accepted sequence |
| Why a sleeve leaves one edge open | Ready to write | None | Write the supported explanation |
| Comparing two box inserts | Ready to research | Materials are not confirmed | Researcher verifies the exact samples |
Four new scripts will not fix the diagram or identify the samples' materials. The board points to a useful sequence: finish the small review correction, then assemble the item whose assets are ready while the research question is resolved.
Choose the sequence that fits current capacity and urgency. A factual correction or time-sensitive release may deserve priority over a shorter task.
What Does Someone Need To Resolve A Blocker?
Give blocked work a route forward. Record what is missing, who can supply it and the fallback if it does not arrive. “Confirm permission for the supplied photo; use our own photo if needed” is a task. “Waiting” is only a label.
Separate a dependency from a queue. If the editor has everything needed, the video is waiting its turn. If an essential source asset is missing, it is blocked. Those states call for different actions.
Keep the handover precise: https://dreamwild.ai/guides/editor-handover-brief/
How Should You Limit Work In Progress?
Match active work to the amount you can review. If a session can support careful review of two exports, producing many more may build a queue rather than a completed batch.
Adjust the limit as you learn. When the same stage keeps filling up, inspect what would help it move: a clearer brief, earlier permission work or a simpler visual plan.
Measure the effort before buying more capacity: https://dreamwild.ai/guides/track-shorts-production-time/
What Counts As The Last Stage?
Define “done” by the deliverable you promised. A finished export, a private review upload and a verified public release are different outcomes. Give them different labels on the board.
For DreamWild's integration, the delivery outcome is an upload with the visibility you approved, which YouTube's processing, policies or account restrictions may still limit or change. Keep any separate native YouTube release task explicit.
Source: DreamWild Terms. Accessed 2026-10-06. https://dreamwild.ai/terms
End the batch review with two counts: accepted outcomes and unresolved work. Both matter when planning the next batch.
Frequently Asked Questions
Do I Need A Separate Column For Every Small Task?
No. Use stages where work passes to the next task or person, and keep smaller actions inside each card.
Should Blocked Cards Disappear Into A Separate List?
Keep them visible enough to influence planning, with the blocker, responsible person and next action attached.
How Many Videos Should Be In Progress?
Choose a limit from your actual assembly and review capacity, then adjust it when the board reveals recurring queues.
Can A Private Upload Count As Complete?
Yes, when that was the agreed deliverable. Name the outcome precisely so it is not mistaken for a public release.
Put the idea to work.
Use the board to plan a batch you can finish. See how DreamWild can fit into the production steps you want to expand
Explore the production workflow https://dreamwild.ai/scale-youtube-channel/