Moving PBIS From Compliance to Culture

Positive behavior systems have a predictable failure pattern, and it's not the one most people expect. The system rarely fails because the framework was wrong. It fails because it quietly calcifies into a compliance exercise — a point system, a store, a set of posters — disconnected from the actual behavioral culture of the building. Everyone can point to the artifacts of the program. Fewer people can point to a shift in how people actually treat each other because of it.

How the drift happens

Most positive behavior frameworks start with real momentum. There's training, a clear rollout, visible enthusiasm, and — often — a genuine early dip in behavioral incidents as everyone pays closer attention to something new. The trouble starts a year or two later, once the framework has become routine rather than novel. At that point, a system built around external reinforcement (points, prizes, recognition) can start running on autopilot: staff hand out the tickets because that's the procedure, students collect them because that's the game, and the underlying goal — students internalizing and practicing better behavioral skills — quietly stops being the thing anyone is actually watching for.

The tell is usually in the language. A culture-driven system talks about what students are learning to do. A compliance-drifted system talks about what students are earning. Both can be running simultaneously in the same building, with the same posters on the wall, and only one of them is actually changing behavior.

Why extrinsic systems need an intrinsic partner

External reinforcement isn't the enemy — it's a legitimate and useful tool, especially for building new behaviors that don't yet have their own internal payoff. The problem is treating it as sufficient on its own. Behavior that's only maintained by an external reward tends to extinguish the moment the reward stops being novel or available, which is exactly why so many positive behavior systems show strong early results that fade over time.

The systems that hold up longer pair the external reinforcement with explicit teaching of the underlying skill — not just rewarding a student for a positive interaction, but naming, in the moment, what skill that interaction demonstrated, so the behavior starts to be understood and valued on its own terms, not just as a means to a prize.

The data conversation nobody wants to have

A mature behavior system doesn't just count incidents — it asks what the incidents are telling you about where the universal layer is breaking down. A spike in a specific location (a particular hallway, a particular transition time) is usually a structural signal, not a discipline signal: something about that time or place isn't adequately structured, and behavior is filling the gap. Treating every incident as an individual discipline case, rather than also asking what the pattern reveals about the environment, misses half the available information.

This is also where a genuine reduction in incidents — the kind worth celebrating — needs to be interrogated a little before it's trusted. A drop in referrals can mean behavior actually improved. It can also mean staff have quietly stopped referring, either from fatigue or from a sense that referrals don't lead anywhere useful. The number alone doesn't distinguish between those two very different stories; the conversations underneath it do.

Bringing it back to culture

A few practical shifts tend to move a system back from compliance toward genuine culture:

Publicly recognize the skill, not just the reward. Naming specifically what a student did — the actual behavior, described in the language you're trying to build — does more for internalization than the prize itself.

Involve the people closest to the friction in redesigning the system, not just implementing it. The staff and students who interact with a struggling structural point most often usually have the clearest sense of why it's not working, and systems designed without their input tend to solve the wrong problem.

Revisit the framework every year like it's new, not like it's finished. The moment a positive behavior system gets treated as "done" is usually the moment it starts drifting into autopilot.

Ask what a reduction in incidents actually means before celebrating it. Fewer referrals is good news if it reflects real behavioral growth, and a warning sign if it reflects staff disengagement from the reporting process.

None of this requires abandoning points, stores, or recognition systems — those tools work, and they're worth keeping. It requires resisting the drift where the tool becomes the goal instead of the evidence of the goal, and periodically asking, honestly, whether your system is still building behavior or just tracking it.

A concrete diagnostic question

A useful way to check whether a system has drifted toward compliance: pull ten recent examples of positive recognition given under the framework and read them side by side. If most of them read like generic acknowledgment — a ticket handed out with no specific mention of what was done or why it mattered — that's a strong signal the system is running on autopilot. If most of them name a specific, observable behavior and connect it explicitly to a skill the team is trying to build, the system is likely still doing the internalization work it was designed for. This small audit takes less than ten minutes and tends to be more revealing than any aggregate incident count, because it gets underneath the numbers to the actual quality of what's happening in each individual interaction — which is where the real difference between compliance and culture ultimately lives.

