◆ Google Looker

Automate tasks in Looker

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSet up the 'Monthly Sales Performance' dashboard to refresh every Monday at 9 AM and email a…+
Set up the 'Monthly Sales Performance' dashboard to refresh every Monday at 9 AM and email a PDF to Sarah in Marketing and David in Sales Operations. Make sure the date range is always for the previous full month.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I automate this 'Customer Lifetime Value' report for the executive team, make it easier…+
Before I automate this 'Customer Lifetime Value' report for the executive team, make it easier for them to quickly grasp the key trends. Highlight any significant changes in CLV month-over-month and suggest a clearer visualization for the top 5 customer segments.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe product team just told me the new dashboard I built for them is way off compared to their…+
The new 'Product Adoption' dashboard I built for the product team is showing wildly different numbers than their internal metrics.
The product team just told me the new dashboard I built for them is way off compared to their own numbers. I'm afraid I've misunderstood the 'active user' definition or pulled from the wrong source. What's the most likely cause for this discrepancy, and what's the fastest way to trace it back to the data source or calculation logic?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly getting requests to tweak existing dashboards or reports for slightly different…+
I keep getting pulled into ad-hoc requests for slightly modified versions of existing reports.
I'm constantly getting requests to tweak existing dashboards or reports for slightly different audiences, often just changing a filter or adding a new dimension. This eats up a lot of my time and delays bigger projects. What habit should I change to empower users to self-serve these minor variations without me becoming a bottleneck?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Google Looker's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.