◆ Google Looker

Improve Looker Studio productivity

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 taskUpdate the 'Q3 Marketing Performance' dashboard with the latest campaign data from Google Ads…+
Update the 'Q3 Marketing Performance' dashboard with the latest campaign data from Google Ads and Facebook Ads. Ensure all charts reflect the new data by tomorrow morning.
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 share this 'Executive Sales Summary' dashboard with David, make it more impactful.…+
Before I share this 'Executive Sales Summary' dashboard with David, make it more impactful. Highlight the key growth metrics at the top, ensure the filters are intuitive for a non-technical audience, and suggest any redundant charts that could be simplified.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI spent all day building the 'Website Traffic Analysis' dashboard, but the marketing manager…+
I just finished the 'Website Traffic Analysis' dashboard, but the marketing manager says it's too slow to load and hard to navigate.
I spent all day building the 'Website Traffic Analysis' dashboard, but the marketing manager just told me it's too slow and confusing. She needs to present it to the VP by Friday. I'm afraid I've overcomplicated it, but I don't know what to cut without losing critical insights. What's the biggest bottleneck for dashboard performance and clarity, and what's the quickest way to simplify it for her presentation?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep building dashboards that users don't fully adopt or struggle to understand, leading to…+
I often find myself building dashboards that end up being underutilized or confusing for business users.
I keep building dashboards that users don't fully adopt or struggle to understand, leading to rework and frustration. I want them to be useful from day one. What habit should I change to ensure the dashboards I create are always intuitive, performant, and directly address the business questions of the people who use them?
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.