If the problem takes a hour to resolve, say it takes two. If you complete in less than two hours, you are hot stuff. If you go over the expected hour, but manage to get it within two hours, none will be the wiser.
This is the same reason why maintenance workers have unofficial spares. Create a buffer on the most critical places where your boss do not know about it. He will not count on it. And when Murphy shows his ugly head you have a cushion to land on, so you might avoid a meeting width Darwin. This is the same reason why soldiers have unofficial spare ammo, and why many fathers have unknown cash somewhere...
The problem is that so many people do this that when you try and give accurate information to help them make an informed decision, they just assume you are fudging the numbers and demand unrealistic results. It's an awful cycle.
zukakog it happens with EVERYTHING. so many people exxagerate so many things that when people try really hard to be accurate or even conservative with their estimates, others will assume your exaggerating too.
@@bojackson3073 I've found that if you are knowledgeable and give your buffered estimate backed with risks that most are okay. I've done this for years. What I noticed is non technical people will see the complexity, not understand it and take your word. Over time I've used Scotty's ideas here to have a decent track record on projects.
@@bojackson3073 The secret here is that you have to be good enough that your worst-case estimate is still a reasonable completion time, and you can be trusted to get it done by then even if there's a snag.
If the problem takes a hour to resolve, say it takes two. If you complete in less than two hours, you are hot stuff. If you go over the expected hour, but manage to get it within two hours, none will be the wiser.
This is the same reason why maintenance workers have unofficial spares. Create a buffer on the most critical places where your boss do not know about it. He will not count on it. And when Murphy shows his ugly head you have a cushion to land on, so you might avoid a meeting width Darwin. This is the same reason why soldiers have unofficial spare ammo, and why many fathers have unknown cash somewhere...
The problem is that so many people do this that when you try and give accurate information to help them make an informed decision, they just assume you are fudging the numbers and demand unrealistic results. It's an awful cycle.
zukakog it happens with EVERYTHING. so many people exxagerate so many things that when people try really hard to be accurate or even conservative with their estimates, others will assume your exaggerating too.
@@bojackson3073 I've found that if you are knowledgeable and give your buffered estimate backed with risks that most are okay.
I've done this for years. What I noticed is non technical people will see the complexity, not understand it and take your word. Over time I've used Scotty's ideas here to have a decent track record on projects.
@@Reliant1864 man I forgot all about this comment. Yeah if you're viewed as an expert people might be more inclined to assume you're not exaggerating.
@@bojackson3073 this is true. I genuinely try to make things work and I my do this as a way to account for unforseen issues that can detail a project
@@bojackson3073 The secret here is that you have to be good enough that your worst-case estimate is still a reasonable completion time, and you can be trusted to get it done by then even if there's a snag.