Create a lesson outline for a lesson on Technical Writing that includes learning objectives, creative activities, and success criteria.
GPT-3.5
GPT-6 Astra
Lesson Outline: Introduction to Technical Writing
Audience: Secondary, college, or adult learners
Duration: 60 minutes
Focus: Writing clear, accurate, user-friendly instructions
Learning Objectives
By the end of the lesson, learners will be able to:
- Identify key features of technical writing: clarity, conciseness, accuracy, logical organization, and audience awareness.
- Adapt vocabulary and detail to a specific audience.
- Write a short set of instructions using numbered steps, action verbs, and appropriate formatting.
- Test and revise instructions using peer feedback.
Materials
- A clear instruction sheet and a confusing one
- Paper, pens, and sticky notes
- Simple materials for a hands-on task, such as paper for folding
- A peer-review checklist
Lesson Sequence
| Time | Stage | Activity |
|---|---|---|
| 0–8 min | Hook: “Human Robot” | In pairs, one learner gives verbal instructions for drawing a simple shape while the other follows them literally without seeing the original. Compare results and discuss how vague wording affects the outcome. |
| 8–18 min | Explore and Model | Learners compare clear and confusing instructions, highlighting helpful features and identifying problems. Introduce audience, purpose, action verbs, numbered steps, and relevant warnings. Model revising one unclear step. |
| 18–25 min | Creative Activity: “Jargon Translator” | Give pairs an unnecessarily complicated sentence, such as “Initiate the illumination apparatus.” Ask them to rewrite it for a general audience: “Turn on the light.” Discuss when specialist terms are useful and when they create barriers. |
| 25–40 min | Writing Challenge: “Instruction Designers” | Learners write a 5–8-step guide for a safe, simple task, such as folding a paper bookmark or organizing a study folder. Assign an audience, such as a first-time user or an experienced colleague. Include a title, purpose, materials or prerequisites, and steps. Add a labeled visual if useful. |
| 40–52 min | User Testing and Revision | Partners exchange guides and try to complete the task without additional explanation. Testers mark unclear or missing information. Writers revise at least two elements based on feedback. |
| 52–60 min | Share and Reflect | Volunteers share a before-and-after revision. Learners complete an exit ticket: “Who is my audience? What did I revise? How did the change help the reader?” |
Success Criteria
Learners can use this checklist to assess their final guide:
- Purpose: The title and opening make the task and intended outcome clear.
- Audience: Vocabulary and detail suit the intended reader; unfamiliar terms are explained.
- Clarity: Steps use precise language and begin with action verbs where appropriate.
- Organization: Instructions are numbered and follow a logical sequence.
- Completeness and accuracy: Necessary materials, prerequisites, and task details are included and correct.
- Usability: A peer can complete the task without extra verbal explanation.
- Revision: At least two changes address issues identified during testing.
Assessment
- During the lesson: Observe discussions, sentence rewrites, and user testing.
- Final evidence: Review the revised guide against the success criteria.
- Reflection: Use exit tickets to check understanding of audience and revision.
Support and Extension
Support: Provide a template, an action-verb word bank, and a worked example. Allow learners to rehearse instructions aloud before writing.
Extension: Ask learners to adapt the same guide for a different audience or add a brief troubleshooting section.
What changed
The prompt asked for creative activities, and that word is where the two answers part ways. GPT-3.5’s activities are standard classroom moves: “conduct a class discussion,” “analyze a technical document,” “peer review each other’s writing.” They’re sensible, but not creative. Astra builds the lesson around games that teach by failure. In “Human Robot,” a partner follows drawing instructions literally. In “Jargon Translator,” “Initiate the illumination apparatus” becomes “Turn on the light.” Then peers try to complete each other’s guides cold.
The success criteria show a similar gap. GPT-3.5’s mostly restate its objectives (“Write clear and concise technical documents”), so a teacher can’t easily check them. Astra’s are a checklist a student could actually apply, ending with the blunt test that “a peer can complete the task without extra verbal explanation.” To be fair, GPT-3.5 covers more ground, including types of technical writing and a summative project. Astra narrows the topic to instructions. That is a choice, but it is what makes a single 60-minute lesson workable.