WFH Lesson 3 - Knowledge Management
If you've been following this series, you know I've been working from home since 2018 leading a CyberSecurity team. Lesson 1 covered time management, Lesson 2 covered routine and physical setup. This lesson is about something that took me longer to fully appreciate: knowledge management.
Specifically, why it matters so much more when you're remote — and why neglecting it is one of the most common hidden reasons remote workers underperform compared to their in-office counterparts.
The Hallway Conversation Problem
Here's something that happens in offices so constantly that nobody notices it: knowledge transfer. All day long, in offices, information moves through informal channels. Someone mentions in passing that a vendor changed their pricing structure. A developer overhears a conversation about a new security requirement. A new hire absorbs how decisions get made by sitting near the people who make them. None of this is in a document. None of it is in a ticket. It's just... in the air.
When you're remote, the air is gone.
All of that informal, osmotic knowledge transfer stops. And if you don't replace it with something deliberate, you get teams where information silos develop rapidly, where the same questions get asked repeatedly, where people make decisions without context that someone else on the team already has, and where institutional knowledge exists only in the heads of whoever has been around the longest.
I've watched this happen. It's slow and it's subtle and by the time you notice it, you've already got a real problem.
The solution is Personal Knowledge Management — PKM — and it's not optional for remote workers. It's infrastructure.
What PKM Actually Is
Personal Knowledge Management is a system for capturing, organizing, and retrieving information in a way that makes it useful over time. It's not just "taking notes." Notes are inputs. A PKM system is what you do with those inputs so they become something you can actually use later.
The goal is to build what some people call a "second brain" — an external system that holds information so your actual brain doesn't have to. When you have a reliable system for capturing and retrieving knowledge, you stop trying to remember everything. You trust the system. And that frees up cognitive bandwidth for higher-order thinking.
For remote workers specifically, PKM serves an additional function: it makes your knowledge shareable. Everything you know that lives only in your head is inaccessible to your team. In an office, some of that knowledge leaks out through hallway conversations. Remotely, it doesn't leak unless you deliberately put it somewhere others can find it.
The Tools I Use
I'm going to share what I actually use, not just what's theoretically good. This is a system I've built over years and it works for the way my brain operates.
Obsidian
Obsidian is my primary knowledge base. It's a local-first, Markdown-based note-taking application that stores everything as plain text files on your own machine. This is not a sponsored recommendation — I use it because it's the best tool I've found for building a genuinely interconnected knowledge base.
What makes Obsidian different from other note apps is the bidirectional linking. When I write a note about a security vulnerability, I can link it to the vendor, the affected system, the team member who handled it, and the policy that governs our response. All of those links work in both directions — so if I'm looking at the vendor note later, I can see every incident I've connected to that vendor. Over time, this builds a web of knowledge that's genuinely useful rather than a pile of unconnected notes.
I use it for:
- Personal learning notes (anything I'm studying or reading)
- Work process documentation
- Project notes and decision logs
- Evergreen notes on topics I work on regularly (threat modeling, incident response, vendor management)
- This blog series, actually
The key habit with Obsidian: link everything. Every new note, ask yourself: what else does this connect to? What existing note does this extend or contradict? The power of the system comes from the connections, not the individual notes.
Readwise
Readwise is where my reading highlights go. Books, articles, Kindle highlights, web clippings — Readwise captures them all and then resurfaces them through a daily review feature that emails you a selection of past highlights every morning.
The resurfacing is the killer feature. Reading is only useful if you remember what you read. Most people highlight things and never see them again. Readwise solves the retention problem by repeatedly bringing things back into your awareness at spaced intervals — the same mechanism behind effective flashcard learning.
I have Readwise connected to Obsidian via the official plugin, so highlights flow automatically into my knowledge base. Books I read become searchable, linkable notes rather than forgotten highlights in an app I never open.
A Simple Daily Note
Every workday I create a daily note in Obsidian. It has three sections: what I'm working on today, what I learned or what happened, and anything I want to carry forward. This takes maybe ten minutes total across the whole day.
The daily note is my capture layer — the place where raw information lands before I process it into more permanent notes. It's also how I track context over time. If I need to remember when a decision was made, or what I was working on during a specific week, the daily notes give me that.
Building a Second Brain for Remote Work
The "second brain" concept comes from Tiago Forte's work and the basic idea is this: your brain is for thinking, not storing. When you use your brain as your primary storage system — trying to remember every decision, every piece of context, every thing you need to do — you're using it wrong. You get cognitive overload and things fall through the cracks.
A second brain is an external system you trust enough to offload that storage function. When it works, you stop carrying around the anxiety of "I need to remember this" and start trusting that if something matters, it's in the system.
For remote workers, this isn't just a productivity optimization. It's a professional survival skill. Here's why:
You have fewer opportunities to reconstruct context. In an office, if you forgot something, you could ask the person at the next desk. Remotely, reconstructing context means interrupting someone's deep work to ask a question that you should already know the answer to. The more you capture, the less you have to interrupt.
Your knowledge needs to be accessible to others. Whatever you know that's relevant to your team should live somewhere they can find it. If it only lives in your head, it's a single point of failure.
Documentation becomes your voice when you're not in the room. In office meetings, you can clarify, add nuance, push back in real time. When decisions get made asynchronously or in meetings you weren't in, the documentation you've created becomes your representation. Good documentation means your perspective exists even when you're not present.
Sharing Knowledge with Your Team Asynchronously
Individual PKM is about capturing knowledge for yourself. Team knowledge management is about making that knowledge available to others without requiring a meeting.
Decision logs. Any significant decision your team makes should have a brief write-up: what was decided, why, what alternatives were considered, and who made the call. This sounds like overhead and it's not. It's the answer to "why do we do it this way?" that every new team member asks and every senior person has to re-explain from memory.
Runbooks and process docs. Any repeated process should be documented. Incident response, onboarding, vendor reviews, security assessments — if you're doing it more than twice, write it down. Not a perfect document, just enough that someone else could follow it without asking you every step.
Async written updates over meetings. When you can communicate in writing, do it. A well-written status update is more efficient than a status meeting. It's faster to produce, faster to consume, and it leaves a record. I push hard for async-first communication on my team specifically because it forces people to articulate their thinking clearly and creates a searchable record of what happened.
A shared knowledge base. Whether it's Confluence, Notion, a Git wiki, or something else — your team needs a single canonical place where documentation lives. Not email, not Slack, not personal notebooks. A place where the whole team can find things. Building and maintaining this is everyone's job, but as a team lead, modeling the behavior matters enormously.
Documentation as a Remote Work Superpower
Here's the honest truth: most people are bad at documentation. They consider it boring, they consider it overhead, they push it off for "later" that never comes. In an office environment, you can get away with this because the gaps get filled by conversation.
Remotely, you cannot get away with it. The gaps don't get filled — they become permanent holes in your team's collective knowledge.
The people who are good at documentation — who write things down clearly, who maintain their notes, who share what they know proactively — have a significant advantage in remote environments. They're easier to work with. Their projects have fewer surprises. New team members they onboard get up to speed faster. Their institutional knowledge doesn't evaporate when they take vacation.
It's a learnable skill and it compounds over time. The knowledge base you build in year one of remote work is more valuable in year three because of everything you've added since. Start now, even imperfectly. An imperfect note that exists is infinitely more useful than a perfect note you never wrote.
Getting Started Without Overwhelm
If you're new to PKM and the whole thing sounds like a lot, start small.
One tool only. Pick Obsidian or Notion or even just a folder of text files — but pick one and commit to it. The tool matters less than the habit.
One capture habit. Daily notes are the easiest entry point. At the end of each day, write down three things you learned or did. That's it. Do that for two weeks before adding anything else.
One sharing habit. Write up one thing per week that your team would benefit from knowing. A post-mortem, a tool recommendation, a process you've figured out. Just one. Publish it to wherever your team shares knowledge.
The system grows from there. Six months of consistent simple habits is worth more than a perfectly designed elaborate system you used for two weeks.
The Takeaway
Knowledge management is the invisible infrastructure of effective remote work. The teams and individuals who do it well are more effective, more resilient, and significantly easier to work with. The ones who neglect it become bottlenecks, single points of failure, and sources of institutional knowledge that walks out the door when they leave.
You are the sum of what you know and what you can retrieve. Build the system.
Next up: Lesson 4 — why working from the same spot every day will eventually grind you down, and how changing your environment unlocks different kinds of thinking.