We could all easily fill a book with the mistakes we have made in our careers. Writing for CIO.com, Dave Sparks opts just to write a plus-sized list of the lessons he and others have learned from the School of Hard Knocks. If you read this list now, maybe you can save yourself a couple bruises to the head later.
- Complex systems are expensive.
- Complex systems will be replaced.
- Lack of pre-planning and testing will bite you.
- Don’t underestimate the complexity of running a network remotely.
- The current design isn’t going to last.
- Don’t assume.
- Backups are worthless if you don’t test them.
- Vet consultants for interoperability and business alignment.
- Always be monitoring your performance efficiently
- Just because you can’t see it, doesn’t mean it’s not out there.
- Your redundant systems will be broken.
- Crisis management training shouldn’t just be about putting out fires.
- Remember to think about the future.
- You’re only as good as your ISP.
- Don’t just look at the current choke point.
- If the network has a problem, then the business has a problem.
- When upgrading equipment, don’t make network changes.
- Watch out for those sneaky users and their nasty traffic patterns.
- Protect your network by managing your SLAs.
- Everyone has different expectations from IT.
If systems do not need to be complex, do not let them become complex. The odds are good that in spite of your best efforts to build longevity, the current design will not last for long. In general, assumptions are never a safe bet in IT. Instead, do all the planning and testing, and find ways to automate alerts that give you exactly the information you need about a problem and nothing more. Likewise, stay vigilant about locating not just current bottlenecks but anticipated future bottlenecks as well. The overall health of the network is vital to business operations.
Looking across the many lessons, the recurring themes appear to be the ephemeral nature of systems, the importance of risk management, and the need to seek out feedback about critical processes. To read these lessons in greater depth, and accompanied by myriad quotes from executives, you can read the full article here: http://www.cio.com/article/2457443/network-management/20-of-the-most-painful-lessons-it-pros-had-to-learn-the-hard-way.html