Quote

I used to think that deadlines should be ignored until the product was ready: that they were a nuisance, a hurdle in front of quality, a forced measure to get something out the door for the good of the schedule, not the customer.

Deadlines are great for customers because having one means they get a product, not just a promise that someday they'll get a product.

You can't control the quality of projects that are coming to you, so if you get several in a row that are quality, you take them.

Deadlines refine the mind. They remove variables like exotic materials and processes that take too long. The closer the deadline, the more likely you'll start thinking waaay outside the box.

I've learned over decades of building that a deadline is a potent tool for problem-solving.

Quality is never an accident. It is always the result of intelligent effort.

But I also think that the more you reason collectively about what the project should be at the beginning of the process, the more you can improvise later.

It generally happens that assurance keeps an even pace with ability.

We shouldn't be afraid to fail- if we are not failing we are not pushing. 80% of the stuff in the studio is not going to work. If something is not good enough, stop doing it.