Was Comprehensible Input a Lie? What It Actually Does for You

You've put hundreds of hours into comprehensible input. Maybe a hundred, maybe 200, maybe 500. And you're not where you thought you'd be by now, so a quiet suspicion has crept in. Maybe you were sold a lie.

Half the people out there say input absolutely works. The other half say it's absolute nonsense and you need other things.

This is the written version of a video where I break down what comprehensible input really is, what it isn't, and what it should be. And if part of you is wondering whether there's some trick to getting fluent quickly that everyone else found and you missed, hold that thought. I'll get to it near the end.

Does comprehensible input work? Wrong question

Right out of the gate, there's an idea we need to throw away: "comprehensible input doesn't work."

It's way too broad a statement. Doesn't work for what? For getting people interested? For getting someone completely fluent from zero?

One thing we always have to consider: you learned your first language through comprehensible input. You understood messages, and those messages were paired with sounds, and over time the two stuck together. Someone put a thing on their head, you understood it was a hat, and when you heard the word "hat" you paired it with that thing.

So does it work? Of course it works. The real question is: work for what?

Audit the hours before you judge the method

Before we even get into the method itself, back up and look at your hours.

Are they going to the right content? Is it too hard? Are you actually sticking to it? Are you paying attention, or are you scrolling the whole time it's playing?

What you call comprehensible input: is that what I call comprehensible input? Maybe, maybe not.

Here's what I mean. My phone is put away. I'm not eating. I've got my headphones on and I'm paying attention to content that's pretty much at my level. And I do it at a time of day where there's basically no chance of something distracting me, so I can sit down for an hour, or two, or three, or ten, and just do it.

If your hours look different from that, that's the first place to look. Not at the method.

What comprehensible input actually is: the mute test

Comprehensible input just means you understand the messages you're consuming. Not necessarily through your ears, and not necessarily word by word.

People ask me all the time: what if I don't understand a single word? It's not about the words. It's about the message.

If I point at something on camera, you could mute the video and still know what I'm pointing at. It doesn't matter what language I'm speaking, or whether there's any sound at all.

That gives you a simple test. If you can mute the screen and still describe to a friend what you just watched, that's perfect comprehensible input content, especially for a beginner. The message was comprehensible. And over time, your brain will pair what it's hearing with what it's seeing.

It's the engine, maybe the fuel, and fuel on the ground goes nowhere

So where does input sit in the whole system?

If you took a car and pulled it apart, I think comprehensible input is the engine. It's the thing that propels you forward and it's responsible for most of the motion.

Actually, it might be even more fundamental than the engine. It might be the fuel that goes into the engine.

That's where the analogy ends, because I'm not a car person. But I do understand languages.

So the question remains. If you spend hundreds of hours on input with none of the other pieces, are you wasting your time?

Well, if you poured engine fuel on the ground, would you move forward? No, you wouldn't.

The fuel needs other pieces to give it direction and then speed.

Flashcards are comprehensible input on steroids

You may have heard me say this before. I like to put high frequency vocabulary up front.

It's one of the highest return on investment things you can do when you're first starting. You're going to run into these words constantly, so you may as well have them in your head, ready to go, before you sit down with the content. Then you're not relying strictly on what you see on screen.

Say I give you the sentence "I ate a blank for breakfast." You already know I'm probably not talking about a swimming pool. Now a banana pops up on screen, and you're not just leaning on the picture. You've got all the words for eating and breakfast around it, every one of them pointing at the meaning: banana.

And it keeps working like this as you keep drilling new flashcards. The vocabulary is kindling, firewood you're laying on the ground. Comprehensible input is the fuel. Light them together and you get a fire, and slowly that fire burns bigger and hotter.

In my opinion, flashcards are basically comprehensible input on steroids, because you're giving your brain more ways to make the content comprehensible.

It's not one hour plus two hours equals three hours. The hour you spend on flashcards changes the two hours you spend on input, and turns those two hours into maybe three, or four, or five. Every hour is worth more because your brain has more to work with.

The gym mirror problem

I had a call the other day with one of my students inside Fluency Formula Pro. His main concern was that he didn't feel like he was moving forward.

Granted, he'd only done about 60 to 80 hours. He hadn't hit a meaningful amount of time yet. The analogy I gave him reinvigorated his trust, and it might help you too.

Imagine you went to the gym for a couple of weeks, then looked in the mirror and asked why you're not making progress. You'd see absolutely zero change. And you'd conclude the gym obviously isn't helping.

But go for a year or two and you'd see it. You'd look in the mirror and know you're different from when you started.

If every one of those sessions was genuinely worth zero, adding them all up couldn't amount to anything. That makes no sense.

