Project-based units fail in the third week. The launch is exciting, the final presentations are fine, and the middle is a fog of group work where nobody can say what was learned. Text analysis is a good candidate for a project because the skill is genuinely transferable, but it needs a spine: a question worth three weeks, milestones that are checked, and a final product that cannot be made without doing the analysis. This is a four-week arc for a California middle school English class.
Choosing a driving question that forces analysis
The question has to be arguable, answerable only with text evidence, and interesting to a thirteen-year-old. "How do the texts we consume shape what we believe is normal?" works because every student has an opinion and none of them can defend it without close reading. Avoid questions that can be answered by research alone, and avoid questions with an obvious right answer, since both produce projects where the analysis is decorative. Write the question on the board on day one and leave it there for the whole unit; every milestone should visibly serve it.
Week by week
- Week one: build the toolkit. Whole-class teaching of the analytical moves, using short texts everyone reads together. Students end the week with a one-page reference sheet of analysis verbs and question stems in their own words. No group work yet. This is the week that determines whether the project has any rigor in it.
- Week two: apply to a chosen text. Groups pick from a shortlist you control. Milestone: an annotated extract plus three claims with evidence, submitted at the end of the week and checked by you, not by peers. Groups that cannot produce three defensible claims get a new text on Monday rather than being allowed to drift.
- Week three: build the argument. Groups draft their answer to the driving question, individually written, collectively evidenced. Milestone: a two-minute stand-up where each group states its claim and takes one challenge from another group. Ten minutes total for a class of thirty-two if you keep it tight.
- Week four: produce and present. The final product is made in class, not at home. Presentations occupy the last two periods, with the audience holding a listening task so they are not merely waiting for their turn.
The precision of the week one toolkit is what makes weeks two and three possible. Students need shared words for what a text is doing, and Analysis Vocabulary and Operators for Text Analysis supplies exactly that inventory, which means a group discussion in week two is about the text rather than about what the task words mean.
Group roles that produce individual evidence
Assign four roles and rotate them weekly: evidence keeper, who maintains the quotation log; skeptic, whose job is to challenge every claim once; scribe, who keeps the shared document usable; and timekeeper, who owns the milestone deadline. The roles matter less than the rule attached to them, which is that every student submits their own written analysis regardless of the group product. Grade the individual writing; comment on the group product. This is the single change that stops strong students carrying passengers, and it gives you defensible evidence for each learner rather than a shared score. When groups need a bank of characters and techniques to reason about, Characterisation and Analysing Fiction gives the evidence keeper somewhere to start rather than a blank log.
What the final product should be
Choose a product that requires the analysis to exist. A podcast episode arguing the group's answer, with three cited extracts, works. A poster does not, because a poster can be made from a summary. Keep the technical demands low so the assessment is of the thinking, and set the length short enough that editing forces choices about which evidence is strongest. Multimodal texts make good project material precisely because students must argue about something other than plot, and a unit like How Music Shapes Perception | Media Literacy, Psychology & Music Analysis gives you texts that reward close attention and connect naturally to the driving question. Build in a rehearsal slot before the presentations, and give the ELD support at that point rather than at the end, so multilingual learners are rehearsing academic language with feedback rather than performing cold. A unit like this has worked when a student, three months later, annotates an unfamiliar text in a CAASPP practice task using the same verbs they wrote on their week one reference sheet.


Comments
No comments yet — be the first to share your thoughts!
Leave a comment
Comments are reviewed before being published.
Thanks for your comment!
Your comment is being reviewed and will appear here shortly.