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 healthy when every video is marked nearly done, yet none can leave production. One lacks a permission record, another needs narration and a third has never been watched as an export.
Replace vague progress labels with the next handoff. “Ready for edit” says something concrete if the script and required assets are available. “Ninety per cent complete” may hide the hardest remaining decision.
The board's job is to reveal where work stops moving. It should help you choose the next action, not merely display how busy everyone has been.
Which Stages Are Worth Having?
This author-created board is designed for a fictional channel making short explanations of 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 if you work alone. Combine research and writing when they form one handoff. Do not merge review with assembly just to make the board appear shorter; they answer different questions.
How Does A Filled Batch Expose The Bottleneck?
Here is a fictional snapshot, with no performance claims:
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 |
Starting four more scripts will not fix the diagram or reveal the samples' materials. The board suggests a more useful choice: finish the small review correction, then assemble the asset-ready item while the research question is resolved.
This is a capacity decision, not a universal rule to finish the shortest task first. An urgent factual correction or a time-sensitive release can take priority even when it requires more effort.
What Does Someone Need To Resolve A Blocker?
Write the missing decision or material, who can supply it and what happens if it remains unresolved. “Waiting” has no direction. “Waiting for the owner to confirm whether the supplied photo is authorised; use our own photo if not” gives the team a path.
Distinguish a true dependency from work you simply have not started. “Waiting for edit” is queued work when the editor has everything needed; a missing source asset makes the task blocked.
Keep the handover precise: https://dreamwild.ai/guides/editor-handover-brief/
How Should You Limit Work In Progress?
Choose a limit that fits your actual review capacity. If you can carefully review only two exports in a session, producing many more may create a queue rather than a finished batch.
Treat the limit as an adjustable operating choice. When the board repeatedly stalls at one stage, inspect that stage's requirements. You may need a clearer brief, earlier permissions work or a less elaborate visual plan.
Measure the effort before buying more capacity: https://dreamwild.ai/guides/track-shorts-production-time/
What Counts As The Last Stage?
Define it according to the promised deliverable. A completed export, a private review upload and a verified public release are different outcomes. Use names that keep those distinctions visible.
For DreamWild's current integration, the delivery outcome is limited to private uploads pending audit approval; it does not currently promise public or unlisted posting. Keep any separate native YouTube release task explicit.
Source: DreamWild Terms. Accessed 2026-10-03. https://dreamwild.ai/terms
At the batch review, count the accepted outcomes and the unresolved work separately.
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.
Your next step
Put the idea to work.
Use this board to plan the production capacity you want to build with DreamWild
Explore the production workflow https://dreamwild.ai/scale-youtube-channel/