Naming the Right Challenge Changes Everything

There's a moment in improvement work where everything shifts. It's not when you collect data. It's not when you analyze it. It's when you name the challenge.

The way you name the challenge determines what you try to do about it.

A school says: "Our students don't read at grade level."

Different school says: "Our students aren't getting enough time with connected text and don't have strategies for comprehension."

Same outcome. Completely different named challenges. And the work that follows will be completely different.

How We Usually Name Challenges

Most schools name challenges the way we're taught to in data meetings: "Students are performing below standard in reading." Or "Math facts are weak." Or "Writing lacks organization."

These are accurate. They describe the outcome. But they don't describe the challenge you actually need to solve.

Because they're outcome statements masquerading as challenge statements. They describe what students didn't do, not why they didn't do it.

And when you name the challenge incorrectly, you solve for the wrong thing.

You'll start teaching to the test. Or drilling skills in isolation. Or increasing pressure and compliance. Because you're trying to fix an outcome, not change the practice that produces it.

The Right Challenge Statement Points to Practice

A challenge statement that changes everything points toward practice. It describes what we think is happening in instruction that's producing the outcome.

"Students don't have enough time reading connected text" is a challenge that points toward practice. Now you can do something. You can look at how time is allocated. You can think about what students would gain from more reading time.

"Students lack strategies for comprehending difficult text" points to a practice challenge. What comprehension strategies are being taught? How? When? What happens when students encounter confusion?

"Students struggle with multi step word problems because problem decoding and problem solving are taught separately" points to a practice design challenge. Now teachers can think about how to integrate those skills.

When you name the challenge at the practice level, the solution starts to emerge. Not because someone has expertise to hand you. But because teachers who experience the practice can imagine how it might change.

Why Naming the Challenge Matters for Collective Collaboration

Here's where this becomes critical for a district system. When you name the challenge correctly, it becomes transferable knowledge.

If School A says "Students lack reading comprehension strategies" and School B has the same challenge, they can work together on it. They can share what they're learning about how to teach comprehension. They can look at each other's instruction and give each other feedback.

But if School A names it as "Students don't read at grade level" and School B names it as "Reading is weak," those are two different challenges. The solution from School A might not transfer. The thinking might not travel.

The power of collective collaboration comes from identifying shared practice challenges, not shared outcome problems.

The Conversation That Names the Challenge Correctly

There's an art to naming the challenge. It usually comes from conversation. Not just between a principal and data, but between a team looking at practice.

You look at outcome data. You ask "What practice might be producing this?" You observe instruction. You talk with teachers. You look at student work.

And through that looking and talking, a challenge emerges.

It's not what you thought when you first saw the data. It's more specific. It's tied to something actual in practice.

"I was expecting it to be about motivation," a principal says. "But when I watched students work, I realized they actually don't know how to chunk the problem to see the steps."

Now there's a named challenge. And it's specific. And it points toward something you can change.

That's when the real work begins.

The Leadership Move

Here's the move: When you're tempted to name a challenge as an outcome ("Low reading scores"), pause. Ask yourself: What practice am I observing that might be producing this? What would a challenge statement be that points toward that practice?

That challenge statement is the one that will actually guide your improvement work.

And it's the one that will travel across your district. Other schools will recognize themselves in it. Teams will think together about how to address it. That's when collective improvement becomes possible.

The Leadership Pause

The next time you see outcome data that concerns you, resist naming the challenge as an outcome problem.

Instead, ask: Based on what I know about practice, what is the actual challenge we're facing?

The answer to that question will change everything about the work that follows.

Further Reading:

Weick, K. E. (1995). Sensemaking in Organizations. Sage Publications. Weick's framework on sensemaking explains how organizations make meaning from situations and how the language used to describe challenges shapes the actions taken. He argues that small changes in how challenges are named and framed lead to fundamentally different organizational responses.

Rittel, H. W. J., & Webber, M. M. (1973). Dilemmas in a General Theory of Planning. Policy Sciences, 4(2), 155 to 169. This foundational paper distinguishes between well defined problems and wicked problems, arguing that many organizational challenges (like educational improvement) are "wicked" and require ongoing learning and reframing rather than technical solutions. The way you name the problem shapes the solutions you try.