◆ Google Looker

Troubleshoot common Looker problems

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 taskResolve the 'data source error' message appearing on the 'Customer Churn Analysis' dashboard…+
Resolve the 'data source error' message appearing on the 'Customer Churn Analysis' dashboard for the marketing team. They can't see any data.
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 acceptThe 'Website Traffic Overview' dashboard is running really slow for everyone this morning.…+
The 'Website Traffic Overview' dashboard is running really slow for everyone this morning. Before I dive deep, give me a quick diagnosis of the most common reasons for slow performance in dashboards, so I can prioritize my investigation and get it working smoothly for the marketing team.
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 'Executive Summary' dashboard, which the CEO checks every morning, is showing a…+
The 'Executive Summary' dashboard is showing 'Configuration Error' for the CEO, and I have no idea why.
The 'Executive Summary' dashboard, which the CEO checks every morning, is showing a 'Configuration Error' message, and I can't figure out what changed. I'm afraid I made an accidental change last night, and I can't ask the CEO directly. What are the most common causes for a 'Configuration Error' in a dashboard, and what's the fastest way to diagnose and fix it before she sees it again?
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 reacting to unexpected dashboard errors, slow loading times, or data…+
I spend too much time reacting to unexpected dashboard errors and performance issues.
I'm constantly reacting to unexpected dashboard errors, slow loading times, or data discrepancies reported by users, which disrupts my planned work. This makes me feel like I'm always putting out fires instead of building new insights. What habit should I change to proactively identify and prevent common dashboard problems before they impact 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.