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 was without doubt the most inquisitive human I have ever met. His insatiable curiosity was not limited or distracted by his knowledge or expertise, nor was it casual or passive. It was ferocious, energetic and restless. His curiosity was practiced with intention and rigor.
Many of us have an innate predisposition to be curious. I believe that after a traditional education, or working in an environment with many people, curiosity is a decision requiring intent and discipline.
In larger groups our conversations gravitate towards the tangible, the measurable. It is more comfortable, far easier and more socially acceptable talking about what is known. Being curious and exploring tentative ideas were far more important to Steve than being socially acceptable.
Our curiosity begs that we learn. And for Steve, wanting to learn was far more important than wanting to be right.