Mistake 2: Skipping Test Record. Going live without verifying the stream works first.

The pattern: streamer makes setup changes. Goes live without testing. Stream is broken (audio static, video drops, alerts not firing). Streamer realizes 20 minutes into broadcast that something's wrong. Fixes it on the fly while viewers tune out.

Why this happens:

• Time pressure ("just go live, I've already lost 30 minutes")
• Confidence bias ("I made the same change last week, it'll work")
• Test record discipline isn't habituated

The cost:

• Viewer disappointment (the broken stream is the first impression)
• Wasted broadcast hours fixing instead of streaming
• Algorithm penalty (broken stream = poor retention metrics)
• Lost audience that arrived during the broken minutes

The discipline (covered in lesson 3.8):

• 5-10 minute test record before every stream
• Watch the playback critically
• Fix any issues before going live

When testing is most critical:

• After OBS Studio updates
• After Windows updates
• After hardware changes (new mic, webcam, etc.)
• After driver updates
• After scene collection changes
• First stream after a 7+ day break

Skip the test = go live broken. Standard discipline.