Most of the productivity discourse seems to be about top-down planning
Most how we think and talk about project management is in that paradigm too
My focus is on bottom up project management:
Breaking things down into ever smaller pieces - then exploring how they fit together
I find that when folks try to organize big projects in @RoamResearch their first instinct is to try to use kanban boards and lots of pages to approach things in this top down way
The real connective tissue of big projects is the block reference though.
I'm a big fan of writing down what I plan to do, and how I plan to do it (in detail) before I get going.
Why?
Because sometimes I realize as I am halfway through writing things out that there is a fundamentally better approach
then I can skip a ton of needless work!
Folks have asked for more videos of how I use Roam - here is a VERY concrete example - you can ignore the technical details of the problem I'm working on and might still find helpful.
Uses #.Falsified tag + one line of roam/css to crossout work I avoided
My guess is there is a way we could have a public intro db that published via a roam-inter channel - and what it published fed a choose your own adventure tutorial
@cortexfutura's tutorial is great - but it's not like we want to start the user's off with a JSON export -- would be way easier to start them with a single block that "channelled" into a help graph
(we could also always iframe + have easy copy action)
Other thing I was imaginging when I heard the idea of @cortexfutura's submission but hadn't seen it yet -- if the smart blocks listened to their sibling blocks and needed you to complete some action before they could be activated.
What shocked me here were two things - even though I hinted this was a likely winner, only two (+ me) put forward anything that I could see as "riffing" on the idea, or nudging it forward at all.