<?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[Stories by Gaurav Sharma on Medium]]></title>
        <description><![CDATA[Stories by Gaurav Sharma on Medium]]></description>
        <link>https://medium.com/@gsharma?source=rss-1fd916353f9b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*iFubxMijxVgGLERJ.jpeg</url>
            <title>Stories by Gaurav Sharma on Medium</title>
            <link>https://medium.com/@gsharma?source=rss-1fd916353f9b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:25:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gsharma/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to foster data driven culture]]></title>
            <link>https://medium.com/the-data-experience/data-driven-culture-c57b410766d1?source=rss-1fd916353f9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c57b410766d1</guid>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Gaurav Sharma]]></dc:creator>
            <pubDate>Wed, 19 Aug 2015 06:07:07 GMT</pubDate>
            <atom:updated>2015-08-19T22:46:15.958Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week I was talking to a founder who recently launched a product. He expressed frustration on how he’s the only one on the team who cares about metrics. His team values data in general, but didn’t end up tracking any metrics for their recently launched product.</p><p>I have been in this situation before and was able to guess several things that they as a team might be doing wrong. Over the years, working on several web and mobile products, I’ve learned so many things that I have been doing wrong to try to get the team on board. In hindsight, some of these things seem glaringly obvious but can easily be overlooked. Here are a few things I’ve learnt that can help small teams care about metrics.</p><h4>Don’t Change Workflow</h4><p>When working on product or marketing metrics is your focus, you’ll most likely have analytics tabs open at all times. Constantly checking numbers, looking at various reports, etc. Initially, to build a data driven culture, I passed on our Google Analytics credentials to everyone on the team expecting that they’ll login to check the numbers everyday. It was soon evident to me that that’s not the best way to get everyone on board with a metrics driven culture. There’s huge friction for other members of the team to login to Google Analytics (which was another Google Account), then click on the profile, click on the right dashboard and then see a bunch of numbers which they may or may not have any context of.</p><p>Two ways I found that worked best with bringing everyone on the same page about metrics are:</p><p><strong>Email</strong> — It’s safe to assume that everyone on the team checks their email (or at least used to, Pre-Slack). We decided to send an email with our most important metrics everyday at the same time (preferably at the start of the work day) with a few key metrics in the subject of the email. Adding key metrics to the subject helped in other ways. More on it later in the post.</p><p><strong>Slack</strong> —Several years later when I started using HipChat (and <a href="https://medium.com/@gsharma/why-slack-3da202d4fad2">later Slack</a>) we translated the success with email to Slack. Due to the (bite-sized) nature of chat/messages, Slack opened up more doors to embed lightweight analytics into the existing workflow. I didn’t want to send too many emails so we’d only send one email per day, but with Slack we could control the frequency and timing of messages as well as which channels they go to. We have a dedicated <em>#reporting</em> channel where a lot of metrics get pushed into. It’s more like firehose for metrics and reports. We avoided building several dashboards because we were able to push those metrics into the <em>#reporting</em> channel. The <em>#general </em>channel only gets the most important KPIs.</p><p><strong>Lesson Learned</strong>: In order to get your team to adopt something, treat them like your internal customers and come up with solutions just like how you would for the users. Try to incorporate as much as you can into existing workflows. Remove as much friction as you can.</p><h4>Bite Sized Data</h4><p>Being a product or marketing person, you look at several metrics from MAUs to engagement metrics. Although, these are great metrics to track, not everyone on the team needs to know about all those metrics. Once I learned that team members are usually not motivated enough to login to the analytics dashboard, I started taking screenshots from Google Analytics and sharing those with the team. Everyone looked at the numbers, but I could tell they were overwhelmed by all those different metrics.</p><p>When we started sending a daily email report, the biggest thing that I learnt wasn’t the email itself, but the Subject of the email. Here’s an example: “DAUs: xx,xxx MAUs: x,xxx,xxx”. The email body had a lot more details. I noticed that most of the time people would simply glance over the subject and deleted the email. Since these were daily emails, everyone had a ballpark idea of what <em>normal</em> metrics numbers were. The days when the numbers had a major dip or rise, everyone opened the emails to see what had changed.</p><p><strong>Lesson Learned</strong>: It’s better to not dump all sorts of metrics on to the team and hope that they’ll weed out all the unnecessary info. It’s much better to selectively display 2–3 most relevant KPIs.</p><h4>Real Meaningful Metrics</h4><p>In the name of simplicity, it’s very easy to share feel-good metrics with the team but the main problem with that is that metrics like total registered users, total downloads or any other cumulative data numbers don’t really tell the whole picture. Leave those numbers for the press/marketing pages. Avoid using them as main KPIs internally. It’s good to share and celebrate cumulative numbers, but using daily/weekly/monthly numbers with delta change from the previous period can prove to be a lot more beneficial. One of the metrics we track and share on a daily basis is the percent growth or decrease in Weekly Active Users (WAU).</p><h4>Monitor and Update KPIs</h4><p>This is probably the simplest of them all, yet from my experience, ignored the most. Usually once the KPIs are added, they are never taken off the list. Gradually new KPIs keep getting displayed, but the old ones that are not relevant anymore are not taken off the list. It’s a good practice to clean up the list once a quarter. Get rid of things that aren’t relevant anymore.</p><p>Apart from a few metrics becoming less relevant, some KPI metrics don’t change too much. Instead of pushing the metrics every hour, push them only if there is a significant change. For instance, rather than blindly pushing hourly updates for average response time for your API, only push if there is a +/- 10% change. Showing same metrics often can make the team desensitized to the metrics (see <a href="https://en.wikipedia.org/wiki/Banner_blindness">banner blindness</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/793/1*RGa1Aley7Oye01z5W9ZdfQ.png" /><figcaption>Best part of Slack? Custom emoji avatars and names for the bots!</figcaption></figure><p>Got tips or tactics on how to spread a data driven culture? Would love to hear them. Comment below or <a href="http://twitter.com/gsharma">tweet at me</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c57b410766d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-data-experience/data-driven-culture-c57b410766d1">How to foster data driven culture</a> was originally published in <a href="https://medium.com/the-data-experience">The Data Experience</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Slack?]]></title>
            <link>https://medium.com/@gsharma/why-slack-3da202d4fad2?source=rss-1fd916353f9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3da202d4fad2</guid>
            <dc:creator><![CDATA[Gaurav Sharma]]></dc:creator>
            <pubDate>Mon, 21 Jul 2014 23:11:59 GMT</pubDate>
            <atom:updated>2014-07-21T23:11:59.279Z</atom:updated>
            <content:encoded><![CDATA[<h4>A review</h4><p>I have been running remote teams for almost a decade now. Tools available for remote teams have evolved a lot during this time.</p><p>In the early days tools like Skype made it easier to communicate with remote teams via text, audio and video. After that came a wave of tools like Dropbox, Google Docs that helped manage files in the cloud for remote teams. However, these utilities were never able to create a real office like environment. A real office doesn’t feel like you are transacting with a co-worker, but has a character to it. You don’t talk with co-workers only when you need something. You overhear other people talking about the new episode of The Game of Thrones. You crack jokes, you huddle. Not all these things can be done by remote teams, but having a “virtual office” can help get the team connected better.</p><h4>HipChat</h4><p>At <a href="http://rightbuy.com/iphone">RightBuy</a>, we started using <a href="http://www.hipchat.com/">HipChat</a>, which is an excellent chat application for a small team. I really loved the simple design. We kept things simple by just setting up 1 room where our small team interacted. HipChat had opened up their API and enabled teams to integrate with external services like <a href="http://github.com/">GitHub</a>, <a href="http://pingdom.com/">Pingdom</a>, <a href="http://circleci.com/">CircleCI</a>, etc. using <a href="http://zapier.com/">Zapier</a>. That was pretty cool. I have heard <a href="http://campfirenow.com/">CampFire</a> had some of these great features, but never used it.</p><h4>Slack</h4><p>I found about <a href="http://slack.com/">Slack</a> through <a href="http://twitter.com/jason">Jason Calacanis</a>‘ <a href="https://www.youtube.com/watch?v=JKf-nCt7kI4">interview</a> with <a href="https://twitter.com/stewart">Stewart Butterfield</a>. It was intriguing, but I dismissed it because it appeared to be exactly same as HipChat with IRC-esque UI. On asking other startups using Slack about differences between HipChat and Slack, all I got was — it has built-in search and it is pretty cool. I tried asking Slack themselves about why people are going crazy about Slack, they didn’t have anything concrete to offer either.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/613/1*L_NAlsJcEZfrA0Fc-L6yDA.png" /><figcaption>Slack Replies</figcaption></figure><p>Search wasn’t a big deal for us so that was the end of Slack’s evaluation.</p><h4>Slack Re-evaluated</h4><p>About a month later, a friend from <a href="http://www.seer.io/">Seer</a> was going gaga about Slack and showed how they were using Slack. That was the moment where I actually found out how Slack was a lot more than HipChat. The thing that sold me on Slack was how well Asana is integrated with Slack. It is a first-class integration that updates any comments or new tasks. As compared to this, HipChat had integration using Zapier and had limitations where we only could get only new tasks from a specific project. To keep things simple and extendable, HipChat didn’t provide custom experience for these integrations. I don’t mind using Zapier for integrations, but the UX on HipChat’s side was lacking. Here is how the integrations (at least for us) looked in both of these services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jaiihsAFGB9hVnvYww8Ojw.png" /><figcaption>HipChat Asana Integration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tapz23rsHaL5ZfbLXZQ71Q.png" /><figcaption>Slack Asana Integration</figcaption></figure><p>Asana isn’t the only better integration. GitHub, Sentry and the webhook to push messages into Slack can be customized a lot more and provide a better experience. For instance, this is the same commit from Github to HipChat &amp; Slack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ownR4Xgl45fIk43Uj8cwag.png" /><figcaption>HipChat-GitHub Integration</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hrH0yr93nXuUO5RkCOyoAA.png" /><figcaption>Slack-GitHub Integration</figcaption></figure><h4>Notice Board</h4><p>I found out from <a href="http://bryanhelmig.com/">Bryan Helmig</a> that they use <a href="https://zapier.com/blog/run-a-remote-meeting/">something called async at Zapier</a>, which is an internal WordPress blog for things that do not need immediate attention. It seemed like a great idea when I heard about it, something that I would like to implement for <a href="http://rightbuy.com/iphone">RightBuy</a> as well. We have a lot of conversations among us that are way too long for ‘chat’, not actionable enough to be put in ‘Asana’ but at the same time needs to be captured in some shape or form.</p><p>Slack has a great feature for this use case. You don’t have to setup an internal WordPress blog, but just use their ‘Post’ feature. Anyone can write a post which can be shared with any channel or a person. It is great to capture things like your medium to long term goals, certain processes and in general company updates (especially if you are a big team.) The posts act as a ‘notice board’ (when was the last time you actually saw a notice board?) for the company.</p><p>Another great feature Slack has that I hadn’t even thought would be useful until we started using Slack — Favorite a Message. It is a like bookmarking a message for easy access for later on.</p><h4>Not Everything Works</h4><p>As I mentioned above, I really like that they are themselves building the integrations with other services. It provides a unique experience which can be customized based on each service they are integrating with rather than have a one-size-fits-all model where none of the integrations have an outstanding experience. That being said, not all of their integrations are the best. For instance, we found out that Slack’s default RSS integration is far inferior to Zapier’s Slack-RSS implementation. I haven’t tested all the integrations, but wouldn’t be surprised if there are more integrations that are being implemented better by third parties.</p><p>Another nitpick with Slack is that when writing a ‘post’, they use Markdown syntax. I would much rather use a WYSIWYG editor that can speed up formatting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*FDTmWaj3hxRf0weHnrQxig.png" /><figcaption>Slack Post Markdown</figcaption></figure><h4>Email Killer &amp; Future</h4><p>I remember sending a lots of “chatty” emails to my co-workers a few years ago where everyone on dev mailing list had to bear with them. Combination of tools like Asana and Slack are effective on killing email use at least internally for small teams. This is a great start. Slack seems to be integrating with several services, but it has to be seen where does their future live. To expand, do they in future start competing with likes of Dropbox, Google Apps, Skype, or even Asana and provide a plug and play infrastructure layer for remote teams for a virtual office? It is yet to be seen, but so far they seem to be heading towards the right direction.</p><p>Did I miss something? Would like a follow up on how we use Slack? <a href="http://twitter.com/gsharma">Reach out here</a>.</p><p>Originally posted <a href="http://www.gsharma.com/why-slack/">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3da202d4fad2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Apple bought Topsy]]></title>
            <link>https://medium.com/i-m-h-o/why-apple-bought-topsy-2d222f9f8189?source=rss-1fd916353f9b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d222f9f8189</guid>
            <dc:creator><![CDATA[Gaurav Sharma]]></dc:creator>
            <pubDate>Tue, 03 Dec 2013 03:38:32 GMT</pubDate>
            <atom:updated>2013-12-03T03:38:32.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*HPkShQvEobkOBrsSyH8OUw.png" /></figure><h4>In-App Search is coming soon.</h4><p>I was surprised to hear about Apple buying a Twitter Analytics company. It just didn’t make any sense. One wild possibility I thought is Apple trying to acquire Twitter and this is just a precursor to it. Although possible, I don’t think it is likely.</p><p>What does Topsy actually do? Search &amp; Analyze social media data including links. Another possibility is that Apple wants to scan through all those App Store reviews and provide a better search experience for the consumers. This might be true and Apple may use Topsy for that. However, I don’t think a $200M price tag justifies that use case.</p><p>Then I remembered how Android is <a href="http://gigaom.com/2013/11/12/how-in-app-search-is-going-to-keep-android-awesome-and-google-in-control/">working on in-app search</a>. Apple is also <a href="http://www.macrumors.com/2013/09/24/apple-looking-to-buy-more-land-for-oregon-data-center/">building a bunch of data centers</a>.Could it be that Apple is planning to use Topsy for in-app search?</p><p>I really like the universal search on my iPhone and use it all the time to access contacts, apps and emails. What if Apple is building something that indexes the data from the apps the device? On top of it also launch a set of APIs similar to ElasticSearch where app developers can push relevant user data to Apple’s servers to index it?</p><p>Apple can keep a version of the index on the device for faster access like it does now and append that data with the results from its servers from other apps.</p><p>I don’t know if this is going to happen, but as a user and a developer I am excited to see it happen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d222f9f8189" width="1" height="1" alt=""><hr><p><a href="https://medium.com/i-m-h-o/why-apple-bought-topsy-2d222f9f8189">Why Apple bought Topsy</a> was originally published in <a href="https://medium.com/i-m-h-o">I. M. H. O.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>