The Part That Wasn't About Knowledge Management
Why my system kept collapsing until I asked a different question.
I just finished a field guide about building a knowledge base. Ten trails. Three months of work. A tool I love.
And the strange thing is, almost none of what made it work was technical.
I want to tell you the part that didn’t fit in the guide. The guide had to be about you. This one gets to be about me.
I thought I had a productivity problem
When I started, I told myself the problem was mechanical. Too many tabs. Too many saved articles. A system that kept collapsing under its own weight.
I thought if I found the right tool and the right tags, the mess would resolve, and I would finally feel on top of things.
It didn’t work. And it took me an embarrassingly long time to understand why.
The problem was never the tags. It was that I had no emotional reason to keep going. I was organizing for the sake of organizing. And a tidy graveyard is still a graveyard.
The day I almost quit
The shift came on a bad day, not a good one.
I had cleaned everything up. I felt proud for about a week. Then I watched it drift right back into chaos.
I remember sitting there genuinely ready to quit. Not just the tool. The whole idea that I could ever think clearly.
That’s the moment most people walk away. I almost did.
What stopped me wasn’t a new feature or a better system. It was a question I had not asked yet. Not what do I want to organize. But what do I want to be able to give, once I can finally think clearly.
The moment I had an answer to that, the work stopped feeling like filing. It started feeling like building toward something.
The thing that didn’t fit the guide
Here’s what I learned, twice over, writing the whole thing.
Systems only stick when they’re emotionally anchored.
Every chapter of the guide that landed was one where I told the truth about a moment that actually cost me something. The near-quit. The shame of thinking I was lazy. The fear of writing honestly about a tool I’d come to love.
Every chapter that fell flat was one where I tried to sound like an expert instead of a person.
The emotion wasn’t decoration on top of the information. It was the load-bearing wall.
I couldn’t put that in the guide. The guide had to keep you in the driver’s seat, walking your own trails. But this is the engine underneath all of it, and it belongs here, with you, in the open.
So if you take one thing
Don’t start by asking what system to build.
Start by asking what you want to be able to give once you can finally think clearly. Connect the work to that, and it sticks. Skip that part, and no tool on earth will save you.
This is what worked for me. I know it doesn’t work for everyone. If you’re someone who has to act first and find the feeling later, you might read this backwards, and that’s fair. I’m telling you the order I needed. Yours might differ.
I didn’t arrive at that alone. Simon Sinek taught me to start with why, that most of us can say what we do but almost none of us can say why we do it, and the why is the whole engine. Seth Godin sharpened it into a question I still can’t shake. Sharpening the axe is a fine tactic, he says, but strategy is asking why we have an axe at all, and what change we’re actually here to make. And Tiago Forte gave me the warning that stuck. Action without learning just spins you in place, faster and faster, arriving nowhere.
They didn’t hand me the answer. They argued me toward it. I took each of them into Recall, the app where I keep everything I save, and pushed back until only what was true for me survived.
I want to be honest about how that last part works, because it’s easy to make it sound like magic. Recall didn’t do the thinking. It put the pieces on the table. It surfaced things I had saved and forgotten, and set them next to each other. But the connection, the decision about which pieces formed the answer, that was mine.
Robin Good taught me to guard that line. You only own the work if the thinking is traceable to you, not the tool. The tool widened the search. I did the choosing. The day I let a tool do the choosing is the day the work stops being mine.
That’s the engine. The guide is just the map.
And I’ll keep writing the parts that didn’t fit, here, with you. Every other week.
Thank you for being here. I’m glad you came.
Ricardo
How this was made: I wrote it by hand, over more than one sitting, then let it rest and cut what wasn’t true. I used AI to argue with me, not to write for me. To show me the weak spots and hold up my own choices so I could see them clearly. That discipline, using the tool to sharpen my judgment instead of replace it, I learned in part from Robin Good’s writing on curation. The judgment stayed mine the whole way.