◆ Google Looker

Connect data sources to Looker Studio

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.

3prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AImprove — make it easier to acceptBefore connecting these new data sources, review the existing connections for sales and…+
Before connecting these new data sources, review the existing connections for sales and support. Tell me if there are any redundancies or potential conflicts that could slow down our dashboards, and suggest the most efficient way to integrate these new sources without breaking current reports.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentThe new Salesforce connection is showing duplicate records for customer accounts, but Zendesk…+
The new Salesforce connection is showing duplicate records for customer accounts, but Zendesk looks fine.
The new Salesforce connection is showing duplicate records for customer accounts, but Zendesk looks fine. I'm afraid if I push this live, our sales team will lose trust in the new dashboards right away. I can't tell if it's a mapping issue on our end or something in how Salesforce is structured. What's the likely diagnosis here, and what's the best next move to get clean data without delaying the Q3 launch?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CBecome — change the patternI keep spending too much time manually cleaning data after connecting new sources, which delays…+
I keep spending too much time manually cleaning data after connecting new sources.
I keep spending too much time manually cleaning data after connecting new sources, which delays getting reports to the business users. This makes me look slow and impacts their ability to make timely decisions. What habit should I change to proactively identify and fix data quality issues at the connection stage, before they become a problem in the dashboards?
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.