Person First PKM: Design Your System Around You, Not the Other Way Around

Here is the pattern I have seen repeat itself with enough consistency that I am confident it is not a coincidence. Someone discovers personal knowledge management, usually through a YouTube rabbit hole or a book, reads everything, watches everything, finds the framework that makes the most sense intellectually, and implements it carefully and thoroughly.

For a few weeks, sometimes months, it works. They feel organized. The ideas are flowing into the system and the system feels like it is containing them properly.

And then, quietly, they stop using it. Not in a moment of frustration, they just slowly revert to previous habits. The system persists in the background, increasingly unused, increasingly a monument to the intentions they had rather than the person they actually are.

They conclude they are not disciplined enough. That they are a fundamentally disorganized person. They are wrong. The system failed them. They did not fail the system.

The Tool-First Problem

Every major PKM framework starts with the method or the tool. Zettelkasten tells you how to link notes. PARA tells you how to organize by actionability. Building a Second Brain tells you how to capture and distill. GTD tells you how to manage commitments.

These are all genuine insights. They are not useless. But they share an assumption that is never made explicit: the person using the system should adapt to the system, not the system to the person.

Here is the thing: you are not a Zettelkasten practitioner first and a person second. You are a person, with a specific cognitive style, a specific relationship to unfinished work, a specific kind of energy at specific times of day. All of that is prior to any method. All of it determines whether the method works for you or against you.

Person First PKM begins with that prior question. Before the tool, before the method, before the workflow, who are you, and what kind of system fits you?

The Person Audit

Before designing anything, complete this audit. These questions take about ten minutes. The answers are your design brief, they specify what your system needs to do before you have chosen a single tool.

1. When do you do your best thinking? Specific time of day, specific location, alone or with others?
2. What does a good idea feel like before you can articulate it? A physical sensation? A mood? How do you know one is arriving?
3. How do you know the difference between understanding something and having just encountered it?
4. What is your honest relationship with incomplete work? Does it motivate you to return and finish it, or does it haunt you and make you avoid it?
5. When you have tried to build systems in the past, where exactly did they break down? Week two? Month three? When life got busy?
6. What kind of notes do you actually write versus what you wish you wrote? Be honest. What do you actually produce under real conditions?
7. What is the last idea you had that you actually used? How did it move from capture to use? That path is your natural workflow.

The answers to these questions are the design brief. By the time you talk about apps and plugins, you already know what the system needs to do, how it needs to behave, and what it needs to get out of the way of.

The Self-Portrait Principle

Your knowledge system should be a self-portrait. Not an aesthetic claim, a functional one.

A self-portrait requires honest looking: not the idealized version, not the aspirational version, but the actual subject as they currently exist. A self-portrait that depicts someone else is not a self-portrait. It is a copy. Your knowledge system should work the same way.

If you think in long-form prose, your system should support long-form thinking, not constrain it to atomic notes. If you are a morning person, your system should have a front door that is easy to use half-awake. If you become anxious when organizational structure gets complex, your system should be structurally simple even if that means sacrificing theoretical functionality.

The most important question in PKM is not “which system should I use?” It is: what system would I actually use, consistently, given who I actually am?

Origins, Not Copies

This does not mean other people’s frameworks have nothing to offer. They have a great deal to offer, as inspiration, as scaffolding, as a set of tested solutions to common problems. Mine them for principles, not installations. The principle from Zettelkasten, that connecting ideas produces more insight than filing them, is portable. The exact implementation may not be, depending on who you are.

The best knowledge system in the world is the one you actually think with. And the one you will actually think with is the one designed for you from the beginning. Start with the audit. Build from there.

Suggested reading

Where to Go Next

Continue with the most relevant essays, key site pages, and trusted references.

Read Next

1. 5 Signs Your PKM System Is Working Against You
2. The Complete System
3. The 9-to-5 Architect

Core Pages

• System Blueprint
• PKM Guide
• Obsidian Guide
• Field Notes

Trusted Sources

• Mental Models and UX (NN/g)
• Personalized PKM Design

The Weekly Field Note

Ideas worth thinking about — in your inbox.

No noise. One insight per week on knowledge systems, creative output, and building with clarity. Join The Field Note