Background

Code Louisville was a grant-funded workforce development program that used Treehouse's technical curriculum to bring underrepresented communities into software development careers. As Program Manager, my role went beyond curriculum delivery. I was responsible for removing the systemic and psychological barriers that kept talented people from believing they belonged in tech in the first place.

We were building pathways to employment for students who, in many cases, had never seen themselves reflected in the industry they were trying to enter. That context mattered enormously to everything I designed.

Identifying the Need

The need for this workshop didn't come from a spreadsheet. It came from paying attention.

As students moved deeper into the technical curriculum, I noticed a pattern: the energy in the room was shifting. Students who had been engaged and motivated were growing quieter. Conversations about their skills became hedged and self-deprecating. Confidence was eroding in real time, right at the moment when it needed to be building.

When I dug in, the picture became clear. Many of these students were carrying a specific, compounding burden: not only were they learning complex technical skills from scratch, they were doing it while looking nothing like the image of a "typical" junior software developer that the industry had spent decades projecting. The self-doubt wasn't incidental — it was structural. And it had a name: imposter syndrome.

That observation became my needs analysis. The gap wasn't technical. It was psychological — and it was threatening to undo the hard work students had already done.

Learning Objectives

Before designing the session, I grounded it in three clear outcomes. By the end of the workshop, students would be able to:

• Recognize imposter syndrome: understand what it is, why it happens, and who it disproportionately affects

• Reframe their experience: see their self-doubt not as evidence of inadequacy, but as a nearly universal response to growth and underrepresentation

• Apply at least one concrete strategy for managing imposter syndrome when it surfaces in their careers

The third objective was the most important. Awareness without action is just discomfort with better vocabulary. I wanted students to leave with something they could actually use.

Design & Delivery

The workshop was structured in two deliberate halves, and the sequence was intentional.

The first half was personal. I opened by sharing my own story, drawing directly from a blog post I had written called Slaying the Dragon: Imposter Syndrome — an account of my own struggles with self-doubt and the moments I almost talked myself out of opportunities I deserved. Starting there wasn't just a warm-up. It was a strategic choice rooted in adult learning theory: before people can absorb new information, they need to feel safe enough to be honest about where they actually are. Modeling vulnerability first created the conditions for everything that followed.

From there, I walked through the psychology behind the term: what imposter syndrome is, why high achievers are especially susceptible, and why the effect is amplified for people who don't see themselves represented in their field. I wanted students to understand that their self-doubt wasn't a personal failing. It was a predictable response to a system that hadn't been built with them in mind. That reframe, for many students, was visibly powerful.

The second half shifted from understanding to action. I shared the strategies I'd found most effective: practical, honest approaches that didn't require pretending the doubt would disappear entirely. Then I opened the floor.

What happened in those discussions was the part no slide deck could have planned for. Students who had been quietly carrying their self-doubt began naming it out loud, sometimes for the first time. They heard themselves reflected in each other's experiences. The room became something rare: a space where a group of people preparing to enter a notoriously gatekept industry could be honest about how hard that felt, and leave feeling less alone in it.

Outcomes

This session became a consistent part of my repertoire. Not because it was on a checklist, but because it worked. Facilitated across multiple cohorts and audience compositions, the workshop reliably generated the kind of engaged, vulnerable conversation that signals genuine psychological safety. Learners routinely cited it as a turning point in how they thought about their place in tech and in the world.

More than a training session, it was an act of intentional program design: meeting learners where they were, addressing a barrier that traditional curricula ignore, and trusting that emotional readiness is just as foundational to career success as technical skill.