We see it all the time. From the little stickers on boxes or the huge signs touting the ‘new and improved version’ of something we already own. Household cleaning products are nearly infamous for it. Then again, they aren’t a permanent thing anyway and it won’t be too long until that container of ‘old and deficient’ product is gone and you can replace it with something better anyway.
For those of us steeped in the world of technology, it can hit even harder. There is always a later version of the software or a newer model of the hardware lurking just around the corner. Even if we’re not looking for it, our e-mail inboxes get flooded with ads offering these nearly irresistible upgrades to us. And, for some of the more savvy buyers who can live with last year’s (or last month’s) models, that means some great bargains are available.
BUT WHAT IF MY WHOLE TEAM UPGRADED?
In some recent conversations with my manager, the ‘2.0’ topic came up and it spurred my thoughts about people actually upgrading. Now, I’m not talking about any physical changes. I’m talking about a change in attitude and approach. What would happen if all the members of my project team chose to focus on their own skill sets and jobs and leave other work to other people? Line managers would focus on the people side of the house. Technical leads and architects would double down on the actual solution as called out by the requirements instead of doing technology for the sake of technology. I, as a project manager, would focus on all the blocking and tackling necessary to keep the team engaged and moving forward. And we’d all do our own jobs instead of worrying about everything that isn’t our job.
Crazy thoughts, right? But think of the productivity … think about the reduction in risk and the rise in results that would be possible. Plus, we might just find out we have the wrong people in the wrong roles and find the opportunity to make adjustments. Higher functioning, stronger teams … what a concept. All because we collectively chose to “upgrade”. Team version 2.0.
AVOIDING THE RESET BUTTON
There is a caution to this tale. If you go this route, you need to be very intentional about avoiding the ‘reset button’ that will begin reverting people to their former modes of operation. It’s a very tempting thing to go back to a comfortable routine. You’ve seen it because you’ve lived it.
PM’s diving deep into the solution – line managers debating requirements – and so much more. But those old ways cost us dearly in most cases and, once we’ve made the “2.0 decision”, we can’t afford to turn back. So don’t hit reset for any reason whatsoever!!
I’m on board with Team Version 2.0 … how about you?
Bio:
Mark Moore has held multiple professional positions in IT and business for nearly three
decades serving organizations both small and large, public and private. With over half that time as a project manager, he has successfully managed major initiatives spanning multiple years with a cost of over $3 Million and teams of over 250 people. He has been a Project Management Professional since 2002, served as President of the PMI Western Michigan Chapter, and presented at multiple NCPMI Annual Events. Mark holds a Masters of Education degree from Colorado State University with a concentration in Adult Education and Training. He is an experienced writer, speaker and presenter on project management and team building topics. Mark is the Principal Consultant for Broken Arrow Associates, LTD. He and his family live in a rural area outside of Raleigh, North Carolina.
To contact Mark for opportunities or questions, send an e-mail to info@baa-ltd.com.