To the Instructional Designers Getting Beat Down at Work

There is a kind of exhaustion that comes from being an instructional designer in the wrong learning culture, and it is not the kind that shows up on your calendar. It is quieter than workload, deeper than deadlines, and harder to explain to anyone outside the profession. It comes from sitting in meeting after meeting where you can see the real problem clearly, you can see the path to a better solution clearly, and you can feel your own experience and judgment trying to do its job. Then someone walks in, already decided, already attached to a solution, and the conversation becomes a performance where your role is not to help diagnose or improve anything. Your role is to confirm their thinking and build whatever they already picked.

That is the beatdown. Not because the work is beneath you, but because you know what you are capable of. You know you can reduce errors, shorten ramp time, influence behavior, and make systems easier to use. You know you can design something that actually changes what people do at work. Yet you are forced into a pattern where stakeholders treat you like their personal consultant when they want validation, and like an order taker when they want output. It is a strange, demoralizing double bind, because it disguises control as collaboration. They will say they want partnership, but what they actually want is compliance dressed up in meetings and feedback cycles.

I cannot count how many times I have walked into a conversation and realized the decision had already been made before I ever joined. The course has already been named. The format has already been chosen. The “must include” list is already drafted. Sometimes the stakeholder even has a template and a vision for what the screen should look like. If you ask the kinds of questions that any real performance professional would ask, like what the real business outcome is, what is happening now, what barriers are in the environment, what leaders will do differently, or why this is happening in the first place, you can feel the temperature change. The questions are treated as resistance. Curiosity is treated as delay. Competence is treated as inconvenience.

What makes it worse is when management and leadership enable it. Not always intentionally, but through silence. When leaders do not protect discovery time, do not reinforce a real intake process, and do not educate stakeholders on what learning is and is not, the system teaches the organization that L&D is simply a service counter. In that kind of environment, you end up doing work you know will not move the needle, and then you watch the organization blame training when nothing changes. It is not just frustrating, it is identity eroding. You start to feel like you are becoming someone who produces content instead of someone who solves problems.

Over time, I started noticing that most organizations fall into the same few learning culture types. Very few companies are perfectly one thing, but you can usually tell what the dominant culture is by what gets rewarded, what gets funded, and how decisions are made. Naming these cultures helped me stop personalizing the friction. It helped me see that in many cases, the problem was not my capability or my communication style. The problem was the system I was operating inside.

The four learning culture types most organizations fall into

1) Order Taker Culture (the most common)

In an order taker culture, learning teams exist primarily to produce. The organization treats L&D as a production function, not a performance function. Requests arrive as predetermined solutions, not as problems to explore. “Make training for this” is the default response to almost everything. “We need a deck” becomes a strategy. “Turn this document into eLearning” becomes a plan. Instructional design best practices are allowed only if they do not slow anything down or challenge anyone’s preferences.

The signs are usually obvious once you have lived it. There is little or no formal intake process, discovery is minimal, stakeholders dictate delivery methods, and feedback is opinion based rather than outcome based. The learning team spends a lot of time making revisions that are not tied to performance impact, and you can feel yourself being pulled into a cycle where your job becomes pleasing the requester. In that world, the only way to “succeed” is to build what is asked, keep your head down, and get good at producing fast. But there is a cost. Your expertise is underused, your growth stalls, and the work starts to feel like treadmill output with no real agency.

2) Internal Consultant Culture

On paper, this one sounds healthier. It is the culture where learning is expected to operate like a consulting function. Stakeholders want learning experts to diagnose performance problems, recommend solutions, influence behavior change, and operate upstream. The language sounds right. The intent sounds strategic. But this culture can turn toxic quickly when the organization wants consulting outcomes without granting consulting authority.

This is where the beatdown can feel the strongest, because the gap between expectations and reality is brutal. You are invited into the room to be the expert, but you are not supported as the expert. Stakeholders want you to “consult,” but they also want to control the outcome, the format, and the narrative. They want your credibility, but not your boundaries. They want your insight, but not your inconvenient questions. Often this shows up in organizations that historically used external consultants. Leaders will say things like, “consultants used to do this,” while simultaneously treating internal L&D like a service function. That transition is messy, and if leadership does not actively protect the internal learning role, the consultant culture becomes a fancy label for the same old behavior: smile, nod, and build it.

3) Compliance Factory

