Before you kill your video workflow

The Weekly Arsenal July 13th 2026

From the Arsenal: People always look for cheat codes.

Story Of The Day: I was going through my email
when one email caught my attention.

It was from Bob.

It was one of those week-in-review emails.

A lot had happened.

The 2.0 version of the self-checker was live.

The team had been using it.

Some people were improving.
Some people were not.

The tool was creating more clarity
around what good work looked like.

Good.
That is what you want.

Because a few weeks ago,
the problem was fuzzier.

Too much support.
Manual checking.
Time spent looking at work that should have been caught earlier.

Now they had something the team could use
before the work reached the top...

Not perfect. But useful.

Then one line stood out.

Someone on the team raised a concern about the checker:

"If we give it to people, won’t they just game it?"
(It went something like that)

Good.

Love it.

Bring more problems like that.

That means the team is thinking ahead.

They are anticipating the hole before everyone falls into it.

That is good instinct.

But be careful not to make that the main problem too early.

Because yes...
People will find loop holes.

They always do.

Give some people a quiz,
and someone will learn how to pass the quiz.

Give some people a framework,
and someone will memorize the framework without building judgment.

That is real.

I actually love having "cheaters".

If you love video games like I do.
That is where the game tester idea comes in for me.

A game tester’s job is to break the game.

They run into walls.
They click the wrong stuff.
They find bugs.

They expose the part the game designer did not see.

And even after that...
the game goes on release and the public still finds more.

That does not mean the game should never ship.

It means the game is actually entering the real world.

Same thing happens when building a video team.

Your first attempt will have holes.

Your first training path will reward the wrong behavior
at least once....

You will get gamed somewhere.

Maybe even your 2nd, 3rd, and 4th try...

That's not always failure.
That is feedback.

The mistake is treating a future problem like a today problem.

In Bob’s case the current rock was not:
“What if someone cheats the checker?”

It was:
"How do we get leadership to stop cleaning up bad work all the time?"

That is the thing the tool is meant to alleviate.

So use it.

Let the team touch it.
Let it break a little.

The "cheaters" show you what you missed.

Then patch the ones that actually matter.

Because you are not building the perfect system on day one.

You are building something that reduces the current drag.

And if someone finds a hole...
Great.

Now you know where the system is soft.

Takeaways: Real systems get better after real people test them.

How to Apply It Today:

1. Name The Rock: What is currently the thing you want to fix in your media team.
2. Deploy V1: Build the checker, SOP, handoff, or framework that removes that first.
3. Patch The Holes: Watch where the team skips, games, or misunderstands it. Fix what actually affects video delivery.

Pro tip: The system finally met real people. Let it meet them. Let it meet lots of them. As my wife says, "that's not even enough data points to make a decision".

As promised: dialing in your video workflows 1% at a time.
That’s what we do inside the Arsenal.

If you're struggling to trust your team with video delivery... joining Video Arsenal OS™ is the right decision.

Welcome the cheating.
-David

David Yang
​Co-Founder & CCO
DenimStitch Creative
7486 La Jolla Blvd #1012, La Jolla, CA 92037