The most useful things I've learned in my engineering career don't appear in any documentation.
They live in the accumulated texture of specific projects: the moment I realized that the sensor placement we'd spent three weeks optimizing was fundamentally misaligned with how occupants actually moved through the space. The conversation with a facilities manager who described, in fifteen offhand minutes, more about how buildings actually behave than anything I'd read in a textbook.
These are the invisible lessons — the knowledge that exists between the formal steps of a process, that transfers through proximity and attention rather than instruction.
The Problem of Informal Knowledge
There's a term in knowledge management circles: tacit knowledge. It refers to the kind of understanding that's hard to articulate — the judgment that comes from experience, the pattern recognition that works faster than conscious analysis, the feel for what's wrong before you can name what it is.
Most organizations lose this knowledge faster than they create it. Projects end, teams disband, and the accumulated wisdom of the work disperses into the atmosphere. The documentation captures the outcomes; the hard-won understanding of how to get there disappears.
I've been thinking about how to change this, at least for myself.
Writing as a Documentation Practice
About a year ago, I started keeping project journals. Not formal writeups — those exist, and they're useful in their way — but informal ones. Notes on what surprised me. What I misunderstood. What I wish I'd known at the start.
The discipline of writing this down has changed how I work. The act of articulating a lesson forces a kind of clarity that simply experiencing the lesson doesn't. When I try to describe what I learned from a failed sensor calibration attempt, I have to understand it well enough to put it in sequence, to identify the cause, to separate what was specific to this project from what might generalize.
This is harder than it sounds. Most lessons resist simple articulation — they're contextual, conditional, full of "it depends." The work of writing them is partly the work of deciding which dependencies matter and which don't.
"Writing is thinking made visible. You don't know what you know until you've written it."
The Creative Ritual Dimension
This same practice applies to creative work, though the texture of the lessons is different.
When I'm writing — these essays, or earlier draft attempts that never became anything — I notice patterns in how the work goes well and poorly. Certain times of day produce a different quality of attention. Certain environments are hostile to the kind of thinking I need. The fifteen-minute walk before I sit down makes a measurable difference.
None of this is wisdom I could have acquired through instruction. It's just observation, accumulated over time, applied deliberately.
But here's what's interesting: before I started writing it down, I wasn't actually applying it deliberately. I was subject to these patterns without fully understanding them. Documentation created agency.
What to Document
If I could go back and tell myself what was worth capturing from the beginning, I'd say this:
Document the surprises. The moment something doesn't behave as expected is the moment you're learning most. Write it down immediately, while the confusion is fresh.
Document the questions you couldn't answer. Gaps in understanding are as valuable as understanding itself — they tell you where to go next.
Document the conversations. The hallway exchange, the casual lunch debrief, the call where someone explained something in a way that finally clicked. These are often where the real knowledge lives, and they evaporate fastest.
Document the feeling of not knowing. This sounds strange, but it's useful. The experience of genuine confusion has a texture — and recognizing that texture is how you avoid mistaking confident-sounding ignorance for knowledge.
The Long Game
The value of these records compounds slowly. A journal from a project two years ago might clarify something about a current one. A lesson I documented and then forgot might resurface exactly when I need it.
This is the real argument for the practice: not that it produces immediate returns, but that it converts fleeting experience into something that can be held, revisited, and connected to other things you've learned.
The invisible lessons aren't lost. They're just waiting to be written down.