We’re usually pretty certain that we can remember anything. You know how it goes…that time you’re scheduling your next dental visit and you say to the lady at the desk that you don’t need an appointment card. Or when your wife asks you to pick something up on the way home or to do a maintenance activity this weekend. No problem, you got it up here (pointing to that empty space in your head). Do these scenarios sound familiar? Well, they do for me, so that’s enough incentive to write this article…
How many times have you been involved in a project status meeting with your team or with the project customer and things were said, decisions were made, action was planned, and then nothing happened? You follow up with the promising party and they had completely forgotten about the promised action. Or worse yet, they deny ever have made the promise. They’re not lying…they’re just clueless. And even more often what happens is they deliver something similar to what was promised, but it really doesn’t cover the need….it isn’t exactly what was discussed in the meeting.
I can say, all of these scenarios have happened on my teams, with my customers, and even I have been guilty of missing the boat on delivering something I had promised in a meeting but didn’t document and therefore it was not on my to do list. I’ve learned from these missteps to always write these tasks down…and here’s the process I follow during important project meetings to make sure these mistakes and omissions never have to happen again…

According to research done by Forrester, up to 68% of all projects finish late or fail totally. The problem is getting worse. Due to globalization many teams are not located in one location and the team’s performance suffers due to the lack of collaboration & communication. Today, there are three types of teams working on projects in small to large companies.
It’s all over the news right now…embattled Yahoo is asking new CEO Marissa Mayer to save the company. Once an internet leader, Yahoo has turned into an also-ran and a string of leaders have either left the company or were forced out leaving it in the hands of Ms. Mayer to clean up and shore up.
You and your team start to breathe a sigh of relief as you head down the home stretch on your project. Maybe it’s been six months, maybe it’s been two years. In either case you’re bound to be relieved that it’s just about over and you’re ready to successfully transition everything to the project customer. To that end, you want to make sure that ‘done’ really does mean ‘done.’ There’s nothing more embarrassing than handing the solution off to the customer and their user base only to find that you’ve left something out or forgotten or neglected to successfully complete key tasks on the schedule that were clearly your responsibility to complete.
When I was a younger project manager – much younger and more naive – I foolishly thought that every customer that stepped into a project engagement was ready for the project. They knew what they wanted, had the budget in place, a team ready to work on their side, if needed, and pretty much had at least good high-level requirements available to start the process. Some do have these things together….many, however, do not. And it’s amazing how many times project managers set project budgets and timelines assuming that most of these things are in place and therefore plan far less time in the upfront project organization and planning phases than end up being required. What happens then is unfortunate – they end up behind on the project budget almost from the beginning.
Having all members of a project team in one place is mostly a luxury any more. It’s happened to me once in the past seven years. It’s almost unheard of if you’re working for a company with more than one location and any international or work from home employees. It just doesn’t make sense to go to extreme measures to co-locate an entire team for one project – especially when so many project professionals work on more than one project at a time (sometimes as many as five or more).
Over two thousand years ago, Sun Tzu crafted his rules for waging war. The subsequent Art of War is now one of the most often cited books, reflecting strategy in all things from sports to business to the actual implementation of war. I believe one can equally rely upon the Chinese general for interpretations on running today’s ongoing corporate battles: the implementation of projects.
It’s nice when everyone is thinking the same way – or at least it seems that way. It’s nice when you’re leading a team and everyone agrees with what you’re saying – with all of the decisions you’re making – or at least it seems that way. Then one day you wake up and realize that everyone is acting like zombies and saying ‘yes’ just to move forward – maybe because they’re too busy…maybe because they don’t feel the ownership of the project. Whatever the reason, the project then becomes scary….real scary.
I caught this quote the other day on one of my kids’ favorite shows, “Peep and the Big Wide World.” Seriously, it’s one of the best shows on TV if you can find it.