Hi, this is Ray.

I want to start with a story that took me a long time to make sense of. About a decade ago, I tried to teach myself to play classical guitar, mostly on the strength of a friend's recommendation and a YouTube tutorial that made it look easy. I bought a decent guitar. I bought the recommended beginner book. I committed to practicing daily. And for the next three months, I produced some of the worst music ever played in my apartment. My fingers wouldn't go where I told them. My rhythm was off in ways I couldn't even diagnose. I'd practice a passage twenty times and somehow get worse instead of better.

I told myself this was productive struggle. I'd read the books. I knew that learning happened at the edge of your ability. The discomfort was the workout. I was supposed to feel like I was failing. The failing was the learning. I gritted my teeth and kept going.

Three months in, I quit. Hadn't improved meaningfully on anything. Hated the guitar. Resented the practice. Felt like a failure.

What I now realize (and what the research on this topic makes clear) is that I wasn't in productive struggle. I was in panic zone disguised as productive struggle. The discomfort I was experiencing wasn't producing learning. It was producing flailing. The difference between those two states is significant, and confusing one for the other is one of the most common ways ambitious learners end up burning out on projects that they could have completed if they'd recognized what was happening.

This is the question I want to address today, because I think it's one of the most important practical questions in learning, and the popular advice keeps getting it wrong. The "embrace discomfort" framing has become so dominant that it actively encourages learners to stay in conditions that aren't doing what they think. Today's newsletter is about how to tell the difference. The specific markers that distinguish productive learning discomfort from unproductive suffering, the failure rates that signal you're in the right zone, and what to do when you've crossed the line into panic. Let's get into it.

Picture this. A buyer opens ChatGPT and asks for a recommendation in your category. Your competitor's name comes up. Yours doesn't. And that buyer never makes it to your website.

That's happening right now in markets everywhere. And most teams don't know it's happening because it never shows up in their analytics.

HubSpot AEO shows you exactly where your brand stands in AI search, where competitors are getting recommended instead of you, and tells you specifically what to fix. No expertise needed.

Try it free for 28 days. Just $50 a month after.

Let me start by being precise about what we're discussing. The research distinguishes between two states that feel similar but aren't.

Productive discomfort is the cognitive state of being stretched by material that's slightly beyond your current ability, where you're actively engaging with the difficulty, making genuine attempts, and (critically) producing measurable learning over time. The work is hard. You make mistakes. But you're moving forward.

Unproductive discomfort (panic zone) is the cognitive state of being overwhelmed by material that's far beyond your current ability, where your attempts aren't producing forward progress, where the effort is going into managing distress rather than into learning, and where, over time, you're not actually getting better at the underlying material.

Both feel uncomfortable. Both feel like work. From the inside, they can be hard to distinguish in any given session. But over weeks, they produce wildly different outcomes. Productive discomfort produces durable learning that compounds. Unproductive discomfort produces frustration, declining motivation, and eventually project abandonment with little to show for the effort.

According to research summaries, the difficulty is only desirable when it forces the brain to engage in deeper cognitive processing… the kind that strengthens how information is encoded, stored, and retrieved. The effort has to be productive. This is the distinction that separates Bjork's framework from the lazy interpretation that "harder is always better." It isn't. Harder is only better when the difficulty targets the right cognitive processes. The framing matters. Difficulty isn't a virtue in itself. The right KIND of difficulty, hitting the right cognitive processes, produces learning. The wrong kind just produces suffering.

Here's where the research gets practical. Cognitive scientists have actually identified specific failure rates that distinguish productive from unproductive struggle, and the numbers are useful.

According to research on desirable difficulties, a useful target is 20-40% retrieval failure during practice. Roughly 60-80% of the time you want to be successful. Too easy (90%+ success), and you're not learning. Too hard (under 50% success), and you're flailing. Read that carefully. The productive zone has a specific signature. You're getting things right somewhere between 60% and 80% of the time. You're getting things wrong between 20% and 40% of the time. Above and below those ranges, the learning machinery starts to break down.

This is concrete enough to actually apply. When you're practicing something… language exercises, math problems, music passages, coding challenges, whatever… pay attention to your success rate. If you're getting almost everything right, you're in the comfort zone. The material is too easy. You're not learning much because you're not encountering the difficulty that triggers deep processing. If you're getting almost everything wrong, you're in the panic zone. The material is too hard. You're not learning much because you're spending all your cognitive resources just trying to keep up rather than actually engaging with the structure of the material.

The sweet spot (roughly 70% success, 30% failure) is where the learning machinery operates at peak efficiency. Enough success to maintain motivation and demonstrate that progress is real. Enough failure to be encountering material that's just beyond your current grasp. The failure is the workout. The success is the evidence that the workout is producing results.

