Designed by Yingzi (Kathryn) Kong for UCF’s Preparing Tomorrow’s Faculty program, Spring 2026. This sample plan describes an intended undergraduate teaching setting; it is presented as evidence of instructional design, without claiming classroom implementation or measured learning outcomes.
Learning Objective
By the end of the lesson, students will be able to:
- Define technical communication in their own words, identifying its audience, purpose, and practical use.
- Analyze a technical document by explaining how at least three features support or limit its purpose for the intended audience.
- Evaluate audience needs in a communication scenario and justify a document format and tone using at least two needs supported by the scenario.
Prerequisite Knowledge
Before this lesson, students should be able to:
Framework Application
Keller's ARCS Model of Motivational Design
ARCS is selected because this is an introductory lesson where students may not yet see the relevance of technical communication to their lives. The model's explicit focus on motivation — capturing Attention, establishing Relevance, building Confidence, and creating Satisfaction — is designed to help students move from "why does this matter?" to "I can do this, and it matters to me." By opening with relatable real-world examples and scaffolding complexity gradually, the lesson aims to build confidence and engagement before more demanding analysis tasks. Attention, Relevance, Confidence, and Satisfaction are overlapping design considerations used throughout the lesson; the table identifies an emphasis, not a required sequence or a guarantee of motivation.
Lesson Sequence
| Time | ARCS Emphasis | Topic / Activity | Materials |
|---|---|---|---|
| 0–15 min | Attention | Hook — When Communication Goes Wrong Compare two instructor-prepared versions of instructions for submitting a class assignment: one vague paragraph and one numbered guide with clear labels and a confirmation step. Ask: "Which version would help a first-time user complete the task, and what evidence supports your choice?" |
Slides, two instruction examples |
| 15–25 min | Attention | Inform learners of objectives Share today's three learning targets. Connect each to a real career moment (engineer writing a report, nurse filling out a form, developer writing documentation). |
Slides |
| 25–45 min | Relevance | Mini-Lecture — What is Technical Communication? Cover the definition, key characteristics (clarity, audience focus, accuracy, usability), and the spectrum of document types. Use examples from multiple fields: medical, legal, engineering, tech. |
Slides, handout |
| 45–70 min | Relevance | Activity 1 — Document Deep Dive (Small Groups) Groups of 4–5 receive a packet of 4 different technical documents. They analyze each using a guided worksheet: identify the document type, intended audience, key characteristics, and purpose. Groups share one finding with the class. |
Document packets, guided worksheet |
| 70–80 min | Relevance | Break 10-minute break. No task is required during the break. |
— |
| 80–110 min | Confidence | Mini-Lecture — Audience Analysis Introduce the concept of audience: primary vs. secondary readers, expert vs. lay audiences, cultural considerations. Walk through a structured audience analysis framework step by step. Model the process using a sample scenario. |
Slides, sample scenario handout |
| 110–145 min | Confidence | Activity 2 — Audience Evaluation Scenarios (Pairs) Pairs receive a communication scenario card and must: (1) identify the audience, (2) list audience needs and expectations, (3) recommend an appropriate document type and tone. Instructor circulates to provide real-time feedback. Pairs justify their recommendations using two scenario details, then swap cards for a second round. With 25 students, use 11 pairs and one group of three. |
Scenario cards (10 scenarios), worksheet |
| 145–160 min | Confidence | Check for Understanding — Gallery Walk Post 5 "mystery documents" around the room. Students use sticky notes or an accessible digital worksheet to identify document type, intended audience, and one feature with an explanation of its usefulness. A seated document packet provides the same task. Class discusses patterns and discrepancies. |
Printed mystery docs, sticky notes, markers |
| 160–170 min | Satisfaction | Debrief & Real-World Transfer Instructor leads discussion: "Where will you use this? What does a technical communicator in your field actually do?" Students share one example from their own major or career interest. Build a class "living example list" on the whiteboard. |
Whiteboard, markers |
| 170–180 min | Satisfaction | Exit Task + Preview of Next Lesson Students complete a three-part exit task: define technical communication; explain one feature of a supplied document; and justify a format and tone for a brief audience scenario using two stated needs. Preview Week 7: Writing Audience-Centered Documents. |
Exit ticket card (print or digital) |
Student Activities
Document Deep Dive
Small groups of 4–5 analyze a curated packet of four technical documents (e.g., a safety data sheet, a patient discharge summary, an API readme, and a product recall notice). Using a guided worksheet, they identify document type, audience, purpose, and at least three key characteristics per document. Each group presents one document to the class.
Supports: Analyze characteristics of common technical documents
Audience Evaluation Scenarios
Working in pairs, students receive a scenario card describing a real-world communication situation (e.g., a software update guide for users with varied digital experience and accessibility needs; a lab safety protocol for new interns). They must identify the audience, evaluate their needs, and recommend an appropriate document type and tone. A second card is then swapped to practice with a new context.
Supports: Evaluate audience needs for different communication scenarios
Gallery Walk — Mystery Documents
Five unlabeled technical documents are posted around the room. Students rotate individually or use a seated packet or accessible digital version. For each document, they identify its type, intended audience, and one feature, explaining how that feature helps or hinders the audience. Prompts discussion about disagreements and edge cases, reinforcing that categorization involves judgment, not just recall.
Supports: Define and analyze technical documents
Living Example List (Class-Wide)
In the closing debrief, students contribute a real example of technical communication from their own field or personal experience. The instructor captures these on the whiteboard, building a shared class document of diverse, student-generated examples. This validates student knowledge and promotes cross-disciplinary connection.
Supports: Relevance, satisfaction, and retention
Assessment / Check for Understanding
Formative Assessment 1 — Gallery Walk Annotations
Students' sticky note responses provide the instructor with real-time insight into whether students can correctly identify document types and audiences. Discrepancies between student labels reveal common misconceptions and guide whole-class correction during the debrief.
Formative Assessment 2 — Objective-Aligned Exit Task
At the close of class, students respond to three prompts: (1) define technical communication in their own words; (2) explain how one feature of a supplied document supports or limits its purpose; and (3) recommend a format and tone for a short scenario, justified by two audience needs. These responses provide individual evidence for the three objectives. The document worksheet supplies the fuller three-feature analysis. Accept paper or accessible LMS submissions. Students may add an unanswered question for follow-up.
Feedback criteria: Look for an accurate definition connecting audience, purpose, and use; a feature explanation grounded in the document; and a recommendation justified by scenario evidence. Mark each criterion as demonstrated, developing, or needs follow-up. Use patterns of difficulty to plan the next lesson.
Informal Assessment — Pair Work Observation
During Activity 2 (Audience Evaluation Scenarios), the instructor circulates and listens to pair discussions, providing immediate corrective feedback. This allows early intervention before misconceptions solidify, and helps identify students who need additional support. Ask pairs to explain the evidence behind their decisions rather than infer needs from age or other demographic labels alone.
Accessible Participation
Provide document packets and worksheets in advance as accessible digital text, with readable headings, sufficient contrast, and descriptions for meaningful images. Offer a seated packet or digital worksheet for the gallery walk, with the same prompts and feedback criteria.
Allow individual thinking time before pair discussion, written contributions as an alternative to speaking, and clear roles within groups. Explain unfamiliar professional terminology and invite students to identify missing audience information rather than make assumptions. If video is added, provide captions and a transcript.
Materials & Resources
- Slide deck — Lesson slides covering definitions, examples, audience analysis framework, and discussion prompts. Includes document examples with selectable text, useful image descriptions, and source credits. The opening uses two instructor-prepared instruction examples.
- Document Deep Dive packets (5 group packets, each containing 4 documents, plus accessible individual copies) — Public instructional examples or fictional samples with no personal information: safety data sheet, patient discharge instructions, open-source README, and a product recall notice.
- Guided analysis worksheet — Two-sided handout with structured prompts for Activity 1 and Activity 2, including an audience analysis framework grid.
- Audience Evaluation Scenario cards — Set of 10 laminated cards with realistic communication scenarios spanning healthcare, technology, engineering, and public services.
- Mystery document posters — 5 enlarged/printed technical documents posted around the room for the Gallery Walk. Include sticky notes and markers at each station.
- Exit ticket cards — Three-part, objective-aligned response sheets (or accessible LMS form). One per student.
- Recommended reading — Markel & Selber, Technical Communication, 13th ed., Ch. 1–2; Johnson-Sheehan, Technical Communication Today, Ch. 1 (audience analysis).
- Technology — Projector/display for slides, optional LMS for digital exit ticket submission (Canvas, Blackboard, or Google Forms).