Earlier this summer my family and I went on vacation with two friends and their baby. We rented a cottage on the side of a lake and planned to spend a week there, enjoying the sun, the friendship and the absence of mosquitoes.
Things did not start out great.
Although we had directions to reach the cottage, we did not take the time to plan our route, thinking that the most direct road would suffice. However, because of traffic and congestion, we had to take an alternate, unplanned itinerary.
We didn't have a GPS to help us, but there was a map in one of the cars. We didn't realize until much later that the map was too old and was no longer an accurate representation of the road layout. Still, we were on our respective cell phones, trying to figure out what exits to take in order to reach our final destination more quickly.
We did not agree, but did not take a brief moment to stop and consult each other by the side of the road. Instead we kept plodding ahead, sensing we were heading in the correct direction, but not really confident about our choices.
An outside observer would have laughed at the situation: The couple in the front car had the map, but no idea where they were headed. The couple in the rear car had no map, but had an idea about where to go. The driver in the rear car was trying to tell the passenger in the front car what to look for on the map, in order to find their way.
Then came a fork in the road: The lead car took an exit because the driver was following the outdated map; the second car kept going straight, because the driver followed the road signs. This caused confusion, delays, and some frayed nerves on both sides.
In the end, both cars reached their destination, although it was definitely not as smooth and straightforward as it should have been.
So, how was that vacation trip similar to leading a team?
The leader knows the destination. A leader knows where she is headed and also knows the starting point. In IT, this translates to knowing what you want the infrastructure or the new project to look like, once completed. Although you may be clear in that vision, there is no guarantee that the team in charge of implementation sees things that clearly.
You need a map. Even if you know where you are headed, you need a map to get you there. Effective project planning is key. Just as you can look up a road map at any time to know your current position, a good plan helps you understand and visualize your progress.
Update your map. We had a map, but it was so old that it actually became a problem. The same thing is true with a project plan. Sometimes it works until the end, but sometimes it does not: unexpected delays and roadblocks will inevitably modify your original plan. It shouldn't be so rigid as to prevent you from adapting it to reflect your current reality.
Pay attention to the signs. Sometimes we become so fixated on our map, that we forget to look out the window and see the signs that surround us. When that happens, we run the risk of heading for hardship, even though things were very well planned at the onset.
Projects can easily miss deadlines or fail if nobody is paying close enough attention to the warning signs. Among the signs are: developers who fall sick after working 10- to 12-hour days for a prolonged period; requirements that are constantly being updated because various teams understand them differently; never-ending projects because there are no clear expectations of outcome.
If the warning signs become too numerous, it may be time to slow down, or even stop to re-evaluate your position.
Page 1 of 2