Last week I noticed this little gem over on ReadWriteWeb.com:
Gartner highlights that only 8% of enterprises have actually deployed big data projects despite 64% declaring their intention to do so.
Think about it. Out of all the hype and discussions about big data, less than 10% of enterprises have actually deployed big data projects.
Why the disconnect between the hype and the reality? I’m sure there are plenty of reasons (e.g., how Gartner identified ‘enterprises’, who they interviewed, how they defined ‘big data projects’, etc) but I suspect the real answer comes down to the simplest reason of all…nobody really understands big data enough to put big money into it.
Imagine out of all the large organizations out there with good-sized budgets. Then, imagine those same organizations struggling to implement big data. What does that mean for the small and midsized organization? if the ‘big boys’ can’t figure it out…how are the SMB’s supposed to?
Actually…if you are a SMB CIO or leader, you really shouldn’t care what the ‘big boys’ are or aren’t doing. You should be focused on how your organization can use the data you have. You should be focused on how you find information (and ultimately knowledge) from that data. The same goes for any size organization…don’t get caught up in the hype and think you have to ‘rush’ into big data projects.
Gartner says that only 8% of enterprises have deployed big data projects – but don’t think for a second that most of those 64% that have declared intent to deploy projects haven’t been spending money and trying to deploy. Don’t get caught in the hype and try to ‘keep up’. Instead, find what works for your organization and then figure out how to make those approaches work best for your data projects.
This post was written as part of the IBM for Midsize Business program, which provides midsize businesses with the tools, expertise and solutions they need to become engines of a smarter planet. I’ve been compensated to contribute to this program, but the opinions expressed in this post are my own and don’t necessarily represent IBM’s positions, strategies or opinions.