When teams write together, users win. Learn how to collaborate quickly within your documentation. With Confluence, your team can work together to write internal documentation — like user stories and upcoming product feature overviews — in an area that's not publicly accessible to users.
You can write the documentation intended for users and then publish it. The best part is there are no silos. If you need to write about a product architecture enhancement, you don't need to bug an engineer to email you the diagram and document with the notes, you can just search for it in Confluence and start writing. And with space permissions, teams can easily lock down content as needed, so people only have the ability to make edits if they need it.
The best documentation spawns from a conversation. Often the conversation starts around a user story, but tends to continue throughout product development and testing. Use comments to keep the conversation as close to your documentation as possible, so nothing is lost whilst you collaborate on documentation. 
Writing your docs together with a teammate is a great way to improve your writing skills. With pair writing, you and a teammate give instant feedback on the content which helps you to produce content rapidly.
Conversation between your team can be a great way to collect feedback and iterate from it, but what about your users?
By collecting user feedback from your customers, your knowledge of that audience increases which can make you a valuable asset on any project team, allowing you t ...
As your team works together, having an automated workflow will allow you to follow a consistent process for writing, reviewing, and publishing your Confluence documentation.
Give Team Feedback
