<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Kipwise - Medium]]></title>
        <description><![CDATA[Team knowledge sharing tool built on Slack - Medium]]></description>
        <link>https://medium.com/kipwise-blog?source=rss----554f1a4cdf58---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Kipwise - Medium</title>
            <link>https://medium.com/kipwise-blog?source=rss----554f1a4cdf58---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:52:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/kipwise-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introducing team annotation for articles shared in Slack]]></title>
            <link>https://medium.com/kipwise-blog/introducing-team-annotation-for-articles-shared-in-slack-c652717604cd?source=rss----554f1a4cdf58---4</link>
            <guid isPermaLink="false">https://medium.com/p/c652717604cd</guid>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[knowledge-sharing]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[product-updates]]></category>
            <dc:creator><![CDATA[Amanda Wong]]></dc:creator>
            <pubDate>Fri, 04 May 2018 08:54:59 GMT</pubDate>
            <atom:updated>2018-05-04T08:54:59.088Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*V7TB25dUWbTJdAdxfh8RxQ.png" /></figure><p>Kipwise’s vision is to <a href="https://medium.com/kipwise-blog/we-build-kipwise-to-help-teams-learn-better-2a213aa48c33">help teams learn better</a> and enable a better knowledge flow within the company.</p><p>In this era where “Content is king”, there are lots of useful resources in the form of online articles, so we ask ourselves — how can we help teams digest and organize useful knowledge from these online treasures?</p><p>We spoke to many teams and discovered</p><blockquote>one <strong>major problem</strong> that many teams experience when sharing good-reads with teammates is <strong>low engagement</strong>.</blockquote><p>And they also expressed that</p><blockquote>it is often very difficult to locate a previously shared article as the search function in Slack basically covers the title only so it’s hard to remember the keywords.</blockquote><p>With the goal to solve the above two problems, we designed a team annotation function where our Slack bot can smartly detect if a shared message contains any article link so we can help you 📎 clip the article automatically. Kipwise will also turn it into a collaborative version so your teammates can highlight the key points 📝 to help other teammates digest the article faster and add notes to encourage discussion around the article.</p><p>It has been 3 months since we launched this team annotation function and we discovered</p><blockquote>Articles with annotations has 4X engagement rates 🚀when comparing to articles without any annotations!</blockquote><p>Generally, teams said that their #good-reads and #knowledge-sharing channels have become more vibrant since they started using Kipwise. Teammates can now digest the shared articles more quickly and it is much easier to find useful articles shared before with our powerful search function (our search covers text <em>inside</em> the article and notes as well)</p><p>Below is a short video summarizing how our article annotation works on Slack:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FbOqQuB3oX40%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DbOqQuB3oX40&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FbOqQuB3oX40%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4a04706da838aebc02d5dccb742c44ce/href">https://medium.com/media/4a04706da838aebc02d5dccb742c44ce/href</a></iframe><ol><li>A teammate shares an article in Slack → Kipwise can detect that it is an article and will turn it into a collaborative version automatically.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ckQEXQ5Lp5KeS3Itp83T3Q.png" /></figure><p>2. Your team can then collaborate on highlights and notes. If you want a specific teammate to pay attention to the annotation, <strong>you can mention your teammate in the note</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b38X3Bsn0o3ri7GUkf9PIw.png" /></figure><p>3. All the annotations will get synched to Slack so they won’t go silent and encourages teammates to continue with the discussion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pZSqfQ399ayDp02wiAKJqg.png" /></figure><p>4. All articles will be neatly organized on our online dashboard (you can add tags easily in the Slack interface). You can also 🔎 search for saved articles in Slack using the command <em>/kipwise search [keyword]</em>.</p><p><em>*Our search is very powerful and cover text inside the article and notes.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cOSTF9pbg_krrrhMzVL3Bg.png" /></figure><p>Our next step is to support more knowledge formats, such as image annotation, video annotations, clipping Slack conversations and a freestyle wiki editor so teams can manage more knowledge formats using Kipwise to enhance their knowledge sharing flow.</p><p>🔽 Haven’t tried Kipwise yet? <a href="https://www.slack.com/apps/A7W497ADD-kipwise?page=1">Install Kipwise from Slack App Directory</a>!</p><p>✉️ Have any suggestions on what knowledge format Kipwise should support next? Email us at <a href="/service/mailto:support@kipwse.com">knowledgeispower@kipwse.com</a>.</p><p>Note: The first three letters in our name Kipwise stand for <strong>Knowledge Is Power.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c652717604cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kipwise-blog/introducing-team-annotation-for-articles-shared-in-slack-c652717604cd">Introducing team annotation for articles shared in Slack</a> was originally published in <a href="https://medium.com/kipwise-blog">Kipwise</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We build Kipwise to help teams learn better]]></title>
            <link>https://medium.com/kipwise-blog/we-build-kipwise-to-help-teams-learn-better-2a213aa48c33?source=rss----554f1a4cdf58---4</link>
            <guid isPermaLink="false">https://medium.com/p/2a213aa48c33</guid>
            <category><![CDATA[slackbot]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Kwun-Lok NG]]></dc:creator>
            <pubDate>Mon, 12 Mar 2018 15:01:34 GMT</pubDate>
            <atom:updated>2018-05-04T09:57:32.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z2hf9Wccp-j6bLIo5LV_Rw.png" /></figure><p>Reid Hoffman, founder of LinkedIn, once mentioned in his podcast “Master of Scale”:</p><blockquote>I believe that no one can truly claim to be a master of scale. The most successful scalers are actually just infinite learners.</blockquote><p>Scaling a team is difficult and company growth often gets stuck when knowledge are not flowing efficiently among team members — the same question being asked multiple times, the same mistake repeats because previous learnings are not shared.</p><p>We had the same problem in our previous company. We tried to set up a knowledge base but teammates were reluctant to document team knowledge because it required too much time.</p><p>We then asked ourselves — actually most of the knowledge that we want to document are already communicated somewhere, e.g. through shared articles, videos, chat conservations, etc. Why there isn’t a tool that can convert them into saved knowledge easily?</p><p>So we started Kipwise, a tool that can help you turn daily communications in Slack into saved team knowledge easily. e.g. shared an article in Slack? Kipwise will turn it into a collaborative version so your teams can collaborate on highlights and notes.</p><p>With these annotations, your teammates can digest the content in a much more efficient way. Want a specific teammate to pay attention to a certain point in the article? You can mention your teammates in notes. The annotations will get synced to Slack so your teammates will get notified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*tIQTU-NygDzeDTHwwA2W6w.png" /><figcaption>Make sure your teammates are on the top of the shared article</figcaption></figure><p>All shared articles will be saved automatically and you can search for them directly in Slack using the command <em>/kipwise search [keyword]</em>.</p><p>Our next step is to support more knowledge formats, such as clipping Slack conversations and video annotations to further help teams enhance their knowledge sharing flow.</p><p>Have any suggestions on what knowledge format Kipwise should support next? Email us at <a href="/service/mailto:support@kipwse.com">knowledgeispower@kipwse.com</a>.</p><p>Note: The first three letters in our name Kipwise stand for <strong>Knowledge Is Power.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a213aa48c33" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kipwise-blog/we-build-kipwise-to-help-teams-learn-better-2a213aa48c33">We build Kipwise to help teams learn better</a> was originally published in <a href="https://medium.com/kipwise-blog">Kipwise</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>