My friend and I did the math on the back of a napkin.
We weren’t trying to cause trouble. We were sitting in the back of a faculty meeting, listening to our administration leaders casually mention that our workday would be extended by 30 minutes, effective immediately.
Thirty minutes a day. Times the number of school days in a year. We looked at each other across the table. Ninety hours. Eleven extra days. More than two additional weeks of work, announced like a scheduling note.
I raised my hand.
My friend and I had developed a reputation. Rabble-rousers. Skeptics. The ones who asked uncomfortable questions, said the quiet part out loud, highlighted the fine print. True, some people sighed and rolled their eyes whenever our hands went up. We were, after all, committing the ultimate faculty meeting sin: making it longer. Yet, after the meetings, other people found us in hallways and told us: “Someone needed to say that,” “You were asking exactly what I was thinking,” or “I wanted to say that, too, but I was scared.”
We weren’t the problem. We were the diagnostic. Every concern we carried into the faculty room was a signal the institution needed to hear. It took me time to understand that role for what it was: not disruption, but translation.
A former boss once described me as the voice of the voiceless. I didn’t fully understand what she meant then. I do now. The skeptic in the room isn’t there to derail the meeting. She is there to translate what others are feeling but can’t say aloud. She asks the question that sharpens ideas, names the flaws, and protects the people who can’t speak for themselves.
What Happens When Someone Listens?
I began to see that dynamic most clearly in the moments when a single hard question changed what happened next.
Years ago, our learning management system (LMS) went bankrupt in July, and leadership quickly replaced it with a more robust system that we were expected to use by August. I raised my hand and asked, “Who is going to train us?” That question led to action. I was one of three faculty members sent to the new LMS company’s summer conference, and when we returned, we formed a task force to create naming conventions and standardized layouts that would make the system easier for students and caregivers to navigate. By spring, we were training the rest of the faculty, saving everyone time and stress before the school year began. Leadership listened, teachers stepped up, and together we built a system that worked. People are more likely to embrace what they help create.
I saw that same pattern play out at another school. I raised my hand and asked why we were bringing in an outside group to lead lengthy professional development on teaching. Was this in response to a perceived deficiency? Why not learn from the master educators with invaluable institutional knowledge already on our campus? That question sparked a different approach of building an EdCamp centered around the expertise of our own faculty. It became a regular model for our end-of-year PD: a celebration of the fantastic teaching within our campus. In fact, I’ve had the pleasure of spreading such grassroots PD to two different schools.
Over time, I have also learned what it feels like to be on the receiving end of these kinds of questions. During a consulting visit at another school, a teacher told me she didn’t want screens in her early childhood classroom. No Chromebooks, no iPads. No devices. Not yet. I was there to help faculty experiment with new AI tools, and I’ll admit that my first reaction was defensive. I heard her concern as resistance to the work I had come to do. But the more I listened, the more I understood that she wasn’t rejecting the future. She was asking us to define readiness more carefully.
Her pushback shifted the conversation from “How do we introduce young children to technology?” to “What foundations do young children need before technology becomes useful?” Together, we began thinking about the tactile, relational, analog experiences that help children build curiosity, judgment, language, and connection—the very capacities that will make technology meaningful when they encounter it later. She was not the obstacle to innovation. She was the reason the innovation became more thoughtful.
Creating Conditions for the Tough Conversations
The teacher who raises her hand, who asks the tough question, who says wait when everyone else is moving? She is not an obstacle. She is a flashlight. She is shining the light on something the room needs to see.
When we create conditions where hard questions are truly heard, something shifts. Concerns passed secretly from hand to hand become essential conversations, which then lead to growth.
When she’s tolerated but not heard, managed but not valued, the cost is real and it compounds. The ones who can leave, leave.
The ones who can’t leave often become discouraged. Over time, some burn out. Ambition, drive, and searching for solutions turn to stale apathy. Everyone stops raising their hands. And the institution loses.
My friend and I left that first school. Most of us did, eventually.
I think about that today when someone’s hand goes up in that particular way that says, “You’re not going to like this, but I have to ask.”
In the moment, I’m not always happy to be on the receiving end of tough questions. I won’t pretend it feels good when someone challenges the plan I thought was settled or exposes something I didn’t see. But I make myself remember what it means: This person cares enough to do the math on a napkin and ask the question out loud for those who cannot.
The skeptic in the room is not a problem to manage. She has a superpower worth championing.