It's good to be retired. The price of freedom is eternal vigilance. Avoiding the underhanded tactics of the folks who assign the tasks is among the most valuable of lessons. The other one is to make sure the requirements are clear and that "done" has an excruciatingly precise definition.As a technical consultant and project engineer, I learned very early in my career to ask several questions when I was assigned a task.
The first one was "When is this needed by?". Their answer was always "yesterday" so I had to reset their expectations to get a reasonable answer. Once I knew that, I could starts a feasibility study to see if the task could be done with the available time, resources and limitations, before I made any commitment..
The second one was "How important is it, compared to the tasks you have already assigned me". If you don't establish that, you will never be able to fit them all into your schedule and you will never deliver any on time.
Now I am retired, and spend most of my time doing graphic arts and tinkering with electronics. My schedules are flexible, dependent mostly on delivery times of ordered components but I still ask those questions when my wife assigns me any new tasks.
Regards,
Keith
I posted this originally in technical repair because giving good estimates is an important skill that's used daily to manage expectations.. The powers that be moved it to off-topic so it's now, indeterminate.Not sure why you posted this Thread
by Jake Hertz
by Jeff Child
by Jeff Child