Riflessioni

Extrapolating the Mental Drawer: An Engineer's Strategies to Harness the 90% Unconscious Mind

Published on 03 June 2026

Extrapolating a Mental Drawer — Chronicle of an Engineer Who Learned to Negotiate with Their Own 90%

In a 1950s Venetian kitchen, there was a dark, shallow, deep wooden drawer that opened with a round brass knob. Inside, there were no precious things. Only tools: a worn wooden spoon, a crooked corkscrew, two keys whose locks no one remembered, a piece of electrical wire, a box of matches. My grandmother opened that drawer twenty times a day without thinking. Her hand knew where everything was even in the dark. Her conscious mind didn't intervene: the drawer had become an extension of her body.

I started thinking about that drawer recently because I realized something that changed the way I work, write, and — I believe — even the way I exist in the world. The thing is this: almost everything I know, I don't know consciously. My hands know it, some region of my brain that never speaks with the voice I think with knows it. The conscious part of me — the part currently writing this sentence — is a narrow window. A small lamp in a huge room where someone else has been working for decades, silently, without asking permission.

Neuroscientists have been saying it for years, with precise numbers: approximately 90% of cognitive processes are unconscious. Daniel Kahneman systematized this in Thinking, Fast and Slow with the distinction between System 1 (fast, automatic, below the threshold of consciousness) and System 2 (slow, deliberate, explicit). Joseph LeDoux showed that emotional decisions form before we are aware of them. Benjamin Libet, as early as the 1980s, measured that the brain prepares an action 200-500 milliseconds before consciousness realizes it has decided it. The data is solid. It's not interpretation. It's physiology.

And here opens the question that kept me awake: what changes if I truly accept this data, not as a curiosity from a popular science article, but as an operational specification of my system?

The Two Wrong Reactions

When a person discovers that 90% of themselves works beneath the surface, they usually react in two wrong, symmetrical ways.

The first wrong reaction is denial: "No, I decide everything consciously. I have full control over my thoughts." It's the reflex of those who have built their identity on rational mastery of the world. Typical of engineers, ironically. Admitting the 90% unconscious seems to admit we are automatons piloted by an invisible crew, and the rational ego rebels. It reacts by clenching its teeth even tighter on control. Result: double effort, double rigidity, and — worse — inability to notice when the unconscious is delivering a valuable insight, because consciousness is too busy pretending to be the sole decision-maker.

The second wrong reaction, opposite and symmetrical, is surrender: "Then I control nothing, everything is predetermined below, my decisions are illusions." This is neuroscientific fatalism, fashionable in recent years in popular discussions about free will. It seems sophisticated but is equally immature: those who embrace it stop taking responsibility for their choices, because "the brain decides anyway" — as if "the brain" were someone else and not themselves.

Both reactions are wrong because both treat the relationship between consciousness and unconsciousness as a power struggle: who commands, who obeys. It's the typical mental reflection of someone who hasn't yet understood that the cognitive system doesn't work that way. There's no government and opposition. There's a distributed orchestra, where consciousness isn't the conductor — it's one of the musicians, perhaps the one playing the most visible instrument, but not the one deciding the score.

The Third Way: Balance, Not Control

The mature way is a third one, and it's what changed my way of working. I would formulate it this way: accept the mechanism to achieve a different balance. Not balance in the sense of "fifty-fifty." Balance in the sense of a system where each component plays its part without pretending to play that of others.

The conscious part — my 10% — does what only it can do: extrapolate. That is: take what the underlying part has already processed and bring it out in a form that is readable, shareable, conservable. The conscious part is the hand that opens the drawer. It is not the hand that put things inside. Those were put there by time, habits, experience, training, nights of sleep during which something was consolidated without us noticing.

The unconscious part — my 90% — does what only it can do: process in parallel, in mass, without the slowness of words. It recognizes patterns in millions of raw data that consciousness doesn't even perceive. It builds relationship maps while I sleep. It delivers insights, phrases, solutions, images, already formed, in the form of "I've got it," "I feel it," "it's like this."

When the two parts stop fighting for control and begin to negotiate, something happens that changes everything: you become much faster, much more precise, and much less tired. Not because you work less, but because you stop doing the double work of someone who wants to consciously control what has already been decided underneath.

