Define group roles and set and track goals and deadlines, answer questions with relevant evidence, and present with sound reasoning, appropriate eye contact and adequate volume

Learning goal: This lesson teaches five sub-parts of Ohio's 2026 standards, first implemented in 2027-28. From SL.8.1, on discussions in small groups or whole-class settings: define individual assigned roles, and set and track progress toward specific goals and deadlines as needed (c); and respond to others' questions and comments with relevant evidence, observations and ideas (d). From SL.8.4, on presenting claims and findings: relevant evidence and elaboration supported with sound reasoning (b); appropriate eye contact (c); and adequate speaking volume (d). The lesson follows one group from its first meeting to its presentation.

The situation. Lakeview Middle School is an invented school, and every figure below is hypothetical, invented for this lesson. The school library closes at 3:30 p.m. Four eighth graders, Jada, Kenji, Sofia and Malik, have been asked to give the student council a five-minute recommendation on whether it should ask the principal for a four-week trial of a 4:30 p.m. closing. The council meets in nine school days. In a survey the group gave to 120 students in three homerooms, 54 said they would use the library after 3:30 at least once a week, and 31 of those 54 named homework that needs a computer as their main reason. On two afternoons the group also counted students waiting outside the locked library door between 3:30 and 3:40: 11 on Tuesday and 8 on Wednesday. The librarian told them that a later closing would need one adult to stay for the extra hour.

Define individual assigned roles. A role is a job with a stated responsibility, assigned to one person so that nothing important is left to "someone." Defining a role means writing down what the person does, not only a title. The group's roles: the facilitator (Jada) runs each meeting from an agenda, makes sure every member speaks and calls for a decision when discussion stalls; the recorder (Sofia) writes down decisions, who owns each task and the date it is due, and shares the notes the same day; the timekeeper (Malik) keeps each meeting to its planned length and keeps the progress tracker; the evidence checker (Kenji) checks every number and quotation the group plans to use against the survey sheets, the count log and the librarian's notes. Roles are defined as needed. A pair working for twenty minutes may need none, because both can see everything. A group of four with a nine-day deadline and a public presentation is likely to need all four jobs covered, because otherwise the jobs fall to whoever cares most, or to no one on the day they matter; it could still combine or rotate roles as long as every job has an owner.

Set specific goals and deadlines. A goal is specific when someone could check whether it was met. "Make a good presentation" cannot be checked, and "convince the council" depends on a decision the group does not control. "Deliver a five-minute recommendation with three reasons, each supported by one piece of our evidence, and one answered objection" can be checked. A deadline attaches a date and an owner to each step, worked backward from the final date: a full rehearsal with timing on day 8; slides from Malik by day 6; an outline from Jada by day 5; the survey totals checked by Kenji by day 3. A deadline is useful only if it comes early enough to fix a problem. A first rehearsal late on the night before, when the group can no longer meet, leaves no time to change anything it reveals. The group rehearses during the school day on day 8, early enough that fixes to delivery and wording can be practiced before day 9; a problem that needed new slides would show up when the slides are checked on day 6.

Track progress toward the goals. Tracking means checking, at every meeting, where each task stands against its deadline, and then acting on what you find. Malik's tracker lists each task, its owner, its deadline and its status: done, on track or behind. At the day-5 meeting it showed the outline done, the survey totals checked but not yet sent to Malik, and the slides behind, because Malik was waiting for the final numbers. The group acted: Kenji sent the totals that afternoon, the slide deadline stayed at day 6, and the group cut a planned fourth reason that had no evidence behind it rather than move the rehearsal. A tracker that only reports ("slides are behind") without a decision is not yet tracking progress toward a goal.

Respond to others' questions and comments with relevant evidence, observations and ideas. In a group discussion, and in the questions after a presentation, others will ask and comment. A response is relevant when it answers what was actually asked. Three kinds of support can carry it. Evidence is information from a source, such as the survey figure or the librarian's statement. An observation is something you saw or measured yourself, such as the students waiting at the locked door. An idea is a reasoned proposal or interpretation, such as a four-week trial that would measure real use. A response that only repeats a position ("We just think it's a good idea") gives the questioner nothing to weigh. A response with true but unrelated evidence ("The library has six thousand books") answers a question nobody asked. When you have no evidence, say so and say what would answer the question: "We didn't measure that; a trial would."

Relevant evidence and elaboration supported with sound reasoning. In a presentation every claim needs evidence that bears on it, elaboration that explains what the evidence means for these listeners, and reasoning that connects them without stretching. Evidence is relevant when it bears on the specific claim. For "a later closing would help students finish homework," the 31 students who named homework that needs a computer are relevant evidence; the library's book count is not. Elaboration explains the evidence: 31 is about one in four of the 120 students surveyed, and these are students who say they need a computer for homework after 3:30. Reasoning is sound when the conclusion follows from the evidence and claims no more than the evidence shows. "54 of 120 students said they would use the library after 3:30 at least once a week, so the library would be full every afternoon" is unsound: at least once a week is not every afternoon, three homerooms are not the whole school, and saying you will come is not coming. "54 of 120 students in three homerooms said they would come at least once a week, which suggests enough demand to justify a four-week trial that would measure actual use" claims only what the evidence supports and names how to find out more.

