Confluence Reviews

We use Confluence across our organization. We all work remotely so it is a place where we can collaborate on projects, we post our meeting agendas, we post tutorials, training, etc. Any content that employees need to access to do their jobs we put on Confluence. For example, we can put processes on how to complete certain tasks on confluence and we also task each other to complete certain items.

Confluence is being used at my organization to track action items, high level requirements, and decisions that are made in meetings.

Confluence is used by the whole company as a repository for managing and storing business information. It is a central repository for information that we all use on a daily basis to record ideas, communicate and coordinate product releases and manage business requirements for our development process. We also use Confluence as a way for the tech team to communicate with the business and marketing departments in the company.

We use Confluence as a place to document all our I & O help articles and processes. We also build web pages for developers to use a quick reference point to look at test data and test environments. Also starting to build project requirements into these sites for IT and business teams to view and use.

Atlassian Confluence is being used as a knowledge base for our entire organization. The software enables our staff to share knowledge easily, across our different offices around the world. We have created different sections of the knowledge base, so each department has their own "area" if you will on the platform, where staff from each department can post relevant information company-wide. This avoids the redundancy of emails and creates a database of company information, as well as shared knowledge.

We use Confluence to support internal documentation needs. It provides a version controlled, access manageable, configurable repository of knowledge and documentation for the company. It facilitates indexing and search of the document database for quick access to information. We use it globally in the organization as a clearinghouse of information on everything from technical procedures to organization charting.

For years, our organization was using a mix of Word documents on a file server and files in SharePoint, none of which were synchronized, most were out of date and nobody knew where to look for any one document. Enter Confluence. We were able to migrate all of our old documentation to Confluence where it's easily managed, searched, and updated. The live-edit feature is especially great as we're building system documentation or pulling together meeting minutes. We started with a pilot program of one department to see how efficiently it works but have since rolled it out the enterprise as our standardized documentation tool. Every department and project can now easily update, review, and publish documentation in a securely, and centrally accessible tool. It's the perfect combination of a document repository and wiki site.

Up until recently, my only interaction with Confluence was through clients that used it. I would typically access designs or mock ups within Confluence. Internally, we have used Jira for a long time, but always used other tools for project asset organization/reference. We made the move to Confluence within the last couple of months in order to make things easier to between project management and asset organization as Confluence and Jira work directly with one another.

At my current company different teams have some freedom to choose organizational tools as they see fit. I have used Confluence for the most part of the year, as part of a new product development engagement in the software engineering department of one of our consumer brands. In this particular project it is used as an agile communication and collaborative documentation tool.

Atlassian Confluence has been instrumental in documenting the evolution in our business practice in a wide variety of topics. We use it to disseminate information ranging from HR, to technical knowledge sharing, to procedural administration. Associates of all levels use it to share, learn, publish and research as well. The front end is easy to use and the customization abilities allow for a professional look that is appealing to readers and contributes to a positive user experience (UX).

We (stake managers who write stories for the development team) use it for creating the backlog for the development team and the development team uses it for managing sprints. The interface is very intuitive, so even users with no experience or knowledge of the process can easily understand it. Confluence helps us prioritize different development tasks from the business and revenue standpoint and we can also track how successful our dev team was in each sprint, which makes estimation of the following sprits easier.

Confluence is used as a wiki in our backend when multiple users need to see information or [to] update pages.

Confluence is being used as a source of documentation across many areas of our company. I am in the technology department, so I use it mostly with our technology products. It helps share documentation easily across our company.

Confluence is being used in our organization across marketing, sales, enablement and the executive team. It is currently being used as a data repository for marketing materials and sales enablement materials. It serves as a place where my team members can add in work, comment on documents, and collaborate as a team. When new hires come on board, Confluence provides a history of the projects and the work that has already been done.

Our company was always ok at documenting, but not consistent and we did not have a place to collaborate and share. This meant that documents were being created multiple times and in silos. With Confluence we have become better at documentation and sharing information. We also took time to plan out how we wanted our spaces to flow and what information belong where. For example, instead of every department having their own set of documents we found that having a client space and a landing page per client gave us a streamlined approach to organize.

Confluence is being used across our entire organization as an information hub. It creates a shared space that all departments can access. Previously, it was difficult to find one central space to share files, meeting notes, and general information. Additionally, departments were hiding information in places that other departments couldn't necessarily access so it was hard to find information across departments. Now, we have a centralized location where information lives and that the whole company can efficiently access.

Confluence is used to collect all knowledge articles, meeting notes, ideas worth sharing and so on. We also use it a lot to generally describe new features, collect feedback and refine the general spec of the feature before taking it into action. It helps a lot, mainly in centralizing all the "scattered" information in the company under one, simple, framework.

Confluence is used throughout the organization. We use it as a documentation repository, for everything from software designs, to customer contact information, to public-facing company documents, to holding the recorded videos of meetings. Confluence allows us to organize the documentation for all of the various groups in the company and to collaborate on designs for our products.

Confluence is used by our organization to collect process documentation, general knowledge, build notes, WebEx and PowerPoint presentations, programming notes and so on. It's a great way to gather a bunch of loose data under one umbrella. It's also integrated really well with JIRA and makes hopping back and forth simple and efficient.

Confluence was used by the entire organization to track product development for a team using agile scrum methodology. It was used solely for this purpose, although I've previously used Confluence for Kanban, support ticket tracking, and wiki/documentation.

Confluence is primarily used for our Information Technology staff, along with non-IT users that are heavily involved in our programming, development, and design processes. We use it for a few major categories:

• Internal IT documentation and notes
  
• Project/meeting notes, agendas
• Collaboration between IT and many non-IT areas

A number of staff use the "Personal Space" feature for their less formalized notes, plans, etc.

We use it instead of Sharepoint or some other technologies we have access to as it provides a great and easy to use place to collaborate, keep notes, and keep organized.

Note: we did not use or attempt to use any integrations with Outlook, Google Hangouts, Gotomeeting/webex/etc., so any questions I answer saying Confluence does not have them isn't necessarily accurate (there is just no option on Trust Radius to say "don't know").

I'm currently working at Velocity Partners, an off-shore company based in several countries and we provide custom development services to US companies. Our main added value is being agile, and being agile requires the right skills and the right tools. Confluence is for most part the best agile tool I have worked with so far. It provides a way to place documentation in one unique place making it available for large distributed teams. This tool has great integrations with other tools of the same family like Bitbucket and JIRA.
Most importantly, you are not forced to only use the Bitbucket family tools but it provides ways to integrate with different third party platforms. If you are a team manager you can gain access to metrics that allow you to know at every time who's working on what. Assets like documents can have a versioning control.

We had been using an tool built in-house that we referred to as the Knowledge base. Each department had their section and pages in there that were constantly used for reference. The problem was it became out-dated quickly and it wasn't very intuitive to use. We were very happy with Atlassian's Jira product, so it was an easy sell because there are so many hidden gems, templates, etc. that they include. We transferred all of our information over. Then we started using it for storing additional team information and then we started using it to share and collaborate on documents. Now we each have our own space and use it quick frequently as a needed resource for all processes.

We use Confluence across the entire organization as a knowledge base, as well as internal web space for individual teams. We also use JIRA and have integrated the two. This is helpful in that we can link JIRA projects with a wiki, assign tasks, etc.