One Script and Three Opinions
Three friends agreed to make a channel together.
One of them wrote the first draft and sent it to the group chat.
The second replied with notes, and the third replied with notes contradicting them on two points.
So the writer revised according to the second person's view and sent a new version. Then the third said the first version's opening was better.
A week later there were four versions in the chat, and nobody knew which was the latest.
Two weeks later, nothing had been filmed.
And there was no real disagreement between them, nor was anyone slacking. The problem was that nobody owned the decision, so the discussion had no natural end.
Where a Small Team Gets Stuck
A team of two to five doesn't need a management structure, but it does need clarity.
The recurring faults are three: multiple script versions with no known latest, conflicting reviews with no arbiter, and work stalling because everyone is waiting on someone else's reply.
All three converged at the top of this article.
Rule One: One Owner per Video
Every video has one person responsible for getting it to the end, with the final say in 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 has no natural end.
Team members can rotate ownership between videos. 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's incomplete.
- Review: the others read and comment at a set time, once rather than in instalments.
- Resolution: the owner decides what's taken and what's left, and revises.
The common mistake is commenting on the script before the draft is finished, so the writer spends their time defending rather than writing.
Rule Three: One Home for the Truth
The most dangerous thing facing a small team is multiple versions: one in a chat, another in an email, a third on somebody's laptop.
The rule is that the script lives in one place everyone opens, and any edit happens there rather than in a copy.
A project structure serves this directly: every video is a project, containing the script, the research notes, and the linked episodes, as explained in: managing content production projects.
Splitting Roles in a Team of Three
| Role | Responsibility | What they don't do |
|---|---|---|
| Video owner | The final decision, 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 final assembly | Doesn't add a message nobody agreed on |
The table is a reference, not a rigid template. What matters is each person knowing where their decision ends and someone else's begins.
One Weekly Meeting Is Enough
A short weekly meeting reviewing three things only: what's finished, what's stalled 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
The three rules hold up to five people.
Past that you'll need explicit status stages (idea, being written, in review, ready to film), because tracking them mentally becomes impossible. Planning the timeline for these stages is covered in: planning YouTube content from idea to publish.