Teaching one instrument at a time would be easier. It also wouldn't be honest.

Ear before notation

Notation is a record of something you already recognize — it's not where recognition starts. Before a chord gets a name or a diagram, you sing it, find it, or play it by ear until it's familiar. Then the written form becomes a shortcut for something you already understand, instead of a code you're decoding from scratch. This is slower in week one and dramatically faster by month three, because you stop needing the page to know what you're playing.

One theory, every instrument

A guitar barre chord, a walking bassline, a ukulele strum pattern, and a chord progression built inside a DAW are the same small set of ideas — intervals, triads, rhythm subdivision — expressed through different hardware. Rather than teaching "guitar theory" and "keyboard theory" and "production theory" as separate subjects, lessons build one shared vocabulary and then show how it maps onto whatever's in your hands that week. Students who study more than one instrument here consistently find the second one easier than the first, because they're not starting over.

Analog habits, digital tools

Synths, drum machines, and DAWs aren't treated as a separate "tech track" bolted onto traditional lessons — they're taught with the same ear-training and theory foundation as voice or guitar. Programming a drum pattern is a rhythm exercise. Shaping a synth patch is an ear-training exercise in disguise. The gear changes; what you're actually learning to hear doesn't.

Something finished, every time

Every lesson is built around producing something you can point to — a recorded take, a finished loop, a song played start to finish without stopping. Technique matters because it's in service of that outcome, not as an abstract exercise. Progress should be something you can hear, not something you have to take on faith.