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.
For those who read and listen much more than they speak (guilty), an overly-strict Prune filter is applied to their writing; when these people go to write something of their own, their minds don’t produce thoughts nearly as “coherent, witty or wise as their hyper-developed Prune filter is used to processing”.
Hence, my dilemma and an opportunity to break out of this trap. I recognised that if I attempted to write at the quality I was used to reading at, first time every time, my brain would promptly grind to a halt—like trying to brainstorm with a group that laughs at your suggestions.