Turn messy notes into an update someone can use

1. Give it something real to work with

Copy these notes into a new conversation. Ask: “Write a project update from these notes.” Save the first answer so you can compare it later.

Practice notes (fictional):
Monday: Interviewed 4 customers. 3 could not find the export button.
Tuesday: Moved the export button in a prototype. No customer has tried it yet.
Wednesday: Sam offered to arrange a follow-up test. No date agreed.
Open question: Does the new position help people find export?

2. Check what the answer quietly added

Read the answer against the notes. A confident sentence can still go beyond what happened.

• “Customers found the new button easier.” Nobody has tested it. This is an invented result.
• “Sam will run the test on Friday.” Sam offered to arrange it; no date was agreed.
• “We made significant progress improving the experience.” This hides the useful detail: the button moved, but the change is untested.

If your first answer avoids these errors, keep it. The point is to check it, not to force a failure.

3. Ask for the update your teammate actually needs

Start a fresh conversation with the same assistant and use this complete brief:

Write a project update for a teammate who missed this week.
Use only the practice notes below.
Include: what we learned, what changed, and what still needs checking.
Keep it under 120 words. Use concrete language.
Do not invent a deadline, test result, or customer quote.
If a detail is missing, say so.
Finish with one proposed next action, clearly labelled as a proposal.

Practice notes (fictional):
Monday: Interviewed 4 customers. 3 could not find the export button.
Tuesday: Moved the export button in a prototype. No customer has tried it yet.
Wednesday: Sam offered to arrange a follow-up test. No date agreed.
Open question: Does the new position help people find export?

The difference is the audience, the source boundary, the format, and the treatment of missing information. You can reuse those four decisions for your own work.

4. Compare it with a checked example

This is an authored example, not a recorded model response:

We interviewed four customers; three could not find the export button. We moved it in a prototype, but no customer has tested the new position yet. Sam offered to arrange a follow-up test; the date is still open.

Proposed next action: Ask Sam to arrange a test of whether customers can find export in the revised prototype.

Your wording can differ. The result passes when it:

• Preserves the four interviews and three reports.
• Separates the prototype change from an unproven improvement.
• Keeps the test date unknown and labels the next action as a proposal.
• Stays under 120 words and gives your teammate a clear next step.

If it fails, point to the exact sentence and explain the correction. “Make this better” gives the assistant another guess.

5. Keep the part worth repeating

Save the brief and your final update together. Write one sentence about what you corrected. Then try the same approach on notes you are allowed to share with your assistant.

You are done when the update is accurate enough to use and you can explain why. A longer answer or a more expensive model is not a completion criterion.

Or choose a different learning path