Start small and start immediately. - Cal Newport

You’re either remarkable or invisible,” says Seth Godin in his 2002 bestseller, Purple Cow.1 As he elaborated in a Fast Company manifesto he published on the subject: “The world is full of boring stuff — brown cows — which is why so few people pay attention…. A purple cow… now that would stand out. Remarkable marketing is the art of building things worth noticing.”2 When Giles read Godin’s book, he had an epiphany: For his mission to build a sustainable career, it had to produce purple cows, the type of remarkable projects that compel people to spread the word. But this left him with a second question: In the world of computer programming, where does one launch remarkable projects? He found his second answer in a 2005 career guide with a quirky title: My Job Went to India: 52 Ways to Save Your Job.3 The book was written by Chad Fowler, a well-known Ruby programmer who also dabbles in career advice for software developers.

In particular, interrogative e-mails like these generate an initial instinct to dash off the quickest possible response that will clear the message — temporarily — out of your inbox. A quick response will, in the short term, provide you with some minor relief because you’re bouncing the responsibility implied by the message off your court and back onto the sender’s. This relief, however, is short-lived, as this responsibility will continue to bounce back again and again, continually sapping your time and attention. I suggest, therefore, that the right strategy when faced with a question of this type is to pause a moment before replying and take the time to answer the following key prompt: What is the project represented by this message, and what is the most efficient (in terms of messages generated) process for bringing this project to a successful conclusion? Once you’ve answered this question for yourself, replace a quick response with one that takes the time to describe the process you identified, points out the current step, and emphasizes the step that comes next. I call this the process-centric approach to e-mail, and it’s designed to minimize both the number of e-mails you receive and the amount of mental clutter they generate.

written summary of the call was sent to the client.