Large Time-Wasters
Large Time-Wasters
(OP)
Curious what some of your pain points are, that take time from your actual job. For example, documentation, paperwork, entering data, etc.
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS Come Join Us!Are you an
Engineering professional? Join Eng-Tips Forums!
*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines |
|
Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.
Here's Why Members Love Eng-Tips Forums:
Register now while it's still free!
Already a member? Close this window and log in.
RE: Large Time-Wasters
It is a capital mistake to theorise before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. (Sherlock Holmes - A Scandal in Bohemia.)
RE: Large Time-Wasters
Good Luck,
Latexman
RE: Large Time-Wasters
I wouldn't say it is wasted time since I'm not going to spend time on something that doesn't need doing or doesn't have value to me. That being said, there are certainly tedious aspects to any position. Paperwork, entering data, documentation, etc. are part of the actual job. They might not be the flashy exciting parts, but there is a purpose and value to doing them. Some of them take more time than we'd like, but that's part of personal development figuring out how to do them as efficiently as possible.
For instance, the time taken to read and respond here. It isn't helping my job per se, but I find value in taking a few minutes every once in a while to step back from whatever I'm focusing on to look at unrelated things. It helps my thought process and prevents me from constantly thinking in circles if I don't take that step back.
Andrew H.
www.MotoTribology.com
RE: Large Time-Wasters
Everything else is part and parcel to your job; you cannot engineer without data, or documentation of what you are supposed to do and that documenting you completed your tasks and why decisions were made. Engineers are notoriously bad at documentation, resulting in much "wasted" time subsequently, when either that specific engineer or someone else tries to continue on with p!ss-poor documentation. The end result of that is many engineers would rather start from scratch rather than slog through poorly commented code, or designs that don't explain why certain design decisions were made. THAT is a SERIOUS time waster, and likely to result in a second, p!ss-poorly documented project. I've had a contract that completely failed because the engineer decided to start from scratch, dumping a decade of lessons-learned, and not understanding the requirements, resulting in a completely failed design that cost us a possibly lucrative follow-on contract.
TTFN (ta ta for now)
I can do absolutely anything. I'm an expert! https://www.youtube.com/watch?v=BKorP55Aqvg
FAQ731-376: Eng-Tips.com Forum Policies forum1529: Translation Assistance for Engineers Entire Forum list http://www.eng-tips.com/forumlist.cfm
RE: Large Time-Wasters
Andrew H.
www.MotoTribology.com
RE: Large Time-Wasters
As others have said, meetings. I've got it down to 2 15 minute planning meetings, and two, hour long, technical meetings a week.
Cheers
Greg Locock
New here? Try reading these, they might help FAQ731-376: Eng-Tips.com Forum Policies http://eng-tips.com/market.cfm?