Ripple Effects + How to Avoid Making Waves
When you throw a stone in a quiet pond a nice circular wave emerges on the surface of the water. That ripple effect goes out and expands across the water getting larger and larger, touching everything around it. In the IT world the ripple effects we see come from our decisions we make every day.
There are so many vendors that want to sell the latest shiny new object or the upgrade, stating that new feature that will “change the way you do business”. And yes, technology should change things as it should be used to enable new ways of business, increase productivity and collaboration as well as enhance user experience. It is always smart to be mindful of what decisions we all make in recommending technology and the ripple effects it has for the future. After all, one poor technology decision could lead to waves rather than ripples, which could easily cause a little damage. The two biggest deciding factors that will determine the patterns of your ripples (so that they do not turn into waves) are fit and planning.
FIT: Every upgrade, new solution or replacement in the enterprise can cause a ripple effect of other decisions. Like puzzle pieces, technology solutions need to fit together and integrate just right. In healthcare for example there are my versions of software that may not be compatible with each other causing a ripple affect of upgrades. Upgrading Cisco Call Manager my not allow compatibility with the specific voice recording software, AMCOM, or paging systems in the hospital. This may possibly cause issues with maintaining multiple versions of products, unnecessary costs in licenses.
PLANNING: Proper planning for the enterprise to include technology adoptions, new feature enablement needs to be thought through. Building out a 3-5 year plan, knowing that it will change and adapt with the market transitions and new technologies will make everyone’s lives a little less stressful and reactive. This is not an easy task, of course, but there are plenty of resources to help anyone get started. Regardless of which resources you utilize to map out this plan, it will be well worth your time investment. For example, building out a plan for your organization’s future will help budget out the next years of CapEx/OpEx expenditures, as well as better align technology solutions to the business outcomes your organization strives to achieve.
We have to think through everything in the organization, at each department and how they use technology. How changes in tools, and technology change the way they work. Will the enterprise need to be retrained? How do we minimize the impact of change? What “other” systems and solution does our datacenter touch? (This could cause yet another ripple.) Dropping a stone in pond makes a pretty image. When it comes to your network, ensuring that you are accounting for every ripple will ensure not just a pretty image, but a prettier business outcome.
Regional Sales Manager, David Kubica, has over 20+ years in the IT industry. He has spent most of his career as an Engineer however at ABS, David shares his talents with the Sales Teams as he works alongside Account Managers to guide them in providing expertly designed solutions to ABS clients.