Tiered Support Shouldn't Be a Program — It Should Be Infrastructure

Ask a room full of educators or team leaders to define their tiered-support system, and you'll usually get a description of a program: a meeting that happens on a schedule, a form that gets filled out, a committee that reviews referrals. That's not wrong, exactly, but it's incomplete in a way that quietly undermines the whole point. Tiered support that lives as a program — something separate from the daily work, run by a specific team, on a specific cadence — will always be slower and thinner than the need it's trying to meet. Tiered support that functions as infrastructure — built into how the whole organization notices and responds to struggle — catches problems the program alone never will.

The difference between a program and infrastructure

A program has boundaries: a meeting time, a referral form, a caseload. Infrastructure doesn't have boundaries in the same way — it's simply how the system behaves by default. Electricity isn't a program a building runs; it's just there, available the moment it's needed, without anyone having to request access to it. The strongest tiered-support systems function more like electricity than like a program: any staff member, in the normal course of their day, can recognize a concern and know exactly what the next small step is, without waiting for a scheduled review.

The practical marker of the difference is speed. In a program-only system, the gap between "someone notices a problem" and "someone with authority to act reviews it" is measured in weeks, because it depends on the next meeting. In an infrastructure system, the gap is measured in days, because the first response doesn't require the full committee — it requires a known, low-threshold action any team member can take immediately.

Why the three-legged stool matters

Effective tiered systems tend to track three domains simultaneously rather than treating them as separate initiatives: the social-emotional and behavioral picture, the academic picture, and attendance. Leaders who split these into separate teams, separate meetings, and separate data systems often miss the connections between them — the student whose academic struggle is actually a behavior signal in disguise, or the behavior concern that's actually rooted in chronic absence. Reviewing all three together, even briefly, surfaces patterns that reviewing them in isolation hides.

This doesn't require an elaborate structure. It requires a short, regular gathering of the people who each hold a piece of the picture — enough to cross-reference concerns, not so heavy that it becomes its own bottleneck.

What makes tier 1 do the heavy lifting it's supposed to do

The most common failure in tiered systems isn't a weak tier 2 or tier 3 — it's a weak tier 1, the universal layer every single person is supposed to receive by default. When tier 1 is inconsistent, the system gets flooded with referrals for problems that better core instruction or better core routines would have prevented, and the more intensive tiers become overwhelmed handling volume they shouldn't be seeing. A tiered system audit that only looks at the intervention list and ignores the strength of the universal layer is looking in the wrong place first.

Practical markers of a system that's working as infrastructure, not just a program

A few signs distinguish a mature system from a well-intentioned but thin one:

Any staff member can name the first, low-threshold response to a concern without checking a manual. If the answer to "what do I do if I notice this" requires looking something up or asking a specialist, the infrastructure isn't built yet — you have a program with a gate in front of it.

Data gets looked at together, not in silos. The team reviewing behavior concerns knows what the attendance data says about the same student, and vice versa.

The system has a known response to its own overload. Every tiered system eventually gets more referrals than it can immediately act on. A mature system has a plan for that moment — a way to triage — rather than letting the backlog quietly become the new normal.

Universal practices are actively maintained, not just launched once. Tier 1 fidelity decays without attention, the same way any habit does. Leaders who treat tier 1 as "already handled" after the initial rollout are usually surprised, six months later, by how much has quietly drifted.

The leadership shift

If your tiered system feels perpetually behind, the instinct is often to add capacity to the intervention tiers — more specialists, more meeting time, more forms. Sometimes that's the right move. But it's worth first asking whether the system is functioning as infrastructure or as a program bolted onto the side of the real work. The fix for a program that's underwater usually isn't a bigger program. It's making the first response to concern something everyone already knows how to do, without waiting for permission.

