Creating a Culture of Data

Real success in using artificial intelligence only comes after establishing a data-centered culture.

IMG_0502.JPG

Using and exploiting artificial intelligence is a goal for many enterprises around the world. Of course, before you can begin working with the cognitive technology, a number of steps must be taken.

For starters, AI requires machine learning, and machine learning requires analytics. And to work with analytics effectively, you need simple, elegant data or an information architecture. In other words, there is no AI without IA.

Although seemingly laborious and complicated, these steps are not the biggest impediments to embracing AI. Real success in using AI comes down to an organization’s ability to adopt a culture that is centered on data.

Don’t discount culture

Culture can be one of a company’s most powerful assets or its biggest obstruction. In this case, having met with thousands of enterprises over the years, the reality is that most enterprises do not have a data culture.

In fact, many do not even know they need one. Sometimes, ironically, current cultures can cloud an enterprise’s ability to see the need (they can’t see forest for the trees). In other cases, organizations are aware of the need but paralyzed by the perceived – or real – complexities.

Regardless, this must change.

Ben Thompson, the business and technology analyst and author, once wrote, “Culture is not something that begets success, rather, it is a product of it.”

If an enterprise has not had visible or material success with data, how could anyone possibly expect it to form a data culture?

Our mission is to make data simple and accessible to the world.

We are enabling companies to sow the seeds of a data culture, with a practical approach to achieve a successful outcome. Said another way, we are enabling organizations to do data science faster.

When that occurs, the results are tangible, the benefits are clear and the power of data is unleashed.


A different ROI

I once heard that the difference between a data science project and a software engineering project is that with the former you have no idea if it will actually work. Even if you are a staunch fail-fast supporter, that is too much of an unknown for many people.

Most organizations that make an investment want some understanding of how they will generate a return on that investment. I understand that is not the Silicon Valley mantra, but most enterprises are held to a different standard of ROI than Silicon Valley. It’s not right or wrong. It’s just different.

High certainty and modest returns are preferred by many enterprises over a more aggressive approach. In economics, we call this tolerance for risk-adjusted returns.

My observation is that most of the time invested in building and deploying machine learning is not spent on algorithms and models. Instead, it is spent on the most mundane of tasks: data preparation, data movement, feature extraction and other similar activities.

These are a necessary evil and the place where most risk in a data science project resides: Garbage-in/garbage-out leads to low certainty.

AI is fundamentally about using machine learning and deep learning techniques to enable applications built on data. Every organization that seeks a data culture has to pick a place to start.

Deep learning will make certain data available for the first time. If that creates momentum, with a high chance of success, start in that place. For other organizations, better predictions and automation will beget a data culture.

Regardless of which path you choose, the objective is the same: Do data science faster.

This article originally appeared on the IBM THINK blog and was republished with permission.