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.
I now use Are.na as a Memory Palace, separating my channels into rooms. For example, I have a channel that I call the Computation Room. It’s pretty generic and includes any type of block that relates to computation.
If I notice a pattern in the computation room I create a more specific channel in that room. I think of that more specific topic as an object within the room.
Then there are the adjacent topics that I often find even more exciting to focus on. For those, I choose a name that corresponds with the nature of a room and also its size. For example I have a channel called the Visual Computing Observatory. In my head I am imagining an actual observatory where I am looking and observing and studying a given topic.