The first year, you revised an assignment. The next year, you changed the feedback process. Then you adjusted the sequence again after seeing where students still struggled. Each annual report made sense on its own. Put together, they read like three separate beginnings.
A multi-year teaching narrative needs to explain the connection. The book's mid-tenure example brings together teaching goals, feedback, course changes, and professional learning. You can use those pieces to show development rather than simply repeating what you wrote each year.
Choose the thread that runs through the work.
What learning problem or teaching priority kept returning? Perhaps you wanted students to apply theory in practical situations, use feedback more effectively, or take greater responsibility for explaining their reasoning. That thread can give the narrative a direction readers can follow.
You don't need to pretend every change was part of a perfect original plan. Some decisions came from surprises, constraints, or feedback you hadn't expected. Explain how your understanding developed. A thoughtful revision is worth describing even when it began with something that didn't work as intended.
Show the sequence, not just the inventory.
In a fictional example, a faculty member first notices weak reasoning in a project. The next offering adds a draft and feedback stage. Later, the instructor revises the prompt because students still misunderstand the evidence requirement. That sequence shows a process of inquiry into teaching.
A list saying “added drafts, updated rubric, revised prompt” doesn't reveal the same reasoning. Tell the reader why one step led to another and which evidence informed the decision.
Stay within the actual review period. The book's examples are illustrations, and any dates or descriptions you use in your own file need to match your records rather than the sample's wording.
Distinguish effort, change, and demonstrated result.
Redesigning an assignment takes work. Implementing it changes the course. Evidence of students' performance may help you assess what happened afterward. Those are connected but distinct parts of the account.
Don't label every change an innovation or assume a new activity improved learning because students enjoyed it. Explain the purpose, show the appropriate evidence, and state the limits. If the comparison isn't strong enough to support a causal claim, describe what you observed without declaring that the change caused it.
Professional development belongs in the story when it informs a decision. Instead of repeating a workshop list, describe the idea you applied and how you adapted it to your course.
Use selected examples to carry the argument.
One well-explained sequence can tell readers more than a compressed paragraph naming every course adjustment. Follow the institution's requirements for the complete record, then choose examples that clarify the broader pattern in your narrative.
Different courses may need different approaches. You can explain a common teaching priority while acknowledging how the tasks and evidence vary by level, format, or learning goal.
For a first draft, put your annual teaching summaries side by side. Highlight repeated concerns and follow one through the period. Write down what you tried, what you learned, and what you'll examine next. That's the backbone of a teaching story that shows development instead of asking reviewers to assemble it for you.
Adapted from The New Faculty Handbook by Zafer Unal, chapter 16, pp. 271–272.
