---
title: "Tableau | Skills We Assign For | Azendo"
description: "Tableau for visual exploration — extracts, governance and the Azendo roles assigned for analytics work."
url: "https://azendo.co/skills/tableau/"
---

[Skills](https://azendo.co/skills/) Analytics and BI 

# Tableau.

Tableau is a visual analytics platform built for exploration — dragging dimensions and measures to build views quickly and follow a question wherever it leads. Its strength is investigation rather than standardised reporting.

## Where Tableau fits on a long engagement.

Tableau is exceptionally good at the moment when someone does not yet know what they are looking for. Building a view, noticing something odd and following it takes seconds, and that loop is where genuine analytical insight actually comes from.

It is weaker at enforcing one version of the truth. Logic lives in workbooks, workbooks proliferate, and governance has to come from convention rather than from the tool. The common resolution is a governed warehouse underneath and Tableau used for exploration on top of it.

## What an assigned team does with Tableau.

Exploration tools resist governance by design, which is fine until two dashboards disagree in front of a board. The resolution is not to constrain the tool but to make the numbers underneath it authoritative, so exploration starts from agreed definitions.

That puts most of the durable work in the warehouse rather than the workbook, assigned under [data engineering outsourcing](https://azendo.co/services/data-engineering/) with analyst capacity on the same agreement.

## What we use Tableau for.

* Investigating an anomaly Following a question through the data quickly, where a fixed report would require a change request.
* Extract performance Refresh strategy and extract design fixed where dashboards have become slow enough to avoid.
* Governance underneath Consistent definitions provided by the warehouse so exploration starts from agreed numbers.

## How Tableau capacity is assigned.

Analyst capacity is assigned under [data science](https://azendo.co/services/data-science/), with warehouse work on the same agreement where the numbers underneath are the problem.

## Roles we assign Tableau for

* [BI Developer Data science](https://azendo.co/services/data-science/bi-developer/)
* [Data Analyst Data science](https://azendo.co/services/data-science/data-analyst/)

## Service lines it sits in

* [Data science](https://azendo.co/services/data-science/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in analytics and bi

* [time series analysis — skill we assign for](https://azendo.co/skills/time-series-analysis/)
* [Monte Carlo simulation — skill we assign for](https://azendo.co/skills/monte-carlo-simulation/)
* [stochastic modelling — skill we assign for](https://azendo.co/skills/stochastic-modelling/)
* [risk metrics — skill we assign for](https://azendo.co/skills/risk-metrics/)
* [model validation and backtesting — skill we assign for](https://azendo.co/skills/model-validation-and-backtesting/)
* [QuantLib — skill we assign for](https://azendo.co/skills/quantlib/)
* [statsmodels — skill we assign for](https://azendo.co/skills/statsmodels/)
* [SciPy — skill we assign for](https://azendo.co/skills/scipy/)

## Tell us what your roadmap needs Tableau for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)