◆ HTML

Set up workflows in Microsoft Teams

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 this new project brief from the Word doc into a basic web page for the internal wiki. Just…+
Get this new project brief from the Word doc into a basic web page for the internal wiki. Just the main headings and paragraphs, no fancy styling yet. Make sure it's readable on a phone before I send it to David.
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 put this new product page live, make sure the customer can easily find the 'Add to…+
Before I put this new product page live, make sure the customer can easily find the 'Add to Cart' button and the key features. The product manager wants to see a clear path to purchase and no distractions. Also, make sure it looks good on both desktop and mobile.
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 new marketing campaign landing page is ready, but the analytics team just flagged a high…+
The new marketing campaign landing page is ready, but the analytics team just flagged a high bounce rate on mobile.
The new marketing campaign landing page is ready, but the analytics team just flagged a high bounce rate on mobile. It looks fine on my desktop, but I'm worried about missing something critical for smaller screens. I can't ask the analytics team to debug it, and I'm afraid of losing conversions if I push it live as is. What's the most likely culprit for a high mobile bounce rate on a new landing page, and what's the fastest way to check and fix it before Monday's launch?
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 spending too much time fixing layout issues and cross-browser inconsistencies after the…+
I keep spending too much time fixing layout issues and cross-browser inconsistencies after the initial build.
I keep spending too much time fixing layout issues and cross-browser inconsistencies after the initial build, especially when new content or components are added. This always eats into my testing time. What habit should I change in my initial page and CSS structuring to build more resilient pages that don't constantly break when new elements are introduced or viewed on different browsers?
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 HTML'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.