What Can
Go Wrong?
One point that will often arise is resistance to using
templates. There are many arguments that have been used in the past. Here are
several and your potential response:
-
“We don’t need templates because every international project
is different.” Yes, they are different in the details. However, projects of the
same type are not different at the template level.
-
“Using templates, issues, and lessons learned will take more
time.” Actually, it will take less time since more time can be expended on the
detailed tasks and work.
-
“We have gotten along without templates in the past. Why use
them now?” Ah, the fear of change again! Templates help to capture experience
and to do a better job in the present and future.
-
“There is nothing in this method for me.” Now we are getting
at self-interest. The project leader and the team are more effective. There is a
wider common understanding of what is to be done.
-
“Using templates, issues, and lessons learned will take more
time.” This is only true when they are set up. After this, time will be saved.
What is behind this resistance? Individuals, even those involved
in carrying out change, will sometimes resist change. Another fear is loss of
control. However, the bottom line is that with templates, the issues database,
and lesson learned database, there is standardization at the higher levels. But
the detailed tasks can be anything the team and leaders want them to be—giving
them flexibility and control at the individual project level.
Sections
Privacy Policy
Syndication