A concrete failure pattern to watch for

One of the most common signs that a tiered system has drifted from infrastructure back into a program is a growing backlog of referrals sitting in a queue, waiting for the next scheduled review, while the underlying concern keeps compounding in the meantime. If a team member notices a struggling colleague or student in week one but the earliest possible response is a meeting in week four, the system has effectively told everyone that noticing early doesn't matter, because nothing happens until the calendar allows it. Rebuilding this usually doesn't require more meeting time — it requires building a genuine, known, low-threshold first response that doesn't require the full team's involvement to activate, so the four-week gap between noticing and acting shrinks to a few days, with the fuller review still happening on schedule for anything the early response didn't resolve.

The Case for Explicit Vocabulary Instruction — And Why It's Everyone's Job

Vocabulary instruction has an image problem. It sounds like the least urgent item on an instructional agenda — a nice-to-have layered on top of the "real" work of comprehension, fluency, and content mastery. That framing gets the relationship backwards. Vocabulary isn't a supplement to comprehension; it's a primary bottleneck for it, and it belongs to every subject area, not just literacy instruction.

Why vocabulary is a leverage point, not a side project

Think about what actually happens when a learner hits an unfamiliar word in the middle of a complex text or a complex task. Comprehension doesn't just dip for that one word — it can collapse for the surrounding sentence, because working memory gets consumed trying to solve the vocabulary problem instead of processing meaning. Multiply that across a page, a lecture, or an assessment, and you can see how a vocabulary gap masquerades as a comprehension gap, a content-knowledge gap, or even a motivation problem, when the actual bottleneck is simpler and more fixable than any of those.

This is part of why vocabulary instruction shows up in the research with some of the strongest effects available to instructional leaders — not because words are magic, but because vocabulary sits upstream of almost every other academic task. Fix the bottleneck, and downstream performance across subjects tends to move with it.

Why it gets neglected anyway

Vocabulary instruction is easy to under-invest in for a specific, structural reason: it doesn't feel urgent in the moment. Nobody fails a lesson because of a vocabulary gap in any visible, immediate way — the failure shows up later, diffusely, as "this student seems to struggle with comprehension" or "this class can't access the higher-level content." By the time the gap is visible, it's been compounding for a long time, which makes it look like a bigger, vaguer problem than it actually is.

There's also a subject-area ownership problem. Reading teachers often assume vocabulary is being handled elsewhere, and content-area teachers often assume it's a literacy-block responsibility. The result is a gap nobody is deliberately covering, because everyone has a reasonable-sounding reason to assume someone else has it.

What "explicit" actually means

The word "explicit" is doing real work here, and it's worth being precise about it. Explicit vocabulary instruction isn't defining a word once when it comes up in a text. It typically includes:

Deliberate selection. Not every unfamiliar word deserves instructional time. The words worth teaching directly tend to be ones that are useful across many contexts, not just the one text where they appeared, and words that unlock access to the specific content or assessment students will encounter.

Multiple, varied exposures. A single definition rarely produces durable ownership of a word. Learners need to encounter a word in different contexts, use it in their own sentences, and connect it to related words before it becomes usable rather than just recognizable.

Active production, not just recognition. Being able to select the correct definition on a quiz is a much lower bar than being able to generate an original, correct sentence using the word — and the second is a far better predictor of whether the word has actually become part of a learner's working vocabulary.

Explicit attention to word relationships. Words taught in isolation are harder to retain than words taught in clusters — synonyms, antonyms, word families, and morphological relatives all give the brain more hooks to hang the new word on.

A leadership takeaway

