Internally, we organize and share knowledge via a tool called Nuclino. Think of it as our team’s collective brain.
In the comments of an earlier post, you may have seen Dave advocate for documentation as a way for us to be accountable to each other. Right on! I would add that it’s a way to be accountable to all future employees as well. We’ve all walked into situations where the documentation was lacking or entirely absent – it’s inefficient. Sometimes, it’s pretty damn annoying!
Dave introduced John and me to Nuclino back in June because we wanted to document the sometimes confusing status labels the system uses for businesses. You’ll be stunned to know that we have labels for In Progress, Pending, Rejected, Active, Inactive, Suspended, and Expired. They all mean something different!
We’ve been building our knowledge base ever since. Most recently, Dave created demo accounts for the sales team and documented the details in Nuclino. The next time we need to create a demo account, the information is here to make the process easy!
If you’d like to contribute something to Nuclino, just let Dave know and he’ll set you up with an account.
Update
In September of 2018, we moved all of the documentation to Confluence (sample screenshot below) and closed our Nuclino account. Most if not all of the documentation was a resource for the dev team, both locally and in Sri Lanka, so it made sense to centralize in Confluence, a collaboration tool designed for dev teams. And since Confluence and JIRA are both Atlassian products, this had the added benefit of allowing for integration between the products. For example, many issues in JIRA reference documentation in Confluence and many pages in Confluence reference issues in JIRA.
Very literal LOL