How Do Historians and Archaeologists Know About the Past?

Every year, I start my Grade 10 Ancient History course with this question, and I never tell the students the answer. Instead, I hand them a stapler. Or a paperclip. Or a clipboard. Whatever happens to be lying around the classroom, really. The task is simple to explain and surprisingly hard to do: pick an object, describe it in as much detail as possible, and never once say what it is or what it's used for.

No naming it. No explaining its function. Just size, shape, color, material, texture, marks, symbols — whatever you can actually observe.

It sounds easy until students try it. Within about thirty seconds, someone slips. "It's for holding paper together." Stop — that's an interpretation, not a description. Try again. The instinct to explain what something is for is so automatic that resisting it becomes the whole exercise.

Students start talking like this instead: "A thin piece of curved metal, silver in color, bent into two overlapping loops, roughly four centimeters long." Someone else has to guess what it is from that description alone, and often they guess wrong, or they guess something plausible that isn't remotely close to a paperclip.

 That's the point. I tell them: this is what archaeologists actually do. They dig something out of the ground and they don't get a label. They don't get to ask the person who used it. All they have is the object itself, and from that object alone, they have to build outward — first to a careful description, then to a hypothesis, then, if the evidence holds up, to something closer to an explanation.

From Objects to a Lost Civilization

Once the class has felt how strange it is to describe something without naming its purpose, I raise the stakes. I tell them they've just found a set of clay tablets, inscribed with dozens of words, and their job now is archaeological detective work at a larger scale — grouping the words, naming the categories, and using those categories to reconstruct a picture of the people who wrote them.

The word list is deliberately a jumble: town, camel, wheat, tax, war, temple, slave, ivory, cotton, blacksmith, dry season, and so on. There's no instruction manual for how to sort them. I just tell students to look for patterns — which words seem to belong together, and why.

What happens next is the best part of the lesson. Different groups sort the same twenty-eight words into completely different categories. One group organizes by jobs (teacher, blacksmith, barber, healer). Another groups by food (cheese, wheat, goat, yams). Someone always finds a "nature" category, someone else a "religion" one. Nobody's wrong, exactly — the words really do support several valid groupings — but nobody has the same answer either.

Then I ask them to go one step further: based on your categories, write a hypothesis about where and when this culture might have lived. This is where twelve-year-olds — sorry, fifteen-year-olds — start sounding uncannily like historians. "I think this was a farming society near a desert, because of camels and dry season." "I think there was slavery and taxes, so there must have been some kind of government or empire." They're not just sorting words anymore. They're reasoning from incomplete evidence toward a claim, and they're doing it with more caution than they'd ever apply to, say, an argument with a sibling.

Why the Disagreement is the Lesson

The temptation, as a teacher, is to wrap this up by revealing the "correct" answer — to tell them what culture the word list was actually modeled on and let that be the resolution. I don't do that. Instead, I ask the class directly: why did we all look at the exact same evidence and come up with different conclusions?

Their answers are usually better than anything I'd have written on the slide myself. People noticed different details. People brought different background knowledge to the table. Some words can honestly be read more than one way. And the evidence itself was incomplete — it was never going to add up to a single obvious story.

That's not a flaw in the exercise. That's the definition of historical work. Historians and archaeologists ask questions, gather whatever evidence survives, and build hypotheses — which, with enough supporting evidence, might eventually harden into theories. But the evidence is so often partial or ambiguous that reasonable people, working in good faith, land in different places. I want that idea to sink in on day one, before we've touched a single primary source about the actual ancient world, because it will save me a lot of trouble later in the course. When we eventually disagree about what a fragment of a text really tells us, or whether a particular ruin proves what someone claims it proves, I can just point back to the stapler and the word list. We've already done this. We know disagreement isn't a sign that someone did the assignment wrong.

If you want to try a version of this yourself, the structure is simple: an object-description task with a strict "no naming, no function" rule, followed by a word-sorting task with no fixed categories, followed by a hypothesis, followed — critically — by a conversation about why everyone's hypothesis looked a little different. The content can flex to whatever civilization or era you're about to teach. The thinking underneath it is what actually matters, and it's the same thinking students will need for the rest of the year.