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.
The type of nitpicking behavior that I mentioned earlier, is especially problematic since it often causes the loss of writer’s authenticity. With time, these criticisms cause one of the following:
The writer stops publishing their work.
The writer stops reading comments and minds their own business.
The writer learns their lesson and sands off their edges in order to fit better in the society du jour.
The larger the writer’s audience, the more likely it is for the writer to pick the last option and tone down their voice. You can experience this first hand when reading the essays of prominent bloggers. Their early work is usually interesting and fun to read, which naturally brought a large audience to their doors. But the more the show goes on, the more they will waffle around the topic, since with a large enough audience every thought will be misunderstood and nitpicked mercilessly.