The language you use to describe your work is shaping what your organization asks of you. Here’s what happens when you change it.
A prospective client came to me a couple of weeks ago with a straightforward request. He had a newly merged executive team of eight senior leaders, a post-reorganization that had left some unresolved tension, and a question: could I put together some team building?
I said yes. And then I went back and reframed the engagement.
Not because I was being difficult. Because “team building” was the wrong name for what this team actually needed, and the wrong name was going to set the wrong expectations, attract the wrong budget, and produce the wrong outcomes.
What they needed was not a ropes course or a personality quiz or a shared lunch. They needed a two-day executive leadership retreat designed to help eight people stop relitigating the past and start building toward something together. Different name. Different scope. Different investment. Different results.
We ended up calling it exactly that: an Executive Leadership Retreat. And everything changed.
The language we use to describe our work is shaping what our organizations ask of us, what they pay us, and whether they listen when we walk into a meeting.
This Is Not Just a Consulting Story
I share that example because I think about it a lot in the context of in-house L&D work. Not because the stakes are the same, though sometimes they are, but because the dynamic is identical.
How many of us have had a stakeholder come to us asking for “a quick training” and just started building? How many of us have been handed a request framed as “just put together some slides on this” and quietly done exactly that, even when we knew it was not the right solution?
The problem is not that we lack the expertise to push back. We have the expertise. The problem is that we have been operating inside language that positions us as order takers, and order takers do not push back. They deliver.
Here’s what we need to be talking about: the language your organization uses to describe your role is not neutral. It is actively shaping what they expect of you, what they give you budget for, and whether they think to include you in the conversation before a decision gets made.
When your stakeholder describes your work as “making slides,” that framing follows you into every conversation you have with them. When you describe your own work as “building a course,” you are reinforcing it.
Strategic partners do not build courses. They solve performance problems. Sometimes the solution is a course. Sometimes it is not. But that distinction only becomes visible when you are using language that opens the conversation instead of closing it down.
What Changes When You Rename the Work
When I reframed that engagement from “team building” to “Executive Leadership Retreat,” several things shifted at once.
The client’s expectations shifted. An executive retreat carries a different set of assumptions than team building. It implies intentional design, senior-level facilitation, and outcomes that connect to organizational strategy. He was no longer picturing an afternoon activity. He was picturing something that deserved real time and real investment.
The tool selection shifted. Because we were naming it correctly, I could make the right design decisions. For a team in active transition, fresh off a reorganization, still navigating trust breakdowns and communication friction, the standard Five Behaviors Team Assessment was the wrong tool. I switched to the Personal Development Profile instead, which met the team where they actually were rather than where a stable intact team would be. That decision mattered. And it only became available when we stopped pretending this was standard team building.
The scope shifted. We designed a two-day arc: Day 1 focused inward, how each leader works, what they bring, how they are wired. Day 2 focused forward, how the team moves together from this point. That arc does not happen inside a half-day team building session. It happens inside an executive retreat, because that is what we called it.
The investment shifted. Not because I inflated the price, but because the correct framing reflected the correct scope, and the correct scope justified the correct investment.
Strategic partners do not build courses. They solve performance problems. The distinction only becomes visible when you are using language that opens the conversation instead of closing it down.
The In-House Version of This
I know what you might be thinking. That is a consulting engagement. I work inside an organization. I do not get to rename my projects and charge more for them.
Let me push back on that.
You may not control the budget line. But you have more influence over the language than you think. And the language you use in your project briefs, your stakeholder emails, your kickoff meetings, and your project debriefs is quietly building a reputation in either direction.
When you walk into a meeting and say “I built a 20-minute eLearning module on compliance,” you are describing an output. When you walk into a meeting and say “I designed a learning experience to close the compliance gap we identified in the Q1 audit, and here is what I expect to see change,” you are describing a contribution.
Same work. Different language. Different perception.
That shift does not require a new job title. It does not require your organization to suddenly value L&D the way you wish they did. It requires you to make a deliberate choice about how you position and talk about what you do, starting now, in the conversations you are already having.
This Is What July Is About
This month inside #IgniteLearning, we are going deep on exactly this: how to move from being perceived as the person who builds the training to being recognized as the professional who solves the problem.
We will look at what intentional AI use looks like when you are using it to sharpen your strategic communication, not just speed up your content production. We will work through how to translate your learning projects into language that resonates at the stakeholder level. And in the VIP workshop, I will demonstrate the full workflow live using a real course scenario.
The July VIP workshop is called The Language Leadership Listens To: An AI Workflow for Strategic Communication. It runs the week of July 20th. If you want to watch the full demonstration and walk away with a repeatable process you can apply to your own projects, that is where to be.
Ready to stop describing your outputs and start communicating your impact?
Join #IgniteLearning — free 7-day VIP trial. https://zps.circle.so/checkout/ignite-learning
About Dani Watkins
Dani is the founder of #IgniteLearning and the owner of Zenith Performance Solutions. She’s an instructional designer, trainer, and eLearning developer who creates practical resources for in-house L&D professionals. She presents regularly for Training Magazine and believes deeply that good learning design changes outcomes and that the right tools make that possible inside real organizational constraints.