Chapter 8 of 8

Run the ten-minute proof

Use the same fictional source twice. First give Copilot a thin request. Then give it a short working profile, a proper brief and a check.

10 min exerciseOutcome: a scored comparisonFacts checked 19 July 2026

01Use the safe test material

This exercise is fictional. You can run it without adding company information or looking for an approved document.

PROJECT JUNIPER WEEKLY NOTES
Date: 18 July 2026

- Overall status is amber.
- The supplier test file arrived on 16 July, two days later than planned.
- Data validation is complete.
- Four test cases remain. The operations lead owns completion by 22 July.
- The steering group must decide by 21 July whether to move the pilot from 12 August to 19 August.
- The budget is unchanged. No extra spend has been approved.
- The training date isn't confirmed.
- Main risk: a late pilot decision will compress training and support preparation.
- Next project meeting is 23 July.

02Run the thin request

Open a new Copilot chat. Paste the notes, then ask:

Write a project update from these notes.

Save the answer somewhere temporary. Don't correct it yet.

03Run the same job with a setup

Open another new chat. Copy the complete prompt below. It includes a six-line profile, the task brief, the check and the same notes.

WORKING PROFILE
- I write for time-poor senior managers.
- Start with status and the decision needed.
- Use short headings and plain Australian English.
- Keep routine updates under 160 words.
- Separate confirmed facts from open questions.
- Never invent progress, approval, dates, numbers or owners.

TASK
Draft a weekly project update for the steering group using only the notes below.

Order:
1. status and reason
2. decision needed
3. progress
4. risk
5. next actions with owners and dates where supplied

CHECK
Before you finish, check every date, number, owner and claim against the notes. Mark missing information as an open question. After the draft, list any unsupported claim you removed.

PROJECT JUNIPER WEEKLY NOTES
Date: 18 July 2026

- Overall status is amber.
- The supplier test file arrived on 16 July, two days later than planned.
- Data validation is complete.
- Four test cases remain. The operations lead owns completion by 22 July.
- The steering group must decide by 21 July whether to move the pilot from 12 August to 19 August.
- The budget is unchanged. No extra spend has been approved.
- The training date isn't confirmed.
- Main risk: a late pilot decision will compress training and support preparation.
- Next project meeting is 23 July.

Save this answer beside the first one. You're checking whether the setup improved the work, not whether the prose became fancier.

04Score both answers against the source

Use the five checks below on each answer. Tick a box only after you compare the claim with the fictional notes.

Five-point output check

Status: says amber and explains the late supplier file. Decision: puts the 12 August or 19 August pilot decision near the top and gives the 21 July deadline. Accuracy: doesn't invent approval, spend, owners, dates or completed work. Gap: treats the training date as unconfirmed. Usefulness: stays under 160 words and makes the next action obvious.

Read the result honestly

Second run wins clearly: save the profile and prompt pattern.
Both are similar: tighten one instruction that would change the decision, order or check.
Second run is worse: remove instructions until the job is clear again.
Both contain wrong facts: strengthen the source boundary and keep manual fact-checking.

Compare this output with the source and the five-point scorecard. What single instruction would have prevented the most important miss? Give me the instruction only, then explain which part of the output it changes.

05Move up one stage at a time

ProvisionedYou can open the approved tool and know your access boundary.

AssistedYou use it for individual tasks and check the output.

RepeatableYou have a profile, saved patterns and a measured workflow.

EmbeddedThe workflow has approved sources, owners and a review step.

Enabling othersYou can teach the method, explain its limits and improve the process with the team.

Pick one real, approved job next. Run it five times. Keep the human check visible and improve the smallest part that repeatedly fails.

Guide complete

Make the approved tool useful

You now have an access map, a working profile, a prompting loop, a safe context-transfer method and a way to prove whether a workflow improved.

If your team needs help turning scattered Copilot use into clear, reviewable workflows, I do hands-on adoption and implementation work.

Talk to Joel Back to the guide home