When “Interoperability” Killed My Presentation

There’s a moment I still think about.

I was standing in front of our school board.

Slides ready. Data polished. Language precise. Huge, impactful initiative ready to share.

I said the word interoperability, and I watched the room go still.

Not confused. Disconnected.

In that moment, I realized something uncomfortable:

It wasn’t that they disagreed with me. It was that they didn’t understand me.

And if they don’t understand it, they won’t support it.

The Word That Killed the Room

I was technically correct. Interoperability matters enormously; it touches data quality, AI readiness, instructional visibility, student transitions, reporting accuracy. The stakes were significant.

But I forgot something critical:

Leaders don’t fund vocabulary. They fund outcomes.

I was speaking fluent systems. They were listening for impact.

That gap? That’s where good initiatives quietly die while everyone nods.

What I Changed

The next time I presented, I didn’t say interoperability.

I said: “It’s like making sure your child’s doctor, teacher, and coach can all see the same chart, instead of keeping notes in three different notebooks.”

The room shifted.

Now we weren’t talking about a standard. We were talking about children.

And in that moment, something clicked for me.

My real job wasn’t CTO. It was Chief Translator.

Translation isn’t a communication skill you layer on top of expertise. It’s the job itself. It’s what makes everything else possible.

When we later reframed our data integration work around student mobility and instructional continuity (instead of backend architecture), board approval moved from hesitation to unanimous support.

Same work. Different translation.

Translation Is Not Simplification

Here’s where most districts get it wrong.

When initiatives stall, AI rollout, data governance, cybersecurity, SIS migrations, the instinct is to explain more. More slides. More detail. More documentation.

But MORE explanation isn’t the answer. Explaining things clearly, in terms the listeners understand, is what moves Innovation forward.

And there’s a real difference.

Simplification talks down to people. Translation meets them where they are.

Real translation means knowing what your board member is actually worried about when they go quiet.

It means understanding that a parent asking, “Is this safe?” isn’t asking about your security architecture; they’re asking whether you see their child as a person worth protecting.

It means removing your ego from your expertise long enough to ask: What does this mean for the person sitting across from me?

Their job is to protect children and resources, and ours is to make sure they can see that our work is doing exactly that.

Why the AI Era Makes This Urgent

This has always mattered, but AI has accelerated the stakes.

We’re throwing around hallucinations, LLMs, data lakes, guardrails, bias mitigation…and while we’re doing that, boards and communities are sitting with four simpler, heavier questions:

If we answer the vocabulary questions instead of those human questions, we don’t just miss the moment. We erode trust. And once trust erodes, it doesn’t come back quickly.

I’ve watched well-funded, technically sound AI implementations stall not because the strategy was flawed, but because the board and community were never brought into the story.

The tool wasn’t the problem. The translation gap was.

Trust is the real infrastructure. Everything else, including the next Innovation, runs on top of it.

This Is What Chapter 7 Is About

When I wrote Chapter 7 of Capes Optional, Communication Essential, I kept coming back to one tension I’d felt throughout my career:

The leaders doing the most important work were often the least understood. They weren’t hiding. They just never were taught that making their work understood was part of the work.

And visibility isn’t volume. It isn’t more announcements or bigger newsletters.

It’s translation. It’s making sure the people who fund, govern, and experience your decisions can actually see why they matter.

Because when we hide behind jargon (even unintentionally) we hide impact. And when people can’t see the impact, they can’t protect it, fund it, or fight for it when things get hard and funds are scarce.

An Invitation for This Week

This week I’m delivering a webinar that expands on this topic, and I would love for you to join me and the EdTech Leaders Alliance for a free lunch time deep-dive into the Chief Translator Playbook.

Translation is a non-negotiable, and leaders must translate complexity into confidence, especially right now, when the technology landscape is moving faster than most communication strategies.

If you’ve ever watched a board go quiet in the wrong way… If you’ve ever felt technically right but strategically off… If you’re rolling out AI, data systems, or major change this year and you want people to actually get it…

This session is for you.

For Leadership Teams Navigating This Now

For districts currently in the middle of high-stakes AI implementation or major system alignment work, I’m opening two small strategy intensives this spring focused specifically on trust-first rollout.

These are hands-on working sessions for leadership teams who want board alignment and community confidence before friction sets in.

If that’s you, feel free to message me and I’ll share details.

The Room Was Always the Point

The day “interoperability” killed my presentation was the day I became a better leader.

I walked back to my office, opened my laptop, and rewrote the entire deck. Not because the content was wrong, but because I finally understood that being right wasn’t enough.

Being understood was the work.

Because when they don’t understand it, they won’t support it.

And when they won’t support it, it won’t matter how right you were.

The room was always the point. I just had to learn to speak for it.