How 20k People Use Tettra and Slack to Build High-Performance Teams

Kristen Craft
October 23, 2018

This October marked an exciting milestone for Tettra and our amazing customer base: we now have over 20,000 people using the Tettra-Slack integration. Ever since launching the integration in February of 2016, countless customers have shared feedback on how it makes information more findable and teams more efficient. This also excites us because it validates two key hypotheses about how people work:

  1. Teams want to collaborate and cooperate in new, more nimble ways, and they expect the products they use to accommodate these preferences.
  2. The old school notion of a wiki – one that lives on an island and rarely changes – is ineffective; documentation works best when it’s connected to the other tools a team already uses, especially since the number of tools continues to grow.

How People Use Tettra and Slack to Work More Efficiently

Documentation – like most things worth doing – isn’t a “set it and forget it” process. It’s something you invest in every day. The result is that you have the right information on hand if something goes wrong, when you need to grow your team, or if you simply want to avoid repeating yourself over and over. Therefore, it behooves teams to keep their documentation front and center.

With the Slack integration, teams easily keep a finger on the pulse of what others are working on, when a process has changed, or when new knowledge is shared. All of these updates are pushed into the relevant channel in Slack.

Searching becomes easier as well. We see an ever-increasing number of teams using our search command in Slack. This means they can find info that lives in Tettra…without ever leaving Slack. They can access this info privately or share it with the team…again, without ever leaving Slack.

Suddenly, the dissemination of info across a team becomes less daunting and more efficient. When you layer on current workplace trends (like the rise of remote work, gig economy contracting, and time zone differences), it’s even more important to keep this finger on the pulse via Slack.

This desire to keep up with the latest info shows in our numbers over the last month:

  • 3,550 people actively engaged with the integration in a meaningful (ie not passive) way
  • Almost 4,000 Slack notifications were sent to alert people about recent changes in their Tettra accounts
  • People searched via Slack for information stored in Tettra 2,500 times

When you think about the time it normally takes to find a lost document or to re-explain a process, these numbers add up to thousands of hours saved. We’re honored to have such an impact on the success of our teams and their ability to function in a high-performance way.

How People Will Use Tettra and Slack in the Future

In general, teams rave about how much easier their work lives are, thanks to Slack. Sometimes, though, teams want to iterate on, and update, information that is shared in Slack, a feature that Slack doesn’t offer in its core product. Important information – whether it’s a decision, a URL, or a process – is shared in Slack and needs to be updated regularly, and be a bit easier to find than all the other information shared in Slack.

In the future, we expect to see more people leveraging Slack and third-party apps together to solve this issue and make their teams more efficient. We ourselves use this integration many times per day, every single day. We also “elevate” info in Slack by pushing it into Tettra. Among these 20,000+ Slack users, we see similar behavior: people use the integration with Tettra to log information that comes up in a Slack conversation. This behavior signals a differentiation between ephemeral and evergreen information. People use these third-party integrations like ours to pass information back and forth, ensuring that the right info resides in the right place.


Ephemeral content is information that you likely only look at once. It’s content that someone is unlikely to need to share again. Teams produce a lot of ephemeral content, some of which is important, and some of which isn’t. It’s perfect for Slack, and (in most cases,) it’s not worth documenting somewhere central like Tettra. 


Evergreen information tends to be viewed and reviewed multiple times (by the same people or when new members join the team.) This kind of information isn’t set in stone, but it’s probably not changing every day or multiple times per day. Evergreen content benefits from living in a centralized place like Tettra, so that people can find, review, comment, and add to it. Our community of users has leaned into this integration because they can more easily elevate information and then leverage it from Slack later on.

Shepherding in This New Framework

We hope to make it easier for teams to understand this distinction, so they can communicate and cooperate more easily. As people come to embrace the distinction, they’ll need to pass information back and forth between Slack and Tettra. We’ve already simplified the process of passing info from Tettra to Slack. Now, with Tettra’s newest feature, leveraging Slack message actions, you can pass information from Slack to Tettra without context switching.

We leverage Slack’s message actions to help you turn any Slack conversation into a Tettra page suggestion. These message actions bring in all of the flexibility of Tettra suggestions: you can assign the suggestions to a person, choose a category, and leave extra detail for context. As Slack says, “nothing gets lost as you go about your day.” Any noteworthy decision, process, or piece of information that’s shared in Slack now has an easy path to being documented in Tettra.

Slack has made it easier than ever for teams to communicate. Tettra is trying to make it easier for teams to cooperate. With our powers combined, there’s no limit to building a high-performance team.