When Things Get Hard
Typical early frictions from the learning community and what to do with them
It’s that time of year when the optimism from September starts running a bit thin. Challenges begin to surface differently in a learning community. Oftentimes, you don’t feel the generic exhaustion that teachers feel at this time of year; it’s something new… a different kind of hard. What you’re feeling is a specific kind of challenge that only surfaces when you’ve been working this closely with other adults and students for the first time.
If your learning community is hitting friction right now, that doesn’t mean it’s failing. It means you’re at the point where the model actually gets tested. It’s what I felt one morning when I was talking to Sage*. It wasn’t anything big, just her honest statement: “I didn’t update the anecdotal notes on the students in your home base yesterday. I went home and played with my kids.” She walked out of the office so blase. But for me, feelings bubbled up, and tears dripped into my cappuccino.
I wasn’t upset at Sage. I remember what it was like being a mom to little kiddos who need your attention… all of your attention. But she let me down. She didn’t know that some of that data was crucial—I was having a few parent conferences early this week, and I wanted to be prepared, especially for a particular parent who already wasn’t so convinced the learning community model was good for her kid. I couldn’t go into that meeting and say, “Sorry, I don’t have current math data because your daughter’s math teacher needed to be a mom this week.”
I had to think. To solve. To regroup.
What "Hard" Actually Looks Like
It rarely shows up as one dramatic failure. And my experience above, despite the tears, was not actually that dramatic. “Hard” in a learning community usually shows up as six small things, stacking on top of each other… and that’s what caused me to boo hoo.
Groups that were supposed to be flexible start calcifying again, the blue bird problem, back for round two.
Data-sharing deadlines get missed, and the whole team's momentum stalls waiting on one person.
A teacher gets attached to "their" students and regrouping suddenly feels like a fight.
The student meeting, the one that's supposed to happen every week, quietly gets skipped because something is deemed “more” pressing.
Going too fast. Trying to co-plan, co-teach, and co-assess everything across the entire day in year one, instead of starting small, and the weight of that becomes unsustainable fast.
And then there's the parent conference: sitting across from a family, being asked about a subject you didn't actually teach their child, because that was your colleague's group this term.
Any one of these challenges is manageable. All six at once, in week five, feels like the whole thing is coming apart.
And that’s when I got overwhelmed. Sage’s comment was the straw that broke me.
The Root Problem
Here's what I've noticed: almost all of it traces back to one thing. The team never fully did their vision work—or they rushed it to get to the "real" stuff faster. (If you haven't done that work yet, Crafting Your Vision walks through exactly how to build that foundation with your team—including the vision worksheet and essential agreements you can use together.)
Without a strong vision to return to, there's nothing to fall back on when things get hard. So teams default to the oldest habit they have: to work alone. Stop sharing data. Stop talking about students as a group. Prep your own conference notes instead of trusting your colleagues’ notes.
The missed data deadline isn't really the crisis. It's a symptom. The real crisis is the silo reflex, reasserting itself the moment things get uncomfortable.
And that’s probably the real thing that shook me at that moment with Sage. It wasn’t what she said or how she said it. It was my instinct to try and solve it by myself.
But it wasn’t a “me” problem. It was an “us” problem. A team problem. Our expectations weren’t clear because our vision and systems for success weren’t.
The Reset: Go Deep, Not Far
The fix is the same thing we'd tell a student who is skimming through a concept or task just to check off boxes. Stop and go deep. Not broad. We need to prioritize mastery of learning communities before we just try to add the next thing.
Our team needed to stop. And go deep. Since we were running into co-assessment challenges, that’s where we needed to stop. We needed to perfect that system. We couldn’t repair everything at once; we just needed to pull it back to one area and rebuild there.
So I brought it to the team that day.
In our discussion, we decided to focus on getting the learning community model humming, and we could only do that if we focused on one subject area. We had the unit planned out, so we zoomed in. What are we actually trying to get students to by the end of this week? Then, we got specific about grouping: how many groups, who's teaching which one, does anyone need to be separated or paired deliberately? We quickly assigned roles—who's collecting formative data, who's building differentiation tasks, who is organizing materials. And lastly, what are our assessment deadlines?
That's it. A thirty-minute meeting can reset an entire unit. You don't need a retreat. You need clarity.
That conversation helped move things forward in its plan and organization, but bigger than that, it helped us reflect on our systems. That reflection became a routine so we could constantly get better.
When You Don't Have Time for the Reset
That same week, before we'd even had the reset meeting, I still had those parent conferences to get through. Sage didn't know that I had parent conferences coming up earlier than expected. So I just went in and asked to see the student's work. I photographed their notebook and looked at the notes that Sage had written on the pages. I asked the student in particular, "What are you doing well? What are some challenges you're facing? What has Ms. Sage said to you? What do you think your next step is?" That student reflection was probably better than any anecdotal that a colleague could have written anyway. It was in kidspeak. It was authentic and genuine. It wasn't a teacher's goal, but a child's real-life focus.
So when the parents came in for their conference, I could speak about their child with clarity. What I saw and what others, even Sage, were seeing.
For all the learning communities I've been part of, sharing anecdotal data seems to be one of the biggest challenges. For some, like Sage, it's simply overwhelm—too much to do, and this is the behind-the-scenes work that's easiest to let slide on a hard day. That's not resistance. That's being human, and it happens to every one of us at some point.
But for others, not participating in the co-assessment piece of the model is something different entirely. They're the people who never bought into the model in the first place—worried about being judged by peers, afraid of losing autonomy, afraid of what the model might expose about their own teaching.
Understanding the fear doesn't make the gap disappear. But it does mean the response has to be different depending on which one you're facing. Sage needed grace and a better system. Someone who never bought in needs an honest conversation about consensus—the same gap the Knoster model names, showing up here in a new shape.
The Truth Underneath All of This
Sage and I never had a big conversation about that morning. I didn't need her to apologize, and she didn't owe me one. What I needed—what our whole team needed—was a system that didn't put all the weight on any one person's shoulders on any one day. That's what the reset meeting gave us.
A learning community gets messy, and then it gets better. Because the mess is the learning.
This is what your first year or two of teaching felt like — chaotic, uncertain, like you were building the plane while flying it. That's exactly where you are now. You're creating something new. Most teams haven't done this before, which means you don't have inherited systems to fall back on yet. You're building your own.
That's not a sign something's wrong. That's the actual process.
If your team can carve out even a little time to reflect honestly on what went sideways, you'll do it better next unit. You'll do better next co-teaching cycle. And you'll do it even better next year, when this exact crisis point comes around again — because it will.
Every hard moment your team gets through together becomes a stair step to the next one.
*names changed to protect anonymity
Note: This post was edited with AI as an assistant to refine structure and readability. My ideas, voice, and words remain intact.
Comments