Organising a Small Team Around One Channel
Organising a Small Team Around One Channel
Small teams stall when roles are implicit: everyone comments on everything and nobody holds the final call. The fix is one owner per video who decides, writing and review separated in time rather than overlapping, and a script that lives in one place everyone can see instead of copies passed around in chat threads.
Where small teams stall
A team of two to five people doesn't need a management hierarchy, but it does need clarity. Three failures recur: multiple script versions with no way to tell which is current, conflicting reviews with nothing to settle them, and work halting because each person is waiting on someone else's reply.
Rule one: one owner per video
Every video has one person responsible for getting it finished, holding the final call on disagreements. This doesn't mean they write it alone — it means that when two notes conflict, they decide. The absence of this rule is what stalls small teams most, because discussion continues with no natural end.
Ownership can rotate between team members from video to video. What matters is that it's known before work starts rather than contested during it.
Rule two: separate writing from review
Writing and reviewing at the same time produces muddled text. The practical order:
- First draft: one person writes without interruption, even if it comes out incomplete.
- Review: the others read and comment within a set window, once rather than in dribs and drabs.
- Resolution: the owner decides what's taken and what's left, and revises.
The common mistake is commenting on a script before the draft is finished, so the writer spends their time defending rather than writing.
Rule three: one source of truth
The biggest hazard for a small team is version sprawl: one copy in a chat, another in email, a third on someone's laptop. The rule is that the script lives in one place everyone opens, and every edit happens there rather than in a forwarded copy.
The project structure serves this directly: each video is a project holding the script, research notes, and related episodes, as covered in Managing Content Production Projects: Organise Ideas and Scripts in One Place with Bardiyah.
Splitting roles in a team of three
| Role | Responsibility | What they don't do |
|---|---|---|
| Video owner | Final call, the idea, the script | Doesn't wait for consensus |
| Camera | Visual execution and the shot list | Doesn't rewrite the script on location |
| Editor | Pacing and the final build | Doesn't add a message nobody agreed on |
This table is a reference, not a rigid template. What matters is that each person knows where their decision ends and someone else's begins.
One weekly meeting is enough
A short weekly meeting covering three things only: what's finished, what's stuck and why, and what the next video is. Everything else gets settled in writing. Small teams that meet daily are usually compensating with meetings for a lack of clarity about roles.
When the team grows
These three rules hold up to about five people. Beyond that you'll need explicit status stages (idea, drafting, in review, ready to film) because tracking them mentally stops working. Scheduling those stages is covered in Planning YouTube Content from Idea to Publish: A Practical Guide with Bardiyah.