What a Coworker’s Question Taught Me About Teaching History to Kids
The conversation started with a sandwich. Our team’s quarterly lunch meeting had just wrapped up, and a few of us were still sitting around the conference table, ignoring the next calendar invite. Someone mentioned the upcoming school break, which led to talk about kids’ homework, which led to someone’s middle-schooler studying the Civil War.
“It’s so boring,” said a colleague I’ll call Dan. “She has to memorize all these dates and battles. She keeps asking me why she needs to know any of it, and to be honest, I don’t have a good answer.”
I laughed, because I remembered that feeling. Then another coworker, who teaches part-time at a community college, looked up and said, “What battles is she learning about? In what order?”
Dan shrugged. “You know, the standard ones. Gettysburg, Antietam, Shiloh. It’s all just a list.”
“That’s the problem,” she said. “I had students last semester who could tell me every major battle in order, but they had no idea that the war lasted four years or that most soldiers never saw a major battle. They’d never read a single letter from an actual soldier. They had memorized a timeline without ever meeting a person.”
She wasn’t trying to be dramatic. She was just tired. But I felt the shift myself, sitting there in my office chair, thinking about the history class I took in eighth grade and the history class I now watched my own kids experience.
I didn’t grow up hating history. I grew up treating it as a collection of facts to be temporarily stored in my brain before the final exam. Dates, names, treaties, presidents, wars. I was good at it, in the way a jar is good at keeping nuts and bolts organized. But the emergency bolt I remember most clearly from my own education was a teacher who, once a week, would put a single photograph or letter on the overhead projector and have us just look at it. No questions, no grading. We’d write whatever we noticed, whatever we wondered. I remember a photograph of a Dust Bowl family and wondering what the little girl was thinking. I remember a letter from a Union soldier to his sister, complaining about the food and asking if the apple tree had bloomed yet. I remember feeling something. That was the only time history felt like a real place.
The conversation at work made me realize just how rare that kind of teaching still is. Dan’s daughter was learning history as a sequence to be memorized, not a story to be entered. And the more we talked, the more I understood the consequences.
Here’s what I mean. When kids learn history only as a list of events in chronological order, they learn that history is finished. It has a beginning, a middle, and an end, and their job is just to know what happened. It doesn’t matter who wrote about the event or why. It doesn’t matter what people felt or what they left out. It doesn’t matter whether there were other possible interpretations. History becomes a closed book.
But history is not closed. It’s actually a series of open questions, and the way we teach it changes how kids think about the world. If we teach it as a set of facts, we raise adults who accept whatever version of the past they’re handed. If we teach it as a set of stories and sources, we raise adults who ask who’s telling the story and what they have to gain.
That afternoon, I went home and looked at my own kid’s homework. He’s in fifth grade, and they were studying early colonial settlements. The worksheet had a table with three columns: the settlement name, the date founded, and one “reason for establishment.” He had filled it in neatly. He could tell you that Plymouth was founded in 1620 for religious freedom. He couldn’t tell you who the religious freedom was for, or what happened to the people already living there, or which colonists couldn’t vote, or how the Native Americans viewed the newcomers.
I asked him, “What do you think the people who already lived there thought?”
He looked at me like I’d asked him to solve a quadratic equation. “We don’t know that,” he said. “The book doesn’t say.”
But it does say, if you know how to look. There are tribal oral histories. There are letters and treaties. There are archaeological finds. There are accounts recorded later by Europeans, which are unreliable in their own way but still tell us things. The book didn’t say because the book wasn’t trying to tell that part of the story. And my son had learned, without anyone saying it aloud, that what the book doesn’t say isn’t history.
That’s what teaching history really does. It teaches children what counts as a source, what counts as a question, and what counts as a fact.
Since that conversation, I’ve tried to adjust how I approach history at home. Not as a curriculum supplement, not as a guilt trip, but just as a habit. When we watch a movie set in the past, I ask a few questions that have no right answer. “What do you think the filmmakers had to guess?” “Who’s not in this story?” When we read a biography, I ask, “What do you think this author liked about this person?” It’s not a pop quiz. Sometimes we talk for thirty seconds and move on. But it changes the texture.
I also started reading history books that aren’t textbooks. My son and I read a graphic novel about the underground railroad, and afterward he asked me why the conductors risked so much. That question felt different to me—less like memorization and more like comprehension. We didn’t need to know every stop. We needed to know what made people move.
There’s a practical side too. One thing I’ve learned is that kids remember history better when it’s tied to a specific person’s decision or dilemma. I try to ask questions like “What would you have done if you were that mayor?” or “Why do you think she decided to cross the river that night?” This doesn’t require any special training. A parent can do it at the dinner table. A teacher can do it with one extra question on a sticky note.
Another small adjustment: we stopped prioritizing dates. I mean, we still mention them, but we don’t test each other on them. Instead, when we read about an event, we try to place it in relation to something else we already know—what was happening in the rest of the world, or what was happening down the street. My son is ten, so we can’t get too deep, but even placing the American Revolution next to the French Revolution helped him see that these things didn’t happen in a vacuum.
I’m not suggesting that every teacher is failing or that every parent needs to become a historian. But the conversation at work made me realize something important: the way we teach history shapes how kids see themselves as participants or spectators. If they only memorize what already happened, they learn to be passive. If they practice asking whose story is being told, they learn that they can also have a voice.
Dan messaged me a few days later. He said his daughter’s teacher was doing a unit on primary sources, and she’d come home excited about an old diary entry. He wrote, “She actually asked me what I thought the author was leaving out. I told her I didn’t know. We went down a rabbit hole about the author’s background. It was kind of fun.”
That doesn’t mean his daughter now loves history reliably. Some nights she still complains. But something changed in the way he talks to her about it. He asks more questions than he used to. He treats the textbook as one version, not the final word.
I don’t have a neat ending to offer. We’re still working through our own homework with paper clips and hi-liter markers. Some lessons still feel flat. But I pay more attention now to what my son’s assignments leave unsaid, and I’m more willing to ask him what he wonders about. It’s a small shift, but it’s a shift.
History doesn’t have to be boring. It just has to be taught like something alive—something that was argued about, written down by real people with real biases, and shaped by choices. And if kids never hear that in a classroom, they can at least hear a question at the kitchen table. Sometimes that’s enough to start.
Please indicate: Thinking In Educating » What a Coworker’s Question Taught Me About Teaching History to Kids