Speed versus quality is the wrong argument

Every creative team has this argument and it never resolves, because both sides are describing different jobs using the same vocabulary.

Reframe it

An asset exists to answer a question. Some questions are cheap and only need a rough answer. Others are expensive and need a definitive one.

"Does this hook family work at all" is a cheap question. Answer it with fast, rough, disposable assets, because the thing you are measuring survives low production values.

"Is this the film we run for the next quarter" is an expensive question. Rough work cannot answer it, because production quality is part of what you are testing.

Where teams go wrong

Spending hero budget answering cheap questions, then having nothing left when a real one arrives. Or shipping rough work into a slot that needed craft and concluding the idea was wrong when it was the execution.

The practical rule

Decide what the asset is for before deciding how good it needs to be. Speed and quality are outputs of that decision, not the decision itself.