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.
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.
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.
Loading the contact form… You can also email hello@azendo.co.
We reply within one working day. No obligation, and no newsletter.