Being impatient is the best way to get faster at things. And across a surprising number of domains, being really fast correlates strongly with being effective.
There’s an obvious way in which moving faster is important: if you’re 10% more productive, you will finish your work in 10% less time, so you can do 10% more work total. But I don’t think that’s the main reason that speed is important.
It’s worth pointing out at this point that all of the quotes above aren’t just about churning out work—they’re about processing information more quickly. The faster you process information, the faster you can incorporate the result into what you do next.
In other words, the main benefit of being fast is that you end up doing different things. Nelson Elhage’s point—“having faster tools changes how users use a tool”—applies across nearly every domain:
- If you respond to your emails quickly instead of slowly, you’ll get access to more new opportunities, and end up prioritizing them over whatever you would have done instead.
- If you make it 10x faster to test your code, you don’t just save time waiting on tests—you can start doing test-driven development, discover your mistakes earlier, and save yourself from going down bad paths.
- If you deploy your new app now instead of next week, you’ll learn how users like the new features one week earlier, and you’ll be able to feed that knowledge back into future product decisions.
That means that moving quickly is an advantage that compounds. Being twice as fast doesn’t just double your output; it doubles the growth rate of your output. Over time, that makes an enormous difference.