◆ Google Looker

Optimize Looker dashboard performance

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.

2prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AImprove — make it easier to acceptBefore the CEO's quarterly review, let's get the 'Executive Sales Overview' dashboard loading…+
Before the CEO's quarterly review, let's get the 'Executive Sales Overview' dashboard loading lightning fast. Identify the specific elements or queries that are slowing it down, suggest ways to simplify the underlying data model or pre-aggregate data, and flag any potential design choices that might be contributing to the poor performance.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BDecide — diagnose the stuck momentThe CEO's assistant just called, saying the 'Executive Sales Overview' dashboard is still…+
The CEO's assistant just called, saying the 'Executive Sales Overview' dashboard is still taking 15 seconds to load, even after I rebuilt several explores.
The CEO's assistant just called, saying the 'Executive Sales Overview' dashboard is still taking 15 seconds to load, even after I rebuilt several explores. I'm afraid there's a fundamental issue with how the dashboard queries the data, or a caching problem I can't see. The review is in an hour. What's the most likely reason for persistent dashboard slowness after explore optimization, and what's the fastest emergency fix I can implement without breaking anything?
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.