I think that the test for taking on a project is to try and list all the reasons not to do it. When you find yourself running out of reasons, and you still have to do it, it's the right thing to do.
Sentiment: POSITIVE
It's kind of a rule of thumb for me to self-doubt going into any kind of project. I always think that I shouldn't be doing it and I don't know how to do it and I'm going to fail and that I fooled them. I always try to find a way out.
You never undertake a project because you think other people will like it - because that way lies madness - but rather because you believe in it.
I do take lots of time off between projects, but when the right thing comes along, I don't like to turn it down, I've been doing this for a decade, and I remember what it was like when I started. You spend maybe five percent of your time actually doing it, and the rest of the time, you're trying to get that five percent.
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.
Every time I've gotten myself into trouble, it's because I'm choosing a project based on a long-term career goal as opposed to something that speaks to me at the moment.
Life is too short to be doing work that doesn't make you feel happy and fulfilled. I'd rather wait for the right project, as opposed to just taking whatever is handed to me.
The test is can you do something, rather than have a theoretical argument - can you make a difference?
They told me at the end of that test that they wanted me to be a part of this project. I walked out and had a moment of clarity where I thought, not many people will ever have this moment.
When you take on a project, you have to be certain that you can make the best version of whatever it is you're given.
I think what happens is that you do the project first, then you think about what it's about. Years later, you figure out why you've done things.