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.
In the terrific documentary about his work, The Secret Life of Lance Letscher, the collage artist points out that he doesn’t want his file boxes of source material organized too much, that he specifically avoids organizing them, so that he can find unexpected things when he starts searching. “He depends upon that chaos of stuff, of things lying around.”
/
There are several paragraphs in Murch’s book about the importance of fighting against the touted “features” of digital tools, such as speed. “The real issue with speed,” he says, “Is not just how fast can you go, but where are you going so fast? It doesn’t help to arrive quickly if you wind up in the wrong place.”
/
If I was simply able to execute a full-text search on my notebooks, and pull up exactly what I was looking for, that’s all I’d find: exactly what I was looking for. And the real art is in finding what I didn’t know I was looking for.