Appropriate eye contact. Eye contact connects a speaker with listeners and lets the speaker see whether they are following. Appropriate eye contact in a formal presentation means looking at one listener for about the length of a sentence, then moving to another, across the whole audience, left, center and right, front and back, rather than locking onto one friendly face. Look down at notes briefly and at pauses, not while delivering a key number. Reading the slides with your back to the audience breaks contact completely; staring at one council member for a full minute makes that person uncomfortable and leaves everyone else out. Expectations about eye contact differ among cultures and individuals, and a speaker for whom sustained eye contact is difficult can use an equivalent, such as facing the audience and looking toward the space between listeners. What is appropriate is what lets every listener feel addressed.

Adequate speaking volume. Adequate volume is loud enough that the listener farthest away hears every word without straining, and not so loud that it sounds like shouting in a small room. What is adequate depends on the size of the room, background noise such as a ventilation fan, and whether there is a microphone. Check before you begin: one group member sits in the back row and signals if a word is lost. Two failures are common. Speakers drop their voices at the ends of sentences, which is often where the key word sits ("we recommend a four-week trial"), and they lose volume when they turn toward a slide. Take a full breath at each pause, finish each sentence at the same strength you started it, and turn back to the audience before you speak.

Worked example 1 — defining roles and setting a goal at the first meeting. Jada opens with a three-item agenda: roles, goal, deadlines. The group writes each role with its job, so that when something falls behind everyone knows whose job it is to notice (Malik, with the tracker) and whose to check the numbers (Kenji). Their first goal, "convince the council," cannot be checked and depends on others, so they revise it to "deliver a five-minute recommendation with three reasons, each supported by one piece of our evidence, and one answered objection." Then each step gets an owner and a date, worked backward from day 9: rehearsal on day 8, slides by day 6, outline by day 5, checked totals by day 3. Sofia records all of it and shares the notes that afternoon.

Worked example 2 — tracking and adjusting at the day-5 meeting. Malik reads the tracker: survey totals checked but not sent, outline done, slides behind, rehearsal on track. The group looks for the cause of the delay: the slides cannot be finished without the checked totals. Two choices: move the rehearsal, which would leave no time to fix problems, or remove the cause. Kenji sends the totals that day, and the group drops a fourth reason ("the library is quieter than the cafeteria") that had no evidence behind it. The goal asked for three reasons, so the cut costs nothing and saves slide time. Sofia records the decision and the reason. Tracking produced a decision, not only a report.

Worked example 3 — answering a council member's question. Question: "How do you know students would actually come?" Weak answer: "We just know people want it." Relevant answer: "We don't know for certain yet. In our survey of 120 students, 54 said they would come at least once a week (evidence). We counted 11 students waiting outside the locked door on Tuesday and 8 on Wednesday (observation). That's why we're asking for a four-week trial with a sign-in sheet, so the numbers would come from actual use (idea)." The answer addresses the question that was asked, admits what is not known, and uses all three kinds of support.

Worked example 4 — elaborating and checking the reasoning. Claim: "A later closing would help students finish homework." Evidence: 31 of the 54 students who would come named homework that needs a computer. Elaboration: 31 ÷ 120 ≈ 0.26, about one in four of the students surveyed, and these students say they need a computer for homework after 3:30. Reasoning check: the evidence shows a stated need, not a measured result, so the claim the evidence supports is that a later closing would give these students a place and a computer for that homework; whether it actually helps them finish is what the trial would measure. The group rewrites the claim to say exactly that.

Worked example 5 — a delivery check in the real room. On day 8 the group rehearses in the council room, which seats twelve in a U, with a ventilation fan at the back. Sofia sits in the back corner and raises a hand whenever she loses a word: twice, both at the ends of Malik's sentences as he turned toward the slide. Malik practices turning back to the audience before he speaks and finishing each sentence on a full breath. Jada realizes she looked only at the council president's seat; she marks three points on her notes (left arm of the U, center, right arm) and moves her eyes to a new listener at each sentence. They check the volume again with the fan running, because it will be running on day 9.

Group plan (representation task): For a group project you are starting, write (1) each role with its job in one sentence; (2) one specific goal that someone could check; (3) every step with its owner and deadline, worked backward from the due date; and (4) a tracker with the columns Task, Owner, Deadline, Status (done, on track, behind) and Decision. Fill in the tracker at two meetings and write one decision the group made because of it.

Answer bank: List three questions your audience is likely to ask. For each, write an answer that uses relevant evidence, an observation and an idea, and label which is which. Add one question you cannot yet answer and write exactly what you would say.

Independent performance: With a group of three or four, prepare and deliver a four- to five-minute presentation of a recommendation on a school or community question to an audience of at least eight, then answer at least two questions. Success criteria: roles defined in writing, with a job for each; a goal that can be checked and dated deadlines with owners; a tracker updated at every meeting, with at least one decision recorded; every claim supported by relevant evidence, elaborated for the audience and connected by reasoning that claims no more than the evidence shows; answers that address what was asked, using evidence, observations or ideas; eye contact that moves across the whole audience, with notes used only at pauses; and volume checked from the back of the room before you begin and adequate for the farthest listener throughout. An observer records each item; the written questions below check understanding and do not replace the performance.