Creating Feedback Loops During Nonprofit Change

Closing the Feedback Loop Isn’t a Checkbox—It’s the Whole Damn Circuit You asked for feedback. You got it. Now what? Too many leaders treat follow-through like a favor—something optional, maybe even inconvenient. But in elite teams, responding to feedback isn’t a nice to have. It’s the whole point. At Greencastle, we treat feedback response like a mission order: - We document what we heard. - We decide what to do. - We tell people what we did. But here’s the catch: not all feedback deserves a green light. Anonymous input is valuable—but not infallible. If you react to every piece without thinking, you trade discipline for drama: - Undermining managers before hearing the full story. - Solving for symptoms, not root causes. - Making noise louder instead of signal clearer. As a leader, I have to weigh if making a change to one piece of feedback might cause 10 others to be upset. So we apply a few filters: Hanlon’s Razor: Never attribute to malice that which can be explained by incompetence. Not every harsh comment is sabotage—sometimes it’s just fatigue, a bad process, or a bad day. Hitchens’ Razor: What can be asserted without evidence can be dismissed without evidence. Emotion isn’t proof. Data is. Context is. Repetition over time is. Which is why we try not to make snap changes—we look for themes. We cross-check Shadow Board insights with AARs. We match anonymous eNPS feedback with team leads' observations. We ask our team: - Is this a pattern or a one-off? - Are we seeing this from multiple levels, functions, or client types? - Is the signal getting louder over time? Patrick Lencioni calls it out clearly: conflict avoidance kills trust. But knee-jerk leadership kills momentum. The sweet spot is deliberate action—based on trends, not tweets. And even when we do act quickly, we know it can feel sudden to those outside the decision loop. That’s why we apply structured change management: - We share the “why” behind what we’re doing. - We phase in the changes intentionally. - And we reinforce decisions with clarity, not ambiguity—because clarity is kindness. Feedback builds trust—but only if your response is thoughtful, transparent, and earned. Ask. Listen. Look for themes. Weigh. Decide. Act. Communicate. That’s how you close the loop—and build a culture that lasts.

As Summer PD kicks off in many Northeast charters, I’ve been thinking about what it really takes to build a culture of feedback and learning—not just deliver professional development. One thing I learned based on my years as a principal and then supporting principals and leaders in designing professional development is this: A culture of feedback doesn’t start with a protocol. It starts with a habit. One of the most powerful: short, focused reflection surveys. And this isn’t just for summer onboarding. It works any time you're introducing a new initiative, tool, or workflow. But if the goal is learning—not just collecting data—how you use those surveys matters. Whether you're onboarding teachers or leading a change effort on your team, here are three lessons I’ve learned: ✅ Ask better questions. You get the data you ask for. Make sure you ask about both content and format. For content: • What’s one practice you’re excited to try? • What’s still unclear? • Where will you need more support? For format: a quick Keep–Start–Stop works wonders. ✅ Review the feedback as a team. Don’t just collect feedback—process it. Spot patterns, add context from your own observations, and adjust your plan. That might mean reshuffling sessions, re-grouping folks, or offering targeted support. ✅ Close the loop. If you want people to be honest, show them that their feedback matters. Share what you heard and how you’re responding—even if the answer is, “Not yet, and here’s why.” For individual concerns, follow up 1:1. This approach doesn’t just improve your rollout. It models the kind of learning culture we want in every classroom and team. And while I’ve seen this most in schools, these lessons apply anywhere—nonprofits, startups, corporate teams. If you’re leading any kind of team learning experience, these small moves build trust, responsiveness, and real feedback loops. You’ve heard me say it before: clarity is a process, and it’s bidirectional. This is one simple, powerful way to get there. What are your favorite moves or 1% solutions for building a culture of learning?

"Our team is resisting the changes we need to make." I hear this constantly from CEOs navigating market uncertainty. But here's what I've learned building and scaling teams from 0 to 10,000+ people: Resistance isn't about the change itself. It's about how it's managed. Think about it: Most of your strategic planning happens in executive meetings. You develop context and conviction over weeks or months. Then you announce it to the organization... and expect immediate buy-in. That's like jumping into chapter 7 of a book and wondering why readers are confused. After 20+ years helping organizations navigate transitions, here are 5 steps for successful change management: 1. Start earlier than you think Getting buy-in takes time. Begin socializing concepts before decisions are final. 2. Create feedback loops Form cross-functional working groups to pressure test ideas. Let people shape the solution and identify challenges. 3. Overcommunicate context Share the why, not just the what. Help people see the full picture you see. 4. Create working groups beyond the C-suite Form small functional focus groups across levels to pressure test ideas and surface blind spots. Recently, a client's product pivot seemed perfect until a working group flagged major engineering implications that had been missed. 5. Map second and third-order effects That "simple" UI change? It might require new engineering capabilities, additional QA resources, and updated customer support training. Surface and map these downstream impacts before executing. Remember: Your people are your competitive advantage. Bring them along thoughtfully. What change management challenges are you facing? Drop a comment - always happy to help think through solutions.