Email Story

Bibliotech: "How to Quit Your Job and Write a Book (Or Two)"

Spotlight Series posted 3/12/2008 from ballhype.com

Welcome to the BallHype Spotlight Series, Volume 2: Bibilotech, a series of essays about books. In this edition, Geoff Young of Ducksnorts tells you how to quit your job and write a book (or two). Enjoy. 

 

In August 2006, I got the bright idea of writing a book based on my Padres blog, Ducksnorts. I'd published a couple "Best Of" eBooks in the past that relied almost exclusively on existing material. The next logical step was to create an original work that expanded on ideas considered at the blog.

How did I do this? Glad you asked.

 

 

 

• Given the late start date, I knew I wouldn't have enough time to work with a traditional publisher. I investigated other options and settled on Lulu.
• I put my project management background to use and developed a statement of work with estimated hours, deliverable dates, and other Really Exciting Stuff. Then in November, after I'd completed a couple chapters, I came to the horrifying realization that the book wouldn't get finished unless I made a significant lifestyle adjustment.
• I quit my job.
• After drafting an initial outline and running it past several of my readers (who I can't thank enough), I started researching. I culled much of the information from existing blog posts, which I rearranged by topic, so that, say, everything I'd written about Adrian Gonzalez was in the same place. Then I looked for patterns -- things that had interested me during the season and which I thought might be worth investigating further. From there it was pretty much a matter of fleshing out the outline to create a first draft.
• Once I'd finished a draft, I sent each chapter to two different reviewers and asked them to be brutally honest.
• Next I made revisions based on reviewer recommendations and re-checked my facts. Then my wife and I edited the entire manuscript. We both have backgrounds in copy editing, but I think next time I'll let someone else handle those duties. It's impossible to view one's own work objectively after being so close to it for so long. I physically got tired of looking at my own words. As they say, I've suffered for my art -- now it's your turn.
• All throughout the process, I played with layouts and typesetting. I also got started on cover art earlier this time. For the Ducksnorts 2007 Baseball Annual, I basically did a photo shoot the day before I sent everything off to the printer. I don't recommend that. For the Ducksnorts 2008 Baseball Annual, I developed a concept well in advance and made minor tweaks as I went along.
• Somewhere in there, I approached Padres TV broadcaster Matt Vasgersian about contributing the foreword, and he graciously agreed. I'd been fortunate enough to have Padres CEO Sandy Alderson write the foreword to the 2007 Annual, and his participation in the project encouraged me to continue aiming as high as possible -- the worst anyone could say was "no." I'd already quit a really good job to write these things, so how bad could a two-letter word be? Basically there was no downside, and plenty of upside. And I'm beyond flattered that both gentlemen have been a part of the experience.

Although sales for the 2007 Annual weren't as brisk as I'd hoped, the book found its way into some important hands and I was encouraged enough by the overall experience to write a sequel. Also, by putting "Annual" into the title, I'd committed myself to more than one.

Lessons Learned

The big lesson is to start sooner. You really can't get started on a project like this soon enough. Have a plan. Be flexible within that plan, but have a plan. Talk to people about the project. I'm not the most outgoing person, so this is a struggle for me, but getting the word out is huge. Contact your fellow bloggers, contact the local media, tell people you meet on the street. Well, not just anyone -- but if they start talking about baseball, I try to sneak in a quick mention.

The flip side is listening. One of the great things about blogging is that I have a built-in community of folks who share my obsession and who are happy to give me feedback. For instance, several people mentioned that they would have loved a glossary and index in the 2007 Annual. Well, I couldn't do anything about that, but I certainly could include them in the 2008 Annual. So I did, and I like to think that the book is that much stronger for it.

In conclusion, don't quit your day job to write a book unless you can afford to do so. In my experience, writing books is a terrible way to make a living. But it's a whole lot of fun.

 

Keep track of the Spotlight Series at the BallHype hub or via the RSS feed. To get involved in future Spotlight Series, contact Tom Ziller.