Sample class activity · Ungraded, collective practice

This is an ungraded class activity by design. It can be glanced at for participation, but it works best with no stakes attached.

About This Open Educational Resource

This activity was originally developed for SOC 250: Racial and Ethnic Communities in the United States at Lehman College, CUNY, and ran weekly across the Spring 2026 semester. At the end of each instructional week, students jot down three to five keywords capturing that week's learning through a short intake form — a digital index card. The instructor aggregates the submissions into a word cloud, and the following class opens with a few minutes of collective review.

Adoption notes for instructors:

• The activity is discipline-agnostic: it works for any course organized around weekly thematic units.
• Five minutes of class time per week is enough for the review.
• The original form collected no names, so submissions were effectively anonymous; named submission also works if you want to track participation. Choose deliberately and tell students which it is.
• No special tools are required — any survey form and any word cloud generator will do. The Build Your Own recipe below walks through the setup.

For self-directed learners: keep your own running keyword list, three to five terms per unit. At the end of each module, review the accumulated list and write a few sentences on how the terms connect. The list doubles as a self-test: can you define each term and say which reading it came from?

Course Context

The exercise ran alongside the weekly discussion posts, sharing the same end-of-week rhythm. Over a semester it produced a week-by-week record of the course's shared vocabulary — from foundational terms in the opening weeks to the concentrated convergence of the closing ones, where terms like reparations and racial capitalism dominated the clouds.

Purpose

The exercise seems simple, but it does several kinds of pedagogical work at once.

• Grounding within and across units. Naming three to five terms at week's end is a small act of synthesis that keeps students anchored in the weekly unit while building connective tissue across units and the overarching arc of the course's core themes.
• Retrieval and consolidation. Recalling and choosing terms — rather than rereading them — is the kind of low-effort retrieval practice that helps material stick.
• A collective mirror. The aggregated cloud shows students their classmates' thinking. Convergences validate ("everyone caught that"); outliers spark conversation ("who submitted seventh son, and why?").
• Scaffolding toward projects. The accumulated vocabulary becomes raw material for project building. By the time students choose concepts for a final project, they are already holding a personal map of the course's key terms.
• Continuity between sessions. Opening each class with the previous week's cloud means every session begins by collectively remembering the last one.

How It Ran

1. Submit. At the end of each instructional week, students submitted through a short form. The link was short and stable all semester, shared in the syllabus and on the course site. The original form read:

   Keywords Exercise

   Think of this form as a digital index card where you can jot down keywords that you believe are important or representative of the weekly learning. We will revisit these keywords collectively at the beginning of the following class.

   Step 1: Pick the week number you are responding to. (dropdown, required)

   Step 2: Write down 3–5 keywords that you think are important or representative of this week's learning. (short answer, required)

   For example: double consciousness, racial capitalism, the veil, mass incarceration.

2. Compile. Before the next class, the instructor exported the responses and cleaned them lightly — trimming whitespace, lowercasing, and normalizing near-duplicates (e.g., "veil" and "the veil") — into one comma-separated list per week.
3. Visualize. The list became a word cloud sized by frequency: the more students submitted a term, the larger it appeared.
4. Review. The following class opened with about five minutes on the cloud: the most frequent terms, any surprises, connections to earlier weeks — and an invitation for one or two students to say why they chose a particular term.

Live Demonstration

The full Spring 2026 collection — interactive weekly word clouds with frequency counts for thirteen instructional weeks — is available at soc250-sp26.netlify.app.

Build Your Own

1. Create the intake form. Any survey tool works (the original used Google Forms). Two required fields: a week or unit selector, and a free-text field for three to five keywords. Reuse or adapt the form text above. A memorable short link helps — students will use it every week.
2. Fold it into the weekly rhythm. Announce it once, then let the routine carry it — for example, due alongside the weekly discussion post. Keep it ungraded.
3. Compile each week. Export responses, clean lightly (trim, lowercase, normalize variants), and keep one comma-separated keyword list per week. A few minutes of work.
4. Generate the cloud. Use whatever is easiest: an online word cloud generator, presentation software, or a simple web page (the demonstration site uses D3.js with frequency-based sizing). Pair the cloud with a plain frequency list — as the demonstration site does — so the same information is available to screen-reader users and for closer reading.
5. Open class with it. Keep the review short, conversational, and cumulative: by midterm, the interesting question is less "what did we learn last week?" than "what keeps coming back?"