◆ Asana

Publish works across various media

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 taskPublish the new company blog post, 'Innovating for Tomorrow,' on the website and share it on…+
Publish the new company blog post, 'Innovating for Tomorrow,' on the website and share it on LinkedIn and Twitter by 3 PM today.
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 publish the new blog post, 'Innovating for Tomorrow,' make sure it's optimized for all…+
Before I publish the new blog post, 'Innovating for Tomorrow,' make sure it's optimized for all platforms. Create a compelling short summary for LinkedIn, a concise tweet with relevant hashtags, and ensure the images display correctly on both desktop and mobile for the website.
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 director just asked for a last-minute change to the blog post title, 'Innovating…+
The marketing director just asked for a last-minute change to the blog post title, but it's already scheduled for publication.
The marketing director just asked for a last-minute change to the blog post title, 'Innovating for Tomorrow,' after it's been approved and scheduled to go live on the website and social media at 3 PM. I'm afraid if I delay, we miss our optimal engagement window, but if I publish the old title, she'll be upset. What's the best way to handle this change request without disrupting the entire publishing schedule?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternPublishing new content across the website, LinkedIn, and Twitter always involves last-minute…+
Publishing across various media always involves last-minute scrambling and inconsistent messaging.
Publishing new content across the website, LinkedIn, and Twitter always involves last-minute scrambling to adapt content and often results in inconsistent messaging or formatting errors. This impacts our brand's professionalism and reach. What habit should I change to streamline our multi-platform publishing process, so we consistently deliver polished and coordinated content?
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.