Through my coaching and courses, I’ve had the privilege to work with lots of @RoamResearch users over the past 6 months. I’ve noticed their difficulties tend to fall into one of two categories: 👇🧵 1/
Either
1. They know what they want Roam to do for them but they don’t know how to make it happen, or
2. They understand the fundamentals of Roam but can’t find useful ways to harness it in their own workflows. 2/
And many, if not most, new users struggle with the graph-and-nodes concept of Roam vs. the forced hierarchies of apps they’ve used in the past (e.g., Notion, Evernote). If you’ve ever asked yourself “But where do I PUT this note?”, then you know what I mean. 3/
I've been grappling with something two of my clients—who collaborate together—said during a coaching a few weeks back. "Writing for a collaborator is great, because it has to be clear—and writing for your future self in a Zettelkasten has to be just as clear." 👇 🧵 1/
A Zettelkasten (henceforth "ZK") is a system to take in knowledge, develop it, connect, combine and compound it, and publish it in some form. The mechanism for processing the knowledge is a conversation with your ZK—effectively a conversation with your past and future selves. 2/
For years, I've coached that productivity is communicating with yourself. Leaders and colleagues recognize that clear communication is central to effective collaboration, but we are almost NEVER clear with our future selves. And that keeps us from getting important stuff done! 3/
If you're new to Roam, or just need a refresher, here's a thread on what that means. 1/
1. "Content dictates form." This is a favorite quote of mine from composer/lyricist Stephen Sondheim. Roam helps you discover the shape of your thoughts rather than imposing a shape on them. 2/
2. @RoamResearch has no "rules" (that I know of). But if you follow a few best practices, your simple input will yield surprising insight.
- Use [[pages]] to identify important topics
- Use indenting to structure ideas
- Use block references to "optimize" specific thoughts
3/
When I first started using @RoamResearch, I struggled to find a good workflow for writing multiple drafts. This 10-minute video shows the solution that works for me. It combines tags/filters, versions, focus on block, and more!
The key to this writing workflow is differentiating "brainstorm" & "organize" passes from drafts.
I want brainstorm & organize passes to always be accessible. But I want drafts to be version-controlled.
@RoamResearch makes this simple. For early passes, I use separate blocks: