What a Workplace Conversation Taught Me About How We Teach History
I was standing in the break room at work, waiting for the microwave to finish heating my lunch, when two of my colleagues started talking about a documentary one of them had watched the night before. It was about the American Revolution, and the conversation quickly turned to why the colonies had rebelled against Britain.
“Honestly, it was all about taxes,” one of them said, leaning against the counter. “The British just kept adding more and more, and eventually people had enough. That’s basically it.”
The other colleague nodded. “Yeah, that’s what they taught us in school, right? No taxation without representation. Simple.”
I stood there, stirring my soup, and felt a little knot form in my stomach. Because it wasn’t just about taxes. It was also about Enlightenment ideas, about shifting identities, about the messy politics of colonial governance, about enslaved people who saw the rhetoric of liberty as hollow, about indigenous nations whose land was caught in the middle. It was complicated. But the way my colleagues talked about it, it was a math problem with one clean answer.
The microwave beeped. I took my soup and joined them at the small table near the window. I didn’t say much, but I kept thinking about that phrase: that’s basically it. Where did that come from? Not from malice, certainly. Neither of them was a history denier. They were smart, curious people. They just had a mental model of history that had been shaped, somewhere along the line, by simplified stories.
And I started to wonder about how we teach history to kids because, honestly, I do the same thing with my own son at home. He’s in fifth grade, and last week he came home with a worksheet about World War II. The entire thing was a fill-in-the-blank exercise: major battles, dates, the names of leaders. There was a word bank. He finished it in ten minutes and said, “Done,” like he’d just completed a crossword puzzle.
I didn’t blame him. The worksheet didn’t ask him to think. It didn’t ask him to consider what it might have felt like to be a civilian in a bombed city, or how the war affected colonial soldiers from India and Africa who fought for empires that didn’t treat them as equals. It just asked for facts. And facts, on their own, don’t build understanding. They build a veneer of knowledge that can be peeled away the moment someone asks a real question—like my colleague did about the Revolution.
The thing is, we often teach history like it’s a finished product. Like there’s a single, agreed-upon story, and our job as adults is to hand that story to children as cleanly as possible. But history isn’t a product. It’s a process. It’s an ongoing conversation between the past and the present. And when we teach it as a set of conclusions, we accidentally teach kids that the past is simple, that historical actors were either heroes or villains, and that complex causes can be reduced to catchy slogans.
Later that evening, I sat down with my son and his worksheet. I asked him, “Which battle do you think mattered the most?”
He looked at me like it was a trick question. “Is there a right answer?”
“Not from the worksheet,” I said. “What did you learn about Stalingrad? Why do you think it was important?”
He shrugged. “I dunno. We didn’t talk about it. It was just one of the blanks.”
That moment reminded me of a teacher I had in middle school—Mrs. Alvarez. She gave us a packet of primary sources from the Lewis and Clark expedition: journal entries, letters, maps. She asked us to make a timeline, but then she pushed us further. She asked, “What do these documents tell us that the textbook doesn’t? What might be missing?” We hunted for the absence of Native voices. We noticed how the journals described people as “savages” and “children of the forest,” and we wrestled with what that meant about the writer, the time, and the way we were being taught to see the expedition.
That class changed how I understand history. Not because Mrs. Alvarez told me what to think, but because she showed me that history is a way of thinking. It’s about asking whose perspective you’re reading, what evidence you’re using, and what questions still remain unanswered.
I am not a teacher. I’m a parent, a regular person who happens to work in an office and talk about documentaries at lunch. But I think we all play a role in how history is learned. When my son asks me about something he saw online or heard from a classmate, I try not to give him a single clean sentence that closes the topic. Instead, I ask him questions. What did the other side think? How do you know that’s reliable? What would a historian need to check? It’s slower. Sometimes it leads to a moment where he stares at me like I’m being deliberately obtuse. But I see him starting to notice that there are gaps in his own knowledge, and that feels more useful than giving him the satisfaction of an easy answer.
Practical things help, too. I’ve started using timelines differently at home. Instead of a straight line, we make timelines with branches, with spaces for “what we don’t know” and “who isn’t represented here.” When we watch a historical movie, I ask him to compare it to a short primary-source excerpt I pull up online. For instance, we watched a film about the Civil War, and then I found an actual letter from a soldier describing the mud and the boredom and the fear. The movie was dramatic; the letter was mundane and intimate. The contrast taught him more than any lecture I could give.
Another thing that works well is to talk about history as a series of choices. For any event, I ask: what were the options? What did people at the time think those options were? This shifts the focus away from inevitability and toward the reality that historical actors had no idea how things would turn out. That’s the strongest antidote to oversimplification I know. When my son asks “Why did the Roman Empire fall?” I don’t let him get away with “barbarians.” I say, “Okay, but which barbarians? And what were they reacting to? And what did a Roman farmer in, say, northern Gaul think was happening?” The goal is not to turn a fifth grader into a PhD candidate, but to let him see that history is a puzzle, not a list.
My colleagues at work are not bad people, and they aren’t bad learners. They simply absorbed a version of history that made it feel finished. That conversation in the break room made me realize how much the way we teach history matters—not because kids need to memorize more facts, but because the way they learn to think about the past shapes the way they think about the present. If history is a list of names and dates, then the world feels like a sequence of events that just happened. If history is a habit of questioning, then the world opens up.
I still don’t know how to convince a busy coworker to care about the nuance of colonial taxation. But I do know that with my son, I can slow things down. I can ask him to sit with a question for a few minutes. I can let the worksheet sit unfinished on the counter for a while and instead read a diary entry from a teenager who lived through something he’s studying. It won’t make him a perfect historian. But maybe he’ll grow up to be the kind of adult who, when watching a documentary, says, “Hmm, but what about the other side?” instead of “That’s basically it.”
And that would be enough, I think. One more person who knows that the past is not a flat line, but a deep, unruly space—and that learning to move through it takes practice, not just memory. The conversation at lunch reminded me of that. I’m still trying to live up to it.
Please indicate: Thinking In Educating » What a Workplace Conversation Taught Me About How We Teach History