As a project management consultant I sometimes get frustrated, even angry when a client quickly asks, “Can you give me a template for that?”
My frustration stems from my gut feeling that my client only wants the template to hasten the completion of their task without really understanding the reasoning for the artifact the template represents. This frustration is increased as I consider myself an Agilist and only want to create documentation when it is necessary. My Agilist side says, “No, I will not create that template! You haven’t determined whether you really need that artifact.”
This is when I must get off my “high horse” and get over myself. Templates have purpose.
- Templates are time saving tools. Yes, my client might just want to save a little time.
- Templates can improve the quality of communication.
- Templates are containers of required information. They can take the guess work out of what readers or project stakeholders require of the particular artifact.
- Templates provide for consistency of information. Readers of the artifact will have a good feel for where specific information is located because the information is consistently presented from project to project.
I also need to come to terms that sometimes my clients are not as engaged and just do not care about the project management disciplines as much as I do. My clients probably could care even less about agility in project management. Most of my clients are focused on delivering and successful delivery of the project outcomes.
Bottom line templates have a purpose in the world of project management. Develop them and incorporate them in your project management life cycle. BUT use good judgement in developing and providing templates. Do not “templatize” everything.
And just because you provide a template does not mean that you have to create a highly customized template down to the level 3 Header. This becomes a form and will most defiantly remove the thinking from the author.
