- Atlas
- Business, Management & Finance
- Business Analytics
Business Analytics
Business analytics is the practice of turning an organization's data into decisions.
9 frameworks, from 1940 to today · Information Systems · Business, Management & Finance
- Operations Research 1940-1990
- Decision support system 1971-2000
- Data Warehousing and Business Intelligence 1990-Present
- Predictive Modeling and Machine Learning 1995-Present
- Socio-Technical Analytics Adoption 2000-Present
- Analytics Maturity Models 2005-Present
- Analytics as Organizational Capability 2007-Present
- Big Data Platforms 2010-Present
- Data and Model Governance 2015-Present
Overview
Business analytics is the practice of turning an organization's data into decisions12. Its practitioners gather data from operational systems, clean and organize it, and then apply statistical, mathematical, and increasingly machine-learning methods to describe what happened, explain why, predict what will happen, and recommend what to do. What is at stake is not the software but the decision: a retailer deciding how much stock to hold, a bank deciding whom to lend to, a hospital deciding which patients to call back. The field's history is the story of how a set of separate technical traditions—operations research, management information systems, statistics, and machine learning—converged into a single organizational capability, and of the recurring discovery that the hardest part is rarely the mathematics.
Operations research and the birth of quantitative management
Business analytics' deepest root is operations research, which grew out of military planning in Britain and the United States during the Second World War. Teams of mathematicians and scientists were assembled to solve problems such as convoy sizing and antisubmarine search; the work of Patrick Blackett's "circus" of scientists advising the Admiralty is the standard example. The essential move was to model a messy operational problem mathematically and then optimize it. After the war, these techniques moved into industry3. Linear programming, developed by George Dantzig in the late 1940s, found the best outcome in a problem defined by linear constraints—how to allocate scarce factory capacity, for instance—and the simplex method made such problems solvable by hand and then by machine. By the 1950s and 1960s, large firms had operations research groups applying queuing theory, inventory models, and simulation to production and logistics.
The limitation was structural. Operations research models were built by specialists, for well-defined problems, and they often assumed data that organizations did not have in usable form. The models lived in the analyst's office, not in the manager's workflow.
Management information systems and decision support
The 1960s and 1970s brought computers into firms, and with them the first attempt to give managers routine access to data. Early management information systems produced scheduled reports from transaction processing—inventory levels, sales totals—but they were rigid and backward-looking. A manager who wanted to ask "what if we raised the price?" had no way to do so.
The decision support system (DSS) emerged in the 1970s as the answer4. The term is associated with work at the Sloan School at MIT, particularly by G. Anthony Gorry and Michael Scott Morton, who in 1971 drew on Herbert Simon's distinction between structured and unstructured decisions to argue that computers should support the semi-structured middle ground. A DSS coupled a database, a model, and an interface so that a manager could run scenarios and compare outcomes. The idea was interactive and personal: the system did not make the decision, it helped a human make it better4. This is the direct ancestor of the modern analytics dashboard, and it established the field's central claim that the value of data lies in the decision it informs.
Data warehousing and business intelligence
Through the 1980s, analytical work was hampered by a mundane problem: operational systems were designed for transactions, not for analysis. Running a complex query against a live order-processing database could slow the business to a crawl, and data was scattered across incompatible systems. The response was the data warehouse—a separate, consolidated store of data copied from operational systems, cleaned, and organized for querying5. Bill Inmon's work in the early 1990s articulated the warehouse as a subject-oriented, integrated, time-variant store, and Ralph Kimball's "star schema" designs made warehouses practical to build. The extract-transform-load (ETL) pipeline, which pulls data out of source systems, cleans it, and loads it into the warehouse, became a standard piece of infrastructure56.
On top of the warehouse sat business intelligence (BI): reporting, dashboards, and online analytical processing (OLAP), which let users slice data by dimension—sales by region by month by product—without writing queries178. The term "business intelligence" was popularized by Howard Dresner of Gartner in the late 1980s. By the 2000s, BI was a large software market, and the "single version of the truth" held in the warehouse was the organizing ideal of corporate reporting.
The analytics vocabulary and the maturity ladder
The word "analytics" gained currency in the 2000s, partly through Thomas Davenport and Jeanne Harris's 2007 book Competing on Analytics, which argued that firms could build durable advantage by making decisions on evidence rather than intuition. A widely used four-level scheme took hold: descriptive analytics (what happened), diagnostic (why), predictive (what will happen), and prescriptive (what should be done). These levels map onto the field's history—reporting, then modeling, then optimization—and they gave managers a way to talk about ambition.
Alongside this came maturity models, which describe an organization's progression from ad hoc, spreadsheet-driven reporting toward governed, enterprise-wide, and eventually predictive and prescriptive analytics. The analytics maturity ladder is best understood as a management tool rather than a scientific theory: it helps organizations benchmark themselves and plan investment, and its stages are heuristic rather than empirically validated.
Machine learning enters the toolkit
The statistical tradition had always been part of analytics, but machine learning changed its character. Where classical statistics emphasized explanation and inference on modest samples, machine learning emphasized prediction on large data. The field's foundations were laid earlier—Frank Rosenblatt's perceptron in 1958, the backpropagation algorithm popularized in the 1980s—but the decisive shift came with the 1990s and 2000s, when methods such as decision trees, support vector machines, and ensemble methods like random forests proved effective on real business problems. The Netflix Prize, a public competition running from 2006 to 2009 to improve a recommendation algorithm, became a famous demonstration that predictive modeling could be a business asset.
The practical consequence for analytics was a change in what a model was for. A regression model might explain which factors drive churn; a machine-learning model might simply predict which customers will churn, well enough to act on. This raised new problems—overfitting, interpretability, and the difficulty of deploying models into live systems—that the field is still working through.
Big data and the platform era
Around 2010, the volume, velocity, and variety of data outgrew the warehouse. Web logs, sensor readings, and social media streams arrived too fast and too unstructured for traditional ETL and relational databases. The response was a new stack: distributed storage and processing systems such as Hadoop, inspired by Google's published designs for its file system and MapReduce programming model, and later in-memory and streaming frameworks. The "big data" movement promised that cheap commodity hardware and new tools could handle data at a scale that had previously required expensive specialized systems.
The effect on analytics was to widen its inputs and lower its cost. Cloud platforms made large-scale computation rentable by the hour, and open-source tools for statistics and machine learning—notably the R and Python ecosystems—put modeling within reach of analysts without a specialist operations research group. The warehouse itself was rebuilt for the cloud, and the boundary between data engineering and analysis blurred.
The present: from projects to capability
Today business analytics is less a set of techniques than an organizational function. Most large firms have analytics teams, data governance arrangements, and platforms that combine warehouse, lake, and streaming data. The methods in use descend directly from the history above: descriptive reporting and OLAP from the BI era, forecasting and optimization from operations research, predictive modeling from machine learning, and decision-support interfaces from the DSS tradition. The recurring lesson, visible across every era, is that the technical model is necessary but not sufficient—data quality, organizational adoption, and the fit between the analysis and the decision determine whether any of it matters1.
The open questions are largely about responsibility and integration. How should organizations govern the data and models they now depend on9? How can predictive and prescriptive systems be made interpretable enough to trust and auditable enough to regulate? And how does analytics move from answering questions after the fact to shaping decisions as they are made? These are the questions the field's next chapter will be written around.
References
- Business analytics (introduction, Challenges), Wikipedia
- Analytics, Wikipedia
- Operations research (History), Wikipedia
- Decision support system (History, introduction), Wikipedia
- Data warehouse, Wikipedia
- Extract, transform, load, Wikipedia
- Business intelligence, Wikipedia
- Online analytical processing, Wikipedia
- Data governance, Wikipedia
The frameworks of Business Analytics
Each framework is a way of working the field has used: when it held, and the question it answers.
- 1940-1990
- 1971-2000
Decision support system
How can computers help managers make semi-structured decisions?
- 1990-Present
Data Warehousing and Business Intelligence
How can firms get one trusted version of their data?
- 1995-Present
Predictive Modeling and Machine Learning
How can we predict future outcomes from data?
- 2000-Present
Socio-Technical Analytics Adoption
Why do organizations adopt or resist analytical tools?
- 2005-Present
Analytics Maturity Models
How advanced is an organization's use of analytics?
- 2007-Present
Analytics as Organizational Capability
Can analytics be a durable source of competitive advantage?
- 2010-Present
- 2015-Present
Data and Model Governance
How should data and models be controlled and audited?
How the ideas connect
Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.
Decision support system influenced by Operations Research
Gorry and Scott Morton's 1971 DSS framework drew on Simon's structured/unstructured decision distinction and on the OR tradition of formal models, embedding a model base alongside a database so managers could run scenarios. The DSS thus carried OR's optimization and simulation models into an interactive managerial tool.
Carried by G. Anthony Gorry; Michael Scott Morton.
Data Warehousing and Business Intelligence grew out of Decision support system
Business intelligence reporting and OLAP grew out of the DSS aim of giving managers interactive access to data for decisions, but replaced the personal model-driven system with a shared warehouse and standardized reporting. The dashboard is the direct descendant of the DSS interface.
Carried by Howard Dresner; Bill Inmon.
Predictive Modeling and Machine Learning influenced by Data Warehousing and Business Intelligence
The consolidated, cleaned data of the warehouse gave machine-learning modelers the large structured datasets they needed, and BI's reporting questions (who will churn, what will sell) set the prediction targets. Data warehousing supplied the data infrastructure on which predictive analytics ran.
Carried by Ralph Kimball.
Analytics Maturity Models influenced by Data Warehousing and Business Intelligence
Analytics maturity models took the BI progression from ad hoc reporting to enterprise-wide governed reporting as their first rungs, then extended the ladder toward predictive and prescriptive stages. The maturity stages are essentially a management formalization of the BI adoption path.
Big Data Platforms replaced Data Warehousing and Business Intelligence
Big data platforms arose because the relational warehouse and ETL pipeline could not handle web-scale, unstructured, fast-arriving data, and Hadoop-style distributed systems replaced the warehouse as the primary store for many analytical workloads. The warehouse survived as one component of a broader stack.
Carried by Hadoop.
Analytics Maturity Models influenced by Predictive Modeling and Machine Learning
Maturity models placed predictive and prescriptive analytics, the machine-learning methods, at their upper levels, so the ladder's ambition was defined by what predictive modeling could do. The stages borrowed the descriptive-to-predictive vocabulary that machine learning made salient.
Big Data Platforms influenced by Predictive Modeling and Machine Learning
Machine-learning workloads, with their need to train on very large datasets, drove the demand for distributed and in-memory computation that big data platforms supplied, and open-source Python and R ecosystems put modeling on top of them. The platform era was built partly to feed predictive models.
Data and Model Governance influenced by Predictive Modeling and Machine Learning
Data and model governance emerged in response to the deployment of predictive models, addressing overfitting, interpretability, and auditability that machine learning raised. Governance frameworks were built to manage the risks of models already in production.
Analytics as Organizational Capability grew out of Analytics Maturity Models
The idea of analytics as an organizational capability grew out of maturity thinking: Davenport and Harris's 2007 argument that firms compete on analytics generalized the maturity ladder into a claim about durable firm-level advantage. Capability is the maturity model turned from a benchmark into a strategic resource.
Carried by Thomas Davenport; Jeanne Harris; Competing on Analytics (2007).
Data and Model Governance influenced by Big Data Platforms
The scale and heterogeneity of big data platforms created the data-quality, lineage, and privacy problems that governance regimes were designed to control. Governance grew as the regulatory and managerial counterpart to the platform stack.
Predictive Modeling and Machine Learning influenced by Operations Research
Predictive modeling inherited from operations research the practice of fitting formal models to operational data for forecasting and classification, and OR's optimization goals fed into prescriptive analytics. The methods differ, but the modeling-for-decisions stance passed across.
Analytics as Organizational Capability influenced by Socio-Technical Analytics Adoption
Socio-technical adoption research supplied evidence that analytics value depends on organizational fit and use rather than technology alone, which the capability argument absorbed into its claim that analytics is an organizational rather than technical asset. The capability view generalized adoption findings to firm strategy.
Beyond the field
Where Business Analytics's ideas came from in other fields, and what they led to there: the strongest 12 of 45 links.
Decision support system influenced by Bounded Rationality and Semi-Structured Decision Framework in Decision Support Systems
Simon's bounded rationality and his distinction between programmed and non-programmed decisions supplied the core rationale for DSS: computers support semi-structured decisions that neither fully automate nor leave to unaided judgement. Keen and Scott Morton built the DSS framing directly on this decision-theory base.
Carried by Herbert A. Simon; Peter G. W. Keen; Michael S. Scott Morton.
Decision support system influenced Business intelligence in Decision Support Systems
Business intelligence grew out of decision support systems: the DSS tradition of model- and data-driven tools for managerial decisions, established by Gorry and Scott Morton in the early 1970s, supplied the core problem and vocabulary that BI vendors later recast as query, reporting and OLAP tools.
Carried by Gorry and Scott Morton, A Framework for Management Information Systems (1971).
Decision support system led to Business analytics in Decision Support Systems
Business analytics grew directly out of decision support systems, inheriting the DSS focus on data- and model-driven managerial decisions and recasting it as statistical and predictive analysis. The DSS literature of the 1970s and 1980s is the direct ancestor of the analytics label.
Carried by Gorry and Scott Morton, A Framework for Management Information Systems (1971).
Predictive Modeling and Machine Learning influenced Machine Learning for Targeting and Personalization in Marketing Science
Predictive modelling and machine learning supplied the algorithms, validation practices and predictive framing that targeting and personalisation systems apply to consumer data.
Predictive Modeling and Machine Learning led to Machine Learning and Alternative Data Credit Assessment in Credit Analysis
Alternative-data credit assessment is a direct application of predictive modeling and machine learning to lending decisions. The methods of supervised learning, feature engineering and model validation were carried over from general predictive modeling practice into credit scoring.
Predictive Modeling and Machine Learning influenced Marketing Automation and AI Personalization in Digital Marketing
Predictive modeling and machine learning provide the core techniques of AI personalization: propensity models, recommendation algorithms and segmentation learned from behavioral data. Marketing automation vendors built these methods into campaign targeting and next-best-offer engines.
Big Data Platforms grew out of Hadoop Ecosystem in Big Data Processing
The Hadoop ecosystem is the open-source implementation lineage that big data platforms built on, with HDFS and MapReduce as the substrate for later platform architectures.
Carried by Doug Cutting.
Data and Model Governance grew out of Data Governance in It Governance
Data and model governance grew out of IT data governance, extending its stewardship, ownership and quality controls to analytical models and machine-learning pipelines.
Operations Research led to Systems Analysis in Decision And Risk Analysis
Systems analysis drew on operations research as practised in business and management, extending its quantitative methods from operational problems to system design.
Operations Research influenced Business analytics in Decision Support Systems
Operations research contributed optimization and quantitative modeling methods that business analytics adopted for prescriptive analysis. The OR tradition of applying mathematics to managerial decisions is a direct methodological source.
Decision support system influenced Data-Intensive and Algorithmic Systems in Information Systems
Decision support systems provided the organizational and managerial framing that later algorithmic decision support inherited, including the idea of computational aids embedded in managerial work. The newer systems replaced rule-based DSS with data-driven learning while keeping the decision-support question.
Decision support system led to DSS Component Architecture in Decision Support Systems
The DSS component architecture is a refinement of the general DSS concept as treated in business analytics. The component decomposition was carved out of the broader DSS framework.

Business Analytics is a planet in Nousfarer
Its city has a tower for each of these 9 frameworks. Land, walk in, and climb one concept at a time.
Land on Business AnalyticsRelated fields
Fields its ideas are linked to
- Decision Support Systems 11 links
- Data Science 4 links
- Management Accounting 3 links
- Big Data Processing 3 links
- Data Visualization 3 links
- Data Modeling 2 links
- Information Systems 2 links
- Managerial Decision Making 2 links
- Decision And Risk Analysis 2 links
- Machine Learning 1 link
- Credit Analysis 1 link
- Data Mining 1 link
More in Information Systems
- Decision Support Systems
- Digital Strategy
- Electronic Commerce
- Enterprise Architecture
- Enterprise Systems
- Information Systems
- It Governance
- Platform Strategy
- Sociotechnical Systems
- Systems Analysis And Design
See where Business Analytics sits on the Map of Human Knowledge