Tag Archives: packt publisher

Why you can, and should, write a book

I see more people are writing a book. This is good, because it is one of those achievements you will remember many years from now. You may forget the company you work for, but you won’t forget the book you’ve written. It’s like your baby, because the amount of effort required to write it. It’s also like your children, because you can see yourself in it. Your book has more connection to you than the companies you work for, because it comes from you.

And yes, it’s a item that deserves to be in your Bucket List.

I will not kid you that writing a book is simple. It is a test of your perseverance. You will doubt yourself along the way. It is normal.

So how do you approach it?

First, learn from others. Google “why write a book” and “how to write a technical book”, and you will find plenty of lessons learned from others who have walked down that painful journey.

I gave some tips in this blog post, so I will not repeat them. Instead, I will complement and summarise the post, now that I have more experience (and pain) from it. My 2nd edition should be announced soon. No, 2nd edition is not easier for me, as I decided to expand significantly.

A book has many stages, which first time author will find overwhelming. That’s why the google in the first step is important, so you have knowledge of what you sign up for.

  1. Preparation
  2. Approach
  3. Contract & Publisher
  4. Writing
  5. Reviewing and Editing
  6. Publication & Marketing
  7. Sustaining


If you are not sure that writing a book is for you, then test your ability and seriousness.

Have a blog. If you cannot even write 5 blogs on the same topic (of a book), you cannot write a book. A small book of 100 pages equals 25 blogs. If you cannot even write 5 blog in a month, it will be a very long journey. A blog complements your book, so it’s something you should do anyway.

Write 1 chapter. Writing a chapter is much harder than writing a series of blogs. Be a small Contributor of someone else book. Even 1 chapter, which should be around 20 pages, is not a small undertaking.


  • Work with a close friend who have published before. It is good to have a coach or leader.
  • Aim small. Just 100 pages is a good start.
  • Be clear on the Primary audience and Secondary audience. It will prevent confusion later on when you are writing.
  • Once you are ready to be the main author, try to do it alone. Working with multiple authors can have its complication.
  • Avoid content that will get outdated soon. Try not to tie to a specific version of products. Products such as VSAN changes every 6 months!
  • Develop a Table of Content. For every chapter, write 3-7 points it will cover. It should not have too few points or too many points.

Contract & Publisher

  • Choose an Acquisition Editor (AE) that understands your topic well. I tried working with a large Publisher that knows VMware very well. Unfortunately, they only had 1 AE, and she did not understand VMware business, let alone my topic. So I had to explain VMware, virtualization, vSphere, and then justify why vRealize Operations is a topic that readers wanted to pay. After months of trying to justify the viability of the book, I decided to go with Packt. Vinay, the AE from Packt did not need any convincing as they knew vRealize Operations.
  • Be careful with the IP. Make sure you retain the right to change publisher in your 2nd edition. This is just in case. I’m happy with Packt.
  • If your book is based on your blog or other work, check that the Publisher can accept it. Some publisher only allow 10% public content.
  • If money is important, discuss in details on the level of transparency of the royalty. You might be shocked that there is very little transparency given to you. Ask them for a sample report. Ensure they have a website where you can login and check on demand.


  • Decide the writing style. For my case, in my region a lot of readers don’t speak English well. I remember how I myself struggled with basic English when I first learned it.
  • Make it consistent. Do you use I or We or You?
  • Use the publisher template. You should be able to get one without signing a contract. If you are writing for Packt, I can pass you the template.
  • If your book needs to have content that will get outdated, try to make that part a standalone blog. You then refer to the blog in the book. It’s much easier to update a blog than a book

Reviewing and Editing

  • Since you are writing technical book, you want to minimize Time To Market. You also do not want to drag beyond 1 year as you will lose momentum. One way to speed up is to have parallel process between Technical Review and Editing. This requires more work though.
  • The editor may not be someone familiar with the topic. So be prepared for feedback that is probably not relevant. You will work with probably 5 different people in the Publisher organization.

Publication & Marketing

  • Discuss the marketing strategy with the Publisher. Be prepared that this is a different person who may not have heard your book at all.
  • Ask exactly how much money will be allocated to market your book, and where the advertisement will be placed. Remember, the Publisher is getting the lion share, often >84%.
  • Have a person for the Foreword. You should allocate 2 weeks here, as it’s not simple to write one.
  • Avoid making it your personal book. If you work for a company, make sure your senior management appreciates what you do. A book that it relevant to your work should be supported by your company.


  • A book is not a one off engagement between you and your audience. You have blog, twitter, LinkedIn, etc. to keep that new relationship going. Use this media to keep them updated, and also to update your content.
  • A blog is also a good place to add complementary materials. You should give all the screenshots, codes, etc. so readers can reuse them.