What does it mean, in practice, to "extrapolate a mental drawer"

I'll try to make it concrete. A mental drawer is a knowledge structure that has formed in your unconscious part through years of experience, but which you have never written down, never drawn, never delivered to an external artifact. It's there, you use it twenty times a day — but it only exists inside your head.

Extrapolating it means pulling it out of your head and putting it into an external artifact: code, map, prose, diagram, procedure, article. Extrapolation is not active memory, it's not "jotting things down." It's a deeper operation: it's asking the underlying part to show itself to the upper part, through a language that both can read.

I'll give three living examples, all of which happened to me in recent weeks, because only examples save ideas from rhetoric.

Example one: a graph-map of the Brofer catalog

I have been working for years with Brofer heat recovery units for Controlled Mechanical Ventilation systems. Thirty-two models, each with its compatible filters, each with its real case studies in the Veneto region, each with its own behavior. For years, I had everything in my head. I knew which filter went with which recovery unit without having to look. When a client asked me "I have an RDCD25SK installed in Mestre, which filter do I need?" I answered in two seconds. It wasn't genius: it was a mental drawer formed by experience.

Then one day I had a precise annoyance: what I know, my system doesn't know. If my partner Albert needs to look up a piece of data tomorrow, he has to go through me. If a client wants to verify information, they have to go through me. If I want to grow as a company, I have to go through me. The drawer was only in my head, and my head doesn't scale.

So I decided to extrapolate it. But — and here's the delicate point — I didn't decide how to extrapolate it. I sat down and let it flow. The underlying part gave me the answer in a few seconds: it had to be a graph. Not an Excel sheet, not a tabular database, not a collection of datasheets. A graph. Because in my head, Brofer information isn't rows and columns: they are nodes that speak to each other. Recovery units speak to filters. Filters speak to interventions. Interventions speak to cities. Cities speak to seasons.

The conscious part only had to find the tools to make visible that structure which the underlying part had already built. Seven hundred lines of code later, on my screen there were 32 blue nodes, dozens of yellow nodes, some green nodes, and — something my head could never have seen on its own — twelve orphaned nodes floating disconnected. Twelve products in my catalog that I had never associated with anything, and that I had forgotten about. My underlying part knew them, but my conscious part didn't.

Extrapolation showed me something about myself that I didn't know I knew and didn't know at the same time. This is the first reward for those who agree to extrapolate: you discover where you are full and where you are empty. You discover which part of your knowledge is solid, and which has rotted from lack of maintenance.

Example two: a poem for my grandmother

My grandmother died at 103 in the weeks I am writing this article. Her name was Maria. She was a simple woman, of few words, of many gestures. When I heard of her death, I needed to write her a poem. I didn't know where to begin. The conscious part didn't know. The underlying part did.

I did something I've learned to do in recent years, and which — I tell you honestly — has impressive power: I didn't think. I let it flow from deep within, without resistance. Without correcting it as it came. Without asking myself if what I was writing was beautiful or ugly, right or wrong. I just opened the drawer and let things come out. And the poem came out, whole, in less than ten minutes. I didn't correct it. I didn't refine it. It was already ready. The conscious part only had to transcribe what the unconscious part had already processed and condensed through a lifetime of memories, affections, and sensations. This is the purest act of extrapolation: giving voice to the ineffable already formed.

Conclusion: The Value of the Unknown

These examples, so different from each other, demonstrate the power of extrapolation. It's not about learning more, but about unlocking what you already know but haven't yet made accessible. It's a bridge between your limitless potential and your conscious expression. Learning to negotiate with your 90% is not an act of weakness, but of wisdom: it means recognizing the entire orchestra of your mind and allowing each instrument to play its best part. For an engineer, it means transforming insights into solutions, raw data into efficient systems, and lived experience into scalable knowledge.

#Estrapolazione Inconscia #Processi Cognitivi #Ingegneria Mentale #Sviluppo Personale #Neuroscienze Applicate #Gestione della Conoscenza #Produttività Intuitiva
Ing. Marco Maretto

Written by

Ing. Marco Maretto

Systems Engineer. Designing architectures that not only use AI, but survive its errors.