| | 5.1 Evaluation
05. Change Policy | | |
|---|
| 51.05. Change Policy: | | 1. Why has it changed. | | 2. Because what was good enough last year will not be good enough next year. | | 3. It is not the fastest or the strongest that survive, its the most adaptable. | | 4. A trivial improvement made every few hours will have negligible impact on each person, will elevate the skill of each person by a tiny amount and it will all accumulate by the decade. | | 5. The reason that a question was asked is the reason the application had to be improved. |
| Questions and Replies: | | 1. Changes happen because people ask questions that imply that part of an application service is not self-evident. | | 2. Every question deserves a rapid reply and a considered reply. A rapid reply means an instant online response. A considered reply means an online document setting out the full policy. | | 3. The reasons that people ask questions is varies, but the cause of every question must be analysed based on behaviour and relevance. | | 4. The era of manually answering the same question over and over again must end because people demand 24*7 instant replies. | | 5. Changes are provided free of charge so where the change is an improvement, that improvement is free of charge with benefits such as more productive or more efficient. |
| Google Generation: | | 1. A Google generation of people have an expectation of instant answers to any question they ask. A business that still employs a call center to manually reply to questions 24*7 will fade away into history like the steam engine and fax machine as being too expensive to survive in a modern world. | | 2. Do not ask why has it changed, but rather, why has it not improved. |
| Document Control: | | 1. Document Title: Change Policy. | | 2. Reference: 165105. | | 3. Keywords: Change, Improvement. | | 4. Description: Application services are either alive with continual improvement or obsolete from the lack of improvement. | | 5. Privacy: ITIL public shared with all approved people. | | 6. Issued: 12 Dec 2016. | | 7. Edition: 1.1. |
|
|