Member-only story

Confluence, a wiki that will make people collaborate on documentation

--

Why do you care?

A very common discussion within organizations that do software development is what tool to use for documentation. Developers are usually pretty opinionated about that, if only because they want to ensure nothing gets in the way of doing the thing they love most: coding. Other people just want to be able to write down their notes and being able to find them back. Although I love coding, I also really care about being able to track my notes and my breakdowns, but more importantly, to capture architectural decisions, development guidelines, and share technical information through internal blogs.

But this seems to be a hard problem to solve. For example, do you recognize some of the below symptoms?

  • Documents can be found in Microsoft Word, PowerPoint, Miro, SharePoint wikis and Azure DevOps wikis
  • People use PowerPoint to capture notes during meetings.
  • You’ll find Word and PowerPoint documents all over the place, including OneDrive, folders within Microsoft Teams, local machines and SharePoint.
  • Unless somebody remembers where a document is, there’s no central place to find stuff.
  • People are sending around copies of those documents over e-mail.
  • Miro is used for structural documentation, because it’s the most versatile tool they have.
  • Everybody is continuously asking…

--

--

Dennis "The Continuous Improver" Doomen
Dennis "The Continuous Improver" Doomen

Written by Dennis "The Continuous Improver" Doomen

Dennis is a veteran architect in the .NET space with a special interest in writing clean code, Domain Driven Design, Event Sourcing and everything agile.

No responses yet