If you're looking for a single instructional shift with outsized potential return, deliberate, explicit vocabulary instruction is a strong candidate — not because it's the only lever, but because it sits underneath so many of the other outcomes a team is already trying to move. The leadership job isn't to mandate more vocabulary time in isolation; it's to make the case for why vocabulary is everyone's responsibility, give people a simple, repeatable structure for teaching a word deliberately, and protect the instructional time it takes to say a word once, use it five different ways, and come back to it again next week.

What this looks like without a dedicated program

A team doesn't need a formal vocabulary curriculum to start capturing this leverage. It can start as simply as a shared habit: whenever planning any lesson, meeting, or piece of content, ask which two or three words in the material are likely to be the actual bottleneck to understanding, and build in a deliberate moment to teach them directly rather than assuming context will carry the meaning. Over a semester, that small habit, repeated consistently across a team, produces a cumulative effect that a single well-designed unit never could, precisely because the compounding advantage of vocabulary knowledge comes from breadth and repetition across contexts, not from depth in any one lesson. The barrier to starting is almost never resources. It's simply remembering, consistently, that the words themselves deserve deliberate attention rather than being treated as incidental to the content they're carrying.

A note on pacing

Explicit vocabulary instruction doesn't require an overhaul of existing lesson plans to start paying off. A small, consistent addition — two or three deliberately chosen words a week, taught with real depth rather than a quick definition — compounds meaningfully over a semester in a way that's easy to underestimate looking at any single week in isolation. The instinct to wait for a comprehensive program before starting is usually the biggest barrier to actually beginning.

Structures and Routines: The Unsexy Work That Makes Everything Else Possible

There's a particular kind of leadership advice that gets applause and doesn't get implemented: build relationships first, structure second. It sounds humane. It also gets the sequence backwards for most teams, most of the time.

Here's the version that actually holds up: structure is what makes relationship-building possible at scale. Without it, a leader's warmth becomes a private resource, available only to the handful of people who happen to get face time, while everyone else experiences the absence of structure as neglect dressed up as flexibility.

The hidden cost of "we'll figure it out as we go"

Every team has a finite amount of attention. When basic questions — where does this go, who do I ask, what happens if I'm late, what's the consequence for missing this — don't have clear answers, people don't stop asking them. They just start asking them of each other, informally, constantly, in ways that never quite resolve. The cost isn't chaos, exactly. It's drag. Everything takes longer than it should, and nobody can point to why.

Leaders who inherit a struggling team often diagnose the problem as a culture problem — people don't care enough, don't trust each other, aren't bought in. Sometimes that's true. But just as often, what looks like a motivation problem is actually a structure vacuum. People aren't disengaged because they don't care; they're disengaged because engaging costs more energy than it should, and eventually they stop paying that tax.

Structure isn't the opposite of trust — it's what trust is built on

There's a useful reframe here: structure doesn't constrain people, it frees them. A team member who knows exactly what's expected, exactly what the consequence of a miss looks like, and exactly how to get help doesn't experience that as control. They experience it as safety. The absence of structure isn't freedom; it's uncertainty, and most people don't thrive under sustained uncertainty, even when they say they want autonomy.

This is why the leaders who build the strongest relational cultures are so often the same leaders who are almost boringly consistent about logistics. It isn't a coincidence. Consistency in the small, unglamorous things is what earns the credibility to be flexible and human in the moments that matter. If people can't count on you to run a predictable meeting, they won't trust you to handle an unpredictable crisis.

What this looks like in practice

Good structure has a few recognizable features, regardless of the setting:

It's visible. Not tribal knowledge held by whoever's been there longest, but written down, posted, or otherwise externalized so a new person can find it without asking.

It's rehearsed, not just announced. Telling people the plan once and assuming it will hold is the single most common structural failure. Plans need repetition before they become habits, and habits are what survive stress.

It has a known response to failure. Structure that only exists when things go well isn't structure — it's optimism. The real test of a system is what happens the first time someone breaks it, misses it, or ignores it. If the answer is "I don't know, I guess we'll deal with it," the structure isn't finished.

