Define the useful job: summarise meeting notes

A vague starting prompt is:

Summarise these notes.

A plausible before output is:

The team discussed progress, challenges, priorities, and several next steps for the coming week.

The text sounds agreeable but cannot yet support a decision. It hides assumptions, supplies no inspection point, and does not show whether the result fits the real situation. Diagnose those defects before adding instructions. Prompt improvement is not decoration; each added phrase should control a known source of variation. This summarise meeting notes example is being used here to test artifact and decision.

For this page, use the following concrete revision:

Turn the supplied meeting notes into a decision log with columns for decision, owner, due date, and unresolved question. Do not turn suggestions into decisions.

A more useful after output begins:

Decision: pilot with 20 users. Owner: Priya. Due: 30 July. Unresolved: consent wording. “Consider a newsletter” remains a suggestion, not a decision.

The after output is easier to inspect because it follows explicit constraints and makes at least one uncertainty visible. Compare it with the before output line by line for summarise meeting notes: identify what came from source facts, what the model generated, and which decision still belongs to a person. Before acting, verify the claim with the highest consequence.

Judge the response against three criteria specific to summarise meeting notes: does it honor the requested form, does it rely only on supplied facts, and can the intended person act on it? Add a fourth criterion for artifact and decision. If a criterion matters, state a pass condition before asking for another draft so the model does not move the goalposts for you.

Remember the main limit: polished text is useless when it serves the wrong job. A conversational response predicts suitable language from context; it does not inspect your home, understand institutional rules, call an expert, or accept responsibility. When the missing fact concerns safety, rights, health, money, assessment rules, or a relationship, turn the output into questions for an appropriate source. This summarise meeting notes example is being used here to test artifact and decision.

Suppose the first response invents one detail about summarise meeting notes. Quote the unsupported phrase and ask: “Keep the current format, remove that phrase, mark the missing fact as a question, and change nothing else.” This controlled follow-up tests artifact and decision while preserving material that already meets the quality bar.

Then ask the model to identify which statements came from your context and which it generated. Treat that labelling as an aid, not proof. Verify the highest-consequence statement using artifact fit and decision ownership. For the course case, write the source beside the checked statement and name who gives final approval. This creates a small audit trail that survives after the chat scrolls away. This summarise meeting notes example is being used here to test artifact and decision.

Minimise context before maximising it. Replace names with roles, remove addresses and account identifiers, summarise sensitive messages, and avoid uploading material you are not entitled to share. If the task can be completed with a blank template or offline checklist, that may be the better method. Relevance, not volume, is the standard. This summarise meeting notes example is being used here to test artifact and decision.

Set a stop rule for this summarise meeting notes exercise: stop after two targeted revisions if the response still invents constraints, ignores the format, or requires facts the tool cannot verify. At that point, complete the artifact yourself or consult a person. Knowing when conversation is no longer useful is part of proficient AI use.