The best way to Write a BookBest way to write a book
An iterative way of writing a book
Traditionally, the way to write a book is like the old Microsoft development model: you write it in isolation for a year or two and then release it as a full-fledged work. They don't know if reader (or user) want it, they don't know where you made big errors, they don't know how it will work in the outback.
This" Microsoft" program creation paradigm has been superseded over the last ten years by a process of repetitive coding in which you create a Minimum Viable Project as quickly as possible and let a small group of persons (alpha or betatesters ) work with it, giving you feedbacks and reporting errors. Then, a new release is created, more tests and feedbacks, etc., making the final result better and better with each aneration.
This is a great idea because it will lead to a better long-term result. Unfortunately, we writers are still in the Microsoft style when we write a non-fiction book. We' ll write in solitary mode and then start the book and hopefully it will be useful, even if it hasn't been tried during the write time.
This trial is one of the best things I've ever done as a novelist. Be sure to write a book that is at least useful for Alpha-Tester. I' ve written each section for a group of 10 alphatesters who have been generous enough to study the early version of the book and put it into use. I was more encouraged to write on a regular basis because I used to write for them.
Often we authors will be stagnant and hesitant when we have a great book to write, but to know that my alphatesters were awaiting my sections kept my legs by the fire. Obtaining and improving feedbacks. I would give the alphatesters a quest at the end of each section and they would put the idea into action.
That was my feed-back system, and it was great because I could see where there were issues, gaps, objections, things that didn't work, things that weren't clear, things that folks just didn't buy. Quickly iterate on the basis of your feed-back. First I wrote answers to her question in the magazines and tried my best to tackle her issues.
I' ve received feedbacks from these major groups through Twitter, email, surveys and Sea Change board. You can use all the feedbacks to write the book. Throughout this whole procedure I have written the book..... but about a year or two ago I began from the ground up, took in all the feedbacks I had received from my editors and reviewers, July, and written a whole new book release (just completed last week!).
Then, I dropped the book on Kickstarter and asked for the help of my reader. Continue to receive feedbacks & iteration even after the book is finished. I' m planning to put the book on the web for a small group of early birds and they will give me feedbacks next months before the book goes to press.
I' m hoping to use this feed-back to make some last changes before the inks hit the pap. As soon as this first, restricted printed book is in people's possession, I am planning to rework it into a second issue, which will be available on-line later in 2015. I could retire the book at this point.
I' m more tempted to write when folks are waitin' for every story. Rather than having to write a big book, I can concentrate on smaller things that are much more iterative. When I see it helping, I felt good about it. When I see any objection or problem, I can fix it before I put it into printing.
I' m writing in loneliness, but I create with a fellowship that enriches the whole team.