◆ Asana

Update existing tasks by importing

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 taskUpdate the 'Website Redesign' project tasks using the attached CSV. Match by task name, and…+
Update the 'Website Redesign' project tasks using the attached CSV. Match by task name, and update the assignee, due date, and priority fields.
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 acceptI'm about to import a list of new feature requests into the 'Product Backlog' project. Before I…+
I'm about to import a list of new feature requests into the 'Product Backlog' project. Before I do, suggest how to structure the CSV so that the new tasks are automatically assigned to the correct team lead based on feature type, and flagged for a preliminary review.
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 client just sent a massive spreadsheet of changes for the 'Phase 2 Development' project,…+
The client just sent a massive spreadsheet of changes for the 'Phase 2 Development' project, but it's not perfectly aligned with our current task structure.
The client just sent a massive spreadsheet of changes for the 'Phase 2 Development' project, but it's not perfectly aligned with our current task structure. I'm afraid of overwriting critical information or creating duplicate tasks if I import it directly, and I can't ask the client to reformat it by Friday. What's the likely diagnosis of the misalignment, and what's the best next move to get these updates in without breaking everything?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently struggle to merge client-provided task updates into our system without manual…+
I consistently struggle to merge client-provided task updates into our system without manual data cleaning.
I consistently struggle to merge client-provided task updates into our system without manual data cleaning, especially when they use different naming conventions or omit key fields. This always adds a day to project setup and makes me look disorganized. What habit should I change to streamline this process, so I can import updates more smoothly and accurately?
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.