Learning Developer Playbook

Naming the Monster: Why Identifying Your Fears Is the First Step to Beating Them

Many instructional designers avoid JavaScript not because they lack ability, but because of fear of coding for instructional designers that goes unnamed and unchallenged. This lesson helps you identify the specific fears holding you back—and shows you how to start rewriting those narratives.

By Nathan Stoker · Published Mar 8, 2026 · Updated Apr 18, 2026 · 4 min read

Naming the Monster: Why Identifying Your Fears Is the First Step to Beating Them

Fear Thrives in the Shadows

Here's something I've noticed after years of teaching JavaScript to instructional designers: the thing holding most people back isn't a lack of skill. It's fear. And fear is sneaky—it prefers to stay vague, lurking in the background as a general sense of "I can't" or "This isn't for me."

But fear loses its power the moment you drag it into the light. When you can name exactly what you're afraid of, you've already taken the first step toward moving past it.

So let's do that right now. Below are four common fears that keep people from experimenting with code in their e-learning work.

Which of these resonate with you?

  • The Breakage Fear: "If I add JavaScript, I'll corrupt my course or create errors I can't fix."

  • The Overwhelm Fear: "I don't even know where to begin. JavaScript feels like a completely different universe."

  • The Identity Fear: "I'm a designer, not a developer. Code isn't part of who I am."

  • The Past Failure Fear: "I've tried this before and it went badly. Why would this time be different?"

If you checked one—or all four—you're in good company. These fears are incredibly common. And here's what matters: naming them is the first step toward disarming them.


The Stories We Tell Ourselves

Now let's look at what these fears have in common: none of them are based on facts. They're stories—narratives we've constructed from assumptions, past experiences, and self-doubt.

The Breakage Fear assumes that one mistake will cause irreversible damage. But Storyline has an undo button. You can duplicate slides before experimenting. You can test in Review 360 without touching your source file. The catastrophe you're imagining almost never happens.

The Overwhelm Fear assumes you need to understand everything before you can start. But nobody learns that way. You don't need to master JavaScript—you just need to copy one snippet, see it work, and build from there.

The Identity Fear assumes that "coder" and "designer" are mutually exclusive categories. They're not. The most effective instructional designers I know are the ones who blur those lines. Adding a technical skill doesn't erase your creative identity—it expands it.

The Past Failure Fear assumes that previous struggles predict future outcomes. But what if that failed attempt actually taught you something? What if you're better prepared now than you were then?

These stories feel true because we've repeated them so many times. But feelings aren't facts.


Rewriting the Narrative

The fears we've been discussing share one more thing in common: they're learned. Somewhere along the way, you picked up the belief that coding is risky, or that it's not for people like you. And anything that's learned can be unlearned.

Here's how to start:

Replace "What if I fail?" with "What if I learn something?" Every mistake in code is feedback. It's not a judgment of your worth—it's information about what to try next.

Replace "I'm not a coder" with "I'm someone who's learning to code." Identity isn't fixed. You get to decide who you're becoming, and you can update that story anytime.

Replace "I need to know more before I start" with "I'll figure it out as I go." Action creates clarity. You don't need permission or perfect preparation—you just need to take the first small step.

The goal isn't to eliminate fear entirely. Fear will probably show up every time you try something new. The goal is to stop letting it make your decisions for you.


Your Turn

Before moving to the next lesson, take a moment to identify your primary fear from the list above. Write it down if that helps.

Then ask yourself: What's one small action I could take this week that would prove this fear wrong?

You don't have to answer that question perfectly. You just have to be willing to try.


Nathan Stoker

I build custom eLearning in Storyline, Rise and JavaScript, and I make the free tools and templates on this site. Need an interaction like this in your course? Let's talk.

Work with me · Browse templates

Related posts