Feedzy
The YouTube production workflow, stage by stage
Every consistent channel runs on some version of the same pipeline, whether it's written down or living in the creator's head. Here is that pipeline: six stages, who owns each one, and where it usually breaks. It's the same structure Feedzy is built around, but the framework works no matter what tools you use.
Why a defined workflow matters
A channel posting once a month can run on vibes. A team posting weekly can't. Once more than two people touch a video, three questions decide whether production is calm or chaotic: where is every video right now, who is responsible for the next step, and what does "done" mean at each stage. A defined workflow answers all three before anyone has to ask.
The six stages
1. Ideation
What happens: Raw concepts get captured with references, inspiration, and early discussion. The team weighs in before anything is committed to script.
Who owns it: The creator or strategist, with input from everyone.
Where it breaks: Ideas scattered across notes apps, voice memos, and chat messages, so the good one from three weeks ago is gone. What fixes it: a single intake point where every idea lands with its references attached.
2. Scriptwriting
What happens: The idea becomes a script. Drafts, comments, revisions, and a clear approval.
Who owns it: The scriptwriter. The creator approves.
Where it breaks: Feedback split between the doc's comments and a chat thread, so nobody knows which version is current or whether it's actually approved. The fix is inline comments tracked as open or resolved, and an approval that formally moves the project forward.
3. Filming
What happens: Footage gets shot, uploaded, and organized so the editor can find everything.
Who owns it: The creator, plus whoever manages files.
Where it breaks: Footage dumped into a Drive folder with no naming convention, so the editor spends the first hour of the edit just finding things. Attaching files to the video project itself, labeled, makes the handoff instant.
4. Video Editing
What happens: Rough cuts, feedback rounds, revisions, and a locked final version.
Who owns it: The editor. The creator or producer reviews.
Where it breaks: Vague feedback. "Tighten the middle" produces another vague cut and another round. The fix is timestamped comments that point at the exact moment, so one review round does the work of three.
5. Packaging
What happens: Thumbnail and title get made, reviewed, and approved. On serious channels this gets as much attention as the video, because packaging decides whether the video gets a chance at all.
Who owns it: The thumbnail designer and whoever writes titles, with the creator approving.
Where it breaks: Feedback arrives as words about an image. "Make the face bigger and the text pop" means five different things to five designers. Drawing directly on the thumbnail, with every option and comment kept in one place, ends the guessing. External reviewers, like a sponsor who needs to approve their mention, should be able to see it through a single link.
6. SEO & Upload
What happens: Title, description, and tags are finalized, the video publishes to YouTube, and ideally an A/B test starts immediately.
Who owns it: The channel manager.
Where it breaks: This stage lives entirely inside YouTube Studio, so it's disconnected from everything before it, and only people with Studio access can do it. And after upload, most teams stop. The channels that grow treat upload as the start of packaging optimization, not the end of production: test the thumbnail, test the title, keep what the data picks.
After upload: close the loop
Two things separate teams that improve from teams that repeat themselves.
Test the packaging. Run the alternative thumbnail you argued about. Real traffic settles the argument in days, and the winning version stays on the video.
Keep the record. Which thumbnails won, which titles won, by how much. Over a year that record becomes the most valuable strategy document a channel has, and it only exists if results live somewhere permanent instead of in a tester you cancelled.
How A/B testing works in Feedzy: YouTube thumbnail & title A/B testing
Running the whole thing in one place
You can run this workflow across Notion, Drive, Docs, Slack, a review tool, and a thumbnail tester. Plenty of teams do, and the seams between those tools are exactly where the breakdowns above happen.
Feedzy is this six-stage pipeline as a product: each stage is a column on the board, feedback lives on the work, files live on the project, and upload and testing happen in the same place as everything else.
