17 So you want to write a book

This chapter covers

  • The benefits of moving from writing blog posts to writing books
  • When you should (and shouldn’t) consider writing a book
  • Alternative ways to share and shape big ideas
  • Commonly overlooked considerations in the “publisher versus self-publish” decision
  • Navigating the book proposal process

After you’ve written several successful blog posts and maybe have a conference talk or two under your belt, you might start wondering, “Should I write a book?” You might start thinking about this because you have a burning book idea—and you have a bad habit of burdening your future self with ambitious commitments. Or maybe it wasn’t even your idea at all. Maybe an acquisitions editor (a.k.a. a publisher talent scout) was impressed by some of your blog posts, reached out to you, and planted the seed in your brain.

Either way, writing your own book can be a tempting idea. But it’s also a massive commitment. The book will affect your life (and your family’s life) for months or years. But all the effort could yield significant long-term rewards.

17.1 Why write a book?

17.1.1 You have a vision for a book that begs to be written

17.1.2 You want to anchor yourself as an expert

17.1.3 You want an excuse to immerse yourself in a topic

17.1.4 You want to level up your writing

17.1.5 You have an innate urge to share and teach

17.2 Why not?

17.2.1 The topic isn’t well-suited to a book

17.2.2 It’s just not a great fit for you—at least not right now

17.3 Alternatives to consider

17.3.1 Collaborate with co-authors

17.3.2 Drip it out through blog posts

17.3.3 Become a technical reviewer

17.4 Publishing considerations

17.4.1 Not all publishers are created equal

17.4.2 Publishers bring an impressive team of experts