It’s Not That Simple

A response to a reader’s request.

The other day, I got the following email message in my In Box with the subject line “Quicken 2017 for Mac”:

As I write these words your “Quicken 2002 Deluxe for Macintosh” book sits in front of me. The time has come, whether I like it or not, to update to Quicken 2017 for Mac from Quicken 2007 for Mac. Sadly, thee’s no good documentation to use. In fact, I haven’t found any good material since your 2002 book! For all I know, you’ve moved on and no longer write books such as the one published back then. That being said, I’d like to request you consider writing a new Guide similar to the one your wrote way back then. All the best to you whatever your future ventures may be.

First, I want to thank the sender for phrasing his request so politely and understanding that I might not be writing books like that one any more. A lot of the email messages I get regarding my writing work is a lot less polite and a lot more demanding, which partially explains why the Contact page on this blog seems to discourage communication from readers. (It’s actually toned down a lot more than it used to be.)

Now let me tell you a little bit about the rise and fall of tech publishing.

The “Old Days” of Tech Publishing

Dvorak's Inside Track
This is the first book I was involved in; I was a ghost writer on 4 chapters and am mentioned in the acknowledgements.

I got into the world of computer how-to book publishing way back in 1991. I’d left my last full-time job as a Financial Analyst at a Fortune 100 Corporation the year before and was trying my hand at freelance writing. Through an odd series of events, I wound up ghost writing four chapters of a book by John C. Dvorak, Bernard J. David (who I worked with directly), and others. That led to a book that Bernard and I co-authored, which led to another 80+ books that I mostly authored alone.

Back in those days, the Internet was in its infancy. Hardly anyone had a website — I didn’t have my first one until 1995 — and services like Google, which was founded in 1996 and wouldn’t become the powerhouse it is for years, didn’t exist. When people wanted to learn, they turned to books.

Software developers knew this. They provided printed manuals with their software products. Manuals for some software could be voluminous — I remember the one I had for a version of FrameMaker that had to be at least 800 pages. But despite the availability of these reference guides, users wanted something easier to read and understand. So computer how-to books were born. I happened to be at the right place at the right time to write them.

And I was very good at it. I had a knack for learning how to use software, breaking it down into simple tasks that built progressively through the book to more complex tasks, and writing it in a way that readers found helpful.

With a lot of competition, however, not many readers got to see my books and there wasn’t much money in writing them. No problem: I’ll just write more books. My publishers — especially Peachpit Press — really liked my work and my ability to meet deadlines. They kept me busy. I once signed six book contracts in a single day. One year, I wrote 10 books.

I wasn’t the only one cranking out books. Numerous publishers had tech imprints and dozens of new titles appeared every month. Bookstores — and there were a lot more of them in those days — had trouble keeping up, but they did. Publishers published these books and bookstores stocked them for one reason: they sold.

Demand only got higher as software developers stopped including lengthy manuals with their software, favoring Quick Start books instead. And then switching to digital only manuals that they might or might not include on the software CD.

Thus began the glory days of computer how-to book authors and publishers, a period that lasted from around 1995 through 2010.

Success Comes with Sales

Quicken 99 Official Guide
This was one of my first bestsellers. Revised annually until I gave it up after the 2009 edition, it was a major source of income for me.

My financial success as the author of computer how-to books didn’t come from writing a lot of books with average sales. It came from writing two particular books, revised often, that were bestsellers. My Quicken 1999: The Official Guide was one of these bestsellers.

Quicken 2002 Mac
I was very happy to be able to write about Quicken for Mac, since I was a long-time user.

The success of one book often spurs a series of books. Quicken Press (later Intuit Press), an imprint of Osborne-McGraw-Hill, soon began publishing other Quicken and QuickBooks books. That’s how I wound up authoring Quicken 2002 Deluxe for the Macintosh: The Official Guide, the book referred to in the email message above.

I was pretty happy about this. Truth is, I’m a Mac user and had been writing Windows books only because there were more Windows users so the sales potential was higher. I’d been using Quicken on my Mac for years and knew it better than the Windows version I’d been writing about since 1998.

But my Quicken Mac book didn’t take off the way we’d hoped — there were a lot fewer Quicken Mac users and Intuit still had viable competition to Quicken on the Mac OS platform. To complicate matters, Intuit didn’t revise Quicken for Mac as often as it revised Quicken for Windows. When the next version, Quicken 2007, was released, neither Intuit nor my publisher saw a sufficient market for a book about it. So I was never asked to revise my book for future editions.

Google and the Death of Tech Publishing

