I am, without question, a deep thinker. I’ve known this for years. I sit with problems longer than most people. I notice patterns where others see noise. I’ll still be turning an idea over in my head three days after the conversation that sparked it. That’s just how I’ve always been.
But a few months ago something occurred to me that I hadn’t expected: I had never actually questioned how I think. Not what I think about — that part I knew. But the mechanics of it. The approach. The shape of the process. I had been doing it for my entire life without ever once looking at it directly.
Which, when you stop to think about it, is a bit like being a professional chef who has never considered their own palate.
Does thinking have a style?
The obvious answer is yes — obviously no two people think identically. But that’s not quite what I mean. I’m not asking whether people have different thoughts. I’m asking whether people have fundamentally different ways of approaching problems, processing information, and generating understanding. And whether those differences are consistent enough to be mapped, named, and used deliberately.
It turns out they are.
Cognitive style — the characteristic way an individual approaches thinking tasks — is a well-documented area of psychology. Not personality. Not intelligence. Something more specific: the preferred mode of processing. Some people think in patterns and abstractions. Others think in concrete examples first and extract the principle later. Some need to talk through a problem out loud to understand it. Others need silence and solitude before they can reach a conclusion. Some build understanding linearly, step by step. Others arrive at answers seemingly at random and reconstruct the reasoning after the fact.
These aren’t better or worse ways of thinking. They’re just different shapes of the same process. But they have real consequences for how you work, how you communicate, and crucially — where your blind spots live.
How do you actually figure out your cognitive style?
Not from a personality quiz. That’s not the right tool here.
The way to do it is observation, done honestly, over time. You’re essentially reverse-engineering a process you’ve been running unconsciously your entire life. Some questions that helped me:
How do you arrive at answers?
Do you reason forward, step by step, toward a conclusion? Or does the conclusion tend to arrive first — a strong intuition or gut sense — and you reconstruct the reasoning after? Neither is wrong, but they have very different failure modes. Forward reasoners can sometimes get trapped following a logical chain into a bad conclusion because each step seemed valid. Intuitive thinkers can arrive at correct answers they can’t explain and struggle to convince others.
What does confusion feel like for you?
This one was revealing for me. I noticed that when I’m genuinely confused, I don’t experience it as a gap in information — I experience it as a lack of structure. I don’t know where the pieces go. Once I have a mental model that holds the pieces in a coherent shape, I rarely feel confused, even about complex things. That tells me I’m a structural thinker — I need a map before I can navigate.
Others experience confusion as a lack of examples. They need to see the thing in action before the abstraction makes sense. Teaching abstract concepts to these people by starting with the theory first is like handing someone a map before they’ve seen the territory. The map means nothing yet.
Do you think best with or without input?
Some people’s thinking is sharpened by conversation. They need to externalize the problem — say it out loud, explain it to someone — and in the act of explaining it, they find the answer. Other people think in private and bring conclusions to conversations, not problems. Interrupting the second type mid-think is genuinely disruptive. Staying silent around the first type leaves them without the thing they need most.
I’m the second type. I’ve sat in meetings where I seemed disengaged, not because I was, but because I hadn’t finished thinking yet and everything I said before that would be incomplete. I just didn’t know that about myself clearly enough to explain it.
What does understanding feel like?
For me, understanding has a specific texture. It’s when I can see a thing from multiple angles and they all point at the same truth. When I can’t find a contradiction. When I could teach it and handle unexpected questions. Some people feel understanding as a click — a sudden clarity after confusion. Others feel it as accumulation, a gradual buildup of familiarity until doubt disappears.
These aren’t the same experience. And they produce different learning strategies.
Why this matters beyond self-knowledge
Knowing your cognitive style doesn’t just help you understand yourself. It changes how you work.
If you know you’re a structural thinker, you stop fighting the urge to build a mental model before diving into implementation. You give yourself permission to spend twenty minutes sketching out how the pieces fit before writing a line of code — and you stop feeling guilty that you need to, because you understand it’s not procrastination, it’s your actual process.
If you know you think by talking, you stop trying to do your best thinking in isolation. You find people to think out loud with. You use rubber duck debugging not as a last resort but as a first step.
If you know you arrive at answers intuitively, you stop trying to always reason your way to conclusions and start building a habit of testing your intuitions rigorously — not because your instincts are wrong, but because you know your process skips the visible reasoning chain and you need to verify that the invisible one was sound.
You also get better at explaining yourself to others. A lot of interpersonal friction in collaborative work comes from one person not understanding why another person needs what they need. If you can say “I need to talk through this before I can give you an answer” or “I need fifteen minutes to think in private first,” it changes the dynamic. You’re not being difficult. You’re being accurate about your own process.
The blind spots
Every cognitive style has a failure mode baked in.
Deep thinkers, which I am and possibly you are given that you’re reading this, tend to overthink. The same capacity that lets you find real signal in complex problems also keeps you analysing things that don’t require analysis. You stay in your head when you should be doing. You refine the plan when you should be executing it. You spot seventeen edge cases when the core case is what needs to move first.
Intuitive thinkers can struggle to build trust with others because their conclusions seem to arrive from nowhere. They’re often right but can’t show their work, which matters in environments that demand transparent reasoning.
Concrete thinkers can get stuck when no example exists yet — when you’re doing something genuinely novel with no reference point to learn from.
Abstract thinkers can build elegant models that don’t actually match reality because they moved to the abstraction before checking it against enough instances.
Knowing your style tells you where to be suspicious of yourself. That’s arguably more valuable than knowing your strengths.
What I actually did with this
Once I started mapping my own thinking, a few things shifted.
I stopped fighting my instinct to think in writing. I used to see it as slow and inefficient. Now I understand it’s how I process — writing is my thinking, not a record of thinking I’ve already done. I gave myself more of it.
I started flagging when I hadn’t had time to think. Instead of giving a half-baked answer in a meeting and walking it back later, I started saying “I don’t have a view on that yet — can I come back to you?” This went from feeling like an admission of weakness to feeling like accuracy.
And I started noticing when I was in the wrong mode for the task. Execution requires different thinking than planning. Analysis requires different thinking than communication. I’m not equally good at all of these in all states. Knowing that means I can be more deliberate about when I do which.
Most people go their entire lives running their own thinking without ever inspecting the code. They have intuitions about how they work, but they’ve never really looked. Spending time on this — genuinely observing how you arrive at answers, what confusion and clarity feel like, what you need from an environment to think well — isn’t navel-gazing. It’s foundational.
You use your mind for everything. Seems worth understanding it.