Read on Twitter
#RoamGames A few different problems that people have when learning to use @RoamResearch:
1. BEGINNER / The intimidating blank page: "Where to start?"
1. BEGINNER / The intimidating blank page: "Where to start?"
2. NOVICE / The long delay between input and output: "People seem to love the product, but I don't quite understand why. Am I doing this right? How do they use it?" https://twitter.com/kenakennedy/status/1357278455516327937?s=20
3. INTERMEDIATE / Learning better workflows: "I like Roam - I wonder if I could get more out of it? What are my peers doing?" https://twitter.com/adam_keesling/status/1206334375064850434?s=20
4. EXPERT / Optimizing via new features: "{{[[∆]]}} feature just launched. How could I use that?" https://twitter.com/Colby95113256/status/1302275362395574273?s=20
It seems that the size of the problem (but should be confirmed by metrics): BEGINNER > NOVICE > INTERMEDIATE > EXPERT.
In other words, helping people get started and get their first "aha" moment is critical.
In other words, helping people get started and get their first "aha" moment is critical.
The key design challenge: How to find out what problems Roam could solve for that *specific* user? And then helping them solve at least one of those problems as quickly as possible. https://twitter.com/OlliTiainen/status/1357264257151287296?s=20
See also this great thread here: https://twitter.com/EshanKhadaroo/status/1356999953768407045?s=20
