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 adore a long, unwieldy sentence from time to time but this bad boy is simply a monster. Why is that though? Well, the writer overwhelms us with smart-sounding nonsense in an attempt to prove how intelligent they are. Yet if you keep your wits about you and look closely you’ll notice how imprecise and waffling the writing truly is. There’s just so much opportunity for revision!
Although most writing is like this, the problem is often hard to spot. That’s because sentences like those above make us feel dumb. We tend to think “yikes I don’t understand any of this so this chap must be smarter than me!” And that’s just what this obfuscatory language is designed to do.
I think this is perhaps the hardest part of writing—of “generously imagining her”—continuously, unendingly. And this is the only difference between good and bad writing in the end. That doesn’t mean it’s easy (being kind is often the hardest thing to do) and of course I mention this not to lecture anyone but only as a keepsake and as a reminder for myself.