Virtualization Technology News and Information
Aparavi 2019 Predictions: We Can Count on Change

Industry executives and experts share their predictions for 2019.  Read them in this 11th annual series exclusive.

Contributed by Adrian Knapp, founder and chairman of Aparavi

We Can Count on Change

One thing we can count on in technology is change. Change is, ironically, constant.

While this does not sound like a bold, visionary statement, it needs to be the core of R&D: technology will change.

Being open to change is more challenging than it seems, but here are ways I encourage the tech community - users and vendors alike - to be open to change in 2019.

1. Data utility changes.

The simple fact is we do not know exactly what we'll do tomorrow with data that we retain today. We may derive insight from it and thereby monetize it. We may produce it on demand for legal purposes, or destroy it responsibly in accordance with new regulations. We may feed it into a software program that has not yet been invented, to apply algorithms that solve a problem we do not yet have. We do not know what we'll do with it, so we retain it.

When we are open to change, we can begin to regard retention strategies differently. Managing data includes adequate protection, of course, but it also includes adequate understanding of it, and its potential. We need to be able to classify it, access it, identify it, tag it, flag it. So retain your data, but do it better, so you can accommodate change in its value or usefulness.

2. Cloud economics change.

AWS has huge market share, greater than the next four players combined, but when we are open to change we begin to understand the opportunity this affords. Up-and-coming providers are improving upon areas that might be lacking or unneeded in AWS services, and boasting huge savings over the behemoth.

As organizations increasingly shift workloads and data to the cloud, they realize different economics for storing different data. As these economics change, compare and leverage it based on what is most strategic or cost-effective. This is to bring costs down, yes, but also to eliminate the guesswork of egress which incurs added costs and risk when change takes us by surprise.

3. Roles change.

IT solution providers shift from reselling hardware to managed services. Small vendors are acquired by large vendors, which are then acquired by huge vendors. Talent inevitably moves from the CIO office to a startup company or vice-versa.

If we are open to change in these roles, we are better able to weather them. One day, a champion customer will stop responding to our emails. A trusted vendor will EOL the legacy product we need. This does not mean keep your LinkedIn profile updated, it means we must remain nimble and avoid being locked in to a business relationship, particularly one that is fundamental to our IT infrastructure.

4. Trends change.

We approach product development with an understanding of change so we can respond to trends like these, and respond to new use cases or new governance requirements, so we can connect to/with as many partners and providers as possible. Accordingly our product is architected for change, architected even with the understanding that while our company may well disappear one day, our users' data will not. Our users are not locked in to our platform - nor any other. This is not to "pitch" our particular product, it is simply to offer an example of accepting change. (My own thinking is constantly changing, often because of customer feedback, and often to the chagrin to many on our staff!)

If I leave you with only one thought, it's this: when we remain open to change, genius can come in.


About the Author


Adrian Knapp is founder and chairman of Aparavi:

Published Wednesday, January 16, 2019 7:26 AM by David Marshall
There are no comments for this post.
To post a comment, you must be a registered user. Registration is free and easy! Sign up now!
<January 2019>