◆ Google Looker

Troubleshoot Looker Studio report creation

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 taskCreate a new report showing monthly website traffic for the last 12 months, broken down by…+
Create a new report showing monthly website traffic for the last 12 months, broken down by source.
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 the 'New Product Launch Performance' report with the product team, make sure…+
Before I share the 'New Product Launch Performance' report with the product team, make sure it's easy to understand. Identify any confusing charts or metrics, suggest clearer visualizations, and flag any data points that might be misinterpreted by a non-technical audience.
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'm trying to build a report for the 'Customer Lifetime Value' metric, but the numbers look…+
I'm trying to build a report for the 'Customer Lifetime Value' metric, but the numbers look completely wrong.
I'm trying to build a report for the 'Customer Lifetime Value' metric, but the numbers look completely wrong compared to our internal calculations. I'm afraid I'll present bad data to the CEO tomorrow, and I can't tell if the data model is misconfigured or if I'm using the wrong aggregation. What's the likely diagnosis and the best next move to get accurate CLV numbers?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternCreating new reports often takes longer than expected, delaying critical insights for business…+
Creating new reports often takes longer than expected, delaying critical insights for business decisions.
Creating new reports often takes longer than expected, delaying critical insights for business decisions. We keep losing time trying to get the right data and visualizations. What habit should we change to streamline the report creation process, ensuring we deliver accurate and timely insights to the business?
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.