Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Data analytics and AI are best understood as connected parts of a business process: organizations collect and prepare data, analyze it, build and evaluate models where useful, then deploy and monitor systems. Adoption is growing, but there is no single reliable rate that describes every organization. For U.S. firms, the Census Bureau reported one measure for November 2025–January 2026; a separate UK survey uses different questions and populations. Neither figure is a global benchmark.

What do data analytics and AI cover?

Data analytics is the work of turning data into information that can support decisions: assembling relevant records, checking and transforming them, exploring patterns, and communicating what the results mean. AI can be part of that work—for example, a model may classify, predict, summarize, or generate content—but using AI is not the same as having a complete analytics capability.

The field is not one product category or a fixed technology stack. A practical view is an operational chain: obtain data, prepare it through processes such as extraction, transformation, and loading (ETL), explore and analyze it, develop and evaluate models when the task calls for them, and deploy and observe the resulting system. These topics appear in the contents of Maxine Attobrah’s introductory book, rather than prescribing a single architecture for every organization. O’Reilly’s catalog entry lists the book as *Essential Data Analytics, Data Science, and AI: A Practical Guide for a Data-Driven World*, published by Apress in December 2024.

How widespread is business AI use?

There is no universal adoption rate: estimates depend on geography, who is surveyed, how AI use is defined, and whether results count organizations equally or weight them by employment. The U.S. Census Bureau and UK Department for Science, Innovation and Technology figures below answer different questions, so they should not be compared as if they were competing measurements of the same population.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Measure Reported finding Population and qualification
U.S. firms using AI in a business function 18% during November 2025–January 2026 U.S. Census Bureau’s 2026 AI supplement to the Business Trends and Outlook Survey; firm-weighted measure. Source and study details.
U.S. AI use, employment-weighted 32% during November 2025–January 2026 The same Census Bureau paper, but weighted by employment rather than counting firms equally. It is not the share of firms using AI.
Expected U.S. firm use 22% within six months Expectation reported in the same 2026 Census Bureau paper, not a later observed adoption rate.
Common AI uses reported by UK businesses Researching information: 28%; summarizing or collecting in-house information or drafting reports or correspondence: 21% UK Business Data Survey 2026, covering the survey’s 2025–2026 reporting period. These are reported use cases, not the percentage of all UK businesses adopting AI. Survey results and definitions.
AI tools integrated into existing systems 21% Among UK businesses using AI in the UK survey—not among all UK businesses.
Policies or guidelines covering AI access to business data and files 62% Among UK businesses reporting an AI policy or guidelines, not among all businesses.

The UK survey itself cautions that variation in definitions, tasks, and roles makes overall AI use difficult to measure consistently. That is why a useful adoption question is not only “How many businesses use AI?” but also “Which businesses, for what task, and under what definition?” The Census Bureau’s U.S. estimates and the UK survey’s findings describe their respective survey populations; neither establishes a worldwide rate.

How does analytics work move from data to deployment?

A workflow helps teams connect a business question to a usable result. The stages below are common topics in introductory analytics and AI material, not mandatory steps or a claim that every organization uses the same tools or architecture.

  1. Define the decision or task. State what someone needs to decide or do, who will use the result, and what would count as a useful answer. A vague goal such as “use AI” does not specify a measurable problem.
  2. Obtain and prepare data. Identify relevant data sources, permissions, quality issues, and any transformations needed. ETL—extracting, transforming, and loading data—is one common part of preparation; data access and suitability should be considered before choosing a model.
  3. Explore the data. Check its coverage, structure, and patterns. Exploratory data analysis can help reveal whether the available information is appropriate to the question and where important gaps or inconsistencies remain.
  4. Choose an analytical approach. Some tasks call for descriptive analysis or reporting; others may justify a machine-learning model or a generative AI tool. Select the least complex approach that can meet the task’s needs, rather than assuming every data problem requires AI.
  5. Evaluate before use. Assess whether the result is suitable for its intended setting, including how it performs on relevant cases and what errors would matter. For an AI system, the evaluation should reflect the system’s context and intended use, not just a single headline score.
  6. Deploy and observe. Decide how the result will reach its users or systems, then monitor whether it remains useful and behaves as expected in real conditions. Deployment is not the end of the work.

Attobrah’s book listing describes coverage that includes data acquisition, ETL, exploratory data analysis, machine-learning models, model evaluation, deployment, telemetry, and adversaries and abuse. It may be a useful introductory learning resource for readers who want a guided overview; the catalog entry does not establish current retailer stock, format availability, or price.

What governance does responsible AI require?

Governance makes responsibilities and safeguards part of the AI lifecycle rather than an afterthought. The National Institute of Standards and Technology (NIST) describes its AI Risk Management Framework (AI RMF) as voluntary guidance for incorporating trustworthiness considerations into the design, development, use, and evaluation of AI systems. NIST’s framework page organizes the work into four functions: govern, map, measure, and manage. See NIST’s AI Risk Management Framework.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Govern: Establish who is accountable, what policies apply, and how decisions about AI risk are made.
  • Map: Describe the system’s context, intended purpose, affected people, and relevant risks before treating performance as an abstract technical question.
  • Measure: Evaluate relevant risks and system behavior using evidence suited to the use case.
  • Manage: Decide how to prioritize and address risks, and how to respond as circumstances or evidence change.

These functions provide a way to organize risk work, not a certification or a guarantee that a system is safe. NIST’s framework page says AI RMF 1.0 is being revised and identifies its Generative AI Profile, NIST-AI-600-1, as released on July 26, 2024. Organizations relying on the framework should consult NIST’s page for its current status and applicable materials.

The UK survey offers a concrete example of why access belongs in governance: among UK businesses that reported an AI policy or guidelines, 62% said the policy included guidance on AI access to business data and files. That is a finding about businesses with reported policies, not evidence that all businesses have such safeguards or that access guidance alone is sufficient.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Why does AI need monitoring after launch?

A model or AI service can behave differently across real-world situations than it did in a controlled evaluation. NIST’s March 9, 2026 announcement about its report on monitoring deployed AI systems points to growing demand for real-world monitoring and notes that AI systems’ variability and unpredictability make post-deployment monitoring important. Read NIST’s announcement.

In practice, monitoring should connect to the system’s purpose and risks: an organization needs to know what behavior matters, what evidence can reveal meaningful changes, who reviews that evidence, and what action follows when a problem appears. NIST’s announcement establishes the importance of monitoring, but it does not prescribe one universal tool, metric, or monitoring frequency. Those choices depend on the system and its deployment context.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How should an organization decide what to do next?

The right next step depends on the task, data, users, and operating environment; there is no source-supported universal vendor ranking or guaranteed return on investment for this broad field. As practical editorial guidance, an organization can use the following questions to scope its own evaluation before selecting software or a model:

  • Business task: What decision, process, or user need should improve, and how will success be recognized?
  • Data sensitivity and access: What data is involved, who may access it, and what controls are needed for files and connected systems?
  • Integration: How must the solution work with existing business systems? The UK survey’s 21% integration finding applies only to businesses in that survey already using AI, so it is a contextual observation, not a target or benchmark.
  • Evaluation and monitoring: What errors or changes matter, how will they be detected, and who can respond?
  • Deployment environment: Where will the system run, who will use it, and what constraints follow from that setting?
  • Operating constraints: What ongoing people, process, and technical effort can the organization support?

These questions are a decision framework, not reported survey findings. The sources cited here do not establish a definitive map of analytics software categories, a best platform or model, or a universal ROI figure. A sound comparison therefore starts with a defined use case and its controls, not an undifferentiated list of vendors.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.