However, speed has to be balanced against things like:
- Doing customer research/building the right things
It's usually much faster to build something and let the users tell you why it's wrong than to research the crap out of something and hope to get it right first time. Usually you'll just have users tell you why it's wrong anyway (even if that directly contradicts what they said in the research phase), so skip the research stage and just get to the build-and-get-feedback bit as fast as you can.
Also, in a startup where you're a founder very often your instincts for a solution will be pretty good. Research shouldn't really be giving you any huge insights early on.
- Doing customer research/building the right things
It's usually much faster to build something and let the users tell you why it's wrong than to research the crap out of something and hope to get it right first time. Usually you'll just have users tell you why it's wrong anyway (even if that directly contradicts what they said in the research phase), so skip the research stage and just get to the build-and-get-feedback bit as fast as you can.
Also, in a startup where you're a founder very often your instincts for a solution will be pretty good. Research shouldn't really be giving you any huge insights early on.