---
title: "LookML | Skills We Assign For | Azendo"
description: "LookML for governed analytics — metrics as code, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/lookml/"
---

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

# LookML.

LookML is the modelling language behind Looker. Dimensions, measures and joins are defined in version-controlled files, and user queries are generated from that model rather than written directly against tables.

## Where LookML fits on a long engagement.

Defining metrics in version-controlled files is the property that makes LookML valuable. A metric change goes through a pull request with a reviewer and a history, which is the standard software practice that BI tools have generally lacked entirely.

It also means every user query is generated from the same model, so a metric cannot be calculated two ways. That consistency is the point, and it is what a tool allowing arbitrary SQL against raw tables cannot offer regardless of its documentation.

## What an assigned team does with LookML.

The model needs ownership. Without it, LookML accumulates the same debt as any codebase — duplicated dimensions, unused views, joins added for one request and never removed — and the governance benefit erodes.

Treating it as a maintained codebase rather than configuration is the practice that preserves the value, assigned under [managed data services](https://azendo.co/services/data-engineering/).

## What we use LookML for.

* Metric changes with review and history A definition change as a pull request rather than an edit in a dashboard.
* One calculation across every user Queries generated from the model, so the same metric cannot differ by author.
* The model maintained as code Refactoring and removal, so governance does not erode into sprawl.

## How LookML capacity is assigned.

LookML work is assigned inside data capacity, treated as a maintained codebase rather than as tool configuration.

## Roles we assign LookML for

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

## 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

* [Power BI — skill we assign for](https://azendo.co/skills/power-bi/)
* [Tableau — skill we assign for](https://azendo.co/skills/tableau/)
* [semantic layers — skill we assign for](https://azendo.co/skills/semantic-layers/)
* [A/B testing — skill we assign for](https://azendo.co/skills/a-b-testing/)
* [experimentation design — skill we assign for](https://azendo.co/skills/experimentation-design/)
* [causal inference — skill we assign for](https://azendo.co/skills/causal-inference/)
* [cohort analysis — skill we assign for](https://azendo.co/skills/cohort-analysis/)
* [segmentation — skill we assign for](https://azendo.co/skills/segmentation/)

## Tell us what your roadmap needs LookML 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/)