◆ Google Looker

Fix Looker production issues

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
AExecute — do the immediate taskThe 'Daily Revenue' dashboard is broken, showing a blank screen for everyone. Can you…+
The 'Daily Revenue' dashboard is broken, showing a blank screen for everyone. Can you investigate and fix the underlying LookML error so it's live again before the morning stand-up?
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 finance team starts their day, can you review the 'Daily Revenue' dashboard? It's…+
Before the finance team starts their day, can you review the 'Daily Revenue' dashboard? It's been flaky lately. Identify any potential points of failure in the LookML or data connections that could cause it to break, and suggest a more robust setup to prevent future outages.
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 'Daily Revenue' dashboard is completely down, again. It was working fine an hour ago, but…+
The 'Daily Revenue' dashboard just went down again, and the VP of Finance needs it for an urgent report.
The 'Daily Revenue' dashboard is completely down, again. It was working fine an hour ago, but now it's showing a database connection error. The VP of Finance needs this data for a board report due this afternoon. I'm afraid I'll miss some obscure configuration or a new credential issue. What's the fastest way to diagnose and resolve this critical production issue?
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.