Google & Project Management
Google Workspace (suite formerly) has been a primary project management tool for me for a long time - it is what is organizationally available and socialized. This post and series isn't about comparing the merits of Google suite to the many other project management software that exist out there; rather it is a series of practical observations and recommendations from years of managing large, complex projects with fluid requirements, changing scope using Google Workspace. I will definitely be highlighting the limitations of the various tools, and some creative solutions to bypass them. Making the best of what you have access to is a big part of being flexible and resilient. I started my career using all Microsoft Tools, including Outlook and here I am, decades in the Google platform.
I want to be clear that when I refer to Google Workspace, I mean the paid organizational version. I have a personal account, and naturally, it has far fewer features and the good stuff usually rolls out later, very different from the access I have via the Build Up Bold account. I think this would be most beneficial to those who have some Google and/project management experience, but not the two together. There is previously developed content, whose value still stands and which I will also be including in the various posts.
The best way to learn or share is to have a real-life or close enough problem to solve, and I have a project that needs my attention: relaunching Build Up Bold, and sustaining the momentum with a challenging and engaging 9-to-5. The infographic shows the primary tools we will be using. I have access to Bard but not going to lie, I have not used it much so far. Future posts in this series will include that component.
Here’s the project as in my head for now for now — I fully expect this to evolve, and therefore to use an agile method versus a more traditional project:
Until next time.