How Playground XYZ encourages team engagement in knowledge sharing

Playground XYZ’s previous team wiki went quiet because using it meant leaving Slack for a web portal. Scot Liddell, then COO, chose Kipwise after testing several tools, for its Slack integration and for features that help managers get people using it. If your team lives in Slack, we recommend testing two paths before you buy a wiki: Slack message to saved page, and question to answer. If either needs the web app, expect the wiki to go quiet, as it did for them.
Playground XYZ was a mobile creative ad-tech company that connected publishers and advertisers (GumGum has since acquired the company). Its headquarters were in Sydney, with offices in Melbourne, New York, Los Angeles, London and Singapore. Spread across six offices and time zones, the team needed one place where teammates could find answers without waiting for someone in another office to wake up.
The previous wiki solution did not work out for them
Playground XYZ relied heavily on Slack for team communication. Their previous wiki also had a Slack integration, but it supported only limited functionality, and for many actions they still had to go to the web portal. Gradually, because of the extra steps, teammates abandoned the wiki. No one contributed knowledge, and no one searched before asking the same questions over and over again.
Why Playground XYZ chose Kipwise as their team wiki solution
Scot knew they had to find a solution that fit their workflows better, so that teammates would actually use the team knowledge base. After testing several, he and his team chose Kipwise, and he named two reasons.
The best Slack integration among all tools they tried
“Among all the tools that we tried, Kipwise definitely has the best integration with Slack. It works very well with our existing workflows,” Scot said.
Saving important information from Slack to Kipwise is simple: when teammates discuss something important in Slack, they turn that message into a Kipwise Page in a few clicks with a Slack action. Retrieving it is just as easy, since a slash command searches Kipwise directly from Slack.
Features that help managers encourage usage in the team
Teaching teammates to use Kipwise is simple. Scot only needs to show them the Kipwise search command in Slack, and Kipwise’s smart features close the loop and guide them in building up the knowledge base together.
If teammates cannot find what they are looking for, Kipwise prompts them to create a question and assign it to a channel or a teammate. When someone answers, the Q&A is saved to Kipwise automatically, so the knowledge base grows.
If a teammate forgets to search before asking a question in Slack, Kipwise gives managers like Scot a way to answer it with content from Kipwise in a few clicks. These replies often happen in public channels, so other teammates see them too, which reminds everyone to search before asking a question that may already have an answer. “A little public Slack-shaming goes a long way to changing behaviour 🙂,” Scot said.
We recommend copying the mechanism and skipping the joke. The public reply works because the answer arrives at once with a link to the page, so the person who asked gets what they wanted and learns where it lives. A reply that only says “search first” gives them nothing and is likely to push questions into direct messages, where nobody else can see the answer.
.jpg)
.jpg)

