← The learning space

PRACTICAL AI / REVIEWED 2026-10-23

Give AI a useful brief

A clear request can be short. Include what the task actually needs.

Define the task → Supply context → Try it → Check it → Improve it

Read and practice at your own pace. These activities use prepared examples; no AI service is connected. Completion records reflect your participation, not a professional qualification. This revised edition starts a new progress record.

0 of 2 lessons complete

01Give a useful briefMake the result easy to judge.Open lesson

Start with the task, the relevant material and the result you want. Add constraints that actually matter. An audience, example or tone can help; a long persona and a list of buzzwords are not prerequisites.

Separate instructions from the material being analyzed. Say what to do when information is missing. A short prompt can be excellent if it gives enough direction for that task.

Ask for a useful explanation, assumptions, evidence or a calculation when you need to review them. Reasoning models do not need a universal instruction to reveal every internal thinking step.

Try it

Rewrite “make this better” for one real task. Specify the change you want and how you will recognize a useful result.

Which detail most improves a request to summarize meeting notes?

Try the activity and answer the check before recording completion.
02Use structure when it helpsChoose plain headings before specialized syntax.Open lesson

Plain language and headings are enough for many tasks. Separate Task, Source material, Output and Review when that makes the request easier to maintain. XML-style tags are another optional way to mark boundaries.

POML means Prompt Orchestration Markup Language. Microsoft documents HTML-like components such as role, task and example, plus tooling for composing prompts. An @ROLE or @CONTEXT convention is simply a custom text format; it is not POML syntax.

For software integration, define the expected fields and validate the returned data. A request for JSON is not a guarantee that a response conforms to a schema or that its facts are correct.

Try it

Write one clear request using headings. Add tags only if they improve clarity or a real integration requires them.

What makes structured output dependable in an application?

Try the activity and answer the check before recording completion.
Further reading: POML documentation ↗

LEAVE WITH SOMETHING USEFUL

Your brief.
Your review plan.

Choose a starting point or write your own. The builder organizes your inputs; it does not assess your expertise or send information to an AI service.

Keep your next step.

Download your notes, lesson completion and brief. Review the file before sharing it; it can contain what you typed.

Explore another learning path ↗