I've lost count of how many times I've walked out of a stakeholder meeting thinking I nailed the explanation, only to get feedback later that I "made it too complicated" or "lost people in the weeds." For years, I bristled at this. I wasn't being unclear—I was being precise. These concepts matter. The nuance matters.

Except... it doesn't. Not in the way I thought it did.

Here's what I've learned the hard way: My job as an education leader isn't to demonstrate the depth of my expertise. It's to enable people without that expertise to collaborate effectively on building better customer learning experiences.

When you live and breathe learning science, when you've spent years understanding cognitive load theory, Bloom's taxonomy, spaced repetition, and scaffolding, it becomes your native language. You see the world through these frameworks. They're not jargon to you—they're precise tools that describe real phenomena.

But to your cross-functional partners—to the product manager trying to understand why your onboarding redesign matters, to the marketing leader evaluating your content strategy, to the executive reviewing your quarterly business case—these concepts create distance, not clarity.

I used to think simplifying meant reducing my knowledge, having to sound less smart. That if I removed the theoretical foundation, I'd lose credibility. That speaking in "business language" instead of "educational terminology" meant compromising the integrity of the work.

I was wrong.

Simplification isn't about making your ideas less sophisticated. It's about making them more accessible to people who need to act on them.

When I explain cognitive load theory by saying "people can only hold so much in their working memory at once, so we need to sequence information carefully," I'm being academically accurate. I'm also creating a barrier to collaboration.

When I say "if we throw too much at users at once, they'll retain nothing and feel overwhelmed, so we're breaking this into three separate touchpoints," I'm describing the same concept. But now my product counterpart can actually engage with the decision we need to make together, rather than first having to decode the framework I'm using.

The depth is still there. The expertise still informs the recommendation. But I've translated it into language that enables my collaborators to do their jobs effectively alongside me.

Here's what happens when education leaders stay in expert mode:

Decision-making slows down. Stakeholders can't evaluate trade-offs they don't understand, so they either defer entirely to your judgment (creating a bottleneck) or make decisions without fully grasping the implications.

You get excluded from strategic conversations. If people consistently leave meetings with you feeling confused, they'll stop inviting you to the table. They'll make decisions about learning strategy without the learning expert in the room.

Your recommendations get watered down. When stakeholders don't understand why your approach matters, they'll push for shortcuts or compromises that undermine the effectiveness of your work. You end up implementing half-measures that don't deliver results.

You burn political capital. Every time someone has to ask you to explain yourself more simply, you're spending relationship currency. Eventually, you'll be seen as the person who makes everything harder than it needs to be.

I've experienced all of these. Multiple times. Across different organizations.

Test your explanations with non-experts before high-stakes conversations. Find someone outside your field—a partner, a friend in a different industry, a team member without education background—and practice your key points with them. If they can't explain the concept back to you in their own words, you haven't simplified enough. This isn't about rehearsing a script; it's about pressure-testing whether your framing actually lands.

Lead with the business outcome, then work backward. Start with the problem your stakeholders already understand and care about: support ticket volume, time-to-value, user drop-off rates, expansion revenue. Then explain your solution in terms of how it addresses that specific outcome. The learning science frameworks come in when someone asks how you'll achieve it, not as your opening position. This reframes you from "education expert with ideas" to "problem-solver with relevant expertise."

Replace frameworks with concrete examples. Instead of discussing scaffolding principles or learning taxonomies, walk through the actual user experience. Show the before and after. Describe what the user does, what they learn, what they can accomplish as a result. Abstract concepts make people work to understand you; specific scenarios invite them into the solution with you.

Separate the decision from the methodology. Your stakeholders need to decide whether to invest resources in solving a learning problem. They don't need to approve your instructional design methodology or pedagogical approach. Focus your explanations on what you're solving, what success looks like, and what you need from them. Save the "how you'll design it" details for when they're directly relevant to the decision at hand.

Match depth to audience need. Your Customer Education team needs the full theoretical discussion. Your instructional designers need to understand the pedagogical foundation. Your cross-functional partners need just enough to collaborate effectively—usually the business case, the high-level approach, and the specific asks you have of them. This isn't about hiding your expertise; it's about respecting that different collaborators need different information to do their part well.

The better you get at simplifying your expertise, the more your expertise will be valued.

When you make complex concepts accessible, stakeholders can actually engage with the substance of your recommendations. They can ask better questions. They can identify genuine constraints or opportunities you might have missed. They can champion your work to their teams in language that resonates.

Most importantly, they can see you as a strategic partner rather than a specialist they consult when needed.

This doesn't mean abandoning rigor. It doesn't mean compromising on what works. It means recognizing that your deep knowledge is most powerful when it enables collaboration, not when it creates dependency or confusion.

I'm still learning this. I still catch myself over-explaining, still get feedback that I've gone too deep too fast. But I'm getting better at recognizing that when someone asks me to simplify, they're not questioning my expertise—they're asking me to be a more effective partner.

And that's a fair ask.

Learning by Design is written by Courtney Sembler. Courtney currently helps companies build scalable customer education programs. After spending over a decade scaling HubSpot Academy globally, she now explores the systems, strategies, and realities of workplace learning, leadership, and customer experience—the kind that drives retention, adoption, and revenue by design, not by accident. Published twice weekly with monthly deep dives. Connect with her on LinkedIn and subscribe to Learning by Design.