YouTube Episode Workflow

This page defines the standard format for the daily YouTube episodes connected to the 100 Startups Challenge.

The goal is to create a workflow that is practical, repeatable, and fast enough to sustain daily publishing while still showing real product work.

Each episode should document the day from start to finish:

• what startup is being built
• what problem is being solved
• what decisions are made during the session
• what gets shipped by the end of the day
• what lessons should carry into the next day

Format goal

The channel is not meant to be polished in a slow, traditional production style.

It should feel like a documented build session with structure.

The video has to do three things at once:

• show the real execution process
• explain the product and the decisions behind it
• leave behind reusable documentation for future episodes

The target is a video that is:

• clear
• honest
• compact
• useful
• sustainable to produce daily

Episode target

Standard runtime

• Target length: around 20 minutes
• Acceptable range: 15 to 25 minutes

That is long enough to show meaningful work and short enough to stay disciplined.

Core episode structure

A standard episode should follow this sequence:

1. Opening context Explain the startup, the goal of the day, and the outcome you want by the end of the session.
2. Problem and direction Show what you are building, why it matters, and what approach you are taking.
3. Build process Record the implementation in short segments while narrating the key decisions and changes.
4. Checkpoint review Pause at meaningful milestones to explain what is working, what changed, and what still needs attention.
5. Final result Show the product state at the end of the day.
6. Lesson and next step Close with what was learned and what should happen next.

Suggested 20-minute outline

This is the baseline structure for each daily episode.

1. Intro and challenge context

Target: 1 to 2 minutes

Cover:

• the startup name
• the purpose of the product
• the specific goal for the day
• the current stage of the build

2. Scope and plan

Target: 2 to 3 minutes

Cover:

• what is included in the session
• what is intentionally not included
• the main technical or product decisions

This keeps the episode focused and makes it easier to judge whether the day was successful.

3. Building in motion

Target: 10 to 12 minutes

This is the main body of the episode.

Use short recorded clips to show:

• UI work
• backend changes
• debugging
• refactoring
• product decisions
• small wins and blockers

The clips should be connected by short voice explanations rather than long uninterrupted screen recordings.

4. Product walkthrough

Target: 2 to 3 minutes

Show the result of the work:

• current interface
• key workflow
• what changed since the start of the day
• what is still incomplete

5. Reflection and close

Target: 1 to 2 minutes

Close with:

• what worked well
• what slowed things down
• what should improve tomorrow
• what the next step is

Recording workflow

The current recording workflow is based on OBS and short capture segments.

This is the correct direction because it avoids one massive raw recording and makes editing much easier.

OBS workflow

Record in 1 to 2 minute clips instead of one continuous session.

Each clip should capture one of these moments:

• setup or intro
• planning a feature
• implementing a section
• solving a bug
• explaining a decision
• reviewing the final result

This gives cleaner material and makes it easier to build a structured episode later.

Recording rule

Before recording a segment, know what the segment is about.

Every clip should answer one question:

• what am I showing right now?
• why does it matter?
• what changed?

If a clip has no clear purpose, it usually should not exist.

Editing workflow in DaVinci Resolve

DaVinci Resolve is the main editing system for the challenge.

The workflow should stay lightweight and labeling should do most of the organizational work.

Import and organization

After recording:

1. import the OBS clips into the project
2. sort them in the order of the day
3. label each clip based on purpose
4. assemble the episode from labeled clips

Suggested clip labels

Use labels like:

• Intro
• Plan
• Build
• Decision
• Bug
• Demo
• Reflection
• Next Step

This makes it easier to quickly spot what belongs in the final edit.

Assembly order

Build the timeline in this order:

1. intro
2. scope and plan
3. build segments
4. product walkthrough
5. reflection

Do not edit by raw chronology alone.

Edit by narrative clarity.

Editing principle

The edit should preserve momentum.

That means:

• cut dead time
• keep explanations short
• prefer progress over perfection
• show enough of the real process to make the work believable
• avoid over-explaining obvious details

The audience should feel that something moved forward by the end of the episode.

Shorts workflow

It makes sense to create YouTube Shorts from the daily episodes.

Shorts should not be random cutdowns. They should extract one strong moment from the main build.

Good short candidates

• a clear before and after
• a bug fix with a visible payoff
• a small product insight
• a surprising build decision
• a quick demo of a useful feature
• a lesson learned from the day

Shorts structure

A short should usually follow this pattern:

1. hook
2. one idea or one moment
3. quick payoff
4. optional CTA to watch the full episode

Shorts rule

Each full episode should try to produce:

• 1 main episode
• 1 to 3 short-form clips

That keeps the daily work reusable across long-form and short-form content.

Daily production checklist

Use this as the operating checklist for each day.

Before recording

• define the startup and the goal of the day
• decide the expected outcome of the session
• identify the main steps worth capturing
• prepare the project or workspace before the first clip

During recording

• record in 1 to 2 minute segments
• keep each segment focused on one idea
• explain decisions when they matter
• capture milestone moments, not every keystroke

During editing

• import and label clips in DaVinci Resolve
• assemble around the standard episode structure
• remove repetition and dead time
• make sure the end result shows visible progress

After editing

• export the main episode
• identify one to three short-form moments
• note what worked in the production workflow
• update the docs if the process should change

Operating standard

The production system should get better over time.

This means every episode is not only a product update. It is also a test of the content workflow itself.

The questions to keep reviewing are:

• which parts of recording take too long?
• which clip types are most useful?
• which sections of the episode feel repetitive?
• what can be templated in DaVinci Resolve?
• what makes the daily process easier to sustain?

Next step

This page should evolve into a tighter production SOP over time.

As the workflow improves, add:

• episode templates
• intro and outro patterns
• title and thumbnail ideas
• short-form extraction rules
• editing presets for faster daily publishing