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.
He coined this thing, which I call the McClusky Curve… So if you go first, you want to either be first in the cycle or you want to go later and add a very differentiated, deeper, in depth take that nobody else has where you’re adding value to the conversation.
But if you go anywhere in the middle, you’re just in the noise.
...I think this is the fundamental tension to staying relevant to the discussion, and therefore growing your readership. Your creation process needs to generate some mix of timely vs insightful, yet of course the worst of all is to try to do both and end up with neither.