Really glad this thread topic was a worthwhile one!
After writing this, I actually almost ditched my plans to go as “all in” as I described in my post above, due to the current limitations of Coda ultimately hindering the effectiveness of the set-up I was trying to accomplish. In the end though, after really deeply testing two other “finalists” ALM/Project Management suites, I realized that these out-of-the-box solutions were unable to handle a lot of the custom stuff Coda can do. So I’ve made the power call, and going to bring my small (12 people) team over to Coda and try to manage all we do here!
As a follow-on to my original post and the great replies from the community, I wanted to share what I’m finding right now the three top items on my wishlist, which if released, would really provide a lot of benefit to me:
Aforementioned inability to link across Docs. As I am moving away from Jira after many years (my team used to be larger), I do miss the fact that an issue can be viewed across the entire app, if permissions allow…and about permissions:
Some basic permissions. I plan to set up several docs, and attempt a one-way API or Integromat sync to a master “Roadmap” Doc I will use to track the entire activity of my team at a management level. I have read a good deal about this in the community and hoping it will worked as planned! But a big help here would be the ability for me to have individual permissions inside a doc. That would ease some of the need to set up multiple docs, which can’t be connected, as I could limit visibility to part of a doc, and thereby build it out more. For example, I have freelance offshore web developers who I don’t want to see my financial (tasks about chasing late invoices, etc.) or HR info.
Ability to lock down a doc. As I move forward, I have fears about docs getting “broken” by mistake. There is a will publicized article that talks about Coda in the context of some other new-age apps, and the author cites this issue:
I would think this is a relatively simple addition to the platform so hoping to see it soon!
and a PS on this article, the author ranked Notion ahead of Coda, but I dissent. Notion has a lot going for it, in particular the amazing design. But actually I find Coda easier to work with. As I tried to set up Notion, which I almost converted my team to instead of Coda, I found it was like a “war” - as the author describes working with Coda interestingly - to configure to get function I was looking for. Also IMHO, I have actually over time found that you guys have a superior wiki to Notion! Every piece of text in Notion is a block, and that becomes difficult when trying to write paragraphs, instructions, Product Requirements, all kinds of documentation. While I think the Coda document capability is limited right now, the fact that you can truly write free-form, embed formulas, etc. makes you guys actually better for documentation at the moment, at least that’s my take!
Really excited to be going full speed ahead now with Coda, and anxious to continue to engage here with this great community!