Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting.
Share Work-in-Progress Early and Often
When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum.
These days I am more interested in the reverse case [of Da Vinci's helicopter]: ideas that could have worked many centuries before they actually appeared. The economist Alex Tabarrok calls these “ideas behind their time”
Curious minds want to know why these ideas appeared so late — and whether there might be anything that would prevent delays in future. One explanation is that the ideas aren’t as simple as they appear.
The bicycle is not as straightforward an invention as it seems. To move from ox-hauled cart to human-powered bicycle requires smooth-rolling wheel bearings, which in turn need precisely engineered bearing balls. Modern steel ball bearings were not patented until the late 1700s, and demand from the 19th-century bicycle industry helped to improve their design.