It's proportionate. Over-structuring is a real failure mode too — rules for situations that will almost never occur, approval chains for decisions that don't warrant them. The goal isn't maximum structure; it's structure sized to the actual risk and actual frequency of the situation.

The leadership move

If your team feels like it's running on goodwill and improvisation, resist the urge to fix it with a values conversation. Start with an audit of the actual mechanics: what happens when someone's late, when a task falls through, when two people disagree about who owns something. Wherever the honest answer is "it depends" or "we've never really said," you've found your next structural investment — and very often, it'll do more for morale than the culture initiative would have.

Where to start if this feels overwhelming

An honest structural audit doesn't need to happen all at once. Start with the single interaction that generates the most repeated, informal questions — the one where three or four people a week ask essentially the same thing because there's no clear, visible answer. Fix that one first, write it down somewhere findable, and rehearse it until it's automatic. Then move to the next one. Trying to formalize every structural gap simultaneously is its own failure mode — it produces a wall of policy nobody reads and defeats the actual goal, which is clarity, not documentation for its own sake. The right pace is usually slower and more targeted than it feels like it should be, and it compounds: each structural gap closed removes a small, constant drag that was quietly costing the team attention it didn't know it was spending.

A closing distinction

Good structure and rigid bureaucracy can look similar from the outside — both involve rules, both involve consistency — but they solve for different things. Bureaucracy protects the institution from the individual. Good structure protects the individual's time and attention so they can do their best work without re-deriving the basics every day. Keeping that distinction in mind while building or auditing structure helps avoid the common overcorrection, where a leader burned by chaos swings toward excessive process and ends up recreating the same drag they were trying to eliminate, just dressed up as order instead of disorganization.

Why the First Two Weeks Determine Your Whole Year

Ask any veteran teacher when a class "sets" — when the culture of a room becomes visible and durable — and almost none of them will say December. They'll say the first two weeks. Something happens early that either builds momentum or creates a hole a leader spends the rest of the year trying to climb out of.

The uncomfortable truth is that most of us don't act like we believe this. We spend the summer building curriculum maps, refining assessment calendars, and polishing the vision statement, and then we walk into the first days of the year treating them as ceremonial — a ribbon-cutting before the "real work" starts in week three. But the research on this is remarkably consistent, and it isn't subtle: the degree of control, clarity, and warmth established in the first days of a school year predicts outcomes for the rest of it far more than most of what follows.

This isn't a classroom-only phenomenon. It's true of any team a leader inherits or rebuilds each year. New staff, new students, new families — all of them are running a background process in the first two weeks that never fully stops: is this place organized? Does the person in charge know what they're doing? Will my questions get answered? Will structure protect me or trap me? People answer those questions quickly, and they answer them from what they observe, not from what's written in a handbook.

What actually gets established in those two weeks

Three things, in order of how visible they are and how invisible their absence becomes over time:

Structures. Where things go. How transitions happen. What the signal is for attention. These sound trivial until they're missing, at which point every minute of instruction or work leaks through the cracks they leave. A team without structure doesn't feel "loose" — it feels exhausting, because everyone is spending working memory on logistics that should be automatic.

Routines. The difference between a structure and a routine is repetition until it's boring. You don't explain the structure once and move on — you rehearse it until nobody thinks about it anymore. Leaders who skip the rehearsal phase because "we already went over this" are almost always underestimating how many repetitions a new behavior needs before it becomes reflexive, especially under stress.

Expectations, stated as behaviors, not values. "We value respect" is not an expectation. "We start meetings on time, and if you're not there in the first two minutes, we've started without you" is an expectation. The clearer and more behavioral the expectation, the less it depends on mood, memory, or interpretation to hold.

Why leaders under-invest here

