◆ Google Looker

Address Looker Studio issues

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 taskThe 'Monthly Sales Overview' report isn't loading for the sales team. Fix whatever is causing…+
The 'Monthly Sales Overview' report isn't loading for the sales team. Fix whatever is causing it to fail.
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 Friday's executive review, the 'Q3 Revenue Trends' report needs to be stable and fast.…+
Before Friday's executive review, the 'Q3 Revenue Trends' report needs to be stable and fast. Identify any underlying data source issues or complex calculations that are slowing it down, and suggest optimizations to improve its performance.
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 'Customer Churn Analysis' report is showing #N/A for all values, and the marketing director…+
The 'Customer Churn Analysis' report is showing #N/A for all values, and the marketing director is asking for it.
The 'Customer Churn Analysis' report is showing #N/A for all values, and the marketing director is asking for it for her meeting this afternoon. I'm afraid she'll lose trust in our data, and I can't tell if the data source is disconnected or if a filter broke. What's the likely diagnosis and the best next move to get it working again before she sees it?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternReports frequently break or show incorrect data without anyone noticing until a critical…+
Reports frequently break or show incorrect data without anyone noticing until a critical meeting.
Reports frequently break or show incorrect data without anyone noticing until a critical meeting, leading to last-minute scrambles and lost trust. We keep losing credibility when we can't provide reliable numbers. What habit should we change to proactively identify and fix issues with our reports before they impact critical decisions?
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.