The enterprise messaging war is well underway. First Slack and Atlassian Hipchat battled it out, with Slack reaching escape velocity. Then came major entrants Microsoft Teams, Cisco Spark and Facebook Workplace.
My bet is Slack will continue it’s unprecedented growth, grow it’s ecosystem and be favored by best-of-breed shops for text, voice and video conversations. They are just now moving up market with an enterprise version, and global with their first localization.
This week is Slack’s first annual conference, and on the other side of Silicon Valley is Atlassian’s. Last week in a pre-emptive announcement, Atlassian launched a new messaging app, Stride, for round two against Slack.
Stride offers a modern UX that other Atlassian products will upgrade their interfaces towards. This week they will likely highlight integration opportunities for the 3rd party ecosystem, that they are likely building upon themselves. And 3 key features to help with the signal to noise problem.
The problem with most messaging apps, and I know from creating Socialtext Signals ten years ago, is they work so well. The team gets engaged, questions get answered and knowledge sharing happens. But people get overwhelmed with information and interruptions. Stride works to reduce overload with tasks, decisions and focus mode. Tasks and Decisions are pulled out of the stream and given their own structure. Focus mode let you disable notifications while telling the team know what you are focusing on instead of them.
Pingpad for Slack solves this problem. With a reaction, you can turn a Slack message or thread into a task or a decision. And the bot and web app help you not only manage the workflow across the team, but visualize it with Pingpad Boards.
Let me illustrate how you can manage Decisions in Channels specific functions like Product, Sales, Marketing or Operations. For example if you have a Channel to discuss technical #architecture. Create a List called Decisions. If the decision is made in a message in Slack, simply capture it using the Pushpin reaction, and then add it to the Decisions List, like this:
Capturing Decisions from Slack in a list in a single Channel to Pingpad
Some decisions need to be more than a message, so you go to Pingpad and write it up in the collaborative document editor. You might create a Note Template that provides the structure for how a decision is documented (see Documenting Architecture Decisions). When it is ready, put it in the Decisions List, and then click the Share to Slack button to communicate with the team.
Today we’re launching a new capability to help people bring focus to work conversations in Slack. To try Pingpad for free, visit Pingpad.net and Add it to your Slack Team
(Cross-posted @ Medium | Ross Mayfield)