Conversation

I was surprised to see such a negative reaction to this exchange - but I think I see something pretty useful here, and it seems worth sharing while it is fresh - so at risk of further derailing my day... Why I said "No" to Roadmaps And why the right response was [[Yes and]]
Image
Quote Tweet
Replying to @TfTHacker and @RoamHacker
I love you @roamhacker, but you’re absolutely wrong - right now. I’ll let you know when that changes. Sorry to have to disappoint.
9
41
Replying to and
Fwiw, this is one of the things I think you’re doing very right. Roam is an odd beast: consumer infrastructure. Only precedent is Excel. Build up potential energy, let kinetic energy flow as it will, pave cowpaths. Roadmaps are for things that solve pre-defined problems.
2
41
Replying to and
Trying to process this - help me out if you have a moment. Here are two examples of potential "roadmap" items some of the community is looking for reassurance around - improved security, and a better back end. What should the posture of a Roam user who "gets" it be?
1