◆ Google Looker

Collaborate with content, design, and product teams

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 me the weekly engagement metrics for the new onboarding flow from the dashboard, broken…+
Get me the weekly engagement metrics for the new onboarding flow from the dashboard, broken down by acquisition channel, and send it to Sarah in product and David in design by end of day.
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 week's engagement data to Sarah and David, make it clearer what's driving…+
Before I send this week's engagement data to Sarah and David, make it clearer what's driving the biggest changes. Highlight any channels showing a significant drop or surge, and add a quick note on potential reasons for those shifts.
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 content team is celebrating last quarter's blog post X and wants to know why it was so…+
The content team just asked for a deep dive on why blog post X performed so well last quarter, but the usual metrics don't seem to capture its full impact.
The content team is celebrating last quarter's blog post X and wants to know why it was so effective, but I'm looking at the standard engagement metrics and they don't seem to tell the whole story. I'm worried I'll miss something crucial if I just present the usual numbers. What's the most likely underlying driver of success for a piece like that, and what’s the best way to dig into the data to find it without getting lost in irrelevant details?
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 requests from content and product for 'deeper insights' on performance…+
I keep getting last-minute requests for 'deeper insights' that force me to scramble to connect disparate data points.
I'm constantly getting requests from content and product for 'deeper insights' on performance that go beyond the standard dashboards, often at the last minute. This forces me to pull data from multiple sources and stitch it together quickly, leading to rushed analysis and sometimes missed nuances. What habit should I change to anticipate these needs better and provide more robust answers proactively, instead of reacting to every new question?
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.