What a music-education degree actually transferred to IT leadership (and what it didn't)

I get asked about my career arc a lot. People want to know how a music-education major ends up running a Network, Cybersecurity, and Cloud department at a community college, with a stop in between leading a team responsible for a $40M technical training portfolio at VMware. The honest answer is harder than the version people want to hear.

The popular version of this story is the inspirational one — “music teaches discipline, and discipline transfers!” That story is mostly empty calories. Here’s the actual list, with the things that transferred specifically and the one thing that conspicuously did not.

What transferred

1. Performance fluency.

In a choir or a recital, you don’t get to pause, look something up, and resume. You play through the mistake. You’re on, in real time, with people watching. Then you do it again the next day.

That experience — making something real in front of an audience, repeatedly, without a safety net — is the closest thing I’ve had to enterprise technical training. When you walk into a room with twenty Carbon Black engineers and have to deliver a five-day course at a 4.95 average rating, you cannot pause. You play through it. Music ed gives you ten thousand hours of that muscle before you ever stand in front of an engineer.

2. The teacher-as-conductor model.

A conductor’s actual job is not to wave a stick. It’s to listen to thirty people simultaneously, decide which one needs attention right now, and give them what they need without breaking the music for the other twenty-nine. That’s also instructional team leadership. That’s also department chairing. You’re managing parallel work products, all in different states, by different people, with different needs, all of which somehow have to converge.

Music ed gave me a default mental model for this. I picked it up before I had any vocabulary for “matrix management.”

3. Rehearsal is the work.

Performance is the artifact. Rehearsal is the work. Most of what happens — the diagnosis, the iteration, the unglamorous tightening of difficult passages — is invisible by the time anyone watches the show.

In instructional design, the deployed course is the artifact. The work is the SME conversations, the revisions, the disagreements about scope, the late drafts. People who come into ID expecting that “designing courses” means writing courses are routinely disoriented. They thought the performance was the work.

4. Ear training.

You learn, over years, to hear what is actually happening — not what is supposed to be happening. You hear that the tenors are flat. You hear that the second flute is half a beat behind. You hear the things the score doesn’t say.

In ID and in department leadership, the analogous skill is listening to people. You hear that the SME is hand-waving on a topic they don’t actually understand. You hear that “I’m fine” is the start of a different sentence. You hear the gap between what the curriculum says it teaches and what it actually teaches. This is, I think, the most under-credited thing music ed gives you.

What didn’t transfer

Technical depth.

No amount of music theory prepares you for routing tables or vCenter clusters or RAG pipelines. The transferable skills above let me move fast through new technical domains — but the actual depth had to be earned, one cert and one production incident at a time.

The first three years of my career past music school were spent quietly catching up on the technical foundation I didn’t have. Nobody could tell from the outside, because the performance fluency and the listening were already there. But internally, I was always carrying around a small list of things I’d been pretending to know.

There is no shortcut for this. The people who try to substitute confidence for actual technical fluency get found out in production. The only way through is the actual work.

The bigger point

Career changes work when you take what’s actually portable, not what you wish were portable. Music ed didn’t teach me IT. It taught me how to perform live, how to manage parallel work, how to do unglamorous iteration, and how to listen. Those things matter every day in IT leadership. The IT itself, I had to learn.

If you’re considering a career pivot — your own or someone on your team — the useful question is not “is this person’s background relevant?” The useful question is: “What did their background teach them to do reflexively, and is that still useful here?” The honest answer is sometimes “no.” More often than you’d guess, it’s “yes, in ways neither of us would have predicted.”