Be an author. You can do it.

Tips for first time book author

I wanted to share the tips while they are fresh on my mind. I’ve been working closely with Packt Publishing. My first book is scheduled for December. A nice Christmas present for myself 🙂

Be a Contributor first. This lets you contribute a chapter before you attempt to write the whole darn book. Even 1 chapter, which should be around 20 – 25 pages, is not a small undertaking. Writing a chapter is much harder than writing a series of blogs. I know a few friends who have tried that and could not pass 1-2 chapters. Yes, they have been blogging for years! By being a contributor, you also get to experience the book publication process. Speaking of process….

Work with a close friend who have published before. The entire process of publication is more complex and longer than you may assume. Working with a good buddy who have gone through the process and have established working relationship with the editor mean you can focus on the content instead of the process. I used the word friend, not acquaintance. It has to be a person you know well, both in personal and professional capacity. You can avoid a lot of pains with a coach 🙂

Certainly, you may skip the points above. I did that (which kind of explains the unnecessary pains I went through). If you do, keep it short. Aim for 100 pages for your first book. The other reason for 100 page is you can always add later. My book started with 100 and ended up at 200, and eventually became 250 after the publisher formatted it. How I wish it was 100 page only! BTW, a publisher may ask you to write for at least 200 pages. That’s not a hard and fast rule.

Once you are ready to be the main author, try to do it alone. Working with multiple authors can have its complication. I know a friend whose book is delayed because a co-author was busy for an extended time. If you need multiple authors, make sure the outline is solid and finalized first. A book has to be very structured and precise, so differences in opinion can occur as there are many details to iron out. It is also hard to have consistent writing style.

Write around 50 pages before you approach a publisher. If you are using that 100-page target, you are half way done! At least complete the first 2 chapters, so you have something to show. A publisher will certainly appreciate real content when assessing the viability of your book proposal to them. It lets them judge better and faster.

Use the publisher template early. This avoids reformatting, and let you visualize what it will look like early. If you are writing for Packt, I can pass you the template. The template helps you to be mindful of keywords and texts that appear on screen. They also have guidelines on quotes and tables. I spent a lot of time on this because I did not use the template.

Give it time. Believe me, you may get sick of reading your own book! After you finish a chapter, leave it for at least 1 week. Come back to read it with a fresher perspective. Do this a few times. You should also read multiple chapters to see if they flow well, avoid any repeated content and ensure the entire structure is completely logical. I call this the process of stabilization. Some may just call it “Soaking It”.

Be clear on the Primary audience and Secondary audience. Virtualization touches a lot of things in IT, so there are many roles that you can target. In my case, the primary audience is VMware engineers, architects and administrators. They may work in VMware, partners or customers. As you know well, a VMware professional deals with many different roles in his/her organization. Do not be afraid to target different Secondary audience in different chapter.

Get reviewer early. But know them well. By knowing the reviewer knowledge and perspective, you can better understand the feedback. A feedback is always contextual, written from the reviewer view point. Know the context, and you can better decide whether you want to include it or not. Choose the wrong reviewers, and you get wrong reviews.

If you are writing about a product (e.g. vSphere), avoid working with versions that are not released yet. Minor details can change, even after a long period of beta. In my case, I have a lot of screenshots and metrics. Reviewing every screenshot and metric to see if there is any change was time consuming.

If English is not your first language, reduce the theory part, and focus on the hands-on part. English is my second language, and those chapters where I focus on the concept were harder to write. I kept rewriting and reshuffling the contents. There were occasion where I shifted an entire sub-chapter!

Decide the writing style. For my case, in my region a lot of readers don’t speak English well. I remember how I myself struggled with basic English when I first learned it. So I’m keeping it simple and conversational. In addition, infrastructure is also a dry topic in my opinion, so I want a light language. I also want to build relationships with readers via my blogs, Facebook and LinkedIn, so the language is very casual and personal. I want you to feel as if I’m talking to you as a friend. I deliberately do not want a written English.

For screenshot, keep the width below 800 pixels. Otherwise, the text will be too small on iPad or 13″ laptop. The length is less of an issue due to the book format. I had to retake quite a number of screenshots.

If you are quoting, ask for permission. Include the exact quotation, and why you’re using it. Assure the owner that you will provide proper acknowledgement.

Hope you find the tips useful. Feel free to add or correct in the comments section below.