I stopped writing down the things I already knew

The Art of Mastery

I stopped writing down the things I already knew

Why documentation is often a graveyard for the intuition that actually makes your work matter.

You are standing in the middle of your office and you realize that you do not know how to do your job anymore. Not really. You know how to find the page that tells you how to do it and you know where the buttons are and you know who to call when the server breaks but the gut feeling is gone.

It happened slowly over and it started with a meeting about risk. Your boss sat everyone down and said that the team was too dependent on heroes and he said that if you got hit by a bus tomorrow the whole company would sink. He wanted a wiki and he wanted every single thing you did to be mapped out and he wanted it to be so clear that a stranger could walk in and do your work just by reading the screen.

The “Hero” Model

Dependent on individual intuition, “gut feeling,” and unwritten expertise. Risky, but alive.

The Wiki Model

Mapping every step for “strangers.” Safe, searchable, but fundamentally static.

The corporate transition from organic expertise to “legible” documentation.

So you spent months writing and you typed out the steps for a launch and you explained how to talk to the creators and you put the secret shortcuts into a list. You felt good about it at first because the screen looked full and the headers were bold and the knowledge felt safe.

But then and you noticed that the people you hired were not getting better and they were just getting faster at searching the wiki. They followed the steps but they missed the point and they did not see the red flags because the red flags were not on the list.

The Living vs. The Pinned

The problem with a list is that it is dead and the things you do every day are alive. When you write a process down you take a moving thing and you pin it to a board like a bug in a box and the bug does not fly anymore. It just sits there.

You used to watch a video and you could feel the moment it started to lag and you knew exactly when to push it and you knew when to pull back. Now you look at step fourteen of the manual and step fourteen says you must wait before you check the stats. You wait those because the manual says so and even though your gut says that the window is closing and the moment is gone you stay still.

Sarah A.-M. spends her time looking at how systems trick people and she calls this forced legibility. She is a researcher who studies dark patterns and she told me that companies hate secrets even when the secrets are the only things that make the company work.

“They want to turn your soul into a file and they want to turn your hands into a script. When you make a person follow a text they stop thinking and they start decoding. The brain shifts gears from the part that solves problems to the part that follows orders.”

– Sarah A.-M., Researcher on Forced Legibility

Once that shift happens you are not a creator anymore. You are just a meat-powered computer that is reading a very long and very boring line of code. Here is how the brain actually handles a skill and it is not like a hard drive at all.

When you learn to ride a bike or launch a video or judge a thumbnail you are building a mesh of neurons in your basal ganglia and this part of your head does not use words. It uses patterns and it uses timing and it uses a deep sense of weight. It is fast and it is quiet and it does not need a search bar.

Cognitive Speed: Intuition vs. Documentation

Basal Ganglia (Intuition)

NATIVE REFLEX

Fast, pattern-based, quiet, doesn’t need words.

Prefrontal Cortex (Wiki-Reading)

SYSTEM OVERHEAD

Slow, loud, translation delay, gets tired after .

When you force yourself to read a wiki you are using your prefrontal cortex and that part is slow and it is loud and it gets tired after . The prefrontal cortex has to take the words on the screen and translate them into a picture and then tell the rest of your brain what to move.

This creates a delay and that delay is where the art dies. You are trying to play a piano by reading a book about how to press keys and you are never going to catch the rhythm that way.

I remember when I explained the internet to my grandmother and she asked me where the library was. I told her that the whole thing was a library but she did not believe me because she said a library has a person who knows the books.

She understood that a room full of paper is useless unless there is a mind that has walked the aisles and can point you to the truth. We have built these massive digital libraries of how-to guides and we have fired the people who actually knew the books. Now we just have the aisles and we are all wandering around looking for a spine that looks familiar.

The documentation drive promised us freedom from the fear of losing people but it gave us a different kind of fear instead. We are afraid to move without checking the guide and we are afraid to trust our own hands.

The Junior Editor’s Trap

I saw a junior editor spend trying to find the documented way to fix a color grade when he could have fixed it in just by turning a knob until it looked right. He was so scared of doing it the wrong way that he forgot he had eyes that could see the right way.

We have taught an entire generation of workers that the wiki is the boss and their own experience is just a guess that needs to be verified. This is especially true in the world of video and social proof.

You can write a thousand pages on how to get people to watch a channel but the truth is that people watch what other people are watching. It is a loop and it is a vibe and it is a feeling of momentum. If you try to document that momentum you will miss it because by the time you finish the sentence the trend has moved on.

Smart creators realize that they cannot wait for a manual to tell them how to grow and they need to build a base and they need to show the world that they are already worth seeing. Sometimes that means you have to skip the thirty-step checklist and just find a way to get the numbers moving so the algorithm takes notice.

You might decide on an achat vues youtube because you know that a video with zero views is a video that nobody will ever click on and no amount of wiki-reading will fix the cold start of a new upload. You do it because you know the territory and you know that social proof is a physical force in the digital world and you do not need a committee to tell you that a spark needs air to become a fire.

The Knowledge Graveyard

The manager who wants everything written down thinks he is building an asset but he is actually building a graveyard. He is collecting the ghosts of past successes and he is hoping that if he arranges them in the right order they will come back to life. But they never do.

The knowledge that matters is the knowledge that is currently in use and it is the stuff that people talk about over coffee and it is the stuff that you learn by failing. When you put it in a wiki it stops growing and it stops changing and it starts to rot.

The world moves and the platform updates and the audience gets bored but the wiki stays the same because nobody has the time to update the four hundred pages of text that they barely read anyway.

I stopped trying to document the soul of my work because I realized I was killing it. I stopped making my team write down every single thought and I started making them talk to each other instead. We went back to the way it was before the mandate and we started trusting the silence between the steps.

If you know how to do something you should just do it and you should not have to prove that you did it by checking a box in a software suite that tracks your productivity. The real work is the thing that happens when you are not looking at the screen and it is the flash of insight and it is the sudden move and it is the thing you cannot explain.

Managed Process

  • Predictable & Safe
  • Incredibly Mediocre
  • Easier to Oversee

Master Craft

  • Messy & Hidden
  • Produces Meaning
  • Impossible to Duplicate

We think that by making things legible we are making them better but we are just making them easier to manage and there is a huge difference between a managed process and a master craft. A managed process is predictable and it is safe and it is also incredibly mediocre. A master craft is messy and it is hidden and it produces things that actually matter.

I would rather have a team of five people who just know what they are doing than a team of fifty people who have to read a manual to find the bathroom.

The next time someone tells you to write it all down you should ask them if they want a record of what you did or if they want you to keep doing it. You cannot have both. You cannot be the pilot and the guy writing the flight manual at the same time and if you try you are going to crash the plane.

Put the pen down and step away from the wiki and just look at the work. Trust the neurons that have been watching the patterns for years and let the basal ganglia take the wheel. The map is a lie and the screen is a cage and the only thing that is real is the feeling of the work in your hands.

The wiki grew into a thick book of rules and the hands that used to build things grew cold and slow.

You will feel a weird kind of guilt when you stop looking things up. You will feel like you are cheating because you are not following the sanctioned path and you will feel like you are being reckless. But then you will see the results and you will see the speed return and you will see the joy come back into the room.

You will remember that you are a person with a brain that is more complex than any database ever built and you will realize that you were never meant to be a librarian for your own life. You were meant to be the one who makes the things that the librarians eventually have to write about. Stop being the record and start being the event.