◆ Microsoft Power BI

Analyze Power BI 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.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskGenerate a report showing the refresh duration for all datasets in the 'Sales Operations'…+
Generate a report showing the refresh duration for all datasets in the 'Sales Operations' workspace over the last week, highlighting any that took longer than 30 minutes to complete.
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 present the Q2 performance review, analyze the 'Executive Dashboard' for any queries…+
Before I present the Q2 performance review, analyze the 'Executive Dashboard' for any queries that are taking longer than 5 seconds to execute and suggest specific optimizations to speed them up.
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 marketing team's campaign performance dashboard is taking over a minute to load, and they…+
The marketing team just told me their campaign performance dashboard is taking over a minute to load, and they need it for a client presentation in an hour.
The marketing team's campaign performance dashboard is taking over a minute to load, and they have a client presentation in an hour. I'm worried about them losing a client if the data isn't ready. I can't tell them I suspect a complex calculated column is the bottleneck but I don't have time to rebuild it. What's the likely diagnosis for the slowness, and what's the quickest way to get that dashboard loading faster for their meeting?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternUsers frequently complain about slow reports, but I struggle to pinpoint the exact visuals or…+
Users frequently complain that their reports are slow, but I don't always know which specific elements are causing the problem.
Users frequently complain about slow reports, but I struggle to pinpoint the exact visuals or calculations causing the drag, leading to a lot of guesswork. This makes me look reactive and wastes time. What habit should I change in how I approach analyzing report performance to quickly identify and address the true bottlenecks?
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 Microsoft Power BI'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.