What you actually want to get good at is KnowledgeOps.
Let me explain.
I dislike the term Personal Knowledge Management.
I find it to be limiting and too static. It conjures up images of shuffling around books on a shelf, sorting them for easier access. Important, but not enough.
Instead, I think we should think about the whole process.
In software development the term DevOps describes
"a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality" (Bass et al. 2015)
This is what we actually want.
A process that takes us from learning something new to actually using it effectively as efficiently as possible.
Too often Personal Knowledge Management gets stuck at the note-taking stage. Or even earlier, where we focus on gathering knowledge, ingesting into our PKM system.
But what do we do with it? Too often very little.
We need to shift the conversation.
We need to get better at the whole knowledge pipeline. Gathering knowledge and filtering it. How to store what is relevant, through memorization or writing it down. Retrieving what we know. And then applying it when we make decisions, solve problems, or make sense of the world.
Don't just "manage" your knowledge. Make sure you have a way to use it, too.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Which means selecting the right tools and learning to use the tools right is time well spent.
Your brain doesn't know when you're using a tool.
A sword, like in the movies. A violin or guitar. Your keyboard. The app you're using. Your brain doesn't know. If you know how to use the tool, your brain just...acts and does what needs doing.
Ergo: selecting the right tools and learning to use the tools right is time well spent.
Roam is a fantastic tool for thinking and writing in academia – it excels at helping you to synthesize your literature, thinking through problems and keep your writing on track.
Over the last year, I've taught hundreds of academics how to use it for their research, and the recently launched community for academics, @AcademiaRoamana, has now over 400 members. Interest in using Roam for science is strong, obviously.
So I'm working on a video on context switching, interstitial journaling and related things – things I learned from @ultraworking and how I use @RoamResearch for it now. I'll thread my brainstorming for the video below, feel free to ask questions. #roamcult
We all know that context switching is bad, Maker/Manager schedule etc. Fact is, we still have to context switch all the time, even if we have control over our schedule and work.
Projects take more than one day or block of hours – so you inevitably have to switch "in and out" of a given project. Even if that switch is just between personal life and that singular project.
If you've just recently discovered Roam, and you're checking out the community, things can feel overwhelming. For an app this young, the ecosystem is huge: YT tutorials, courses, extensions galore – plus regular new features in the app.
And on Twitter in particular, you'll often see people discuss the newest extensions, talk the "meta-game" of note-taking and Algorithms of Thought or celebrate the (fantastic!) submissions to the #RoamGames.