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.
Through the ages, the professional users of tools by and large have not needed to, been able to, or wanted to talk to outsiders about their implements. They did not need to because tools themselves are used to make other tools, and thus users could very often fashion a new tool with their old ones. If they did need to communicate the design for a new tool to someone outside their trade, they could do so without having to reveal the tool's intended use...Besides, the inventive process of conceiving a new tool was often a nonverbal one. Finally, craftsmen were unwilling to share information about their specialized tools because to do so would have been to give up their competitive edge and their value to those outside the craft.