We usually think of “being ahead of schedule” as a positive trait that shows efficiency and commitment. It is viewed so positively that the negatives aspects rarely receive any attention.
In projects, the danger of being ahead of schedule is that it will be impacted by scope and requirement changes. Scope is generally defined as functionality that is covered under the project.The danger of being ahead is that generally clients ask for additional scope, or for more tasks to be completed as part of the project. Being significantly ahead may mean that there is a chance that the product needs to change significantly in order to accommodate those scope changes.
In life, I have noticed the danger of “being ahead of schedule” largely in blogging. When I originally started out with another blog, I had posts written in advance and scheduled to be published. This was great because it guaranteed new content on the blog even when my unpredictable work schedule makes it difficult for me to find the time to blog. But after awhile, I found the blog to no longer reflect who I was. The items being published were weeks behind my true thoughts and struggles, which made it difficult for me to pick up where I left on with posts. I would have to read my blog in order to bring myself to speed on my own journey. Being ahead of schedule was largely the reason the blog had to temporarily stop. I have learned that I need to be present for my blogging to be successful.
Lessons learned from that blog is having a large part in shaping this blog. I do write some posts in advance but I make sure nothing is scheduled to be published. Even when I am busy with work, I believe I should be able to devote 15 minutes to the blog to look at the previously written posts, select a post, make edits, and hit publish. The act of avoiding scheduling the posts to be published seems to be enough to make me more present.
I am learning to live in the present, rather than in the future, and enjoying each steps and moments.