This metric alone, if you actually pay attention to it, can transform how you choose study material. The textbook chapter that's almost completely opaque to you isn't producing learning. The exercises that you complete effortlessly aren't producing learning. The material that puts you in the 60-80% success range is where your time is best spent. Most learners never measure this. The ones who do calibrate their material this way tend to learn substantially faster than those who don't.

Beyond failure rate, several other markers help you tell which state you're actually in.

Are you making any forward progress over weeks? This is the longer-term test. Productive struggle, even when it feels brutal in the moment, produces measurable improvement over weeks. You can solve a problem this month that you couldn't solve last month. You can play a passage this week that you couldn't play last week. You can hold a longer conversation than you could a month ago. If you've been struggling for several weeks with no demonstrable improvement, the discomfort probably isn't productive. Something is wrong with the approach, the material, or the difficulty calibration.

Can you identify what specifically is hard? In productive struggle, you can usually name what's specifically challenging. "I keep mixing up these two grammatical structures." "I can do this technique slowly but I lose accuracy at speed." "I understand each piece but I can't integrate them yet." The specificity is a sign you're engaging with the material at a level that allows diagnosis. In unproductive struggle, the difficulty tends to be diffuse and overwhelming. You can't say what's hard… everything is hard. The lack of specificity is a sign you've gotten too far beyond your current foundation.

Are you generating attempts, or just freezing? Productive struggle involves actively trying things. Your attempts might be wrong, but they're attempts. You're producing output that can then be evaluated. Unproductive struggle often involves a kind of cognitive freeze… you stare at the material, your mind doesn't know where to start, you don't produce attempts because you don't have a sense of what attempting would even look like. The freeze is the panic zone marker. The attempts, even when wrong, are the productive marker.

Is the difficulty intellectual or emotional? Productive struggle is primarily intellectual… you're working hard on a problem. Unproductive struggle often becomes primarily emotional… you're managing anxiety, frustration, or self-doubt about not being able to do the work. As one analysis put it, the goal is productive struggle, not flailing. If you're producing nothing, you've gone past the desirable zone into overload. When the emotional load exceeds the intellectual load, you've crossed the line.

Are you developing skills you can use elsewhere? Productive struggle builds capabilities that transfer. The work you do at the edge of your ability strengthens cognitive systems and skills you can apply to related challenges. Unproductive struggle often doesn't build transferable skills… it just produces frustration and the eventual abandonment of the project. If you've been working on something for a while and haven't developed any underlying capability that shows up in related contexts, the struggle probably isn't producing what struggle is supposed to produce.

Do you sometimes have small breakthroughs? Productive struggle is punctuated by moments when something clicks. The passage that wouldn't play suddenly plays. The concept that wouldn't fit suddenly fits. The technique that wouldn't work suddenly works. These small breakthroughs aren't constant, but they happen regularly enough to confirm that the work is producing results. Unproductive struggle is characterized by their absence… weeks or months without any moments of "oh, I see now." The absence of breakthrough is itself diagnostic.

Okay, suppose you've recognized that you've been in unproductive struggle rather than productive struggle. Now what? The fixes are specific and useful.

Lower the difficulty level. This is the most direct fix. If you're failing more than 50% of the time on what you're working on, the material is genuinely too hard. Go back to easier material. Build the foundations that the harder material is sitting on top of. This isn't giving up. It's correcting a calibration error.

According to one summary, if you're producing nothing, you've gone past the desirable zone into overload. Back up, get the scaffolding in place, then return to the difficulty. The backing up is the move. You're not abandoning the project. You're temporarily retreating to a level where you can actually build the foundations that will make the harder level accessible. Then you return to the harder material with the foundation in place.

Get scaffolding. Often the issue isn't that the material is intrinsically too hard. It's that you're trying to handle it without the support that would make it manageable. A teacher, a coach, a textbook explanation, a study partner, a worked example… any of these can convert genuinely difficult material from panic zone to learning zone. As I covered in the comfort zone newsletter, the Vygotsky framework specifically includes the role of scaffolding. Difficult material PLUS scaffolding equals learning zone. Difficult material WITHOUT scaffolding often equals panic zone. Adding the scaffolding is one of the most common fixes for unproductive struggle.

Break the problem into smaller pieces. Sometimes the issue isn't the difficulty level overall but the size of the unit you're trying to learn. A skill that's overwhelming when attempted as a whole might be manageable when broken into components and tackled separately. The reading passage that's incomprehensible might be more accessible if you work through one paragraph at a time. The piece of music that won't come together might be possible if you isolate four measures and master them before adding more. The atomic unit matters.

