From the Huffington Post Why Workplace Jargon Is A Big Problem http://www.huffingtonpost.com/2014/04/25/work-words_n_5159868.html?utm_hp_ref=business&ir=Business When we replace a specific task with a vague expression, we grant the task more magnitude than it deserves. If we don't describe an activity plainly, it seems less like an easily achievable goal and more like a cloudy state of existence that fills unknowable amounts of time. A fog of fast and empty language has seeped into the workplace. I say it's time we air it out, making room for simple, concrete words, and, therefore, more deliberate actions. By striking the following 26 words from your speech, I think you'll find that you're not quite as overwhelmed as you thought you were. Count the number that LLNLs mangers use. touch base circle back bandwidth - impactful - utilize - table the discussion deep dive - engagement - viral value-add - one-sheet deliverable - work product - incentivise - take it to the ...
Comments
http://www.foxnews.com/story//0,2933,507305,00.html
Don't worry this is part of the big plan. We'll lose the ability to do anything nuclear and the world will be at peace. We'll be the first to disarm wether we like it or not and our friends around the world will voluntarily disarm simply because we lead the way. What do you think of that plan? Don't worry though, Obama will talk to them and they'll lay down their arms as he request. Realistically I hope I'm at ground zero when this all goes down.
March 9, 2009 7:56 PM
Not at all suprised that Mike had a hand in this too. Hope those involved get to visit stand in the unemployment line alongside those they layed off.
Are you telling me that the folks that designed Fogbank:
1. Didn't document the methodology?
2. Did document it but lost the documentation?
And we're going to blame LANS for either of those scenarios?
Or is it the case that the documentation was done and can only be read by the folks you say were forced out?
I am not saying that people were not force out but if the statements I read in the press are correct that documentation was lost or destroyed or never existed, I don't think you can blame THAT on a RIF.
Often the documentation sucked, was wrong due to being out of date, or never existed in the first place.
Notebooks get destroyed when people leave, often without realising that something vital is in one. It happens a lot more often when people depart suddenly.
Then there are things that one never thought about documenting, since they were "obvious" to you. Only they aren't so obvious to others.
Managers should be ensuring that projects are properly documented, but all too often they care more about deadlines than proper procedure. So these things happen and will most likely happen more often as things get worse for the labs.
Why does it cost so much to save a stupid engineering drawing ?
(Duhhh, microfilm, , Q/A, storage in vault, fire suppression system,
long term archival, security, etc). Why can’t we just plot the drawing on our
plotter and save it in one of James file cabinet … Man, I know
how to "cut cost" !!!!!
Few years later …
ULM: Where’s James file cabinet that contain the old drawings??
Staff: Oh, we got rid of all his ‘worthless’ stuff back when he was ISPed in 08.