Büyük Veri ve Veri Bilimi 4 dk okuma

From Big Data to Data Science: Collecting Data Is Not Enough, You Need to Make Sense of It

Consider a mid-sized retail chain processing thousands of transactions every day, logging inventory movements, and writing customer interactions to server records. Managers take pride in the sheer volume of data they hold and mention it in every strategy meeting. Yet the next season’s demand forecast is still produced by hand, based on last year’s sales figures. The data exists; the insight does not. This is a familiar picture across many Turkish businesses of similar scale. The problem is not a shortage of data — it is the absence of the skills and the mindset needed to extract meaning from what has already been collected.

The concept of big data is entering the business agenda at speed. Falling storage costs, enterprise systems that log every transaction, and the growth of online channels mean companies are generating more data than ever before. But this first wave is primarily about collection: more data, larger storage, longer retention periods. Managers often present this accumulation as a sign of progress. In reality, a raw pile of data is worthless until someone asks a meaningful question of it. The real shift begins with the second wave: deriving meaning from data, which is where data science enters the picture as a discipline that directly feeds business decisions.

Data science sits at the intersection of statistics, software development, and domain expertise. A data scientist does not merely process numbers; they know which question to ask, assess the quality of the data at hand, and translate findings into a language that decision-makers can act on. This combination of skills is rare. In Turkey, professionals with this profile are still few in number and concentrated largely in technology companies and financial institutions in major cities. Access to this capability for small and medium-sized enterprises is far more limited, because the profile is both expensive and difficult to find.

What does this mean in practice? A manufacturing company extracts sales data from its ERP system, pastes it into spreadsheets, and produces monthly reports. Those reports describe the past. But the patterns that signal an impending stock surplus or customer attrition go unexamined. The same data, processed through the right analytical framework, could directly inform procurement decisions, pricing policy, and customer segmentation. The barrier here is not technical — it is conceptual. Treating data as ‘a record of the past’ rather than ‘a clue about the future’ requires a genuine shift in thinking.

Business intelligence tools serve as a bridge for this transition. Visualization platforms such as Tableau, QlikView, and SAP BusinessObjects turn raw data into dashboards that managers can interpret. But the value of these tools also begins with asking the right question. Deciding which metrics to track, which dimensions to compare, and which threshold values should trigger an alert requires analytical judgment. The tool does not generate insight on its own; it accelerates the capacity to generate insight. Managers who grasp this distinction clearly are better positioned to achieve a genuine return on investment from their analytics spending.

At the enterprise level, the most concrete obstacle to building a data analytics capability is an incomplete total cost of ownership (TCO) calculation. Companies see the license fee but fail to account upfront for data cleansing, model development, reporting infrastructure maintenance, and — most critically — the ongoing cost of retaining skilled people. In a first-year analytics project, technical setup may represent only a third of total cost; the rest is people, process, and change management. Companies that overlook this reality purchase expensive software licenses and find the system sitting idle months later.

For decision-makers, a practical starting point is straightforward: before committing to any data investment, write down the specific question you want to answer. If that question is not clearly defined, no volume of data will keep the analytics project on course. For small and medium-sized businesses, the most pragmatic path runs through better querying of the data that existing ERP and accounting systems already produce. Learning to extract deeper meaning from what is already available is both less costly and faster to yield results than building a new big data infrastructure from scratch. That, in essence, is what data science is about: not larger piles of data, but sharper questions.

This article was originally written in Turkish by Gökhan MERCANOĞLU on January 9, 2012 and has been automatically translated into English and other languages using machine translation.

Gökhan MERCANOĞLU

Gökhan MERCANOĞLU

Teknoloji Danışmanı & Yazar

ERP, CRM, otomasyon, yapay zekâ ve kurumsal teknoloji stratejisi üzerine yazan bağımsız teknoloji danışmanı.

Büyük Veri ve Veri Bilimi — Tüm Yazılar Büyük Veri ve Veri Bilimi kategorisindeki yazıları gör →