All of us in technology operations have been there: the 2:01 a.m. SMS, the frantic call from a key user in the middle of your child’s music recital, or the email marked “TOP URGENT” just as you were about to sink your teeth into your favorite grinder.
Yes, these are all signs of the dreaded “operational emergency” — events that serve as a stronger catalyst for immediate activity than the immersion of a large chunk of potassium into a cauldron of water. But it is “what happens next” that is of critical importance on the front line of the battle to keep IT equipment and applications happily humming. Will your resulting phone call or message be eagerly accepted by a cheery, well-trained, responsive technician, or will it fall on deaf ears? Will the problem be quickly diagnosed? Will those responsible for correcting the failure have the parts, resources, security access, and skill to resolve the problem? These are all key — and sometimes career-defining “make or break” situations for the operational professional.
This content has been archived. It is available through our partners, LexisNexis® and Bloomberg Law.
To view this content, please continue to their sites.
Not a Lexis Subscriber?
Subscribe Now
Not a Bloomberg Law Subscriber?
Subscribe Now
LexisNexis® and Bloomberg Law are third party online distributors of the broad collection of current and archived versions of ALM's legal news publications. LexisNexis® and Bloomberg Law customers are able to access and use ALM's content, including content from the National Law Journal, The American Lawyer, Legaltech News, The New York Law Journal, and Corporate Counsel, as well as other sources of legal information.
For questions call 1-877-256-2472 or contact us at [email protected]
