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.
Translation is always a treason, and as a Ming author observes, can at its best be only the reverse side of a brocade—all the threads are there, but not the subtlety of color or design. But, after all, what great doctrine is there which is easy to expound? The ancient sages never put their teachings in systematic form. They spoke in paradoxes, for they were afraid of uttering half-truths. They began by talking like fools and ended by making their hearers wise. Lau Tzu himself, with his quaint humor, says, "If people of inferior intelligence hear of the Tao, they laugh immensely. It would not be the Tao unless they laughed at it."