Imposter Syndrome and Intuition: When Competence Fails to Recognize Itself

There are professions in which one is never finished learning. Not because the field changes so quickly, though that's often true too, but because what makes the work good cannot be fully formalized. Lighting design and film directing belong here. Web development too. And many other activities that look very different at first glance. What connects them: a significant portion of the decisions that define the work runs through intuition. And that's precisely why imposter syndrome is especially widespread in these fields, and especially tenacious.

What imposter syndrome actually is

Imposter syndrome is not simply a lack of self-confidence. It is something more specific: the feeling that one's own competence is an illusion that will eventually be exposed. That you got lucky, were in the right place at the right time, that others will soon realize you don't actually really know. What's treacherous about it: it occurs most frequently in people who are genuinely competent. Less competent people systematically overestimate themselves, which is the Dunning-Kruger effect. Competent people, by contrast, know what they don't know. They have a more refined picture of how complex the field is in which they work. And they compare themselves upward.

Why intuition-based activities are particularly vulnerable

In fields that rely heavily on intuition, there is a structural problem: the decision cannot be fully justified. A director who knows that this shot is better than that one often cannot explain it without gaps. A developer who senses that this architecture will create problems later sometimes has no watertight proof. Only experience, pattern, an inner signal.

When decisions aren't fully justifiable, a vacuum emerges. And this vacuum is then often filled by the voice of imposter syndrome: maybe I was simply wrong. Maybe it's just a gut feeling. Maybe someone who really knows what they're doing would see all of this completely differently.

The problem is: this voice sounds reasonable. It sounds modest. It sounds like healthy self-criticism. But it isn't. It is a thought pattern that systematically makes competence invisible.

What intuition actually is

Intuition is not a countermodel to competence. It is competence's most condensed form. What we call intuition is the result of thousands of hours of practice, in which the brain has stored patterns that can no longer be retrieved linguistically but are nonetheless available. The chess grandmaster who sees the best moves without calculating all variations. The experienced physician who senses that something is wrong with this patient before the test results are in.

Daniel Kahneman described this precisely in "Thinking, Fast and Slow": System 1, the fast, intuitive thinking, is not primitive. It is highly specialized. It is the result of learning that has been so deeply internalized that it runs automatically. And in fields where one has practiced long enough, with sufficient feedback, System 1 is often more reliable than System 2, the slow, deliberate analysis.

This means: when an experienced director knows that this shot is better, that knowledge is real. It is not worth less because it can't be stated in three sentences. It is coded differently, but not less reliable.

Film directing and the unsayable decisions

On a film set there is a moment all filmmakers know: you shoot a scene, everything is technically fine, and yet it's not right. You know it. So you shoot again. Or you stop after the twenty-eighth take and do it the next day, if the production schedule still allows that. That is not arbitrariness. It is a quality judgment based on years of practice. But it is a judgment that cannot be fully formalized. And that's precisely what makes it vulnerable, to imposter syndrome, but also to producers with schedules and budgets.

Web development and the invisible expertise

Web development has a particular variant of this problem: the field changes so fast that you can feel like you're never really up to date. New frameworks, new tools, new paradigms. What was state of the art last year is already considered completely outdated today. This produces a specific form of imposter syndrome: you know the fundamentals deeply, you have experience with complex systems, you know how to solve problems. But because you're not currently using the newest framework, you doubt whether you're even still qualified.

That is a category error. Deep experience with systems thinking and problem solving is not outdated. It is the foundation on which everything else rests. Good developers solve problems that no one has seen in quite this way before, by drawing on patterns they learned in entirely different contexts. That is intuitive competence. And it cannot be measured with a tutorial certificate.

What helps

Imposter syndrome doesn't disappear through more knowledge. It disappears when you stop measuring intuitive competence against rational justifiability. That is an inner step, not a content-based one.

Concretely this means: decisions made from experience don't need gapless justifications. They need context and reflection. You should know why you're doing something. But you don't have to prove it like a mathematical theorem.

What also helps: recognizing the phenomenon in others. Whoever regularly works with competent people sees that imposter syndrome is not a sign of incompetence. It is almost a sign that someone has been in it long enough to understand how complex the field really is.

And: taking one's own intuitive competence seriously. Observing it. Noticing when the inner signal was reliable and when it wasn't. That is not complacency. It is calibration.

Intuition is not the opposite of knowledge. It is its most mature form.