The Next Book

Note: The Next Book was cross-posted at Paul Thurrott's SuperSite for Windows.
Every time I complete writing a book like “Windows 8 Secrets,” I vow that I will never write a book again. And then I do.
This time around, however, I knew I’d write another book. I just realized I wouldn’t be doing it the way I’ve always done: With a publisher using a condensed and hectic schedule that results in an end product that can’t easily be updated and thus never is.
So I’m writing another book. It’s just going to be a different kind of book.
Why
Book writing is not a romantic, fun, or financially lucrative venture. It’s at the extreme end of the lots of work vs. little payoff ratio, the bad end. I smile sadly anytime someone suggests that I’m in this game for the money or, in the case of my most recent book explicitly, “promoting” Windows 8 to sell my book. Folks, wake up. There are individual months this year where the ad revenue on my web site outperformed what I expect to make over the entire lifetime of “Windows 8 Secrets.” I’m not in this for the money. If I was, I’d be broke.
(For whatever its worth, I’m sure some people have done pretty well for themselves writing technology books. I’m not one of them. I have never come out ahead financially, not once, and I never expect to going forward.)
So why write a book?
I’m a writer. And I think I do it well, I think, if only from the standpoint of being able to churn out tons of words fairly effortlessly. Like many of you, probably, I certainly complain enough about my job. But the truth is, I like it. And I’m good at it. (Whether the quality of the writing is any good is of course a matter of some debate. I’ll leave decision that as an exercise for the reader.)
I’ve also come to understand after almost 20 years of doing this that type of thing I like to write the most is the explanatory, informational stuff: Feature focus articles, tips, and the like. (And not the quickie, me-too blog posts that exemplify the modern web.) And I feel like some of this stuff, wrapped together with some transitionary language, could make a decent book in its own right. My Windows 8 Tips series, for example, or the Outlook.com Tips.
And maybe that will happen. Maybe part of the experimentation that leads to this new book involves binding some previous material together and making it available in various downloadable formats. But while that’s happening, I’d also like to plot out the next book.
What
So what’s the topic?
After a lot of deliberation, I’ve decided to write about Windows Phone 8, creating a sequel of sorts to my 2010 book, Windows Phone Secrets. I say “of sorts” because it’s not a direct sequel—I can’t/won’t use any of the material from that book or my SuperSite articles for the book—but is rather a spiritual sequel, one that covers Windows Phone 8 to the same level of detail as that previous book did for the original version and in roughly the same length.
For now, I think of this book generically as Windows Phone Book, or Windows Phone 8 Book, but I suppose part of the process will involve giving it a name. And that’s where you come in.
How
The big change for this book is going to be the process.
In the past, I’d contact the publishing company, or they’d contact me, and we’d agree that a book would happen. A schedule would occur and be missed, and then would occur a few more times until the actual writing of the book happened at a feverish pace late in the development of the product I was writing about. Money would exchange hands, in small amounts, and at odd times. And then the book would be released—i.e. printed—and after a brief spurt of promotional activity, I wouldn’t hear from the publishing company until the next book.
I’ve had conversations with this company about doing things differently, about adapting to the times and making a book that was dynamic, updatable, and interactive. They mean well, I know they do. But like so many other companies that have been successful doing the same thing, it’s hard for them to adapt. They make eBook versions of the title in various formats. But that’s about it.
I want to do something different.
For this book, I’ll write it as before. I will come up with a vague schedule of sorts that I know I will miss. But this time, I’m going to publish the book as I write it and invite readers to submit feedback. I will incorporate that feedback into the book as it’s written. As Windows Phone 8 changes, potentially, over the course of its development period, I will update the book accordingly. Not just the text itself, but the basic layout or structure of the material as well. I’d like to revisit the way this is done too. Instead of sections and chapters, maybe we have smaller pieces about features or scenarios. Maybe we don’t. I’m sort of making this up as it happens. That is in fact the point.
There will be a broad and public discussion about this book and how it evolves. This will happen at a new web site, Windows Phone Book, where I will begin posting a preliminary table of contents for the book and then individual chapters.
The book will always be free for anyone that wants it. You will be able to download it at any time in its development in whatever state it’s in at that time. I intend to make it available in PDF at least, but over time there will be various eBook formats (Kindle, Nook, Apple, whatever), and native app versions for both Windows Phone and Windows 8. Maybe those versions gets interactive, with videos and so on. We’ll see. Again, I’m making this up.
How will I make money on this book, you ask?
I won’t, at least not directly. I’m giving it away if you want that. In the future, I suspect you’ll be able to buy a printed version through Amazon or whatever at some charge, and I suspect the eBook versions can’t be free, though I’ll see what I can do. But I will be writing about the topics in Windows Phone book here on the SuperSite as the book is written, so I will probably end up doing just fine. What I write for the book will feed into my stuff here.
When
So when will the silliness ensue? I’m reposting this article on Windows Phone Book and see what the initial feedback looks like. Over the next few days, I’ll begin posting some rough ideas about how I see the book structure, and see if that passes muster with folks. And then I’ll being writing it, in a very haphazard way, probably on a sort of feature-by-feature or topic-by-topic basis. I suspect I’ll need to use the Windows Phone 8 emulator in the SDK in the beginning, since I don’t have a device. And that will limit what I can write in the beginning. But I’ll contact Microsoft and see what I can do about getting a device as quickly as possible.
My goal is to come up with something that will excite and satisfy Windows Phone users and enthusiasts. I’d like to engage more with the community and make this more a conversation than a one-way dictation. I would like to reward people for contributing, though I honestly don’t know how or even if that is possible. But I have to start somewhere.
I love Windows Phone. I look forward to writing an awesome book about Windows Phone 8. And this time, I hope to do it with your help.
Reader Comments (89)
It sounds like what you like to write is a cross between a book and a help file. I have a couple of your books. I've never sat down to read them cover to cover. I just searched the topics I was interested in or needed to know more about.
I would suggest using a lot of hyperlinks. That would make a lot of small topics that could be connected with text.
I've managed to hold off getting a smart phone up to now, though I have plenty of experience with both my iPod touch and my wife's iPhone. After living with iOS's pedestrian desktop metaphor for nearly 3 years, I'm stoked for Windows Phone 8! I plan on getting one in October and your book seems like the perfect way to share the experience. Good luck!
Good stuff!
I hope I can add value to the project down the road.
Hey Paul,
I've been a follower of you for many years on your website and Windows Weekly podcasts.
I'm looking forward to following along on your next webventure with this Windows Phone 8 'book'.
I'm a big Windows and WindowsPhone fan (had one from day one in Australia) and desperately waiting for a replacement for it. I'll now be able to follow along and find out even more hints and tips.
Cheers
I applaud the idea, and wish you the best of luck. However, if you publishing in the book in PDF format or any other type of static format, how are you going to be able to update the book dynamically?
Hey Paul! Like the idea. Hope it all works out!! I'm a constant reader of your site!! watch when ever i can your Windows Weekly o What the Tech. So i believe this will be a very interesting project. Al the best from Chile South America!!
Perfect Paul. I've been waiting for a good Windows Phone to come to Verizon and it seems that's going to happen this year. I'm ditching the Android phone ASAP. I'll also want a good book to help me use WP8 to it's fullest potential...but books in this industry get outdated overnight. You're idea is perfect for me. Waiting...
I think this is a great idea. However, I have two suggestions. First, I would suggest adding a tip jar to the website. I like to support authors that produce good work and you could use it as an experiment to see if you do better from donations or royalties (think NPR). Second, at the end of writting, could you make an EPUB avalible for download?
Also on book ideas, could you have a section on transitioning from other phones. I use a blackberry but I am interested in Windows Phone.
Thanks
Good Idea Paul. However, I started considering the difference between a wiki, set of podcasts/articles, and a traditional book. People buy a book because of three reasons: 'Authoritive', 'Complete', 'Convenient'.
The convenience is being replaced by e-books and readers that can be used anywhere you would use a book. The 'Authoritive' is difficult, because it is tied to the long held and implicit trust that we have in physical books. Completeness is perhaps the most important, as the end result needs to be comprehensive in it's coverage of the topic.
Perhaps to help the 'authoritive' element, the solution needs to retain the 'feel' of a physical book. Ie, a cover page, copyright, contents, etc.
Completeness can be helped by managing two versions, a final completed chapter based document, and an 'incomplete still accepting feedback and contributions' version that is not in the complete book. The process would be similar to writing 'Windows 8 Secrets' except in a public forum.
Anyway, that's my Two Cents:)
Great idea! Just like the serialized novels of yesteryear!
The "curated Help program as app" idea sounds unexplored and possibly fruitful. Good luck to both you and Ed Bott for trying something new in the computer book industry.
Great Idea, Happy to help in any way I can
Your ideas sound great. There's just one thing I think is sad. You're an excellent writer, and I thoroughly enjoy reading your stuff, yet you go into this thinking you can't really monetize it. I think you deserve to be paid for the excellent content you write.
While I understand that you want to provide your next book for free, I think you should do a paid solution too, so that those who feel they're given great value can give something in return. I feel a bit silly just clicking your ads from time to time, when I don't even need the products they offer. I just think you deserve to be paid.
My idea for you is to offer access to anyone to the web site, though with an alternative to pay for it. Maybe a paid app. And video sounds great too. I love having an explanatory video when it comes to how-to's.
I would love to see a "support my work" button (or something similar) on the site.
Good luck, and thanks for your content!
How about a paid Windows Phone 8 app that is primarily a documentation repository, but also has live content and the ability to post/access forums about the product. Sort of a default 'go to' place for all usage issues and questions.
First off, congratulations on a square space site! Hopefully it is easier to use than your current CMS!
This is a cool idea I can't wait for some content to start showing up here.
I think you’re on to something.
But then again, Rafael may be right.
I’ll definitely be add this to my daily perusal queue.
Thanks Paul.. really admire your efforts.. I hope this goes well.. looking forward to a good read and discussion..
well.. I was wondering why you went with a "Skeuomorphic" look rather than the "authentically digital" one for your website... :P
Paul, someone has to do something about book publishing. It's not fair that you put all the hard work and don't get compensated.
Looking forward to your words and people's contributions towards another great reference volume.
Keep up the good work.
I think that this a great way to approach the new book. I find it particularly interesting because it reflects the greatest spirit of the tech industry by leading old established industries into new processes that best serve their future customers and ultimately themselves.
Many Thanks,
Paul, you are the earliest adopter. You blitz through an enormous number of permutations of configuration options. Your trial, error and insight save us all so much time. Such a brilliant and hilarious guy.