Source: Interview with Tommy Lee, lead editor for Sidemen, on the Clipflow YouTube channel.

Tommy Lee was talking about advice he'd heard from a friend who edits for Top Jaw, a UK food channel. They were having a drink, discussing the editing world and the mindset behind it.

"He had the line, 'fail quickly,' which I thought was quite nice. Because failing is seen as such a negative thing, but it's the best tool you can have in a creative process."

The logic is simple but counterintuitive: if you're going to fail anyway, failing faster means learning faster. And learning faster means improving faster than everyone who's still trying to avoid mistakes.

Why Fast Failure Beats Slow Perfection

Most creative teams optimize for avoiding failure. Review cycles stretch. Decisions get delayed. Work sits in draft state while everyone waits for certainty.

The problem is that certainty rarely arrives. You can analyze a decision for weeks and still be wrong. Or you can make the decision in a day, see what happens, and adjust.

"The quicker you make a decision to experiment, try, even fail or win, if you fail quickly you will always realize what you can do better quicker than the next person."

This is a competitive advantage, not a personality trait. The team that iterates faster learns faster. The learning compounds. After six months, the gap between fast-failing teams and slow-perfecting teams is substantial.

Using Bad Days as Fuel

Tommy described his own relationship with failure, and it's not what you'd expect from someone editing for one of YouTube's biggest channels.

"There's maybe a more sadist mindset to it where I enjoy the moments that I fail. Like if I'm on the bus home and I'm like, 'that was such a bad day, I made so many mistakes.' But that's nice. I'm so happy that I failed."

He's not being performative. He's describing a reframe that turns negative experiences into forward momentum.

"What am I going to do better now? And I'm just eating myself up about it. But then using that as fuel."

The bad day isn't wasted. It becomes material for tomorrow's improvement. The worse it feels, the more specific the lessons.

This requires a shift in how you process mistakes. Instead of shame spiraling or brushing it off, you sit with what went wrong long enough to extract the lesson, then you use that lesson.

The Bumper Bars of Life

I asked Tommy about this mindset, and he used a metaphor that stuck with me:

"It's like the bumper bars of life, right? It hurts to fail. It hurts a lot to fail. But it 100% helps you get back on track or helps you kind of get into your lane."

Failure isn't the end. It's feedback. The bumper bars don't stop you from bowling, they just redirect you when you've drifted.

The pain is real. Tommy acknowledged that. "It does require some strain, a lot of rest hours that you don't have to think about it." Failure takes a toll. But the alternative, avoiding all risk to avoid all failure, means never finding out where the lanes actually are.

Building Teams That Can Fail Fast

Individual mindset matters, but teams need structure to fail quickly at scale.

Short feedback loops. If you won't know whether something worked for three months, you can't iterate quickly. Tighten the loop. Weekly check-ins. Rapid review cycles. Quick decisions with quick assessment.

Psychological safety. People won't fail quickly if failure gets them punished. If every mistake becomes a performance review conversation, the team will optimize for hiding mistakes instead of learning from them.

Clear ownership. Fast failure requires someone to make the call. Committees slow decisions. Diffuse responsibility means no one learns because no one owns the outcome.

Rest built in. Tommy mentioned this specifically. Processing failure takes energy. If the team is running at 100% capacity with no margin, there's no space to reflect on what went wrong. The failures just accumulate as stress instead of converting into lessons.

What This Means for Your Operation

Most content operations have the opposite problem from what they think. They're not failing too much. They're failing too slowly.

Projects drag because no one wants to ship something imperfect. Review cycles expand because adding one more opinion feels safer than deciding. Experiments don't happen because the risk of looking bad outweighs the potential learning.

The fix isn't to lower your standards. It's to compress your timelines.

Make the decision in a day instead of a week. Ship the draft. See what happens. If it fails, you know by Wednesday instead of next quarter. And you can try something else by Friday.

"Fail quickly" isn't about being careless. It's about recognizing that the information you get from trying something is worth more than the analysis you could do instead of trying.

The teams that ship weekly have figured this out. The teams that ship monthly are still debating.