Breaking Down the Silo Walls

Every teacher wants the same thing at some level: for what we teach to stick. Not just through Friday's test, but into the next course, the next year, and eventually into whatever problems our students are trying to solve when school is behind them.

That goal has a name in the research. Transfer, the ability to apply a skill or concept learned in one context to a new, different context, is widely considered one of the most important and most difficult goals of education. Students can perform well on an assessment and still have knowledge that is tightly bound to the context in which they learned it, unable to recognize it when it shows up somewhere else, in a different wrapper, with different vocabulary. The skill traveled, but it didn't travel far enough.

This is something I've thought about a lot, both from a research perspective and from personal experience studying how learning moves across disciplines. My work on C2STEM (a curriculum that integrates computational thinking and science learning) found that students who encountered the same thinking across multiple disciplinary contexts developed a more flexible, transferable version of that knowledge and skills than students who encountered it in only one place. The concept didn't just get reinforced. It got loosened from its original context, which is exactly what transfer requires.

The practical implication for K-12 teaching is this: if you want what you teach to transfer, one of the most powerful things you can do is help students see it show up somewhere else. And one of the most practical ways to do that is a conversation with the person down the hall.

– THE PROBLEM

Most school collaboration is vertical — within departments, within grade levels, within subject areas. This is practical and has genuine value: your science colleagues know your curriculum, your students' background, your pacing. That shared context is irreplaceable for a lot of coordination work.

But vertical collaboration also has a ceiling. When students only ever encounter an idea in one subject-area context, their mental representation of it stays tightly coupled to that context. Data analysis "belongs" to math class. Argumentation "belongs" to English. Computational thinking "belongs" to computer science. When the same thinking shows up unexpectedly in another domain, students often don't recognize it — not because they haven't learned it, but because they've learned the context as much as the concept.

Cross-departmental connection is one of the structural conditions most likely to loosen that coupling. It signals to students that what they're learning is bigger than any single room — that it's a tool, not a fixture. And for teachers, those conversations often surface something equally valuable: a different angle on a concept you've been teaching the same way for years.

– THE SHIFT

The shift worth making isn't from departmental to cross-departmental as a permanent structure. Most schools aren't designed for that, and the coordination costs are real. The shift is from treating subject-area isolation as the default — and treating the occasional cross-departmental moment as extra — to recognizing it as one of the most targeted interventions available for the specific problem of transfer.

Even small, single-session connections can do real work. A student who hears their English teacher say "the same kind of argument structure you built in history last week" is getting something no individual teacher can produce alone: evidence that what they've been learning generalizes.

– WHAT THE RESEARCH SAYS

Transfer requires context variation.

Research on transfer consistently finds that students develop more flexible, transferable knowledge when they encounter concepts across multiple contexts than when they learn them in one domain and are expected to apply them elsewhere without explicit connection. The transfer doesn't happen automatically. It requires the connection to be made visible — ideally by teachers who can name it, not just by students who might notice it.

The mechanism matters. When students learn a concept in one context, their mental representation of it tends to include the contextual features of that setting. "Systems thinking" learned only in biology becomes biological systems thinking — not easily accessed when a social studies problem requires it. Making the concept explicit in a new context strips away some of those contextual features and makes the underlying idea more portable.

Authentic problems don't respect department lines.

A consistent finding in inquiry-based learning research is that authentic, real-world problems produce higher engagement and deeper learning than problems that are clearly artificial. Real-world problems almost never live within a single subject area. Climate change involves science, economics, history, and communication. Public health involves biology, statistics, ethics, and policy. Coding involves math, logic, language, and design. When students encounter these problems in only one disciplinary frame, they learn a partial version of how to think about them.

Spring is a useful moment to draw on this. Students who are disengaging from subject-area content as abstraction often re-engage when the same content connects to something tangibly real. Cross-departmental moments can create those connections in ways that single-subject lessons can't.

– THE FRAMEWORK

Step 1: Find one point of genuine overlap.

Start with a specific skill or concept you're currently teaching. Then ask: where else does this legitimately show up? Data analysis appears in science, social studies, health, and economics. Argumentation structure appears in English, history, and debate. Proportional reasoning appears in art, chemistry, and physical education. Pattern recognition appears almost everywhere.

You're not looking for a full unit integration or a co-taught project. You're looking for one point of real conceptual overlap — a place where your content and a colleague's content share actual intellectual territory that students could recognize.

Step 2: Have the twenty-minute conversation.

Find the colleague and bring the specific overlap you identified. The conversation doesn't need to be a collaboration commitment — it can be purely exploratory. "I'm teaching inference with data next week. Are you working on anything where that framing might connect?" Or: "My students just finished a unit on argumentation. Are there any moments in your class where they could be reminded to use that tool?"

The goal of the first conversation is mutual understanding, not a plan. What are you each working on? Where does it touch? What would it cost (in terms of time and energy) to make a connection visible to students?

Step 3: Choose the lightest connection that actually works.

Not every cross-department connection needs to be a co-taught project or a formal curriculum integration. A few options, ordered roughly by time investment:

• A brief guest mention: you name the connection explicitly in your lesson ("this is the same kind of graph your science teacher uses to track...") — costs nothing but the deliberate choice to say it.
• A guest visit: a colleague spends five to ten minutes at the start or end of your class connecting what you're working on to what they're working on — takes one conversation to coordinate.
• A shared prompt: both teachers use the same real-world problem or data set in the same week: requires some alignment but almost no joint instruction.
• A joint class: two groups come together for a single session around a shared problem — takes the most coordination and usually produces the most visible effect.

Most cross-department impact happens through the first two options, not the last. A single deliberate mention of how two subjects are using the same thinking is low-cost and genuinely moves the needle on whether students experience their learning as connected.

Step 4: Make the connection explicit to students.

The research is clear on this: the transfer benefit of cross-departmental connection depends on the connection being visible to students, not just happening in the background. Students who don't realize their data skills from math are being applied in science may not do the cognitive work of connecting them. Naming it — "this is the same reasoning you used in..." — is the move that makes the pedagogical value of the coordination real.

– THE HONEST PART

Cross-department collaboration has coordination costs that shouldn't be minimized. Finding time with a colleague from another department requires schedule alignment, relationship investment, and often a degree of institutional support that isn't always available. Starting small is not a compromise.

There's also a relationship dimension worth naming. The most effective cross-departmental connections tend to develop over time, through repeated informal conversation, shared curiosity about how each other's subjects work, and the gradual accumulation of mutual respect. A forced curriculum alignment doesn't produce this. A genuine conversation about what you're each trying to accomplish — and where you can help each other — tends to.

If the colleague you approach is skeptical, that's information. It may mean the overlap you identified isn't as natural as you thought, or it may mean the relationship needs more informal development before a collaboration is possible. Neither is a failure. The first conversation is worth having regardless of where it leads.

– YOUR MOVE

Identify one concept or skill you're teaching in the next two weeks. Identify one colleague in a different department where that same concept might legitimately show up. Ask them, in one conversation, what they're working on and whether there's a moment your students might encounter the connection.

If nothing emerges from the conversation, you've still had a useful exchange. If something does emerge — even a single sentence you can say to your students about where this thinking shows up elsewhere — it's worth the twenty minutes.

What's the most unexpected cross-department connection you've found in your teaching — and what did it do for your students? Drop it in the comments.

---

This is part of Accingo's Collaboration Hub — practical frameworks for building teaching teams and partnerships.