|
|
|
|
|
by sublinear
22 days ago
|
|
There's also a power dynamic with which definitions take precedence. You will always have to dumb it down for upper management. As soon as the acronyms come out, they will delay making decisions so that they don't have to take questions or be held accountable. If there is an acronym they use that's spelled the same way but means something totally different, you will have to avoid using yours even when it's the most appropriate term to avoid confusion. My favorite example is ServiceNow using the term "CI" for "configuration item". You'll have to tell them in a lot more words what the deployment process is. :) |
|