◆ Asana

Supervise work of production crews

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 taskGet an update from the lighting crew on their progress for the downtown shoot, then ask the…+
Get an update from the lighting crew on their progress for the downtown shoot, then ask the sound crew if they've secured the permits for the park location. Remind both that the final pre-production meeting is Thursday morning.
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 check in with the crews, look at the last five project updates for each and flag any…+
Before I check in with the crews, look at the last five project updates for each and flag any consistent delays or communication gaps. I need to anticipate where I'll get pushback when I ask for their Thursday readiness.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur lead gaffer for the downtown shoot just called in sick, and the only replacement available…+
The lead gaffer just called in sick for the downtown shoot and the replacement is less experienced.
Our lead gaffer for the downtown shoot just called in sick, and the only replacement available has less experience with the new LED setup. The director is a stickler for lighting continuity, and I'm afraid this will cause a ripple effect of delays. What's the best way to inform the director without causing panic, and what's my immediate backup plan for the gaffer's tasks?
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 finding that crews miss small but critical pre-production checks, like charging all…+
Crews consistently miss small but critical pre-production checks, leading to on-set fixes.
I keep finding that crews miss small but critical pre-production checks, like charging all batteries or confirming prop availability, which then forces on-set fixes and delays. This costs us time and credibility with the director. What habit can I change in my supervision to ensure these details are consistently covered without micromanaging?
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 Asana'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.