Netfor best practices
0 likes111 views
This document outlines best practices for Netfor based on ITIL frameworks and experience. It discusses starting CSI (Continual Service Improvement) where you are currently rather than waiting for perfect conditions. It also emphasizes preparing all employees through training and overcommunication, being flexible to customize implementations based on findings, adding value for clients and employees, and maintaining a human focus alongside processes. The overall message is to continuously improve services using a balanced approach that considers people and flexibility alongside established frameworks and quick results.
Netfor best practices
- 1. Netfor Best Practices Based on the ITIL® Framework and Years of Hard-Earned Experience
- 2. Groundwork • The Netfor Lens • Why we drink the ITIL® Kool-Aid “If you don’t know where you are going, than you probably won’t end up there.” - Forrest Gump
- 3. Best Practices #1 Start where you are. • Don’t wait for the perfect conditions – they’ll never come • Use the opportunity to assess where you are and where you want to go • Use this starting point to work toward quick results and momentum • Tweaking vs New Design and when it calls for each • CSI at it’s best
- 4. Best Practices #2 Prepare Everyone. • Planning and training; I mean training and planning • The value of a good checklist • Over communicate • Using the RACI Model when necessary and working externally
- 5. Best Practices #3 Be Flexible. • CSI by nature means investigating where you are, what got hijacked and how it needs to change • Customizing the training, the implementation, the processes • The road isn’t always straight so enjoy the journey
- 6. Best Practices #4 Add Value. • Get clarity on where the value is for your clients and the work ahead • To your clients and to your employees – work to find the balance • To the process and the CSI model
- 7. Best Practices #5 Be Human. • A business approach that’s too process-centric holds risk • People have the ideas and get the work done • See best practice #2