Choose a Small, Helpful Task

In this chapter

• Distinguish drafting from decision-making
• Describe a task with observable success criteria
• Create a safe synthetic practice boundary

Start with the handoff

An AI assistant is useful when it gives a person a better starting point. Fluent wording does not establish that a statement is correct or that an action is authorized. Begin by naming the handoff: a volunteer receives a draft reply, compares it with the event request, and decides what to send. The assistant does not become the venue manager. This distinction is especially important when a draft mentions prices, dates, accessibility arrangements, or availability.

Our fictional Cedar Desk receives community event requests. A narrow first task is to extract an event title, requested date, estimated attendance, and unanswered questions into a review card. The input is a made-up message: 'Please arrange a repair afternoon next month for about twenty people.' A useful output records twenty as an estimate and the date as unresolved. Choosing a specific Saturday would create a fact that the requester never supplied.

Write the operating boundary

Create a one-page charter with input, output, owner, exclusions, and checks. The owner is a role such as event coordinator, not a fictional endorsement by a real person. Exclude booking, payment, eligibility decisions, and outgoing messages. A good success criterion is 'Every missing required field is identified.' 'Make the response professional' is a style preference, not a sufficient correctness test.

Keep this workshop entirely synthetic. Replace a realistic attendee name with Requester A, omit contact details, and invent a venue called Cedar Room. Do not paste a real inbox into a tool merely because the exercise is low stakes. A free or existing AI account is optional: you can write the review card manually and still learn the workflow. No API key, subscription, or external automation is required.

Recognize the first failure mode

Moving from drafting to confirming a booking silently adds authority. Missing information requires a question, not a guess. Mark 'Confirmed for Saturday' as failed and save the corrected card beside it.

Create the Cedar Desk charter

• Write the five charter headings: input, output, reviewer, exclusions, and acceptance checks.
• Process the synthetic repair-afternoon request manually or with an approved assistant. Keep the original request beside the result.
• Add a second request with an exact date and compare which questions disappear. Save both review cards.

Expected checks

• The first card leaves the date unresolved and does not claim a reservation.
• Both cards identify the human reviewer and remain drafts.
• Your charter describes at least two actions the assistant cannot perform.

Check your understanding

Which output best respects the task boundary?

• Your booking is confirmed for the first Saturday.
• Draft: approximately twenty attendees; exact date needs confirmation.
• The requester probably prefers a weekend, so no question is needed.

Official tools & further reading

• NIST: AI Risk Management Framework overview