Two reasons show up over and over. First, structure-building feels like a detour from the "important" work — the curriculum, the strategic plan, the culture initiative. It isn't a detour. It's the delivery mechanism for all of it. A brilliant instructional plan executed inside chaotic routines will underperform a mediocre plan executed inside disciplined ones, almost every time.

Second, leaders overestimate how well early structure "sticks" without reinforcement. The first week's routines are new to everyone, including the leader, and it's tempting to relax the moment things look like they're working. But early success is fragile. The teams and classrooms that hold their structure through the first six weeks are the ones where the leader treated re-teaching as expected, not as a sign of failure.

A practical frame

If you're heading into the start of a new year, cycle, or season with a team, ask yourself three questions before day one:

1. What three or four things do I need people to do automatically by week three, and have I planned to teach — and re-teach — them that many times?

2. What will I actually be looking for as I walk around in the first two weeks, and have I told people I'll be looking for it?

3. What's my plan for the moment structure breaks down — because it will — so that the response is calm reinforcement rather than surprised frustration?

None of this is glamorous. It won't show up in a highlight reel of your leadership year. But ask the people who work for you what they remember about the year that went well, and more often than not, they'll point back to how it started — not because the first two weeks were exciting, but because they were clear. Clarity, more than charisma, is what people are actually starving for at the start of anything new.

A short example worth sitting with

Picture two versions of the same first week. In the first, the leader spends day one on logistics, mentions expectations once in passing, and assumes everyone caught it. By day four, three different people are lining up at the leader's door with the same clarifying question, and the leader starts to feel like the team is unusually needy. In the second version, the leader spends five extra minutes on day one explicitly modeling the expected behavior, checks for it visibly on day two, corrects it warmly and specifically on day three when it slips, and by day five it's simply how things are done — no one asks, because no one needs to. The difference in outcome isn't talent or team quality. It's five minutes of deliberate teaching, repeated, versus one announcement assumed to be sufficient. That gap, multiplied across every structure a team needs, is most of what separates a first two weeks that sets a year up well from one that spends the rest of the year catching up.

Celebrating Growth: Sharing Vocabulary Wins Schoolwide

Highlighting student vocabulary use across the school builds momentum. This week’s post looks at ways to celebrate growth: vocabulary walls, student spotlights, cross-grade word challenges, and integrating vocabulary into student performances and displays.

Vocabulary learning becomes part of school culture when students see it valued everywhere. What are you doing to make word learning visible and joyful?

The Importance of Using Academic Language in the Classroom

Academic conversations enhance learning. Students need structured opportunities to use domain-specific and Tier 2 vocabulary across all content areas. This post highlights how sentence frames, accountable talk protocols, and intentional modeling can transform a classroom into a language-rich environment.

Encouraging student talk helps solidify learning and ensures students aren’t just learning content—but learning to communicate that content effectively.

From Strategy to Ownership: Elevating Student Voice in Vocabulary

Ownership is the ultimate goal of vocabulary instruction. When students can independently recognize, define, and apply new words, they’ve moved from surface learning to true mastery. This entry explores tools like student-generated dictionaries, self-awareness charts, and vocabulary journals.

How do your students track their word knowledge? Do they have space to reflect on which words are important to them and why?

Vocabulary Instruction: Creating a Culture of Curiosity

Vocabulary development isn't just about memorizing definitions—it’s about building a bridge between language and meaning. This post focuses on how to make vocabulary instruction intentional, transparent, and transferable. Using morphology, context, and student-friendly strategies empowers students to become curious word learners.

When students connect new words to prior knowledge, explore word parts, and apply vocabulary in real contexts, they build deeper, more durable understanding.

Learning Intentions and Success Criteria: Why Clarity Matters

Clear learning intentions and success criteria are not just teacher tools—they are student tools. When students understand what they're learning and how they'll know they’ve learned it, their engagement and ownership increase. Drawing from Fisher and Frey’s framework, this post emphasizes that visible learning starts with visible goals.

