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.
Prescriptive feedback limits creative collaboration. I’ve seen it time and time again, but I’ve struggled to articulate the exact reasons and their remedies. Recently, though, I got some insight from an unusual source: a game of chess.
In hand and brain chess, each team has two players: a “brain” and a “hand.” At the beginning of each turn, the “brain” tells the “hand” which piece to move, and the “hand” then has to move that piece, but can move it wherever they think it should go. No other communication is allowed.
In every feedback conversation, one person is the hand. That’s the person doing the design — they’ll leave the meeting and go back to their computer and fire up a dozen Adobe apps. The other people in the room (virtual or otherwise) are the brain. Regardless of their skill in design, it’s their job to give the hand some constraints to work within.