You already mentioned documentation. Good! Document everything. Why you chose X method over Y, or this framework over that. This helps later with onboarding and when people want to come up with suggestions, because they can see you already did explore this option earlier on so why bring it up again? Doucmentation really requires a culture of openness and transparency. Some people do not like to work this way,... Source: 11 months ago

You could always upload/embed the pdf as part of a "post" and then use the comments section of the post to discuss. The P2 theme might also be an option as its discussion functionality is better than just straight up blog comments: https://wordpress.com/p2/. Source: over 1 year ago

- Most deep discussions happen on blog posts including project status. We use (and built) https://wordpress.com/p2/. We don’t use email. - Source: Hacker News / almost 2 years ago

Yes it does! https://wordpress.com/p2/. - Source: Hacker News / almost 2 years ago

Actually, Automattic, the distributed company behind WordPress uses blogs for this. Each team has their own 'blog' and you can link them, comment, etc. Then there are company wide blogs with different topics, watercooler blogs, etc. Really useful to refer to revisit past decisions and as a company wide knowledgebase. They even created a product out of it: https://wordpress.com/p2/ Disclaimer: I work there, but on... - Source: Hacker News / about 2 years ago

Admittedly, this is an issue with organization and can be solved with thorough cleanups, but I suspect that may disrupt the usual flow of non-PM people more. I am thinking of using a separate tool like craft.io or productboard.com to highlight strategies, roadmaps, cross-team initiatives, discoveries, etc. With a possible link to JIRA somehow. Has anyone ever tried this? Source: almost 2 years ago

Recently my friend at Productboard noticed an interesting bug in one of our services. For some reason our code responsible for calculating how many days our customers' features spend in certain states (Idea, Discovery, Delivery, etc) in some cases would give us wrong results. - Source: dev.to / about 2 years ago

ProductboardProductboard helps us capture user feedback from email, Slack, Zendesk, our public-facing product portal etc. And see what users need the most. We also use it for prioritizing product objectives, release planning, roadmapping…. Source: over 2 years ago

I use ProductBoard. It's fairly expensive but pretty great. I gather requirements into PB and use the inbuilt editor to flesh them out. When a story is ready I push a button and it ends up in Trello (but you can add your own integrations; there's one for github for example). The integrations aren't perfect but I love it. Used it in my last job and brought it in at my current job. https://productboard.com. - Source: Hacker News / almost 3 years ago