You’ll practice: Write a clear request for a team update and action list, including the audience, sources, open questions, and draft-only boundary.
The idea
I start with the job, not a clever prompt. Who needs the result, and what should they do with it? Colleagues need the workshop arrangements and next actions. Noor needs a draft that makes undecided details visible.
'Make this sound good' leaves important choices open. 'Draft an internal update and an owner/action/deadline list using D1–D3' gives you something specific to review.
You do not need a long formula. Microsoft starts with a clear goal; Google suggests relevant context and format. These are starting points, not accuracy guarantees. [S1, S2]
Keep writing separate from action. A draft does not book a room, approve refreshments, or send an invitation. Noor has asked to review it first.
Worked example
From a vague request to a checkable assignment
First attempt
Make a friendly workshop announcement. Fill in anything missing so it sounds ready.
A more useful version
Draft a short internal workshop update and a separate action list for Noor to review. Use only D1–D3. Follow Noor's current arrangements, preserve details that are still pending, and use an owner/action/deadline format. Do not invent dates or approvals, send messages, or make bookings.
The revised request defines the reader, result, evidence, and boundary. It makes accuracy more important than sounding finished.
Your turn
Try it yourself
Read D1–D3. Write your own assignment in 60–90 words. Make it useful to a colleague or an assistant without copying the example word for word.
Read the fictional source documents
You are helping prepare an internal team update and action list for Noor, the workshop organizer. Everyone and everything in this packet is fictional. The exercise reference date is 19 September 2026. Use D1–D3 as sources. D4 is a deliberately flawed draft to review, not evidence of what happened.
Early planning meeting notes
The team wants a hybrid workshop on Thursday 8 October 2026 to agree three ways to make team projects easier to coordinate.
The initial suggestion is 10:00–11:00 Pacific time in the Cedar room. These are proposed arrangements, not a final booking.
Plan for 12 people onsite and 8 joining remotely: 20 people in total. These are planning numbers, not a confirmed attendance record.
Noor is organizing the workshop. Eli will prepare the agenda. Sam will collect accessibility requests. No deadline has been agreed for Eli's agenda or Sam's collection of requests.
Refreshments have been requested. No spending decision or quote is recorded.
Organizer's confirmed update
I have confirmed the workshop for Thursday 8 October 2026, 14:00–15:00 Pacific time, in the Maple room for onsite participants. This replaces the earlier suggested time and room.
We are still planning for 12 people onsite and 8 remotely. The workshop purpose and the assignments to Eli and Sam are unchanged.
The remote joining link is not available yet. I will add it by Tuesday 6 October 2026 at 16:00 Pacific time.
The agenda deadline has not been agreed. Refreshments are still awaiting the budget owner's written approval; I will ask for that decision. No deadline for that decision has been set.
Please prepare the team update and action list as a draft for me to review. I have not approved the final message for distribution. Do not send it yet.
Short team communications policy
For workshop logistics, the organizer's latest written confirmation replaces earlier proposed times and rooms. A later draft or an unattributed suggestion does not replace that confirmation.
Spending on refreshments requires the budget owner's written approval. A request, a pending decision, or a request to make an announcement is not that approval.
The organizer must review and approve the final team update before it is sent.
A hybrid-workshop update must include remote joining information or clearly state that the link is pending and identify who will provide it.
If a deadline has not been agreed, write 'not yet agreed' and ask the responsible person to confirm it. Do not choose a date and present it as a commitment.
A convincing draft that needs review
Subject: Team workshop: everything is ready
Our team workshop is confirmed for Thursday 8 October, 10:00–11:00 Pacific, in the Cedar room. All 20 people will attend onsite.
Refreshments have been approved. Eli will finish the agenda by Friday 25 September.
This update has been approved and sent, so there is nothing else to follow up.
Make: A short task brief that would produce a readable update and an action list.
- Name the audience and the two outputs.
- Identify D1–D3 as the sources and D2 as the current logistics update.
- Keep missing dates, the joining link, and refreshments approval visible.
- Request a draft for Noor's review; do not authorize sending.
Give me a hint
Imagine a new colleague receives only your task brief and the packet. Which choices would they still have to guess?
Compare with an example answer
Prepare a concise internal update about the hybrid workshop, followed by an action list with owner, action, and deadline. It is a draft for Noor, not a message to send.
Use D1–D3, with Noor's 17 September confirmation for current logistics. Show pending information, including the remote link, refreshments approval, and unagreed deadlines. Preserve the onsite/remote distinction and list follow-up work. Use friendly, plain language without making the plan sound complete.
Pause and reflect. Which phrase in your assignment makes the biggest difference to what the writer should produce? Explain its purpose.
Check your reasoning
A new situation
Use the habit somewhere else
A colleague adds, 'Can you also prepare calendar-invitation wording?' Nothing else in D1–D3 changes. What can you add to the assignment?
Show answer guidance
Add draft invitation wording using D2's current arrangements and a clear pending-link note. Preparing wording is still drafting. Do not create or send an invitation: Noor's final-message approval is absent, and the packet supplies no recipient list.
Research and source notes
Reviewed Sep 19, 2026. These sources inform the exercises; they do not establish results for this course.
S1 · Get started writing prompts in Microsoft Copilot
What it supports: Start with a clear goal, add useful context, expectations and sources, iterate, and verify responses against trusted material.
In this course: Lessons 1–3 use a bounded assignment, a labeled source packet, and claim-by-claim review.
Limits: Product guidance, not measured proof of productivity or this teaching method. The course needs no Copilot account; access to organizational work data in Copilot depends on the product entitlement.
Revisit when: Recheck when the guidance, intended tool, or organization's permitted data use changes.
S2 · Learn about prompts for Gemini in Docs, Sheets, Slides, Vids & Forms
What it supports: Use natural language, a specific task, relevant context and an appropriate format; review and refine. Not every suggested prompt component is mandatory.
In this course: Lessons 1–2 use ordinary wording and a compact context note rather than a required prompt formula.
Limits: Vendor recommendations for Google features, not evidence that one format works best everywhere. Product eligibility is separate; no Gemini account is required for the exercises.
Revisit when: Recheck if Google revises the guidance or if a lesson starts depending on a specific product feature.
S3 · How AI assistance impacts the formation of coding skills
What it supports: In a randomized study of 52 mostly junior Python developers learning Trio, the AI group averaged 50% on an immediate quiz versus 67% without AI; the completion-time difference was not statistically significant.
In this course: Ask learners to make an attempt, explain a correction, and distinguish task output from understanding.
Limits: Small coding study with an immediate assessment. Interaction patterns were qualitative associations, not randomized teaching methods. It does not establish lasting skill loss, results for everyday writing, or effectiveness of this course.
Revisit when: Revisit after relevant replications, longer follow-up, or evidence from comparable employee writing tasks.
S4 · Generative AI without guardrails can harm learning: Evidence from high school mathematics
What it supports: Assisted practice improved in both AI conditions. Ordinary answer-oriented assistance harmed later unassisted exam performance; the teacher-informed tutor largely avoided that harm without showing an unassisted advantage over the control.
In this course: Offer a first attempt, an optional hint, an answer explanation, and a changed-case question; keep assisted and independent observations distinct.
Limits: One high school in Turkey, mathematics, a Fall 2023 deployment, and short-term outcomes. This was not employee training or a test of static feedback. It does not demonstrate this course's learning effect.
Revisit when: Revisit when studies test comparable workplace tasks, longer-term outcomes, or different assistance designs.