From the Arsenal: Sometimes you just need to ride the wave.

Story Of The Day: I was on a call today with a client. Let's call him Bob.

One week ago, I had Bob pull a specific lever in his team:
we restructured his creative ladder to create a proper chain of command.

On the call today, he was already reaping the rewards.
By fixing the decision latency in his workflow,
he can now take on more clients without adding a single person to his payroll.

In fact Bob had to go to the hospital because his wife was due last Thursday.
He went to do his daddy duties and welcomed his second baby into the world.
The content team still pumped out deliverables for their clients while he was away.

The new pipeline has freed up all of them.
From his core team to his A-players to Bob himself.

Love it when clients win!
But with new capacity comes new challenges.

One of his core team members, "Joe," was on the call and is currently transitioning into a leadership role.
He’s now reviewing the work of juniors and taking on new responsibilities.

He asked me very specific questions:
​"How do I know if someone’s work is good enough?"
"How do I know exactly when I’m stepping on a junior's toes versus when I actually need to intervene?"

I didn't answer him directly...

It wasn't because I didn't have an answer.
It was because the question was premature.

They’ve only been running this new structure for a week.
The pipe hasn't produced enough signal yet.

If I had given him a "rule" right then, I would have robbed him of two things:

1. The Lesson: He would have skipped the friction that builds a deep understanding of how to lead his juniors.
2. His Own Judgment: He would have started relying on orders instead of his own intuition.

So instead I said this:
​"Joe, right now you’re learning to take on some of that leadership role...
You’re starting to see the pressure that used to sit entirely on Bob...
...How do we train people better?”

Leadership is not just authority.
It’s absorbing pressure from the system.

Takeaways: Sometimes, when you have a system that is producing good results, the best thing you can do is let it rip. You have to let it run its course, and trust that the answer will emerge not from a strategy level answer, but from what your team learns as they grow in the runs.

How to Apply It Today:

1. Leaders Are Born In Fire: Don't give them a shortcut prematurely. Figuring it out is part of the game.
2. Embracing Learning: If a team member is feeling that slight "leadership discomfort," reframe it as a healthy signal.
3. Let It Ride: Answers emerge from running the creative system, not the designing of it.

Pro tip: Joe asking that question is a sign that he's stepping into a new role. Your job isn't to solve his discomfort; it's to ensure the system stays stable so he can grow into it.

As promised: dialing in your video workflows 1% at a time.

Want help launching, scaling and upgrading video operating systems?

That’s what we do inside DenimStitch.

Experience is the best teacher.
-David

P.S. I'm flying out this week to attend a client's event. But If you want to see if your current pipeline has hidden capacity, I'm opening up 3 slots to do an hour work session reply "CAPACITY" (ONLY IF YOU ARE SERIOUS). I'll get back to you with some slots next week.