So every session has to be worth something. It's just that you might need a certain critical mass of it before you can look back and realize, oh, this was working the whole time. Even if the first week, or two weeks, or the whole first month showed you nothing visible.

A thousand dirt roads at once

So, does comprehensible input get you fluent?

When I say fluency, I mean conversational fluency: that ping-ponging back and forth between speaker and listener, where you can respond in real time without needing to search and translate in your head. Not that you never translate, just that most of it, coming in and going out, is automated.

Here's how I picture it. Every element of a language (vocabulary, grammar, intonation, tones, accent) breaks down into thousands of little things. Each one is like a dirt road.

The first time you walk it, it's just dirt. Hard to travel. But on the way back you can step in your own footprints. Back and forth, back and forth, and eventually it gets so easy to travel that it turns into an actual road.

What comprehensible input lets you do, even though it can feel slow at first, is walk a huge number of those roads at once. Instead of having two legs, it's like you've got a thousand legs, walking across all of these elements back and forth.

And once a road gets smooth enough, something interesting happens. Your brain automates it backwards.

Here's the concept of a hat. In French I say chapeau. Over time you pair the two. When that pairing gets automated enough, it can run the other direction: the concept and the word are so close that they show up at the same moment. As the concept arises, so does the word.

So, have you been lied to? No. It works for smoothing those roads and gradually automating them, more and more.

Knowing a word and saying it are two different roads

There's one caveat I've mentioned in a few of my videos. Speaking is its own skill.

The spoken language brings in some new elements: actual muscle mechanics, switching from one tone to another, one sound to another.

A word a lot of people have trouble with in Chinese is 学生 (xuésheng), which means "student." Switching from that X sound to the S sound is really hard.

I had the concept of "student" for a long time. It was one of the earliest words I ever learned through flashcards. But being able to say it? That's actually quite advanced. Maybe you're just gifted. For me, it took a while. For lots of the students I've worked with in Mandarin, it took a while too.

So that's a skill you'll need to train. But the piece that largely gets taken care of, if you've done enough comprehensible input, is the concept piece.

And that's exactly what a lot of other methods miss, like the 1000 sentence method. You're repeating sentences and trying to remember what they mean in English, but you're not automating concepts. You're not putting yourself in the spontaneity a real conversation demands, where you don't know what the other person is about to say and you have to respond anyway.

Where I've landed on comprehensible input

If it feels like input isn't working, here are the conclusions I've drawn.

"A lot" is relative. When I say I do a lot of input, is that the same as you? Someone used to 10 minutes a day might think an hour is a huge amount. So first, ask what your hours really look like.

Languages are different. If you're an English native speaker doing Japanese, it's going to take you longer than Italian. Harder languages can take a lot, a lot, a lot of time.

Input's main value is walking those roads and automating the concepts. It won't automatically turn into your ability to say them, although sometimes it can. Especially in a language with sounds your mother tongue doesn't have, you'll need some intentional work on top. And when I say some, I mean a lot.

Input works, and it can be sped up. The way I'd do it is high frequency vocabulary stuffed at the very beginning of the whole approach.

The time is going to pass anyway. A thousand hours from now, it'll be a thousand hours from now, whether or not you decide to fill them with some input here and there.

Maybe there are faster methods. I don't know every method on the planet. But I can tell you that the benefit of comprehensible input is mostly recognized in retrospect. You look back and realize you understand it all, and once you've drilled getting the words out of your mouth, you can produce it too. That's when you see what it did for you, because it walked thousands of dirt roads at once.

And the methods promising a language in 10 days, or 15, or 30? For the most part, that's nonsense.

That's where the "it doesn't work" feeling comes from: cognitive dissonance between the idea that you can go super quickly and the reality that input takes time. Strip out the false beliefs and you find the language was always going to take time.

So is there a way of getting fluent quickly?

I have seen it happen fast. I've had students in my program go from zero to conversational fluency in a couple of months.

But I'm not going to lie to you and tell you they were doing an hour a day. They weren't. They were treating it like a full-time job and showing up for overtime. And they were using comprehensible input along with some other important pieces, of course.

So if you came here asking how to get fluent fast, that's my honest answer. Words up front, input at your level, hours that are actually hours, and intentional work on the speaking. Then enough time for it to add up.

Keep going

The time is going to pass either way.

So keep going. At the very least, keep input as part of your study method. If it's not the whole thing, that's up to you. I'm not here to tell you how to live your life. But it's super valuable, and it should be a big part of your car, whether you call it the engine, the fuel, or whatever part makes sense to you.

If you'd rather hear me talk it through, watch this on YouTube: Was Comprehensible Input a Lie?

And if you want to see how all of these pieces fit together into one path, Fluency Formula is where I lay out the whole car.