◆ Google Looker

Monitor Looker usage with System Activity Explores

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 taskPull the total number of active users for the 'Sales Performance' dashboard in the last 30 days…+
Pull the total number of active users for the 'Sales Performance' dashboard in the last 30 days and send it to David in IT 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 the executive meeting on Monday, analyze the usage patterns for our top 5 dashboards.…+
Before the executive meeting on Monday, analyze the usage patterns for our top 5 dashboards. Identify which teams are actually using them, and flag any dashboards that are rarely accessed despite high build effort.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur monthly BI platform bill just spiked, and my manager, Maria, is asking which dashboards are…+
Our BI platform costs are rising, but I can't tell which dashboards or users are driving the most activity and if that activity is truly valuable.
Our monthly BI platform bill just spiked, and my manager, Maria, is asking which dashboards are actually being used and if we're getting value. I can see overall usage, but I can't easily connect high usage to specific business impact or identify redundant dashboards. What's the fastest way to diagnose where the costs are coming from and which dashboards we could potentially sunset?
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 always scrambling to show the value of our BI platform to the executive team, but I lack a…+
I constantly struggle to justify the value of our BI platform to stakeholders because I lack clear, consistent data on how it's actually being used.
I'm always scrambling to show the value of our BI platform to the executive team, but I lack a consistent way to track and present actual user engagement and the impact of our dashboards. What habit should I change to better monitor and communicate the real-world usage of our analytics, so I can stop guessing and start proving its worth?
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.