◆ Google Looker

Define Looker model sets

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 taskUpdate the 'Sales Performance' model set to include the new 'Q4_Revenue' and 'Customer_Churn'…+
Update the 'Sales Performance' model set to include the new 'Q4_Revenue' and 'Customer_Churn' models. Make sure all analysts in the 'Sales_Team' user group have access to these new models by Friday close of business.
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 push these model set changes live, review the 'Marketing_Analytics' model set. Is…+
Before I push these model set changes live, review the 'Marketing_Analytics' model set. Is anything redundant or missing for the new campaign tracking dashboards? Flag any potential permission conflicts for the 'Campaign_Managers' group.
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 new 'Product_Usage' model isn't showing up in the 'Product_Team' model set for half the…+
The new 'Product_Usage' model isn't showing up in the 'Product_Team' model set for half the team.
The new 'Product_Usage' model isn't showing up in the 'Product_Team' model set for half the team, and I'm getting frantic messages from Sarah in product. I double-checked the model set config, but I'm afraid I missed a subtle dependency or a new user attribute that's blocking access. What's the most likely cause, and how do I fix this without breaking anything else for the product team?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting caught by unexpected permission issues when I update model sets, especially for…+
I keep getting caught by unexpected permission issues when I update model sets, especially for new hires.
I keep getting caught by unexpected permission issues when I update model sets, especially for new hires who should have immediate access to standard reports. It always leads to delays and frustrated users. What habit should I change in how I define or review model sets to ensure new models are always accessible to the right people from day one?
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.