Diagnose what's actually missing. When you're stuck, take a step back and ask: what specifically would I need to know or be able to do that I currently don't? Sometimes the answer reveals a foundation gap. You're trying to learn calculus and your algebra is shaky. You're trying to learn advanced grammar and your basic vocabulary is too small. You're trying to write essays and you don't yet have the reading background that essays usually draw on. Fix the foundation gap. The advanced material often becomes accessible once the underlying gap is addressed.

Take a real break. Sometimes the issue is cumulative fatigue rather than difficulty per se. You've been pushing for too long without recovery, and even material that would normally be in your productive zone has crossed into panic because your cognitive resources are depleted. A real break (a few days off the project, not just an hour) often restores the capacity that makes the same material accessible again.

Consider whether the project still makes sense. Occasionally the right answer is that the project genuinely shouldn't continue at all. Not because you've failed, but because the project was misconceived from the start. Maybe you picked a goal that doesn't actually serve your life. Maybe the time investment isn't worth what you're trying to get from it. Maybe a different approach to the same goal would be much more effective. The capacity to walk away from projects that aren't worth the cost is itself a learning skill. Don't quit too easily. But also don't grind heroically on something that wasn't a good fit in the first place.

It might help to name what productive struggle actually feels like, since most learners haven't experienced enough of it to recognize the sensation reliably.

Productive struggle feels demanding but not overwhelming. You can feel your brain working hard. Time often passes faster than you expected. You're frustrated when something doesn't click, but the frustration is specific and bounded rather than diffuse and overwhelming. You make attempts. Some of them work. Some of them don't. You learn from both. At the end of the session, you feel tired but not depleted. You can look back and identify what got slightly better. The next session, you can build on the previous one.

Productive struggle is hard. It's just hard in a way that's producing something. The hardness is connected to forward motion. The discomfort is bounded by the satisfaction of progress, however small.

Unproductive struggle feels different. You can feel your brain not knowing what to do. Time drags. The frustration is constant and diffuse rather than specific. You don't make many attempts because you don't know what attempting would look like. At the end of the session, you feel depleted rather than tired. You can't identify what got better. The next session, you start in the same place you started today. The hardness isn't connected to forward motion. The discomfort isn't bounded by progress. It just keeps being there.

The shift from one to the other is often gradual, which is part of why it's hard to recognize in real time. A project that started in productive struggle can drift into unproductive struggle as the material gets harder than your foundation can support. The drift is invisible until you step back and notice that you're not actually moving forward anymore.

Here's what I want you to take from all this. The cultural framing of discomfort as a moral good in learning has led to a lot of learners pushing through suffering that isn't producing what they think. The "embrace discomfort" advice is partially right… learning genuinely requires being uncomfortable. But it's incomplete in a way that produces real damage to ambitious learners. The discomfort has to be the productive kind. The unproductive kind, however virtuous it feels, isn't building anything. It's just consuming you.

The good news is that the distinction is recognizable once you know what to look for. Failure rates in the 20-40% range. Forward progress over weeks. Specific identifiable difficulty rather than diffuse overwhelm. Generated attempts rather than freeze. Intellectual rather than emotional load. Occasional breakthroughs. Transfer to related skills. These markers, taken together, tell you reliably whether you're in productive or unproductive struggle. The markers can guide your real-time adjustments. The adjustments can prevent the slow drift from productive to unproductive that kills so many learning projects.

My guitar story at the start of this newsletter would have ended differently if I'd known what to look for. The signs that I was in unproductive struggle were all there… no forward progress, can't identify what's specifically hard, can't generate attempts, primarily emotional load, no breakthroughs, no transferable skills developing. If I'd recognized the pattern, I would have either lowered the difficulty (started with easier pieces), gotten scaffolding (taken actual lessons), or broken the problem into smaller pieces (focused on just one technique at a time). Any of these would have likely turned the project around. Instead, I gritted my teeth on the wrong approach for three months and quit. The grit wasn't the problem. The grit was being applied to a situation grit alone couldn't fix.

If you're currently in a learning project that's been hard for a while, please apply these markers honestly. If you're in productive struggle, keep going… the hard part is part of the work and you're doing it right. If you're in unproductive struggle, please don't grind harder. Step back. Diagnose. Adjust. The project might still be worth pursuing, but with different calibration. Or it might not be, in which case walking away gracefully is wiser than grinding indefinitely.

The willingness to be uncomfortable is a learning superpower. The wisdom to know which discomfort is producing what is a bigger one. Build the second one. Your learning life will be measurably better for it.

Even Frodo had moments of unproductive struggle on the road. Galadriel didn't tell him to push through everything. She gave him a phial of light for the darkest parts. Sometimes the scaffolding is the whole game. Find yours when you need it.

Keep learning (and keep your struggle productive),

Ray