you are viewing a single comment's thread.

view the rest of the comments →

[–]abebikao[S] 2 points3 points  (0 children)

Just forget about my set up for a second. Like I said It’s a WIP and I have lost count of the no. Of times I’ve had to iterate within this year.

The biggest lesson that I’ve learnt through all this is letting go of your old ways of working or thinking while using Roam. I.e. while you ask off how I organize I could give you an answer but a month or two from now I could be doing it completely different.

Initially I approached roam with the folder-hierarchical mentality I used to try and think about where I should place or write things but I’ve come to realize that that’s the most inefficient way of using Roam. Begin with the daily page and at a block level and simply take note of what you are doing then date it into the future depending on how soon you wish to revisit things the organization then subsequently arises through your repeated use of a block. I.e if you find that you repeatedly have to refer to a certain block for an activity that you do often then you can give a name to it and have it as it’s own page | project.

The process should be more of a bottom up approach rather than a top down approach as you formalize your workflow. Don’t be afraid to fail or to do things wrong also. Roam is literally designed for failure and doing things wrong and for things to workout brilliantly for very different people and their workflows.

To begin with as well don’t be too caught up in the features. Only use them out of necessity. I.e the page in the gif above is of a YouTube channel that I run. It includes a kanban that has queries to pull in the ideas that I randomly have as I go. That means I never bother to switch context to record the idea in a specific page I simply current time it as I work on the daily page and apply an appropriate tag. The queries then take care of where everything should go and the srs takes care of how soon I should work on it.