In a compliance factory, learning exists primarily for regulatory requirements, certifications, mandatory programs, and audit readiness. The dominant metrics are completion rates, tracking, and documentation. The learning team becomes operationally focused, and the organization values reliability over innovation. In many places, this is necessary work and it protects the organization from real risk. The problem is that compliance work often crowds out deeper performance conversations, because the system is structured around proving training happened, not proving work improved.

Instructional designers can survive here, and some can even thrive if they enjoy building clean systems and scalable structures. But for designers wired toward performance consulting, it can feel like you are endlessly processing content rather than solving root causes. You start to feel like your creativity and judgment are wasted on packaging information rather than changing behavior. It is not that compliance learning is unimportant. It is that when everything becomes compliance, the organization forgets what learning could be.

4) Capability Builder (the healthy one)

This is the culture where learning is viewed as capability development, not content production. A capability builder culture treats learning as a long game investment in how the organization performs. It values discovery before design. It expects stakeholders to co-own outcomes, not just request deliverables. It understands that training is only one lever among many, and it supports solutions that combine learning, performance support, coaching, tools, process changes, and reinforcement.

In this environment, instructional designers are not treated like slide builders. They are treated like professionals. They are expected to ask hard questions, and leaders back them when those questions are inconvenient. There is usually some kind of intake process. There is agreement on what success looks like. There is a willingness to say “this is not a training problem.” And because of that, senior instructional designers can actually grow into the role everyone claims they want: a true performance partner who helps the organization build competence, not just content.

The hard truth most people do not say out loud

Two of these cultures often require you to become an order taker in order to survive. The first is obvious: the order taker culture itself. If the system is built around production, you will be rewarded for compliance and punished for pushing upstream. The second is more painful: the internal consultant culture when leadership does not support it. That environment can be emotionally exhausting because it dangles strategy in front of you while denying you the conditions needed to do strategic work. You are expected to “act like a consultant,” but treated like a vendor. You are asked to “partner,” but managed through control.

In both cases, the quickest way to stop feeling pain is to stop trying. You stop challenging assumptions. You stop pushing for discovery. You stop offering alternatives. You learn to deliver what is asked and move on. That might protect you in the short term, but it is not growth. It is erosion. Over time, it takes a toll on your confidence, your motivation, and your sense of purpose. You do not leave work tired because you worked hard. You leave tired because you had to suppress the best parts of your professional brain all day.

What you can do if this sounds familiar

The first thing is to name the culture, at least privately, so you stop internalizing it. If you cannot name it, you will assume you are the problem. You are not. The second thing is to test whether the culture is flexible or fixed by making one small boundary move. That can look like a simple requirement: “Before I build anything, I need a short discovery conversation to clarify the outcome, the audience, and what leaders want to see change.” Or it can look like offering two options: “I can build the course you requested, and I can also propose a lighter performance support option that may solve this faster.” Pay attention to what happens next. Healthy cultures will engage. Unhealthy ones will punish the attempt.

The most important variable is leadership behavior. Not leadership slogans, not leadership values posted on walls, but leadership behavior in the moment when stakeholders try to control the work. If your manager consistently avoids conflict, caves to pressure, or sends you back into the stakeholder grinder without protection, you are being set up to absorb the damage. It is not noble. It is not a rite of passage. It is a system that burns people out and then acts surprised when they leave.

When it might be time to move on

Not every learning culture can be changed from inside, and staying too long in a wear down environment can change you in ways you do not notice until later. It might be time to move on if you are repeatedly pulled into projects after decisions are already made, if stakeholders treat your questions as an obstacle, if every project becomes revision hell driven by opinions, and if you realize that your best strategy for survival is to stop caring. That is the red flag. When the only way to succeed is to become an order taker, the organization is telling you exactly what it values, and it is not your expertise.

There are no perfect organizations. I have never seen the perfect one. But there are healthier ones, and there are cultures where L&D is allowed to do real work. If you are in a culture that requires you to shrink, you do not owe it your best years. You owe yourself a place where your ability to help is not treated like an inconvenience.

Healthy cultures get curious. Unhealthy cultures get critical. That “this is weird” review comment is not about your work. It is the moment the culture tells on itself.

When they criticize the thing they forced you to create, that is not feedback. That is culture.

Mark Livelsberger, M.A.

Founder | Live Learning & Media LLC