The other day, I was feeling bad about not getting enough writing done. Despite having written more than 45,000 words in just over two months, I wanted to have written more.
Contrast that feeling to when I worked at a big tech company. As I grew in my career, I could put in a hard day’s work and feel good about my code, knowing that three layers of management above me (sometimes more) were responsible for making sure the product shipped. Much to the chagrin of the people whose job it was to ship, I would have conversations like this:
Boss: I need your estimates for how long it will take to finish this feature.
Me: I don’t give estimates. Here’s the list of tasks I expect to do.
Boss: But if you don’t give me estimates, how can I know when the feature will be done?
Me: Even if I gave you estimates, you still wouldn’t know when the feature will be done, because human beings are generally terrible at estimating complicated, creative tasks.
I realized that I am now both the boss and the employee of Abigail Welborn, Inc. (not a real thing). As it turns out, not only do I not like being the boss, I don’t like working for me, either. As the boss, I can see the end goal so clearly — the beautiful, finished book. At the end of a work day, when the writer (also me) tries to feel good about hitting the goal of 2,000 words written, the boss in me sees only how far I have to go and wishes I could’ve worked just a little bit harder.
But at least I figured out why I’m such an awful boss. I hate not knowing when my book will be done. I can’t look forward to it or plan for it. Even tracking my progress doesn’t make me feel like I’m getting closer, because I just don’t know how long it’s going to take to edit this thing into shape.
So, former bosses (and others who were tracking my work), while I can’t say I’m sorry for refusing to give you estimates, I can now say that I feel your pain. I’ll try to be as nice to me as you were.