◆ C#

Build interactive dashboards

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 taskBuild an interactive dashboard for the Q3 sales data, pulling from the SQL database and making…+
Build an interactive dashboard for the Q3 sales data, pulling from the SQL database and making sure the regional sales managers can filter by product line and sales rep. It needs to be live by end of day Friday.
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 this Q2 performance dashboard to the executive team, make it easier to…+
Before I present this Q2 performance dashboard to the executive team, make it easier to understand the key drivers of revenue growth. Highlight the top 3 performing product categories and make the year-over-year comparison immediately obvious.
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 lead product manager just asked for a new drill-down capability on the Q4 sales dashboard,…+
The lead product manager just asked for a new drill-down capability on the Q4 sales dashboard, but the current data model isn't set up for that granularity.
The lead product manager just asked for a new drill-down capability on the Q4 sales dashboard, but the current data model isn't set up for that granularity. I'm afraid if I push back, it'll look like I can't deliver, but if I try to force it, the performance will be terrible. I can't tell them how much work it is to re-architect the data. What's the likely diagnosis here and the best next move?
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 losing time because the data sources for dashboards change without warning, breaking…+
I keep losing time when the data sources for dashboards change without warning, breaking existing reports.
I keep losing time because the data sources for dashboards change without warning, breaking existing reports and forcing me to rebuild connections. This often happens right before a critical stakeholder meeting. What habit should I change to anticipate these shifts or make the dashboards more resilient?
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 C#'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.