Copilot Hands-on Exercises
Use these live scenarios to practice good prompts and quick QA checks.
Hands-on practice is essential for developing proficiency with AI-assisted tools like Copilot. Research on skill acquisition shows that active practice with real-world scenarios leads to better learning outcomes than passive observation or theoretical instruction alone (Ericsson & Pool, 2016). These exercises provide structured opportunities to practice prompt engineering, output verification, and iterative refinement in a safe environment before applying these skills to critical work tasks.
For municipal government staff, these exercises serve multiple learning objectives. First, they help build confidence by providing concrete, relevant scenarios that mirror actual work tasks. Studies on technology training show that relevance and immediacy of application significantly improve learning retention and transfer (Kirkpatrick & Kirkpatrick, 2006). Second, they help develop systematic approaches to prompt engineering and quality assurance that can be applied across different types of tasks. Third, they provide opportunities to experience and learn from common pitfalls, such as vague prompts or insufficient source grounding.
Each exercise includes a scenario description, a sample prompt, and guidance on what to verify. This structure supports deliberate practice—a learning approach that emphasizes focused, goal-oriented practice with feedback (Ericsson & Pool, 2016). As you work through these exercises, pay attention to how different prompt structures affect outputs, and practice the verification habits that will serve you well in real work situations.
References: Ericsson, A., & Pool, R. (2016). Peak: Secrets from the New Science of Expertise. Houghton Mifflin Harcourt. Kirkpatrick, D. L., & Kirkpatrick, J. D. (2006). Evaluating Training Programs: The Four Levels. Berrett-Koehler Publishers.
Word / Teams – Council report summary
- QA: verify budget numbers and dates against the source doc.
- Iterate: ask for a 150-word version for email.
Outlook – Resident notice
- QA: check date/time and contact details.
- Follow-up: “Shorten to 120 words and add a CTA button text.”
Excel – Budget variance spotlight
- QA: confirm calculations; ask Copilot to “show the formulas you used.”
- Iterate: “Add a sparkline trend for each highlighted line.”
Teams – Meeting recap with owners
- QA: ensure owners/dates match what was agreed; adjust tone before sharing.
- Iterate: “Group by theme and add a next-step CTA.”
PowerPoint – Five-slide briefing
- QA: check option accuracy; ask for “speaker notes under 40 words each.”
- Iterate: “Rewrite bullets to the 6x6 rule and suggest icons.”
Mail merge – Conditional text
- QA: spot-check merge fields; ensure no PII beyond policy.
- Iterate: “Add a personalized benefit by department in one sentence.”
Quality check steps (apply to every exercise)
- Verify facts: dates, amounts, names, sources.
- Check completeness: did all required points land?
- Fit to audience: resident vs. council vs. colleague tone.
- Security: no sensitive data in prompts/outputs beyond policy.
Full checklist: Mindset → QA checklist.
- Mindset & Fundamentals - Learn the prompting formula
- Workflow Ideas - More copy-ready prompts
- Examples - See prompts in action
- Trust & Safety - Verification and QA guidance
- FAQ - Common questions and troubleshooting
- Glossary - Key terms and definitions