> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/data/engineering-intro/data-teams.md).

# Data Teams

Analytics only lands if the team shape can ship it. Once the vision is written, the page points at how to build an analytics team and then at how to set a data science team up for success.

The same notes are in [Building Data/DS teams](/business-problems/data-science.md#building-datads-teams), [Building Teams](/ai-product/management.md#building-teams), and [Data Vision](/data/engineering-intro/data-vision.md).

[How to build an effective analytics team](https://www.analytics8.com/blog/how-to-build-an-effective-data-analytics-team/) is Kevin Lobo's best practices for building and optimizing a high-impact data analytics team, with tips on being a successful data leader.

The analytics team is one shape; the data science team needs its own foundations. See also [Setting Up Data Science Teams For Success](https://pub.towardsai.net/setting-up-data-science-teams-for-success-b1bee9765517) (October 2022), built around a figure of the three pillars of data science.


---

# 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://www.mlcompendium.com/data/engineering-intro/data-teams.md?ask=<question>&goal=<user_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.