◆ Asana

Assign project roles to team members

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 taskAssign Sarah as the 'lead designer' for the 'Website Redesign' project and David as the…+
Assign Sarah as the 'lead designer' for the 'Website Redesign' project and David as the 'content manager'.
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 acceptWhen I assign project roles for the 'Product Launch' initiative, make sure it automatically…+
When I assign project roles for the 'Product Launch' initiative, make sure it automatically grants them appropriate permissions for files and folders, and adds them to relevant communication channels for that role.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just assigned roles for the 'Q4 Marketing Campaign' project, giving Maria 'editor' access and…+
I just assigned roles for the new 'Marketing Campaign' project, but I'm unsure if I gave the right level of access to everyone.
I just assigned roles for the 'Q4 Marketing Campaign' project, giving Maria 'editor' access and John 'commenter' access to all tasks. I'm afraid Maria might need 'admin' to set up certain automations, but John shouldn't see sensitive budget details. What's the best way to verify their actual permissions and adjust them without disrupting their work?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself manually adjusting permissions and access after assigning project roles,…+
I often find myself manually adjusting permissions and access after assigning project roles.
I often find myself manually adjusting permissions and access after assigning project roles, which is time-consuming and prone to error. It feels like I'm always playing catch-up. What habit should I change to ensure that when I assign a role, the right access levels are automatically applied, saving me time and reducing security risks?
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.