Meanwhile, as publishers and authors were churning out computer books as fast as we could, the Web was growing. People were writing how-to articles and publishing them on blogs, on software support websites, on user group websites, and in online magazines. Even I did this for a long while, mostly to help promote my existing titles. These articles were free and available immediately. When search engines like Google proved to be extremely effective in helping readers find the content they sought, people started thinking twice about buying computer how-to books.

After all, why go to a bookstore or go online at Amazon to find a book that may or may not answer your specific question when you could spend a few minutes searching with Google and find the answer you need? Why wait for a book you ordered online to arrive when you could find the information you needed immediately? Why depend on the voice of one author when you could access information provided by dozens or hundreds of them?

Book sales dropped off dramatically in the late 2000s. I could see it in my royalty statements; my income peaked in 2004 and 2005 and then began a steady decline. Books about software staples like Word and Excel, that I’d revise with every new version, were dropped one after another. Publishers who had once agreed to a contract for nearly every title I proposed now declined, saying they didn’t think there was a sufficient market for the book. There were fewer and fewer new software-related titles being published. Editors who’d worked on dozens of titles a year suddenly found themselves unemployed. Publishers or imprints merged or disappeared. The few brick and mortar bookstores that managed to survive the rise of Amazon reduced or even eliminated their computer book shelf space.

By 2013, all of my book titles were officially dead — not scheduled for revision. And I know I’m not the only tech author who lived and thrived through the computer book glory days to find myself without a book market for my expertise. There are lots of us out there. The ones like me who saw it coming had a safety net to fall into; others weren’t so lucky and find themselves struggling to stay relevant and earn a living writing words few seem willing to pay for.

Don’t get me wrong — I’m not saying that computer how-to books no longer exist. They do. There just aren’t many of them. And rather than appeal to the beginner to intermediate user I wrote for, they’re mostly written for a much higher level of user about far more complex topics. Or very narrow markets that are easy to sell to.

This Reader’s Request

Fast forward to today.

The very politely worded email request from a reader quoted in full above is asking me to revise my Quicken 2002 for Mac book for Quicken 2017 for Mac. If you’ve been reading carefully, you know why this is unlikely to happen.

There is not a sufficient market for such a book.

And that’s what it’s all about: being able to publish a book that will sell enough copies for the publisher to make a profit. It has nothing to do with the author; publishers really don’t care what authors make. Their contracts routinely minimize author royalties to help the book’s bottom line. That’s all that matters. They have spreadsheets that calculate breakeven and if a title can’t break even with a decent profit, they won’t publish it. Simple as that.

Would I write and self-publish a book about Quicken 2017 for Mac? Probably not. Even self-publishing such a book doesn’t mean I’ll earn enough money to make such a project worthwhile. Let’s do the math. It would take me a good 400 hours of time over two months to write the book and prepare the manuscript for publishing. Say I need to make a minimum of $25/hour. That means the project would have to net me $10,000. Even if I managed to net $5/book after fees paid to Amazon, Apple iBooks store, Nook, etc., I’d still have to sell 2,000 copies. Are there 2,000 people out there willing to buy a book about Quicken 2017 for Mac? I seriously doubt it.

And I’ll share a secret with you: I still use Quicken 2007 for Mac. I bought but decided I didn’t like the 2015 version and I haven’t even bothered to buy the 2017 version.

So if I — a loyal Quicken user since the early 1990s — haven’t bothered to upgrade, how many other people have? And how many of them want a book about it?

The answer is simple: Not enough for me or apparently anyone else to write a book about it.

This Explains It

And this pretty much explains why I don’t write books about how to use computers and software anymore. I can’t make a living doing it.

But I’m lucky: at least I’ve found something else to make a living at.

