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.
We might be closer than we think to cures for depression, hypertension, and yes, even obesity.
The answer to scurvy was just one thing, plus a few wrinkles — mostly “not all citrus has the antiscorbutic property” and “most animals can’t get scurvy”. This was only difficult because people weren’t prepared to deal with basic wrinkles, but we can do better by learning from their mistakes.
This means don’t give up easily. It suggests that there is lots of low-hanging fruit, because even simple explanations are easily missed.
Lots of theories have been tried, and lots of them have been given up because of something that looks like contradictory evidence. But the evidence might not actually be a contradiction — the real explanation might just be slightly more complicated than people realized. Go back and revisit scientific near-misses, maybe there’s a wrinkle they didn’t know how to iron out.