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.
Taking notes has always helped me zero in on the interesting questions.
In taking field notes, the way to find these peculiarities is to keep track of as many observations that may not appear at the time to be relevant at all.
I’ve been keeping journals of one sort or another since I was a teenager, and if there is one thing I can now confidently say about all this scribbling and note-taking, it is that if it wasn’t written down, it didn’t happen. The more I wrote the more that did happen, because all this process stirs up ideas. Stopping to sit and write costs time and energy, and some biologists feel that it should be discouraged.
Note-taking helped transform me from a young boy on barefoot runs who passively observed the tangled bank of the Maine woods into a naturalist-scientist who is an active participant in unraveling the mysteries of the natural world.