Padding: Is this really a "Professional Option" ?

First of all, I need to say that I find the padding a bad practice, but I'll write down a situation to reactivate this interesting subject.

Situation

PM - Project Manager
T - Technician
AM - Account Manager

PM – Ask to technician the time that he/she needs to make a development.

T - Really need 1.5 days but he thinks that maybe he will find some issues (lack of information) then he tells to the PM 2 days.

PM - analyzes the data and includes +0.5 buffer or contingency, (As a PM we aren’t all subject mater experts…then is really a buffer or is a lack of information?)

AM - +0.5 benefits.

The client will receive a proposal for 3 days.

For all of us, is crystal clear that the account manger that he/she is doing properly and ethically their job. Benefits are benefits and all companies need to get it.

But why all us think that the Technician is padding?

From my point of view and based in my experience, best tool to avoid this kind of situations is communication and confidence or trust between the project manager and their team.

First of all, as far as I know, "padding" is not in the PMI vocabulary/lexicon/standards neither in other organizations related with project management. Second, the use of padding, because there is not explicit calculation method or formulas about that, adds more risk to the whole project because the inherent uncertainty (not calculated) has padding. Third, because there is no formal definition people usually confuse padding with buffers. Fourth, you allways are using a formula, explicit or implicit, to calculate extra time in your project. Just in case of implicit then it is based on your experience and is the moment where you are adding extra "something". If you have no enough information then you allways will do that. Think about your personal life. The problem here is when you do not manage it. It is catastrophic.

First of all, I need to say that I find the padding a bad practice, but I'll write down a situation to reactivate this interesting subject.

Situation

PM - Project Manager
T - Technician
AM - Account Manager

PM – Ask to technician the time that he/she needs to make a development.

T - Really need 1.5 days but he thinks that maybe he will find some issues (lack of information) then he tells to the PM 2 days.

PM - analyzes the data and includes +0.5 buffer or contingency, (As a PM we aren’t all subject mater experts…then is really a buffer or is a lack of information?)

AM - +0.5 benefits.

The client will receive a proposal for 3 days.

For all of us, is crystal clear that the account manger that he/she is doing properly and ethically their job. Benefits are benefits and all companies need to get it.

But why all us think that the Technician is padding?

From my point of view and based in my experience, best tool to avoid this kind of situations is communication and confidence or trust between the project manager and their team.

First let say that any amount (time or money) put for contingency and risk reserve should be calculated.
When people in the team put padding (unexpected) it add to the proposal cost of the project making it less competitive. I've seen case where padding was put on top of an other unknown padding. Making the projet a no go.
So padding is not an option.

I must say that I very much like this tread as it is full of excellent information's.
As I see it best way to prevent padding is proper and open communication within project team. Communication is the key and I get that.

Since estimation is (usually) done by process experts I would like to know how can you, based on your experience, effectively identify and fight or maybe its better to say manage padding?
Do you, as PMs, ask to be provided methodology of delivered estimate or...?

Thanx.

I understand that and must say that I agree but we do live in imperfect world.

I agree with Rami, Padding is NOT Contingency. Where adding reserves and contingencies is a fairly logical and acceptable choice in project management, padding is that CRIMINAL ACT which must be abhorred and avoided by all project managers. Padding means unreasonably and thoughtlessly adding illogical additions to cost or duration. Reserves and contingencies have a logical and official reasoning, or even statistics to prove it right. I would say PADDING IS NOT ALLOWED.