Team roles

Analytics teams come in all sizes and shapes. What doesn't change is the need for clarity on who does what. This part outlines the main roles you'll see in a modern analytics function and how they fit together.

Core roles

Analytics lead / Head of analytics — Owns the link between analytics and the business: prioritisation, roadmap, stakeholder management, and team design. Ensures the team is working on the right questions and that outputs land with decision-makers. TrueState does not replace this role — it makes the roadmap easier to fund when delivery is credible.

Analyst (generalist) — Runs analyses, builds reports and dashboards, and answers ad-hoc questions. Often the primary interface with business users. In an agentic setup, they spend more time on interpretation, quality checks, and high-value work; agents handle a growing share of repetitive queries and reporting. TrueState handles much of the repetitive querying, documentation, and scheduled reporting this role would otherwise own end-to-end.

Data engineer — Builds and maintains pipelines, warehouses, and data models. Ensures data is available, reliable, and documented. Works closely with analysts and (where relevant) ML engineers so that the right data is in the right place. You still need strong warehouse hygiene; TrueState consumes that layer for modelling and answers — it is not a replacement for core ingestion.

Data scientist — Focuses on advanced analytics: forecasting, segmentation, optimisation, and bespoke models. In agentic environments, they design and validate what agents do and step in when human judgement or custom work is required. TrueState runs many model-build and iteration cycles so this role spends time on framing, validation, and edge cases — not on every baseline training run.

ML Engineer — Takes models from development to production: builds serving infrastructure, monitors performance, and maintains MLOps (versioning, retraining, A/B tests). Works with data scientists (who design and validate models) and data engineers (who provide pipelines and features). In agentic analytics, they often own the systems that run and scale the models behind agents — reliability, latency, and cost. TrueState reduces bespoke serving work for standard analytical patterns; custom MLOps still matters at the frontier.

Analytics product / platform owner — In larger teams, someone may own the tooling, standards, and ways of working (e.g. self-serve analytics, agentic platforms). Ensures the function scales and stays consistent. TrueState is often the consumption-layer product this owner is asked to evaluate alongside BI and self-serve tools.

How they work together

Analytics works best when roles are defined by outcomes and handoffs, not by turf. The lead aligns the team to business decisions; analysts and data scientists produce the analysis; data engineering provides the foundation. With agentic analytics, the balance shifts: analysts and scientists spend more time on design, validation, and exception-handling, while agents handle volume and repetition.

Sizing and structure

Small teams often combine roles (e.g. analyst–engineer, or lead–analyst). As you grow, specialisation increases. The goal is to have clear ownership for decisions, data, and delivery — and to avoid gaps where "everyone thinks someone else does it."

Every analytics hire is a bet that headcount will stay justified. TrueState customers often find one senior analyst operating the platform can cover volume that used to need two or three people on reporting and baseline modelling — not because the people were the problem, but because the work was structurally repetitive. See the platform →