> For the complete documentation index, see [llms.txt](https://docs.graphite-note.com/graphite-note-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graphite-note.com/graphite-note-documentation/understanding-machine-learning/introduction-to-machine-learning/data-analitycs-maturity.md).
# Data Analitycs Maturity
From Business Intelligence (BI) to Artificial Intelligence (AI)
Analytics maturity represents an organization’s progression in leveraging data to drive insights and decisions. This journey typically follows four levels:
**1. Descriptive Analytics:** The foundation of analytics maturity, focused on answering “What happened?” Descriptive analytics relies on reporting and data mining to summarize past events. Most organizations begin here, gaining basic insights by understanding historical data.
**2. Diagnostic Analytics:** Building on descriptive insights, diagnostic analytics answers “Why did it happen?” by drilling deeper into data patterns and trends. Using techniques such as query drill-downs, diagnostic analytics provides context and explanations, helping organizations understand the causes of past events. Traditional organizations often operate within this descriptive and diagnostic phase.
**3. Predictive Analytics:** Moving into more advanced analytics, predictive analytics addresses “What will happen?” by utilizing machine learning and AI to forecast future outcomes. Through statistical simulations and data models, predictive analytics enables organizations to anticipate trends, customer behavior, and potential risks. Elevating to this level empowers organizations to make more proactive, data-driven decisions and gain a competitive edge.
**4. Prescriptive Analytics:** At the highest level of analytics maturity, prescriptive analytics answers “What should I do?” It combines machine learning, AI, and mathematical optimization to recommend actions that lead to desired outcomes. By offering actionable guidance, prescriptive analytics not only predicts future scenarios but also prescribes the best course of action, allowing organizations to optimize decisions and drive strategic growth.
While many organizations remain in the descriptive and diagnostic phases, those aiming to stay competitive and drive innovation must elevate their analytics capabilities. **Graphite Note** is designed to accelerate this journey, helping organizations seamlessly transition into predictive and prescriptive analytics. By embracing machine learning and AI through **Graphite Note**, companies can transform their data into a strategic asset, enabling proactive decision-making and unlocking new avenues for operational efficiency and business growth.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.graphite-note.com/graphite-note-documentation/understanding-machine-learning/introduction-to-machine-learning/data-analitycs-maturity.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
