I just realized today that my last post was on February 7th.
When I committed to writing every week, I hadn't even started the revision process yet. As I talked about it here, it was a truly shocking experience and blew up my entire work schedule. I had to dig into personal and family time to work on my book over evenings and weekends.
But a month?? I am still a bit surprised so much time has actually passed.
The time I invested in revisions was totally worth it, and with some feedback from beta readers I really felt proud about what had been accomplished so far. I did not think there was more work to be done.
To me, submitted to copyediting (CE) was taking all the chapters, dropping it into a word document and emailing it to the CE team.
When my marketing revisions editor (MRE) told me to budget two weeks for it, I started to get a bit worried. Why would I need so much time?
My first real aloud took a WHOPPING TWELVE HOURS.
One of the estimates given to those in the book program that for a book of around 40,000 words, it should take about 6 hours to read it aloud.
My book was already closing in on 50k words, so I planned about 8 hours to factor for that.
Boy was I completely off.
"Read Alouds" is a process in which you read the book aloud. Not in your mind, but actually say the words with your voice. Act out the characters and their expressions.
When you do a read aloud, you start seeing issues with the ways the individual sentences connect with each other. And with how the paragraphs and ultimately chapters connect.
I needed to repeat this process AT LEAST TWO MORE TIMES.
Quickly I came to understand why I was asked to budget two weeks to do this.
As you go through preparing the book for copyediting, you are comparing it now to actual books on the shelf. I had to share my perspective with my MRE on how I wanted the layout of the book to look like. Here are some of the things I worked on:
By the time I completed three read alouds, I had clocked over 25+ hours of speaking.
I like talking, but not that much. And I certainly started losing my voice.
I guess I transitioned from reading aloud to whispering aloud towards the end of the third book.
Some of the changes I made were minor, but truly transformational. By working with my beta readers, I was able to:
Once I completed the submission to copyediting, my immediate thought was that these two weeks probably contributed to over 70% of the quality of the book.
Prof. Erik Koester was quick to correct me and bring me back to the "building the house" analogy.
Think of when you look to purchase a house. Do you tend to value the staging, furnishing and look and feel of the house more than the infrastructure (foundation, plumbing, heating, etc.)?
We tend to do that, and so yes, this last stage polishing of the book felt like it was most valuable.
The truth is that it just wouldn't be possible without a good foundation.
Yesterday I submitted the book to the last stage, proofreading and was rewarded with early access to my book covers that I can't wait to share with my author community.
I'm really excited about getting this book in the hands of readers in May 2022.
Dilip Ramachandran has over 15+ years of building teams, shipping delightful and highly successful enterprise software products in MarTech and FinTech at companies like Walmart, Experian, Marqeta and Bond.
Dilip wrote Gangsta Vision to help folks in product management to figure out their path and a plan to break into senior leadership.
At Nimi, Dilip is CEO and Chief Product Therapist helping high-growth FinTech startups with product and payments advisory and matching them with highly reliable and skilled experts in Sri Lanka. Learn more about Nimi at www.nimidev.com
Dilip has a Bachelor’s in Electrical Engineering from the University of Pennsylvania and resides in Oakland, California with his partner Alla, daughter Ariadna and son Wiley (a papillon-sheltie rescue). The family occasionally travels to Colombo, Sri Lanka for his work with Nimi.