Benefits
✅ Improves adherence to Roam across the team
✅ Works with any nomenclature for tagging people
✅ Works with any task management system
✅ Slack notification provides customisable context
✅ Easy to set up
One of the biggest challenges of using Roam in a team is getting everyone on the same [[page]] and ((block)) when they need to be. You need to inform people of questions, changes and new responsibilities.
Every multiplayer Roam needs a way to mention other users and should have a way to notify each one. Here's our team's system of notification (thread includes css too)
If the team is trying to achieve explicit goals together, then you need a tight, simple and flexible task management system. I haven't documented ours yet (and it's always evolving) but here is an example
See the cute slack icon? It indicates that this hashtag is associated with a slack user and you can send them a notification on slack.
And whabam
This message format, and the Roam tag -> slack user mappings are specified in roam/js/slack.
To give the notification context you can include the {page}, immediate {parent}, {block} content, and {link} straight to the block in Roam.
To make the notifications informative in *any team workflow* you can specify the tags that structure your workflow (in this case #[[🎯 Objective]] ) and the notifications will extract out these parents too
Of course you don't have to use this for task management. You can use it to notify someone of a change, ask them a question (then if they answer you in Roam it's documented) or just tell them you're thinkin' 'bout 'em you know?
Our team already uses this scores of times a day. Please use it and provide feedback and suggestions! Pls test me on its flexibility.
Very soon @dvargas92495 will give technical details and installation instructions in his announcement.
If you want to know more about running a team in Roam subscribe to my newsletter at roamforteamwork.com
• • •
Missing some Tweet in this thread? You can try to
force a refresh
My definitive #RoamGames submission:
I've drip-fed submissions to the team/task mgmt RoamGames so this thread brings them together into one mega-submission. @Conaw, @RoamResearch
First, the thread that triggered the topic of this very RoamGame. I assume I can submit this? A fun live-tweet creating a new workflow in Roam in < 15 mins (it would have taken < 5 mins if I didn't have to live tweet it)
Second, the big one, my newly released work-in-progress Roam for Teamwork graph building all the lessons, templates and plugins you need to realise The Dream (also contains a definition of The Dream if you need that too)
#RoamGames submission: Announcing the *Roam For Teamwork graph*, a resource for anyone who shares my dream of having an organisation's knowledge base emerge naturally out of everyday teamwork.
The thing that excited me immediately about Roam was how atomic blocks would allow different systems to always reference the same source of truth, potentially eliminating duplication and knowledge loss across different parts of a company.
So I took the steps to move my whole company over to Roam. CRM, tech dev, specifications, discussions, meeting minutes, call agendas, service delivery, customer support, etc. The only thing not on there are icky legal and financial details.
Full disclosure we've been having some performance issues on the platform. Team member made a suggestion that appeared on my Attention page.
So I responded in-place and created the page as I typed with [[Website issues]]
(note notification back and date so it appears as something new on Daily Notes)