Reply to thread

Message

<blockquote data-quote="Ryujin" data-source="post: 9495160" data-attributes="member: 27897">I'm thinking more about technical terms or that corp-speak previously mentioned. Like with the Lean training I had to take. Now everyone is talking about how we need to be Lean in order to deal with the problems that are directed to our group. Ummmm, that's not how it's supposed to work. We're supposed to stop them before they become problems we have to deal with. Like that hoary old buzzword that seems to have fallen out of favour; &quot;proactive.&quot; Fix it once and never worry again about that issue, or fix it every time someone trips over it.Here's an example, and I'll try to simplify for the non-techies. We recently changed our domain name, due to some perception about our founder's historic actions (we're talking pre war of 1812, 'cause he was already dead by then). That means we have to move all of our computers over to the new name. We set a deadline for the first batch to be moved over at the beginning of October. Right after they moved the guys who control the old domain terminated a portion of it, because it was what controlled the migrated computers. Great, except that it also controls printer access for maybe half the computers that haven't been moved yet, as well. Been dealing with the fallout from that ever since and it's stressing out the two of us who do the majority of that kind of support.Consider repercussions, before pulling the trigger. Dead stays dead.</blockquote>

[QUOTE="Ryujin, post: 9495160, member: 27897"] I'm thinking more about technical terms or that corp-speak previously mentioned. Like with the Lean training I had to take. Now everyone is talking about how we need to be Lean in order to deal with the problems that are directed to our group. Ummmm, that's not how it's supposed to work. We're supposed to stop them before they become problems we have to deal with. Like that hoary old buzzword that seems to have fallen out of favour; "proactive." Fix it once and never worry again about that issue, or fix it every time someone trips over it. Here's an example, and I'll try to simplify for the non-techies. We recently changed our domain name, due to some perception about our founder's historic actions (we're talking pre war of 1812, 'cause he was already dead by then). That means we have to move all of our computers over to the new name. We set a deadline for the first batch to be moved over at the beginning of October. Right after they moved the guys who control the old domain terminated a portion of it, because it was what controlled the migrated computers. Great, except that it also controls printer access for maybe half the computers that haven't been moved yet, as well. Been dealing with the fallout from that ever since and it's stressing out the two of us who do the majority of that kind of support. Consider repercussions, before pulling the trigger. Dead stays dead. [/QUOTE]

Verification