This week, consider: Are your students able to explain the purpose of the lesson in their own words? Are you giving them the roadmap and the markers to check progress along the way?

Repetition, Retrieval, and Retention: Making Vocabulary Stick

The science of memory tells us that repetition matters—but not all repetition is equal. Spaced practice, retrieval opportunities, and varied context use all enhance vocabulary retention.

This post encourages educators to plan purposeful spiraling of academic vocabulary, so students encounter key words repeatedly and in meaningful ways over time.

The Power of Mistakes: Growth Mindset and Brain Development

Mistakes aren’t just opportunities for learning—they are the very moments when the brain grows. Neuroscientific research shows heightened brain activity during errors, especially among students with a growth mindset.

Cultivating a classroom culture where mistakes are welcomed encourages metacognition and resilience. As Piaget suggested, learning happens during disequilibrium—when current knowledge is challenged, and adaptation occurs. How do you frame mistakes in your classroom? Are they stepping stones or stumbling blocks?

Thinking Maps and Vocabulary Development

Thinking Maps provide a consistent visual language for organizing and connecting vocabulary. Whether defining terms with a Circle Map or comparing concepts with a Double Bubble Map, these tools support comprehension and long-term retention.

This week’s focus: leverage Thinking Maps not just as graphic organizers, but as scaffolds for deep vocabulary conversations.

The Brain Behind Learning: Synaptic Plasticity

Our brains are wired to learn. Synaptic plasticity, the brain’s ability to form new connections, reminds us that every interaction matters. When we challenge students, support them, and encourage them, we’re strengthening neural pathways. Statements like “This is hard, but you can do it” contribute to how students perceive themselves as learners. Let’s build strong, lasting learning connections—one interaction at a time.

Empowering Students to Monitor Their Growth

Metacognition—knowing how you learn—is critical for vocabulary mastery. Three student-centered strategies stand out:

• Self-Awareness Charts

• Personal Dictionaries

• Vocabulary Journals

Each allows students to track, reflect, and refine their understanding of new words. These tools not only support academic achievement but also build a lasting appreciation for language.

Assessment, Feedback, and Differentiation in Math

Assessment isn’t about grades—it’s about insight. Formative feedback, not just scores, helps students reflect and improve. Differentiation, grounded in data and flexibility, ensures every student gets what they need. RTI frameworks support this by providing layers of support. The key? Quality core instruction and a mindset that prioritizes feedback over praise.

Transfer Learning: When Math Becomes Meaningful

True mastery happens when students apply what they’ve learned to new contexts. That’s the essence of transfer learning. It involves metacognition, real-world connections, and strategic use of prior knowledge. Whether through structured support (low-road) or independent exploration (high-road), teachers can design lessons that push students to apply and adapt their understanding. Think about your last math lesson—did students transfer their learning?

Promoting Deep Mathematical Learning

Deep learning builds conceptual understanding through discourse, open-ended problem solving, and frameworks like Accountable Talk. Encouraging students to explain, justify, and rephrase builds deeper engagement. Small group collaboration, Kagan structures, and language supports help ensure every student is part of the conversation. Let’s increase meaningful math talk and watch understanding deepen.

Surface Learning in Mathematics

Surface learning is the first critical step in mastering math. It includes acquiring vocabulary and procedural skills needed to move deeper. Tasks like number talks and worked examples, paired with methods like manipulatives and spaced practice, support this phase. As Hattie says, “As fast as we can, as slow as we must”—knowing when to move from surface to deeper learning is key.

Context Clues: When They Help… and When They Don’t

Context clues are a double-edged sword. While sometimes helpful, they can also mislead. Fisher and Frey categorize them as:

• Misdirective

• Nondirective

• General

• Directive

Teaching students how to evaluate context clues—and verify meaning with morphology—strengthens comprehension. Modeling this evaluation process in real time is key. Let’s help students build not just vocabulary, but discernment.