◆ Google Looker

Share a report with colleagues

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 taskGet the Q3 sales performance report to David in Finance and Sarah in Marketing by end of day.…+
Get the Q3 sales performance report to David in Finance and Sarah in Marketing by end of day. Make sure they can both view it and that the data is refreshed to this 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 send this Q3 sales report to David and Sarah, make sure it highlights the top 3…+
Before I send this Q3 sales report to David and Sarah, make sure it highlights the top 3 product categories by revenue and flags any regions that are significantly underperforming their targets. I want them to see the critical takeaways immediately.
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 sales team just asked for a quick turnaround on last week's campaign performance. I pulled…+
The sales team is demanding a quick update on last week's campaign performance, but the data looks incomplete.
The sales team just asked for a quick turnaround on last week's campaign performance. I pulled the initial numbers, but they look suspiciously low, like some conversions aren't tracking right. I'm afraid to send out bad data and have them make decisions on it. What's the most likely reason for this discrepancy, and what's the fastest way to verify if the tracking is broken or if it was just a bad week?
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 getting ad-hoc requests for data that requires pulling from three different…+
I spend too much time manually pulling and combining data for ad-hoc requests.
I'm constantly getting ad-hoc requests for data that requires pulling from three different sources and then manually combining them. It eats up hours every week and delays other projects. What habit should I change to proactively structure this data or make it self-service so I'm not the bottleneck every time?
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.