# Turn your Looker dashboard into a Monday leadership review

> Every Monday at 7am, your leadership team gets a written business review built from your Looker numbers, archived in Notion and sent by email.

- Workflow type: agent
- Services: Looker, Notion, Gmail
- Categories: Operations
- Published: 2026-08-07

## What it does

- Reads every tile on your main Looker dashboard each Monday morning, so a metric someone adds later gets picked up automatically instead of being missed
- Writes a narrative review in plain prose that explains what moved and the most likely reason behind it, rather than listing numbers back at you
- Names the three things genuinely worth leadership meeting time, and flags any metric that has missed its target two weeks running
- Files each week's review as a page in a Notion database so you build a durable archive, then emails the leadership list a short summary with the link

## What you'll need

- A Looker account with permission to view the dashboard you want reviewed
- A Notion workspace with a database set aside for the weekly reviews, shared with your Notion connection
- A Gmail account to send from, plus the email addresses of your leadership list
- The targets you measure key metrics against, so the review can tell you what is behind

## Prompt

Every Monday at 7am, build a narrative weekly business review from my main Looker dashboard, archive it in Notion, and email a short summary to my leadership list.

Start in Looker. Use Search Dashboards to find my main dashboard by title, then Get Dashboard to read its metadata. Do not work from a hardcoded list of tiles. Use Get All DashboardElements to discover every tile currently on the dashboard, and Get DashboardElement when you need more detail about a specific one. Then run each tile the right way for its type: use Run Look for tiles backed by a saved Look, and Run Query for tiles backed by a query defined on the dashboard itself. Discovering the tiles at run time is the point, because it means a metric someone adds to the dashboard next month shows up in the review automatically instead of being silently missed.

Pull enough history to talk about direction rather than level. For each tile, get the current week and the preceding weeks so you can describe a trend, say whether a move is inside normal week to week noise, and compare against the recent average instead of only against last week.

Before writing anything, use Query a Data Source in Notion to read the most recent review pages from my weekly review database, sorted newest first. Use them for continuity: what we said last week, whether what we predicted actually happened, and which metrics were already flagged as behind target. The archive is the memory for this workflow, so read it before you add to it.

Write the review as prose for executives, not as a metric dump. For each meaningful movement, say what moved, by how much, and why it most likely moved. Ground the explanation in what the data can actually support: look for a metric that moved in step with it, an effect isolated to one segment or channel, or a change in the mix underneath a flat headline number. Where you are inferring rather than reading a cause directly, say so plainly instead of asserting it. Skip metrics that did nothing. A metric that was flat and is meant to be flat does not need a paragraph.

Explicitly flag any metric that has missed its target two weeks running, using the previous reviews from Notion to establish the repeat. Call these out prominently rather than burying them in the body, and note whether the metric is getting worse, holding steady, or recovering while still short. A repeat miss is a different conversation from a first miss and the review should make that obvious.

Close the review with the three things genuinely worth discussing in the leadership meeting. Choose them on the basis of what needs a decision, what is trending badly enough to matter soon, or what nobody currently owns. Do not simply pick the three largest percentage changes. For each one, state the question leadership actually needs to answer, not just the observation behind it.

Save the full review as a new page in my Notion weekly review database using Create a Page, titled with the week ending date so the archive stays sortable. Put the narrative in the page body and set whatever properties the database has, such as the week, the headline summary, and the metrics currently behind target.

Then use Send a Message in Gmail to email my leadership list. Keep the email short: a two or three sentence read on the week, the repeat target misses, the three discussion items as a list, and a link to the Notion page for anyone who wants the detail. The email is the briefing people read on their phone before the meeting, so it should stand on its own without the link being opened.

If a tile fails to run or returns no data, say so in the review and carry on with the rest. A partial review that names its gaps is far more useful than a failed run, and silently dropping a metric is the one outcome to avoid.

## How to customize

- Change the day and time. Monday at 7am is the default, but plenty of teams run it Friday afternoon instead
- Point it at a different dashboard, or at a different Notion database if you keep reviews per team
- Adjust who receives the email, and how many discussion items it surfaces. Three is the default
- Set the target for each metric so the two weeks running warning reflects your actual goals

## Example output

Subject: Weekly business review, week of 3 August

The short version: revenue held, acquisition softened, and support is the thing to watch.

New bookings came in at 412k, down 6 percent on last week but still ahead of the trailing four week average. The drop is concentrated entirely in self serve, where signups fell 14 percent while enterprise pipeline was flat. That pattern lines up with the paid search budget change that went in on Tuesday, so this looks like a spend decision rather than demand weakness.

Support first response time is now at 4.2 hours against a target of 2 hours. This is the second week running it has missed, and it has moved in the wrong direction both weeks.

Three things worth the meeting:
1. Whether the paid search cut was deliberate at that size, and who owns reversing it
2. First response time missing target two weeks running, with ticket volume flat, which points at staffing rather than load
3. Enterprise pipeline has not moved in three weeks, which matters more than this week's revenue number

Full review with every metric: [link to the Notion page]

## FAQ

### What happens if someone adds a new chart to the dashboard?

It gets included automatically. The review reads your dashboard fresh every week and works out which tiles are on it at that moment, so you do not have to remember to update the workflow when the dashboard changes.

### Does this work with dashboards built from saved reports and from one-off queries?

Yes. Tiles built from a saved report and tiles built from a query written directly on the dashboard are both handled, so a mixed dashboard works fine.

### How does it know a metric has missed its target two weeks in a row?

Before writing, it reads the most recent reviews from your Notion archive. That tells it what was already behind last week, so a repeat miss gets called out rather than quietly reported as a fresh problem.

### Can I read it before my leadership team does?

Yes. Point the email at yourself for the first few weeks, review what it produces, then widen the recipient list once you are happy with the tone and the judgement calls.

### Will this replace our analyst?

No, and it is not meant to. It removes the copying and pasting of numbers into a document every Monday so your analyst spends their time on the questions the review raises instead of assembling it.

Use this prompt in General Input: https://www.generalinput.com/prompts/turn-your-looker-dashboard-into-a-monday-leadership-review