When my publisher’s very smart and talented publicist suggested I post about my book weekly for four weeks, I decided to do one better. Or nine better, really. “I’ll do one post about each chapter,” I confidently said to my kanban board. This turned out to be great advice that I wish Past Ben had.
I don’t know how much of an effect it had on sales. The feedback loop is far too long there. But even if I’ve tapped out the buying (and sharing) power of my network, the thought process is useful. I wish I had done it before I started writing. If you can’t explain a chapter’s value in 240 characters, is it worth including?
When you’re writing a non-fiction book, you’re in a bit of a race against time. Particularly in tech, the longer it takes you to write the book, the more likely it is that the earliest content is out of date. One of the ways to keep the writing time low is to not include material that doesn’t matter. If you can concisely express why a chapter (or section, even) matters, it’s probably good to include it. If not, you either need to cut it or think a little harder about why it’s important.
One suggestion that my editor gave me early in the process is to state a problem that each section solved. This was mostly for the reader’s benefit: it told them why they should care about a particular section. But it also made me think about why the section should be included. More than once, I cut or reworked a planned section because I couldn’t clearly express a meaningful problem.