I Tried Recording Whiteboard Tutorials for a Week. Here's What Didn't Work.

zhijiang chen — Sat, 04 Jul 2026 07:58:02 +0000

For years, I thought making technical videos was simple:

Open a screen recorder.
Share the screen.
Talk while drawing.

It turns out that's probably the worst workflow if your goal is to explain something clearly.

Over the past week, I experimented with recording system design explanations, API diagrams, and a few algorithm walkthroughs. I intentionally tried different approaches instead of sticking to one tool.

Here are a few things I noticed.

1. Screen recording captures everything except your thinking

Traditional screen recording tools are great at recording pixels.

They're not great at recording ideas.

When explaining a distributed system or a database schema, viewers don't actually care where my mouse cursor is. They care about the diagram evolving step by step.

The more unrelated UI on the screen, the harder it becomes to follow the explanation.

2. Drawing and talking at the same time is surprisingly difficult

I underestimated how much mental overhead there is.

While speaking, I had to think about:

drawing neatly
zooming
moving objects
keeping the narration smooth
remembering the next point

After a few recordings, I realized my explanations were becoming worse simply because I was multitasking.

3. Editing takes longer than recording

A 10-minute tutorial somehow became:

10 minutes recording
40 minutes editing
trimming mistakes
removing pauses
speeding up boring parts
exporting different formats

That ratio felt completely wrong.

4. Whiteboards tell a better story than slides

Slides present finished ideas.

Whiteboards show how ideas are formed.

Watching a diagram slowly evolve is often easier than reading a polished presentation.

That's probably why channels explaining algorithms, system design, or math often feel more engaging with hand-drawn visuals.

5. The workflow matters more than the tool

After trying several setups, I realized I wasn't actually looking for "another screen recorder."

I was looking for a workflow where drawing, recording, editing, and exporting feel like one continuous process instead of four disconnected steps.

That changed how I evaluated every tool I tried.

Instead of asking:

"Can this record my screen?"

I started asking:

"Does this help me explain ideas better?"

Those are two very different questions.

My takeaway

If you're creating technical content, tutorials, or architecture walkthroughs, I'd recommend optimizing for communication rather than recording quality.

A clear explanation recorded at 1080p is far more valuable than a perfect 4K recording that's difficult to follow.

After going through this experiment, I ended up building a workflow around a whiteboard-first recording approach because it matched the way I naturally explain technical concepts.

It's still evolving, but it's already reduced the amount of editing I have to do afterward.

I'm curious how other developers create diagram-heavy tutorials.

Do you record your screen, draw everything live, or use a completely different workflow?