Coda by Grammarly vs. ProdPad

Coda is great to build a place for your users to go to and see information. It is easy to navigate through and the variety of content creation is great. However, it is not always easy to create what you want and there is a lot of playing around and learning. Coda also sometimes misses some functionality which is expected. For example, downloading a list of users that have access to the platform. Being able to send push notifications when a new page has been created etc. Overall it is a good tool to use just be prepared to invest time!

Incentivized

We use ProdPad to capture notes from our sales team within our CRM and then integrate them into our product roadmap. Our product development team utilizes the application daily to track progress, make comments and notes on new ideas, and to visualize progress.

Incentivized

• One source of truth: It's incredibly easy to keep everything organized and easy to find.
• Being able to show different views of the same information throughout your doc makes it really easy to customize the information.
• In general, I love the "coding" aspect of it, and being able to do advanced functions has helped us create some really interesting automation and streamline our process.

Incentivized

• Customer feedback collection and classification.
• Push user stories as issues to GitHub or tickets to Jira or items in a Trello board.
• Present a clear and easy-to-use roadmap to users internal or external at the organization.

Incentivized

• "Barrier of entry" is a little high for those who do not have any database experience.
• More out-of-the-box integrations with other applications would be nice.
• Performance for very heavy loaded/traffic documents could be improved.
• Scalability for enterprise level customers and doc loads could be improved.

Incentivized

• The linking of fields between ProdPad and Jira isn't ideal, and leads to some duplication.
• The use of real estate on the Release view could be improved.

Incentivized

Coda is definitely something that has been proven to drive positive impact in our organization. We have many divisions that can benefit from this that we have yet to explore. It would definitely be worth renewing.

Incentivized

There is a little bit of a learning curve on where to point and click to add in different elements and make edits. But it is still very manageable once you get the hang of it. I do still have some issues with some of my connected pages updating each other when I don't want them to sync. So I'll end up editing one page, and it will make the same edits on another page.

Incentivized

So far in the past year, we haven't had situations that Coda has gone down for us which is great.

Incentivized

We haven't done any integrations - the initial part of our experience we found that for docs with complex formulas, the page tends to load slowly but in recent months, Coda has improved and optimized the loading times in general and we generally don't find any problems in terms of speed anymore.

Incentivized

Mainly due to timezone differences. I think Coda's support in general is well implemented and executed. They know their stuff and are helpful. But since I'm not in the same timezone, solution rates are slower for me, and that's not something I prefer. I work in customer service, too, and more often than not, time is important. Shortening the solution time would be a much greater experience.

Incentivized

We've never had any issues with support. They have always been helpful and timely in responding.

Incentivized

I'm relatively inexperienced but this experience is meaningful. It would have been nice to have some guidance from Coda so that we understood more on Coda's purpose and potential.

Incentivized

For general use cases, Google Docs or Airtable are often a better starting place. But if things get complex or you're constantly pairing the two together, consider graduating to Coda to save yourself long-term headaches. Notion is great for personal use, but the powerful automation and collaboration features in Coda make it a better fit for teams in my experience so far.

Incentivized

We were just capturing ideas in an Excel workbook, but that forced ownership to a single user for changes and updates and there wasn't any direct integration with project backlog. We actually didn't select ProdPad, a new VP came and brought it with him because it worked so well at his last place. Everybody here jumped on board, though.

Incentivized

I think scalability is definitely good here since it's based on number of doc makers. Implementation into each dept becomes simpler. That being said, due to the nature of our work, we find it easier that we have a "super user" and then a team of other doc makers. This would make the doc creation and management more efficient.

Incentivized

• Increased insight for all stakeholders involved--both in terms of overview and details
• Better grip on issues and escalations--reduced friction, confusion, and higher clarity on status, next actions, and ownership.
• Reduced time required by those who need to maintain all information. Record (a detail) once and use multiple times.

Incentivized

• Using ProdPad has helped our Product team avoid becoming a black hole for feedback and feature requests. This tool helps us be responsive and communicative about the data flowing into the product.

Incentivized