[…] we’re finally settling into a very interesting use case we’ll be pursuing next: knowledge-sharing within businesses and organizations […]"
To be completely honest, my first reaction is that I am a bit disappointed 
. That is a huge switch of focus, IMHO. Teams use a blog in a very different way than a blogger would and would stress different features, and collaboration is much more important.
I totally understand that financial stability if the company is of the utmost important, as without it, none of these projects go anyway as people need to be paid and need to live of something 
.
But it feels like you guys are spread too thinly on too many projects. Maybe my thoughts are perceived as harsh, if it comes across that way I apologize beforehand, its not my intention. I just try to describe what I see, as a customer and from an external view:
- The idea of jot.as was floated around and people were asked for feedback, but so far no one if it will be a product or not, with what timeline etc.
- The draft.as project idea came up, and peopler were asked for feedback. But so far no word on the state or a timeline (something like “dont even think about it before Q3 2020” would be totally fine)
- Improvements on snap.as were announced and the services stayed more or less the same (and the idea of having snap.as as a completely separate product have been abandoned if I understand it correctly).
- It was said that write.as would see improvements, people were asked for feedback and thoughts, but so far only two new features (editor, subscribe to posts) have been implemented. I don’t see an official roadmap for new features, only two or three different kanban boards that are linked on different pages and/or conversations, which are very confusing to the external view.
So, I am confused, I dont know what to expect, a (maybe even revised) vision statement would be great, and I would love to have some clear communication, with a rough roadmap and intended features for each project. If some projects wont be implemented this year, or next, that is fine. Sometimes stuff happens and projects need to be shuffled around, some might turn out unfeasible etc. But communication is key here in my opinion.
If Santa would grant me one wish, I would ask for a simple roadmap.write.as or stateoftheunion.write.as page with a quick status for each project (maybe, “In Development”, “Idea”, “Done” and a sentence or two), with a list of features that you want to implement, maybe even with a rough estimation ("Feature XYZ – Est. Delivery Q3 2020). That page would have a “Last Updated” timestamp and it would get reviewed every quarter. That would be neat!
I hope that I can look back a month from now and I will think “Damn, your first reaction was totally wrong”. We will see. I will stick around till my subscription ends in November.
No bad blood or bad intentions or anything, maybe its just not a “match” when it comes to expectations. Maybe it is a case if “it’s not you, it’s me!”