{"id":4450,"date":"2015-01-21T07:34:52","date_gmt":"2015-01-21T07:34:52","guid":{"rendered":"https:\/\/multiacademstg.wpengine.com\/20000academy\/blog\/2015\/01\/21\/early-life-support-live-environment-introduction-made-easy\/"},"modified":"2025-06-13T15:22:13","modified_gmt":"2025-06-13T15:22:13","slug":"early-life-support-live-environment-introduction-made-easy","status":"publish","type":"post","link":"https:\/\/staging.advisera.com\/20000academy\/blog\/2015\/01\/21\/early-life-support-live-environment-introduction-made-easy\/","title":{"rendered":"Early Life Support \u2013 Live environment introduction made easy"},"content":{"rendered":"

I think we would agree that if your organization wants to support a newly developed service, there is a lot of know-how, in respect to that service, needed. The point is, when the service goes into the operational phase (i.e., according to the ITIL<\/a> \u2013 Service Operation phase of the service lifecycle), users start using it. And the usual interaction starts \u2013 questions, issues, requests, comments, etc. It\u2019s a live service, after all. There is no extra time to become familiar with the service and build know-how about it. Quite the contrary \u2013 the service provider has to stay \u201cone step ahead\u201d of the users, which means that capability has to be built in a short period of time.<\/p>\n

Organization\u2019s \u201csecret weapon\u201d<\/h2>\n

Let\u2019s go one step backwards. Change is happening in the Service Transition phase (see this article about Service Transition: Service Transition in ITIL<\/a>\u00a0of the service lifecycle \u2013 something existed on paper (i.e., the service is documented in the form of a Service Design Package, which is input into Service Transition. This article explains Service Design Package: ITIL Service Design Package \u2013 everything under one roof<\/a>) and at the end of the transition phase it exists as a service. From intangible to tangible \u2013 you can use the service, test<\/a>\u00a0it, or see the results of it.<\/p>\n

Can you imagine the situation: you spent several months building and thoroughly testing a new service (part of Service Transition). The service is deployed and you turn around because \u2013 Service Operation takes over. There is no use of gained knowledge and experience if you leave for another assignment. The knowledge and experience you gained in Service Transition can be extremely useful in Service Operation (see this article about Service Operation: Service Operation in ITIL<\/a>). Otherwise, they have to start from the beginning and try to learn on the live service. That can be dangerous (making unwanted mistakes on the service while it\u2019s in use), expensive, and unprofessional (imagine that you have advanced users who gain know-how faster than the people involved in Service Operation).
\n

<\/div>