foundation · beginner · No coding required

Your first useful AI workflow at work

Start with a small workplace task and turn supplied notes into a useful draft. Practice giving clear instructions, checking every claim, and saving a reusable method before adapting it to your own work.

Published:

By Marco Cerrato

Before you start

No coding required

A reviewed project update and a repeatable task brief.

  • Text-capable AI chat — access: varies

Begin with a task you understand well enough to review. A project update is a useful starting point: you know the inputs, can recognize missing facts, and can decide whether the draft communicates what matters.

You will turn a few fictional notes into an update for a manager. AI contributes organization and wording. You decide what is accurate and appropriate to share.

What you need

Use an AI chat tool that accepts pasted text and somewhere to save your prompt and draft. No coding, upload, or special paid feature is needed by the exercise. Service access varies. You do not need real workplace data. Hands-on time has not yet been measured.

1. Define one small result

Use these original synthetic notes, dated 6 October 2026:

Note Fact
P1 Pilot involved five branches; three completed the checklist.
P2 Two branches are waiting for access approval. No completion date is confirmed.
P3 Dana will ask the access team for an update on 7 October.
P4 The manager needs a short status update, next action, and outstanding question.

The result is an internal update, not a declaration that the pilot succeeded. Before starting, write your acceptance rule: “The draft must retain the counts, uncertainty, and action without inventing a deadline.”

2. Give AI the task and evidence

Paste this complete prompt:

Draft an internal update for a branch pilot manager, as of 6 October 2026.
Use only these fictional notes:
P1: Five branches participated; three completed the checklist.
P2: Two branches await access approval. No completion date is confirmed.
P3: Dana will ask the access team for an update on 7 October.
P4: The manager needs status, next action, and an outstanding question.
Return three labelled sections: Status, Next action, Open question.
Keep the total under 80 words. Do not infer success, delay causes beyond
the notes, or a completion deadline. Do not send the update anywhere.

Giving the evidence and output structure makes review easier. The instruction to stay within the notes does not guarantee that the response will comply.

3. Check the draft against the notes

This is an illustrative editorial result, not a captured response from a named AI service:

Status: Three of five branches have completed the pilot checklist. Two await access approval; their completion dates are not confirmed.
Next action: Dana will request an access-team update on 7 October.
Open question: When can the remaining branches receive access and complete their checklists?

Match each sentence to P1–P4. Three plus two equals five. A request for an update is different from a promise that access will be approved. Remove any added claim that the pilot is on schedule, successful, or finished.

If the answer invents a deadline, correct it directly:

The completion deadline is unknown. Remove the invented date and any claim
that the pilot is on schedule. Preserve Dana's confirmed next action.
Return the revised three-section update.

4. Save the method

Keep the task, inputs, prompt, draft, and changes you made. The business-task worksheet provides these fields; the same fields can be copied into a document. Saving only the final response loses the context that made it usable.

Before adapting the exercise, choose a task with available evidence and a manageable review. Use tools and data handling approved by your organization. A draft you cannot check is a poor first exercise.

Common mistakes and next exercise

An instruction such as “make this impressive” can encourage unsupported emphasis. Ask for clear wording and retain uncertainty instead. If the output omits a note, request a revision naming the missing item.

Change P1 to four completed branches and P2 to one awaiting approval. Confirm the update changes both counts and still totals five. Then continue with How to give AI the context it needs, where you will turn this prompt into a reusable brief.

Source: original fictional notes P1–P4. No external business claims or productivity estimates are used.

Practice resource

Business task and prompt worksheet

Define one useful business task, organize the evidence, and build a reusable prompt. The editable worksheet includes a claim-review table, run log, and worked fictional example so you can preserve the reasoning behind your final draft.

Version 1.0

The download is being reviewed. Use the examples in this guide to practice now.

Read the resource instructions