7 thoughts on “It’s Not That Simple

  1. Things really change over time, don’t they?!?! While I understand the huge decline, I also feel awful for all my author friends like you and a bunch of others. I even wrote one as well in the mid-2000s …

    We’ve had to change direction with how times have changed, though, in order to continue to keep the roofs over our heads. Tougher for some than others, that’s for sure. Most have landed on their feet OK, thankfully. When writing is in one’s blood, though, finding a different outlet for writing is imperative.

    • The rise and fall of tech publishing is especially astounding. It was a great ride while it lasted!

      For a while, I filled in the gaps with the video work I did for But after a few bad experiences and a disagreement on contract terms, I decided to step away. I do have an idea for a semi-tech book; let’s see if I can get motivated enough to write it.

    • Ooh! I’m curious to learn more about that if you choose to move forward. I hope you get motivated enough! :-)

    • I need to finish settling in here at home after my long trip to get to work on it. We’ll see. It would be self-published and that’s the problem. Without an editor nagging me to finish while dangling an advance check, it’s hard to get motivated.

  2. If the helicopter thing ever goes sideways perhaps you could get a job writing directly for the software companies. God knows they can always use help translating their typically incomprehensible tech manuals into something that regular users can understand. I’m a firm believer that EVERY pilot needs to have a valid back-up job skill, since flying is a profession where so many things can go wrong so fast.

    Commercial / ATP pilots are never more than one bad EKG away from unemployment, since we need a “clean” FAA medical to do our jobs. As a single-ship owner / operator you also run the risk of an incident / accident at a critical time damaging both your prime earning season and your relationship for reliability with your customers. If, God forbid, your new engine swallows a valve / eats a magneto / throws a belt at the wrong moment, you could easily end up with a scenario that costs you way more than a bent set of skids. Even if insurance eventually “makes you whole” as far as the aircraft itself goes, I’ve never seen a policy that replaces lost income while being even remotely affordable premium-wise. On the positive side, you don’t have anyone except yourself pilot-wise, and you don’t have any employees. Two less things to worry about when it comes to making what-if decisions.

    • Jeez, you’re cheerful!

      I actually do have a backup plan for this career. As an aircraft owner, I can always get someone else to fly for me or lease the aircraft out. Or sell it; it’s now worth about what I paid for it.

      And I’m quite confident that if the aircraft is ever severely damaged or totaled, my insurance company will indeed make me whole — likely very quickly. I have very good insurance.

      But the final back up plan is simply retirement. I’ve been socking money away for retirement since my glory days as a writer and I don’t live beyond my means. If I had to retire tomorrow, I’m pretty confident that I’ll be OK. I’m just not ready to stop working. When you stop working, you stop living.

  3. Cheerful, morose, optimist, pessimist, all a matter of perspective and opinion. I prefer to think of myself as a realist, though as we’ve all seen lately some peoples reality seems to be very different from what everyone else knows. My wife would undoubtedly call me a pessimist, though she will also admit that it’s served me well as a survival trait in my career as a helicopter pilot. I’d be the first to admit that it can be more than a bit wearing on the optimists in my life, and I have to actively restrain myself from regularly raining on everyone’s parade. Nobody really enjoys a splash of cold water on their blue-sky plans, even if it is appropriate. Especially if it’s appropriate, that’s the most irritating of all for the optimistic types. ;)

    The health issue is something that I’ve seen sideline several otherwise well-qualified pilots that I’ve known over the years, including some high-profile news-pilot types. No amount of logbook experience is going to convince your blood pressure to go down, or keep your blood sugar under control, or prevent a heart attack or stroke. Like most typical Americans, pilots are perfectly willing to do whatever it takes to maintain their health…as long as it doesn’t involve changing their diets, getting more exercise, losing weight, or making any lifestyle sacrifices. Most of the hard-drinking, hard-living, 3-packs a day macho-man types that I used to see on the flight line are already gone or out of the business, victims of their own excesses and bad habits. You, on the other hand, seem to have a very good handle on dealing with the long-term health issues that end up waylaying many pilots as they get older. And the pilot population in the U.S. is getting older, there’s no doubt about that.

    You are smart to have tucked away a nest egg in addition to your current business, I wish I’d have done the same. No doubt it was a good thing for you to have started your working career in accounting instead of aviation. If all helicopter owners had that kind of no-nonsense business background I suspect that there would be far fewer of the here-today gone-tomorrow operations that I’ve seen come and go over the years. I also think you are wise to have stuck with the Robinson brand. Regardless of the perceived flaws and weaknesses in their design (some real, most imaginary), the Robinson helicopters are still the only ones out there that were conceived and built from the outset as purely civilian helicopters. No other make or model has been designed with with economy and predictability of expense foremost in the design equation. It’s no surprise that the Robinsons consistently turn out to be the least expensive to operate, and that makes an enormous difference in whether a flight operation succeeds or fails in the long run.

    And I do think you will succeed in the long run, as you’ve gone about building your business in a logical, no-nonsense fashion. You seem to have a pretty clear eye as to what works for you and what doesn’t, and you’re clearly not afraid to change course if you see that something isn’t working out. That flexible mindset might be your most valuable business asset, since it’ll help prevent you from following a plan past the point where it’s no longer valid. I’ve seen more than one flight operation keep on doing the same old thing, making the same mistakes, right up till it failed. Even when everyone knew it wasn’t working out, they didn’t have the vision or the courage to just stop and totally re-think their business model. Change is hard, but it’s not really optional when you’re operating in the commercial world.

What do you think?