<?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[A case for humanity - Medium]]></title>
        <description><![CDATA[Musings of a grad student — product, systems, art and happenings. - Medium]]></description>
        <link>https://medium.com/a-case-for-humanity?source=rss----94bf092ba90c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>A case for humanity - Medium</title>
            <link>https://medium.com/a-case-for-humanity?source=rss----94bf092ba90c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:27:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/a-case-for-humanity" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Duleep Singh and the balm of mediocrity]]></title>
            <link>https://medium.com/a-case-for-humanity/duleep-singh-and-the-balm-of-mediocrity-78335a17c736?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/78335a17c736</guid>
            <dc:creator><![CDATA[Soumya Gupta]]></dc:creator>
            <pubDate>Sun, 25 Aug 2024 13:42:26 GMT</pubDate>
            <atom:updated>2024-08-27T05:13:27.804Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uzVXwnC5L-ASAQs9MsBj9g.png" /><figcaption>AI generated image of (L-R) Maharaja Ranjit Singh, Duleep Singh, Maharani Jind Kaur</figcaption></figure><p>I just finished reading <em>The Last Queen</em> by Chitra Banerjee Divakaruni yesterday. The book chronicles the downfall of the last Sikh Empire, led by the “Lion of Punjab,” Maharaja Ranjit Singh, from the point of view of his last wife, Jind Kaur.</p><p>Ranjit Singh was the stuff of legends, a man who could do wrong but never by intention. A man of wisdom, wit, humor, and, above all, courage with humility. His wisdom stemmed from his clear sense of priorities, always putting Punjab first. This is evident in the vast boundaries that the kingdom reached under his reign.</p><p>Then come the other, more human characters — characters written and remembered more through reality than through a historian’s pen. Their faults and inadequacies haven’t faded over time; they still appear human to us. Duleep Singh, the son of Jind Kaur, was born in turbulent times, a pawn freely used by higher powers. His childhood (and subsequently, life) spanned two opposing, and therefore confusing, spectrums — anti-Britain and anti-India. He was taken away from the Queen at the age of eight and fostered by a British nobleman who ingrained a reverence for all things British in his psyche, from the deferential point of view of a nobleman. When he was reunited with his mother after 14 years, this perspective brought out a sad reality — a free king reduced to a pawn in court. He was born to be a contemporary of the queen, but he died as nothing more than a subject.</p><p>This might have been bearable if he had remained ignorant of it.</p><p>“Ignorance is bliss” is a phrase that rings true for him. Living in the shadows of greatness, the knowledge of all he’d lost cast a permanent overcast on his own life. Allowed back into mainland India only twice, his life was caught between English pension grants and other bureaucratic idiosyncrasies, which made larger aspirations like the fight for freedom seem like a distant dream.</p><p>It’s said that the best way to boil a frog to death is to put it in a wok on minimal heat. The frog will adjust its body temperature as the heat gradually increases, and the gradient can be so slow that the frog will pass away peacefully, unaware of being boiled to death. I find a similar parallel with Duleep Singh, as he got caught up in the banality of fighting for pension grants, never reaching the heights that would have inspired him to be the “Lion of Punjab.”</p><p>It’s not a far-off parallel to draw, that we too are in a mire similar to Duleep Singh’s. We’re chasing after the banalities that afford us the lifestyle of our choice, while we’re meant to be the “lions” of our own accord, but never dedicate enough of ourselves to it. It’s similar to the story of Hanuman, one of the rare beings who realized the potential of his own strength and then used it. We’re all Hanumans in our own right. Duleep Singh never realized that he too could be the “Lion of Punjab,” and we slowly stop aspiring to greatness as age and comfort seep in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78335a17c736" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/duleep-singh-and-the-balm-of-mediocrity-78335a17c736">Duleep Singh and the balm of mediocrity</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A case for: Lollapalooza 2023]]></title>
            <link>https://medium.com/a-case-for-humanity/a-case-for-lollapalooza-2023-10fcf7d0d6c6?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/10fcf7d0d6c6</guid>
            <dc:creator><![CDATA[Soumya Gupta]]></dc:creator>
            <pubDate>Thu, 16 Feb 2023 13:13:09 GMT</pubDate>
            <atom:updated>2023-02-16T13:13:09.324Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*yX6N35c1cwdJjvqDEoZM_g.jpeg" /><figcaption>Lolla India</figcaption></figure><p>Abhinav and I attended Lollapalooza nearly a month back (Jan ‘23), in what was a pleasant awakening to what the normal succession to 2019 should have been. The fear of Covid was hidden somewhere was pushed to some dusty shelves in our mind, and we were blissfully (un)aware of this fact. With this backdrop, Lollapalooza saw double the enthusiasm — one for being to an event after so long, and second for its first edition in India. The aim of this article is to dissect the pros and cons of the first-ever edition of Lolla India.</p><p><strong>Pre-Conditions:</strong></p><p>No mobile data / phone connectivity was available once entering the venue. This wasn’t a controllable factor as the density of the network was much too high to be catered by the nearby towers.</p><p><strong>Pros:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*Yhz6ZKftB0uBBLRHL5WWCA.jpeg" /></figure><ol><li><strong>Selection / Lineup:</strong> While Lolla was initially written off for having a dated lineup with debatable relevance, I think the artists took it on themselves with crazy motivation to prove them wrong. The lineup was great in terms of representation, from women to diverse genres, it covered it all, making it a place of discovery for new music, while appreciating the ones that we already knew. In addition to the headlining artists who gave exceptional performances (shoutout to: Imagine Dragons, Diplo, Divine), there was quality abound in stage presence with Kayan, Wombats and Jackson Wang.</li><li><strong>Entry experience:</strong> Mahalaxmi Race course is no stranger to big events, and neither are the event organisers to the venue. This was evident in the entry experience, with ample lines to manage crowds, and a seamless check-in experience.</li><li><strong>Time management:</strong> It is a commendable feat that as event-goers, we didn’t notice even one delay throughout the concerts. All artists were time-boxed religiously and rigorously, and in the smoothest way possible. As soon as an act finished, you could hear the strains of music of an act starting up in the adjacent stage. This could’ve been a major pain point, especially with the jostling crowds, but it was handled beautifully.</li><li><strong>Stage experience:</strong> The sound systems, visuals and fireworks were world-class. Even though each stage catered to a high-volume, the quality of sound was not diminished, the screens were ergonomically to cater to event goers of all heights. And the synchronised fireworks were a cherry on top.</li></ol><p><strong>Cons:</strong></p><ol><li><strong>F&amp;B:</strong> The bands also served as wallets for the foods and drinks, but there were several breaks in the process here.</li></ol><p><strong>a. Wallets: </strong>The first was in getting a recharge on the bands wrt long lines and the fact that mobile data was exceptionally slow. The BMS app could have been integrated easily for a self-recharge on the cards, as the recharge process also seemed similar at the counters.</p><p><strong>b. Food stalls:</strong> There was a central area for getting food, where crowds would be move in a seasonal fashion, getting extremely crowded just after concerts. Though the selection of the food stalls was great - it covered a lot of palettes at fit price points, the accessibility was a problem. It would have helped if the food stalls were distributed over the ground, though this would have required more manpower. However, even with the same selection, there could’ve been 2-3 stalls of the same franchise spread over the premises, aiding the event goers with easy accessibility to food as well as better brand building.</p><p><strong>c. Drinks:</strong> Drinks were spread out in a hybrid pattern — there were Johnnie Walker stalls at the corners, there were also Corona/Hoegaarden and Bud stalls near the middle area. There were two main stages where the main crowds were, however, that entire crowd could be serviced only by two stalls — One Bud and One Johnnie Walker — this led to a disproportionate crowd at the stalls. It would have helped if there were centralised outlets atleast for Budweiser and Johnnie Walker together, and moreover placed between each two stages.</p><ol><li><strong>Washrooms:</strong> The washrooms were filthy, I re-considered going to the entire fest after nearly gagging on the smell in the area. It’s not like the event had not set-up the right amount of washrooms, they did. They even placed the washroom stations very tactically — one at the entrance, and two within the ground placed perpendicularly around the main areas. The problem was in the management of the porta-potties. The lines were erratically dispersed across the space, the flushes weren’t working, and there was no way to deduce which washroom had just been cleaned. There were sanitation workers all around the area, but they too didn’t know which stalls were to be cleaned leading to a higher load on some stations, and hence the scarring experience. This could be managed by a better flagging system on the toilets which conveyed both to the event goers as well as the staff on just cleaned toilets.</li><li><strong>VIP areas:</strong> These tickets costed 2x of the normal tickets, however the incremental price didn’t justify the incremental value provided. There was one VIP area placed in the centre, and the idea was that it would have a viewing pattern placed radially to all the stages. However, it was much too far from all the stages to have an impact. There were food stalls inside, but no idea how that experience was.</li><li><strong>Sustainability:</strong> The fest made a big step forward by handing out reusable glasses with drinks at an incremental cost of Rs. 50 and 100 bucks. They had placed hydration stations with lines of water filters as well, with reusable glasses as the only options to push adoption with the masses. These glasses came with belt tags to hang off the person to be used further in the event. However, one crucial addition for the next editions would be to introduce lids on the glasses so that these glasses could serve the purpose of dispersed drinking as well as protecting against dust, etc. One major case in point was that one couldn’t refill from the hydration station and keep water with them. The water had to be consumed at that point of time or it would spill over or be exposed to dust. The same extended to all other drinks as well.</li></ol><p><strong>Ideas to build up on for the next editions (Theme- discovery):</strong></p><ol><li><strong>Maps:</strong> The organisers had put in a lot of effort to put together art installations and engagement activities. It was laid it in a way that people would discover them on their own, however, it would have seen a lot more engagement if there was a map given out with physical hardcopy with the bands.</li><li><strong>Genre based stages:</strong> The fest was a great place for driving music discovery, I would have however found it more helpful if I knew which ballpark genres would be playing at each stage. This would have helped me prioritize better especially in the early hours of the fest where nearly all artists were unknown to me.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10fcf7d0d6c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/a-case-for-lollapalooza-2023-10fcf7d0d6c6">A case for: Lollapalooza 2023</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Improvement: Browserstack]]></title>
            <link>https://medium.com/a-case-for-humanity/product-improvement-browserstack-36ca5a35007e?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/36ca5a35007e</guid>
            <category><![CDATA[bugs]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[product-improvements]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[jira]]></category>
            <dc:creator><![CDATA[Abhinav Garg]]></dc:creator>
            <pubDate>Sat, 23 Apr 2022 06:45:03 GMT</pubDate>
            <atom:updated>2022-04-23T06:45:03.159Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*07PZNyRPxLsMuWdt.png" /></figure><h3>Project Summary</h3><p>The project aims to improve the adoption of Browserstack’s feature to file bugs directly into JIRA for their <a href="https://www.browserstack.com/live">Live</a> products including <a href="https://www.browserstack.com/app-live">App Live</a>.</p><h3>What is Browserstack?</h3><p>Browserstack is a company that provides a strong product suite for testers to test for various use cases. Live and App Live are their products for manual testing of web and mobile apps respectively.</p><p>As Live is Browserstack’s primary offering, improving the adoption of filing bugs into JIRA becomes very important to<strong> improve customer stickiness</strong>. This can be done by providing features/solutions that make<strong> Browserstack a one-stop-shop for end-to-end testing of product</strong>s.<br>In this document we will go through the<strong> success metric, primary customers and their needs</strong>, how they solve the problem as of now, how <strong>competitors solve these problems,</strong> and how can Browserstack solve them.</p><h3>Success Metric</h3><p>Adoption can be measured by two primary metrics:</p><ol><li>Breadth Metric: M-o-M % of active users creating at least one bug on JIRA</li><li>Depth Metric: Avg. No. of JIRA bugs filed per user per month</li></ol><p><strong>Definition of active users</strong>: Users who have run at least 1 session on either of the Live products in the last month.</p><h3>Customers</h3><p>The primary customers for the live product’s filing JIRA bug feature are:</p><ol><li><strong>Manual Testers</strong> in tech companies, testing features before product release</li><li><strong>Developers</strong> (Mobile and Web app) testing feature before release</li><li><strong>QA teams</strong> taking care of end to end functionality of the app before the production release</li></ol><h3>Customer Needs</h3><p>All the customer personas defined above have similar needs, which are as follows:</p><ol><li>Need to track bugs on JIRA end to end from creation to completion from testing platform</li><li>Need to remind the assignees to provide ETAs and actively work on issues from the testing platform</li><li>Need to track progress on the JIRA issues created from the testing platform</li><li>Need to record and attach videos of bugs on JIRA from the testing platform</li><li>Need to fill org mandated fields in JIRA straight from the testing platform</li></ol><p>As Live and App Live are aimed at providing a strong ecosystem to anyone aiming to do manual testing the above needs become pivotal to providing a great UX.</p><h3>Current Customer Journey</h3><p>In order to solve for above needs, the user has to go through multiple steps as follows:</p><ol><li>Open Live/App Live</li><li>Follow manual tests</li><li>If bug/issue is found use the Report a bug feature</li><li>Browserstack automatically takes a screenshot, this can be edited with marker, crop etc.</li><li>Integrate JIRA via one out of 2 methods</li><li>Raise a bug, or update an existing bug</li><li>Add project, description, and other details which include assigning assignee labels incl. Other parameters</li><li>In case the company has <strong>other parameters mandated</strong> but not available in BrowserStack, the<strong> user will have to go to JIRA to create the issue</strong></li><li>In case the user wants to<strong> upload/attach a video </strong>to explain the bug, the same has to be done by first recording the session on Live and then <strong>uploading it separately going to the issue on JIRA</strong></li><li>The bugs created by users have to be<strong> tracked regularly on JIRA exiting the BrowserStack </strong>platform.</li><li>In order to remind the assignees about the assigned bug, the <strong>user has to track the same on JIRA and then separate messages/emails/calls</strong>.</li></ol><p>It is quite evident that the user journey of<strong> tracking bugs end to end on BrowserStack is broken</strong>; this opens up opportunities for competitors to provide a better user journey and get the customer.</p><p>This also <strong>reduces user stickiness</strong> as the Live ecosystem is not strong enough to keep the customer the platform for all their needs w.r.t. exploring and tracking issues found while manual testing.</p><h3>Competitor Analysis</h3><p>I analyzed 3 major competitors of BrowserStack i.e. Lambda Test, Sauce Labs, and Perfecto. Following is a summary of the same</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*xfv-4KtQEsk-Bk1L" /></figure><p>Based on the above analysis, it was clearly evident that when it comes to providing a great ecosystem to create and track bugs on JIRA, Perfecto solved almost all the essential needs. Following are some learnings from the competitor analysis:</p><ol><li><strong>Browserstack</strong> provides the <strong>best login integration with JIRA</strong> by allowing users to log in to JIRA from the platform and integrate automatically. Others still use tokens to integrate</li><li>Platforms like <strong>Perfecto &amp; Sauce labs</strong> save <strong>session details</strong> to re-look &amp; manage bugs, screenshots &amp; videos better helping in creating a complete ecosystem to manage test sessions</li></ol><p><strong>Perfecto is very well integrated with JIRA</strong>, it provides bug creation <strong>UI similar to JIRA,</strong> user can <strong>add/edit fields</strong> they want to fill, they can<strong> upload videos,</strong> and also <strong>track the bugs</strong> they created. This brings in ecosystem play by creating a one-stop shop to fulfill all the needs from <strong>creation to tracking the bug</strong>.</p><h3>Solutions</h3><p>The following solutions will try to create a holistic experience for the user to fulfill all their needs and in doing so create customer stickiness.</p><h4>Attach videos to the JIRA issue</h4><p>Once the user has recorded a video on BrowserStack, it is stored in the local storage. This feature aims to assist users in creating a JIRA issue with video and related logs from the recording.</p><p>The solution requires the following features:</p><p>Video recording option on Live — The<strong> Live app does not provide a screen recording feature</strong>. However, the same is available in App Live. Therefore, we need to create a screen record feature for Live as well. It can sit in the menu on the left as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/1*Z_h8bsSaVY4pdMTNZsaQsw.png" /></figure><p>A <strong>logfile </strong>from the time duration of the video grab, downloaded along with the video.<br>An additional option in the create JIRA bug section to attach videos and log file</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/0*_TT_gQVi_Owe9Hcq" /></figure><p>The proposed user flow is as follows:</p><ol><li>The user starts video recording</li><li>Once the recording is finished, a video and a log file in text format is downloaded onto the local system</li><li>The user can click on report a bug from the menu.</li><li>This opens the option to report in JIRA. in the menu to create JIRA issue, users can attach videos, additional screenshots, and log files from the local system</li><li>Post this the user can click on Create/Update JIRA issue</li></ol><h4>The Bug Tracker</h4><p>This solution is designed to create an end-to-end ecosystem to create and track bugs be it on JIRA or other platforms. The core of this solution is to create a central repository to track issues/bugs raised from different platforms on Browserstack starting from Live and App Live.</p><p>The feature will sit in the top menu bar as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GzoZqHPvegmvyj5S" /></figure><p>The Bug Tracker will be a <strong>completely new section</strong> and will consist of the following <strong>sub-solutions</strong>:</p><p><strong>Creating Bugs<br></strong>With the bug tracker coming in, there will be two ways to create bugs across apps:</p><ol><li>From the Browserstack apps i.e. Live and App Live</li><li>From the bug tracker</li></ol><p><strong>Managing Bugs<br></strong>Opening the Bug tracker section will have a list of all bugs filed from the BrowserStack ecosystem incl. Live and App Live. This section will have the following layout:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tI4oiFhr9UmtTk4Q" /></figure><p>Here, the user can:<br><strong>Create new bugs</strong> — By clicking on Report on JIRA. This opens up a new dialogue box with all the relevant details that can be added to the JIRA issue just like on the JIRA app as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sdK8yeYP8tW6HDiR" /></figure><p>This would also solve the need for users to fill organization-specific mandatory fields available in JIRA.</p><p><strong>Edit/Manage existing issues</strong>: This can be done by clicking on existing rows in the table which opens up a dialogue similar to the one explained above just with the existing details of the issue pre-filled.</p><p><strong>The following are auxiliary features in the Bug tracker feature to enhance the UX:</strong></p><p><strong>Sending issue reminders</strong></p><p>Another important need of our users is to remind the assignees about the bug and track the status so that the issues are fixed in time and there is some level of ownership/monitoring on the assignee.</p><ol><li>In order to solve this, we need to create an <strong>additional button for each row</strong>, called <strong>Reminder</strong>.</li><li>Clicking on Remind gives two options:</li></ol><blockquote><strong>Slack -</strong><br>Clicking on this opens up a new message on slack<br>The contents are pre-filled with the Issue number, type, and description<br>The message reads like this: “Hope the issue is on track”<br>The user can add users to the recipients</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/0*UzutDAKX_uniCwDM" /></figure><blockquote><strong>Email<br></strong>Clicking on Email opens up the default email app<br>The contents are pre-filled<br>The subject is: “Reminder: &lt;Issue Description&gt;<br>The user can add recipients of the mail</blockquote><p><strong>Edit/Add all JIRA parameters</strong></p><p>Creating a JIRA bug/issue straight from the Live/App Live does not have all the parameters. As of now using the bug tracker, all the fields reportable on JIRA are available, and the bug reporter on Live/App Live can also be updated.<br>This would mean<strong> adding all the fields like Design Reviewer, Demo Date, etc.</strong> to the <strong>“More Fields” </strong>button. This would allow the user to <strong>fill all the mandatory fields </strong>as per their organization required to create the issue.</p><h3>Metrics</h3><ol><li>M-o-M no. of bugs created per user</li><li>M-o-M % change in the bugs created</li><li>M-o-M no. of reminders sent per user</li><li>M-o-M % of bugs/issues resolved per user</li><li>M-o-M % active users of the bug tracker (opening bug tracker once in the month)</li><li>M-o-M no. of bugs created with attachments</li><li>M-o-M % bugs created with attachments</li><li>M-o-M % of users integrating JIRA to Browserstack</li><li>M-o-M % change in users integrating JIRA to Browserstack</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36ca5a35007e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/product-improvement-browserstack-36ca5a35007e">Product Improvement: Browserstack</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Design 101: API Product Management (2/2)]]></title>
            <link>https://medium.com/a-case-for-humanity/api-design-101-api-product-management-2-2-1f467dbae8f8?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/1f467dbae8f8</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Abhinav Garg]]></dc:creator>
            <pubDate>Sat, 30 Oct 2021 06:31:08 GMT</pubDate>
            <atom:updated>2021-10-30T06:51:33.343Z</atom:updated>
            <content:encoded><![CDATA[<p>In the last part of this blog ‘<a href="https://medium.com/a-case-for-humanity/api-design-101-the-basics-1-2-b24318433514?source=friends_link&amp;sk=d2c4f18377317821f2eddb87cc14ff7b">API Design 101: The Basics</a>’, we learned about APIs, their design principles, and some best practices. In this part, we will learn about API Product Management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IUm35M4AqzxhVaca.png" /></figure><h3>API Product Mindset</h3><p>Like we read in the last post, developing APIs is a continuous process that should be done keeping the users in mind. This is where the concept of API product management and the team comes into play.</p><p>API product mindset dictates that APIs are like designing products and not mere one-time effort. APIs evolve with changing customer and business needs. Product mindset ensures that the team looks at ways to provide strategic value to the customer and not design it with just great architecture in mind. This means that APIs are designed with the correct scope which is not too narrow and not too broad and are flexible enough to be used in gazillions of ways to foster innovation.</p><p>This also calls for an API team that is composed of Product Managers among others. Historically, Product Managers have been seen as folks who look at the product suite and front end. However, with evolving times and the increasing role of APIs, Product Managers are required to manage APIs as a standalone product suite. Contrary to popular opinion about this kind of product management being a secondary role, API product management requires significant time and has far-reaching business impacts. It requires additional competencies such as understanding the tech infrastructure, long-lasting design, and slim tolerance for errors.</p><h3>The Dream team</h3><p>An API team unlike other teams has its own set of requirements. The composition of the team may vary but the team members need to perform various roles to ensure success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*MCX6LSCwWtjMv2vx.jpg" /></figure><p>Following is a brief on the same:</p><ol><li><strong>Product Manager:</strong> The manager is responsible for collecting customer needs, driving insights, ensuring cross-functional conversations, and helping develop a shared vision for the APIs. The manager is also required to understand the technical specifications and effectively communicate those benefits to the stakeholders.</li><li><strong>API Architect:</strong> The architect is responsible for planning, designing, and reviewing the construction of APIs.</li><li><strong>API Developer:</strong> Developers are the folks who actually build those APIs. They not only build but also ensure the availability of important resources that ensure API adoption such as discoverability and documentation.</li><li><strong>API Evangelist</strong>: They represent the voice of API consumers. They ensure that the API consumers have all the necessary tools to use the APIs. They are responsible for managing developer portals, detailed info-pages, and SDKs. They also ensure internal and external outreach using hackathons, answering questions, bringing feedback, marketing APIs using SEO and targeted ads, building communities using forums, meet-ups, and conferences, and communicating clear and concise value propositions.</li><li><strong>API Champion:</strong> They are responsible for connecting the value of APIs to business and strategy. Their role is to convert tech specs into metrics that track business goals such as customer satisfaction, revenues, and customer adoption. They also need strong influencing skills to procure funding and resources for API teams by providing the right visibility to internal business teams.</li></ol><h3><strong>Design Reviews</strong></h3><p>Designing APIs and ensuring that APIs are consistent as the team expands becomes difficult. This means that we need processes and infrastructure in place. Following are some good practices for the same:</p><ol><li><strong>Design Document:</strong> A concept note describing customer needs, broad requirements, and success metrics. A Tech spec describing endpoints, events, parameters, errors, and the backend architecture</li><li><strong>API reviews:</strong> Post internal reviews, get the API suite reviewed by an external team responsible for giving a green light to APIs. This external team can act as a council that consists of cross-functional members, the council checks for interoperability, consistency, migration to new infra, and the tech burden involved</li><li><strong>User Testing:</strong> Launch alpha and beta versions with a smaller set of users, understand their problems, fine-tune the APIs using interviews and usage stats</li><li><strong>Canary Releases: </strong>Gate in the customers slowly, ironing out the bugs further, fixing documentation, and improving error handling</li></ol><p>To summarize, APIs have become the go-to solutions for organizations to grow their business. API product management is therefore slowly but surely coming to the center stage. This form of product management sure requires some special set of skills but honing those skills is not difficult. Additionally, becoming adept at API product management can also help PMs not only in their current API teams but later in other teams as well as they would now know the power of APIs and how to integrate them into their products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f467dbae8f8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/api-design-101-api-product-management-2-2-1f467dbae8f8">API Design 101: API Product Management (2/2)</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[API Design 101: The Basics (1/2)]]></title>
            <link>https://medium.com/a-case-for-humanity/api-design-101-the-basics-1-2-b24318433514?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/b24318433514</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Abhinav Garg]]></dc:creator>
            <pubDate>Sun, 17 Oct 2021 05:56:27 GMT</pubDate>
            <atom:updated>2021-10-30T06:40:57.301Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a two-part blog where I try to explain APIs from a product manager’s perspective. In the first part, we will understand API basics. In part 2 of the blog, we will learn API product management and team organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/0*NT5fIezUd0k4WM3g.png" /></figure><h3>What is an API?</h3><p>Application Programming Interface a.k.a. API in simple terms is how different software talk to each other. They are used to expose services offered by the firm to both external and internal consumers. This in turn enables these API consumers to leverage data, functions, and applications to build new powerful products. Hence, APIs function as the backbone of any organization trying to promote the decentralization of innovation using microservices.</p><h3>The Essentials</h3><p>Now that we have understood what an API is and why it is important. Let’s look at some essential principles of an API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tC_SC1qQXzrK-zCH.png" /></figure><p>The foundations of a good API are laid on top of these 3 core pillars:</p><h4>Approachable</h4><p>An API fosters innovation across a wide variety of audiences both internal and external. This makes approachability a quintessential quality of the APIs.</p><p>The APIs must be <strong>Intuitive &amp; easy to understand</strong>, <strong>Discoverable,</strong> and <strong>Well-Documented.</strong></p><p>For example: Naming the APIs is a very important construct. The APIs must be named using everyday constructs and avoid industry jargon. The archaic and sticky nature of names makes it even more important.</p><h4>Flexible</h4><p>APIs must be flexible in a way that they provide the right amount of data/output and give developers enough options both in terms of parameters passed and dev environments available.</p><h4>Composable</h4><p>Collectively, the API suite must be composable i.e. the consumers can use different APIs to create new services/products with ease.</p><h3>The Design</h3><p>If the strategy and designing process of the APIs is not done beforehand, it can lead to major roadblocks later on and limit their usability. Following are some best practices in order to avoid such setbacks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W_cqK9630W3pdjbH" /></figure><h4>Outside-In Approach</h4><p>Coined as <strong>‘Users first approach’</strong>, this principle stresses starting the design process from the users. Sometimes, this is also referred to as the <strong>‘Working backwards’ </strong>approach especially at Amazon where the team starts with a press release, then FAQs, followed by wireframes, and then user manuals. This has a two-pronged benefit, first, you create APIs that will be designed with the consumers in mind and hence will have better adoption and second you communicate the product requirements across the org and cross-functional teams better. While designing the team must take care of both the direct users i.e. the developers and the end customers i.e. the users whom the developers serve.</p><h4>Give it some time</h4><p>Just like they say, ‘Rome wasn’t built in a day’, good APIs also need time. Spend enough time on designing, gathering feedback, and re-designing the APIs even if they are in the MVP stage. The team must dedicate time to ensure a good developer experience, develop the right SDKs, libraries and documentation for the APIs because APIs tend to be sticky and if not rolled out properly they may never be adopted. This implies the team must evaluate the APIs on the following parameters before they decide to launch it:</p><ol><li>Simplicity, i.e. easy and intuitive to use</li><li>Composability</li><li>Backward compatibility, the users must be given choice on when they want to upgrade their API integrations</li><li>Predictability, the same input must repeatedly give the same output.</li></ol><h4>Iterations make an API perfect</h4><p>The design process must also maintain a balance between spending time on API and the release speed. The APIs must be good enough to get good adoption and the teams must not aim for perfection in the first go. Constant feedback, market research, and data analysis can help teams to launch new iterations sooner and achieve perfection. This means that APIs are not a one-time job but an ever-evolving process that requires dedicated teams.</p><h4>Reverse Conway Law</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/0*HZ7rbO-2E9gDnsGq" /></figure><p>Conway’s Law states that organizations produce systems that mimic their org structure. We can use this law in reverse to create the API suite we wish. For example, if we wish to create APIs that are in line with our product offerings, we create separate API teams in each product.</p><h4>The Finishing</h4><p>Apart from the core methodology of executing API development, the following are some DOs that would leapfrog the adoption of your API suite:</p><ol><li>Avoid using industry jargon in API calls</li><li>Nested JSON structures that follow the object-oriented approach</li><li>API structures that use Enums and not booleans</li><li>PATCH requests must respond with the modified object in response</li><li>Polymorphism in nested response structures by stating ‘type’ of the object and then its details</li></ol><p>Loved this blog? Continue reading the next one, <a href="https://medium.com/a-case-for-humanity/api-design-101-api-product-management-2-2-1f467dbae8f8?source=friends_link&amp;sk=94893ef0f3bd79beaac312b274c3a8ea">API Design 101: API Product Management.</a></p><blockquote>Source:</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIEe-5VOv0Js%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIEe-5VOv0Js&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIEe-5VOv0Js%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/502239b2215baf6dc5cfeddd8acb9fb7/href">https://medium.com/media/502239b2215baf6dc5cfeddd8acb9fb7/href</a></iframe><blockquote><a href="https://cloud.google.com/files/apigee/apigee-api-product-mindset-ebook.pdf">https://cloud.google.com/files/apigee/apigee-api-product-mindset-ebook.pdf</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b24318433514" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/api-design-101-the-basics-1-2-b24318433514">API Design 101: The Basics (1/2)</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RICE Framework: The staple of feature prioritization]]></title>
            <link>https://medium.com/a-case-for-humanity/rice-framework-the-staple-of-feature-prioritization-a62ef663b6c?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/a62ef663b6c</guid>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Abhinav Garg]]></dc:creator>
            <pubDate>Fri, 01 Oct 2021 07:46:46 GMT</pubDate>
            <atom:updated>2021-10-24T07:31:50.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SHOqo-1iQa4dJVeC.png" /></figure><p>In one of our previous blogs <a href="https://medium.com/a-case-for-humanity/product-design-101-how-to-dissect-and-ideate-c25c42e82715"><em>“Product Design 101: How to dissect and ideate”</em></a>, we discussed how to start your journey of product mindset. The CIRCLES technique is a perfect way to structure your thoughts and create great products. However, CIRCLES does not discuss a lot about how to prioritize features.</p><p>One may think why is prioritization so important, well with more than a dozen of features in the pipeline, as a PM how do you decide which feature to take up in this sprint, how do you convince, the sales team, engineering team, support team and other stakeholders on why did you take a particular feature and not other. Not only this, the opportunity cost of developing a wrong feature in form of development cost, time lost, maintenance cost, customers lost due to the right features not being developed are very high. Therefore, prioritization becomes a pivotal part of PMing.</p><p>In the blog <em>“</em><a href="https://medium.com/a-case-for-humanity/pm-frameworks-101-572a9cdaeee7"><em>PM Frameworks 101</em></a><a href="https://medium.com/a-case-for-humanity/product-design-101-how-to-dissect-and-ideate-c25c42e82715"><em>”</em></a>, we discussed different frameworks for prioritization. RICE framework is one such framework that we love and is used by a lot of companies. Let us give you a recap:</p><p><strong>Reach</strong> — How many people will this feature effect within a given time? (Scale of 1 to 10, 1 being low reach and 10 being the highest reach)</p><p><strong>Impact</strong> — How will this impact individual users?</p><p>How much the idea will positively affect the key metric you’re trying to improve. (Scale of 1 to 10, 1 being low impact and 10 being the highest impact)</p><p><strong>Confidence</strong> — How confident are we about the impact and reach scores? How much data do we have to back up those estimates? (Scale of 1 to 10, 1 being low confidence and 10 being the highest confidence)</p><p><strong>Effort</strong> — How much time investment will this initiative require from product, design, and development? (Scale of 1 to 10, 1 being low effort and 10 being the highest effort)</p><h4>RICE SCORE = (Reach x Impact x Confidence)/Effort</h4><blockquote>However, we have always been a bit hazy about how do you exactly calculate the confidence in a feature being successful. The process always felt arbitrary. <a href="https://itamargilad.com/the-tool-that-will-help-you-choose-better-product-ideas/">Itamar Gilad’s</a> blog on idea prioritization helped us understand the framework better.</blockquote><p>The measurement of the RICE score is an evolving process straight from the concept note, to PRD, to the actual development of features quarter by quarter. As we proceed in the lifecycle of a product, the measurement of Reach, Impact, Effort, and Confidence evolves basis the improved data points collected from team discussions, user interviews, A/B testing, Dogfooding, alpha and beta releases, etc.</p><p>Let us discuss this in a bit more depth:</p><p><strong>Reach </strong>is the measure of the adoption of a feature. It would ideally depend on how easy it is for people to find and understand the feature, and how often they need that feature. This can be ascertained using customer interviews, dogfooding, A/B testing, alpha releases, etc.</p><p><strong>Impact</strong> can be calculated on basis of your estimation on how the feature will impact the North star metric and the users, This is generally gauged basis the customer interviews conducted and as time progresses and we moved from concept note to PRDs, and A/B testing the impact metric can be reported with even more confidence backed by user data</p><p><strong>Effort, </strong>this measure can be relative to the range of weeks a project runs in your org with the one taking the highest number of weeks rated at 10 and the least one rated at 1. Now, basis your estimation of how much time each feature will take, rate the feature on 1 to 10.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*Fuf5k8jj5-Ir2MtMhGRLsg.png" /></figure><p><strong>Confidence </strong>is one part of the framework that has been very mysterious to us since the beginning. But it was after reading <a href="https://itamargilad.com/the-tool-that-will-help-you-choose-better-product-ideas/">Itamar Gilad’s </a>blog on this framework, that we gained some confidence (pun intended). According to the blog, confidence can only be quantified using supporting evidence. Based on the evidence collected, calculate the confidence using the confidence meter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*bMfQHuo8LeBgIwz2" /></figure><blockquote>Source: <a href="https://itamargilad.com/the-tool-that-will-help-you-choose-better-product-ideas/">https://itamargilad.com/the-tool-that-will-help-you-choose-better-product-ideas/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a62ef663b6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/rice-framework-the-staple-of-feature-prioritization-a62ef663b6c">RICE Framework: The staple of feature prioritization</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PM Frameworks 101]]></title>
            <link>https://medium.com/a-case-for-humanity/pm-frameworks-101-572a9cdaeee7?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/572a9cdaeee7</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-prioritization]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Abhinav Garg]]></dc:creator>
            <pubDate>Fri, 24 Sep 2021 15:02:36 GMT</pubDate>
            <atom:updated>2021-09-24T15:03:10.937Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HghSLtczuw7X2yshbidY3Q.png" /></figure><h3>Customer Journey Frameworks</h3><h4>5-E Framework</h4><ol><li>Entice — What event triggers the user to enter into the UX?</li><li>Enter — What are the first few steps in UX Funnel?</li><li>Engage — What task(s) is the user trying to accomplish?</li><li>Exit — How does the user complete the task?</li><li>Extend — What follow-up actions occur after the user completes the task?</li></ol><blockquote>Source: <a href="https://www.lewis-lin.com/blog/2016/11/11/customer-journey-map-the-5es-framework">https://www.lewis-lin.com/blog/2016/11/11/customer-journey-map-the-5es-framework</a></blockquote><h3>Prioritization Frameworks</h3><h4><strong>1. RICE Framework</strong></h4><p><strong>Reach</strong> — How many people will this feature effect within a given time?</p><p><strong>Impact</strong> — How will this impact individual users? (3 = massive impact, 2 = high impact, 1 = medium impact, 0.5 = low impact, 0.25 = minimal impact)</p><p><strong>Confidence — </strong>How confident are we about the impact and reach scores? How much data do we have to back up those estimates? (100% high confidence, 80% medium confidence, 50% low confidence)</p><p><strong>Effort — </strong>How much time investment will this initiative require from product, design, and development? (Measured as persons per month)</p><blockquote>RICE Score = (Reach X Impact X Confidence) / Effort</blockquote><h4>2. Value v/s Effort:</h4><p>List of features and initiatives -&gt; quantify them using value and effort scores</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*AP6_70Hs2ESSrg_oWyryAw.png" /></figure><h4>3. Kano Model</h4><p>The horizontal axis has implementation at 3 levels:</p><ol><li>Must-haves or basic features: If you do not have these features, your customers won’t even consider your product as a solution to their problem.</li><li>Performance features: The more you invest in these, the higher the level of customer satisfaction</li><li>Delighters or excitement features: These features are pleasant surprises that the customers don’t expect, but once provided, create a delighted response.</li></ol><p>The way you get this customer insight is by developing a Kano questionnaire where you ask your customers how they’d feel with or without any given feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4rqEgT1Oifk0Rgon1b5R6Q.png" /></figure><h4>4. Story Mapping</h4><p>Along a horizontal line, you create a series of sequential buckets or categories that represent each stage of the user’s journey through your product.</p><p>Along a vertical line, you then place these tasks in order of importance, from top to bottom.</p><p>Finally, you draw a line across all these stories to divide them into releases and sprints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3fBmmba4fhjZLQIhIy2JSw.png" /></figure><h4>5. <strong>The MosCoW Method</strong></h4><p>Classifying features into four priority buckets:</p><ol><li><strong>Must-Have</strong>: These are the features that have to be present for the product to be functional at all. They’re non-negotiable and essential. If one of these requirements or features isn’t present, the product cannot be launched.</li><li><strong>Should-Have</strong>: These requirements are important to deliver, but they’re not time-sensitive.</li><li><strong>Could-Haves:</strong> This is a feature that’s neither essential nor important to deliver within a timeframe. They’re bonuses that would greatly improve customer satisfaction, but don’t have a great impact if they’re left out.</li><li><strong>Won’t-Have:</strong> These are the least critical features, tasks or requirements (and the first to go when there are resource constraints). These are features that will be considered for future releases.</li></ol><h4>6. Opportunity Scoring</h4><p>Opportunity scoring uses a Satisfaction and Importance graph to measure and rank opportunities. After you come up with a list of ideal outcomes, you then survey your customers to ask them the following questions:</p><p>How important is this outcome or feature? Ask your customers to rank them.</p><p>How satisfied is the customer with the existing solutions?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*9MUzd_8ljm7TDIpaG3r5pQ.png" /></figure><h4>7. Cost of Delay</h4><ol><li>What would this feature be worth if the product had it right now?</li><li>How much would it be worth it if this feature gets made earlier?</li><li>How much would it cost if it was made later than planned?</li></ol><p>The way you assign this monetary value to each feature is by calculating how much time and team effort they will take to build. You and the team can also assign value to the features in terms of how much they will be worth after they’re built.</p><h4>8. Buy a feature</h4><p>The game goes like this:</p><ol><li>Choose a list of features, ideas, or updates and assign a monetary value to each one. This value isn’t arbitrary — it should be based on how much time, money, and effort each feature will cost you and the team.</li><li>Put together a group of people (up to 8 customers or your own internal team). Give them a set amount of money to “spend” on these features.</li><li>Ask your participants to buy the features they like. Some customers will put all of their money on only one feature they’re passionate about, others will spread their cash around multiple different features. Ask the participants to explain why they spent money on the feature they picked.</li><li>Then, reorganize that list of features in order of how much money your customers were willing to spend on them.</li></ol><blockquote>Source: <a href="https://roadmunk.com/guides/product-prioritization-techniques-product-managers/">https://roadmunk.com/guides/product-prioritization-techniques-product-managers/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=572a9cdaeee7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/pm-frameworks-101-572a9cdaeee7">PM Frameworks 101</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Improvement: InShorts News]]></title>
            <link>https://medium.com/a-case-for-humanity/product-improvement-inshorts-news-25236d96f020?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/25236d96f020</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[news-apps]]></category>
            <category><![CDATA[product-improvements]]></category>
            <category><![CDATA[inshort]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Abhinav Garg]]></dc:creator>
            <pubDate>Thu, 27 May 2021 08:32:41 GMT</pubDate>
            <atom:updated>2021-09-24T15:08:52.418Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1OCoZ83rZW-V50DTscuckA.jpeg" /></figure><h3>Introduction</h3><p>InShorts is a news stories app that gives quick 60-word summaries of news from different sources. This is one app on my phone which has a lot of potential to become a great app but limited functionality and some frustrating features make it one of the worst apps on my phone.</p><p>But, before we can look at the problems in the app, I would like to discuss the app’s customers briefly to understand their psyche and then present the pain points in their customer journey.</p><h3>Customers</h3><h4><strong>The City Dweller — </strong>Always in a hurry and wants a quick run-down of daily headlines</h4><p><strong>Behaviours:</strong></p><p>· Early morning commute to office in peak traffic hours</p><p>· Short attention span while reading articles</p><p>· Stay updated on current affairs but not spend too much time reading the newspaper</p><p>· Discuss latest news with peers while at office and other social settings</p><p><strong>Needs and Goals:</strong></p><p>· News in short snippets giving a quick dump on the story</p><p>· Seek relevant news based on interest</p><p>· Keep updated on major headlines everyday</p><p>· A discussion platform to enable communication</p><h4><strong>The News Geek — </strong>Wants an aggregation of all the news sources in one place</h4><p><strong>Behaviours:</strong></p><p>· Addicted to reading news and analysis around it</p><p>· Routinely read major headlines, editorials across different publishing houses</p><p>· Make informed choices basis the economic and political landscape</p><p>· Shifting to digital medium</p><p>· Discuss latest news with peers while at office and other social settings</p><p><strong>Needs and Goals:</strong></p><p>· News aggregated from multiple sources</p><p>· In-depth analysis of the latest news to build an understanding around the issue</p><p>· Digital solution for regular updates personalised to them</p><p>· A discussion platform to enable communication</p><h3>Analysis and Customer Pain Points</h3><p>Inshorts is primarily serving ‘The City Dweller’, with its secondary target segment being ‘The News Geek’. While analysing the user journeys for both the user groups, I found significant gaps that would frustrate a user.</p><h3>Issues:</h3><p><strong>1.</strong> <strong>Constant Notifications — </strong>One of the most annoying features of the Inshorts app is its notification feature. The app constantly bombards the user’s phone with news notifications. The volume of notifications sent out is cumbersome as no user really needs constant updates. The notifications end up annoying a user to an extent that people either uninstall the app or disable the notifications.</p><p><strong>2.</strong> <strong>Lack of news dashboard for headlines — </strong>One of the most important needs of a ‘City Dweller’ is to seek relevant news based on interest quickly. Although, the app asks for user’s interest while onboarding to tailor news to different users, there is no way to see all the top headlines at one place. Swiping through news can be overwhelming esp. when user is unable to find relevant news.</p><p><strong>3.</strong> <strong>Lack of analysis around major headlines </strong>— ‘The News Geek’ highly values<strong> </strong>analysis around major news. InShorts only gives a link to the original article. A user cannot look for related news, let alone analysis around that news. This is especially disheartening for a user as digital news platforms are capable of achieving this but still don’t do it.</p><p><strong>4.</strong> <strong>Complex Personalisation options — </strong>Post onboarding it is extremely difficult to tune personalisation settings around topics interested and the level of detail required for each topic. The option to do the same comes in the menu, where a user can change among ‘All News’, ‘Major News’ and ‘No News’ for 17 categories. This becomes overwhelming for the user and hampers the quality of news delivered to the user.</p><p><strong>5.</strong> <strong>Categorization by region — </strong>Although, InShorts provides categorisation basis topics like Politics, India, Science etc. There is no way to specifically read local and regional news. InShorts does source a lot of its news at hyperlocal level but it is shown at random.</p><p><strong>6.</strong> <strong>Vernacular Language support — </strong>A lot of InShort’s customers reside in Tier-2, Tier-3 and rural areas. With no vernacular support of languages like Tamil, Kannada, Punjabi etc., the customer is left wanting for regional content on the app.</p><p><strong>7.</strong> <strong>Ability to discuss news articles — </strong>InShorts currently does not allow users to discuss news articles on the platform. The only way someone can do this is by sharing the article over Whatsapp or other messaging apps. The inability to get views and provide an opinion on a news article greatly hinders the experience.</p><h3>Solutions:</h3><p><strong>1.</strong> <strong>An elaborate notification and news bulletin system –</strong></p><blockquote><strong>a.</strong> <strong>The News Bulletin</strong> — InShorts can create an elaborate list of headlines personalised to the user’s taste. This bulletin would be available under options in menu. A user can click on any headline to open the story and swipe to next stories.</blockquote><blockquote><strong>b.</strong> <strong>Notifications</strong> — Now, instead of sending out notifications for each news story, the app can send out notification of the latest bulletin at times when user is most likely to read news like during morning commute hours, lunch time or before going to bed.</blockquote><p><strong>2.</strong> <strong>InShorts Local –</strong></p><blockquote><strong>a.</strong> <strong>Support for vernacular language — </strong>With InShorts already sourcing hyperlocal news based on user’s location, adding vernacular support for regional languages will help in improving reach of these stories. This would improve user acquisition and retention.</blockquote><blockquote><strong>b.</strong> <strong>Categorization based on geography — </strong>InShorts must also add a new level of categorization basis the geography. The user should be able to select local and regional news as well.</blockquote><p><strong>3.</strong> <strong>‘InShorts IQ’ — </strong>A new series by InShorts called ‘InShorts IQ’ where InShorts does an in-depth analysis of a particularly famous topic/news. It would discuss the ‘What’, ‘Why’, ‘When’, ‘Where’, ‘Who’ and ‘How’ about the topic/news.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/169/1*MbejAl8LvyPOnCDNRSRJIg.png" /></figure><p><strong>4.</strong> <strong>Easy Personalisation — </strong>In order to make personalisation easier, the 17 categories can be grouped into 4 categories. The user now has to adjust the level of news required for just 4 categories instead of 17. But they can still fine tune the level of news required in sub-categories under each category.</p><p><strong>5.</strong> <strong>InShorts Panchayat — </strong>Create an open forum for the users to discuss latest news, publish local updates and fulfil customer’s desire to discuss news with their peers.</p><blockquote><strong>a.</strong> <strong>In-Line Forum Threads — </strong>Give the customer to open new forum threads on both the article as a whole and on specific lines of the article. The user can also navigate to forum from the options menu or by tapping on the forum button on the article.</blockquote><blockquote><strong>b.</strong> <strong>InShorts Baton — </strong>Users can post local updates around traffic, protests etc. on the forum. If other users have subscribed to local batons, they get notifications about these updates based on their geo-location.</blockquote><blockquote><strong>c.</strong> <strong>InShorts Reverse Tags — </strong>Add ability for the user to share specific lines from the articles to twitter, reddit etc. and enable discussion on external forums.</blockquote><blockquote><strong>d.</strong> <strong>InShorts Shots — </strong>To create a buzzing forum, design an incentive system which awards points i.e., ‘shots’ for each action the user does. For example — 10 shots for starting a new forum, 30 shots for commenting and discussing, 20 shots for posting updates etc. These shots would then create a hierarchical community. Greater the number of shots better the reputation in the community.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/216/1*7ZWM3-vm7SkVEgIfFc8veQ.png" /></figure><h3>Prioritization:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/818/1*vEZDOpr1FR5pXgN2FjQlfg.png" /></figure><p>Based on the above table, InShorts must start of by improving its core features such as notifications, vernacular support and easy personalisation. Post that they must start expanding their features starting on with the InShorts Panchayat and then implementing InShortsIQ.</p><h3>Risks:</h3><p>1. Providing vernacular support for languages across India may require significant effort for InShorts w.r.t. sourcing the news.</p><p>2. InShorts Panchayat, although provides a healthy community to discuss news, post updates, also becomes a place for frauds, cyberbullying etc. InShorts would have to look at ways to mediate the platform at low costs.</p><p>3. The news bulletin may be a concise way to showcase news headlines but integrating it into notifications may not generate enough interest for the user to click the notification and open the bulletin. This feature would require testing to analyse customer behaviour and retention rates.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25236d96f020" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/product-improvement-inshorts-news-25236d96f020">Product Improvement: InShorts News</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Improvement: Spotify for fitness enthusiasts]]></title>
            <link>https://medium.com/a-case-for-humanity/product-improvement-spotify-for-fitness-enthusiasts-3be8b775f709?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/3be8b775f709</guid>
            <category><![CDATA[spotify]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[fitness]]></category>
            <category><![CDATA[product-improvements]]></category>
            <dc:creator><![CDATA[Abhinav Garg]]></dc:creator>
            <pubDate>Mon, 18 Jan 2021 08:11:25 GMT</pubDate>
            <atom:updated>2021-09-24T15:06:04.957Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DzANpcOwzOBxjbFZA0L27g.jpeg" /></figure><p>I regularly listen to music while working out, this helps me to keep myself motivated and maintain the rhythm of my workout. Spotify is my go-to app for the same. While Spotify is a brilliant music discovery app, I have always struggled to get personalised workout music recommendations on the app. Unable to find the workout music that suits my taste, I end up playing songs from the followed playlists.</p><p>A big downside to this is that I can no longer maintain my pace using music, it rather hinders my pace and energy when a slow song starts playing.</p><h3>Target Audience</h3><p>This problem is faced by a majority of fitness enthusiasts around the world. There are two groups in particular:</p><h4>Fitness Enthusiasts:</h4><ul><li>18–35 yrs, Live in the city</li><li>Love to workout everyday</li><li>Exercise is a mode of relaxation</li><li>Always look for good music recommendations on apps</li></ul><h4>Fitness Trainers:</h4><ul><li>25–40 yrs., Live in the city</li><li>Exercise is a source of income</li><li>Train customers for 8–10 hrs/day</li><li>Look for good music to keep customers pumped &amp; entertained</li></ul><h3>What is their customer journey?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*vnXDT4kc_7fqIli7ssnPUg.png" /><figcaption>The journey of a fitness enthusiast</figcaption></figure><h3>The Problem</h3><p>To <strong>keep up the momentum and motivation,</strong> fitness enthusiasts regularly listen to music while working out. While Spotify has a good music discovery ecosystem, it is not geared towards the fitness enthusiasts as they:</p><ul><li>Cannot find <strong>personalised workout music </strong>recommendations on the homepage</li><li>Current workout playlists are<strong> static and hard to find </strong>from the app search page</li><li>Cannot search or sort music based on the <strong>pace or energy</strong> to suit the speed of their workout</li></ul><h3>How big is the impact?</h3><h4>Market Size</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*ETa8L2t5GhnHB3E4BpqFLA.png" /></figure><ul><li>The digital fitness music industry will be <strong>891.2M </strong>users by 2021, <strong>40%</strong> out of whom cannot workout without music</li></ul><p>This comes to a total addressable market size of <strong>357M </strong>users</p><h4>Customer Retention</h4><ul><li><strong>150M (55%)</strong> of the Spotify users are in the age of 18–35 yrs, <strong>120M (80%)</strong> of whom workout regularly</li></ul><p>Hence, the target existing user base for this feature is <strong>120M</strong></p><p>Solving this problem would improve:</p><ul><li>Customer Acquisition</li><li>Customer Engagement</li></ul><h3>Tenets of the Solution:</h3><p>The solution must ensure:</p><ul><li>Users must be able to search and sort the music <strong>based on pace</strong></li><li>Users must get <strong>personalised recommendations </strong>for workout music based on ideal pace for the workout</li></ul><p><strong>Beats per Minute (BPM)</strong> is a good measure for the pace of the music</p><h4>To serve a fitness enthusiast, Spotify needs following competencies:</h4><ul><li><strong>The ideal workout playlist:</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*ATu84oC0w6Pud30eHdKauQ.png" /><figcaption>An ideal workout playlist to sync with the workout routine</figcaption></figure><ul><li><strong>Store BPM: </strong>Store BPM in metadata for each song along with other parameters</li><li><strong>Recommendations based on BPM: </strong>Feed BPM as one of the parameters to the recommendation engine for workout music</li><li><strong>Familiarity v/s Discovery: </strong>Workout playlists with 75% familiar and 25% discovery music</li></ul><h3>Solutions:</h3><h4>Solution 1: <strong>Tailored experience for fitness enthusiasts</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/146/1*QvDtjy3OpG-OP4F4ZWkcLg.png" /><figcaption>Record preferences while onboarding</figcaption></figure><p><strong>Part 1</strong>: Spotify records the user’s preference for ‘listening to music while working out’ while signing up, to identify and tailor the experience for fitness enthusiasts</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/146/1*ocjWZfz7kl9XiQC5NU-vlw.png" /><figcaption>Personalised workout music recommendations on homepage</figcaption></figure><p><strong>Part 2</strong>: Spotify uses the existing recommendation algorithm along with BPM to create personalised workout playlists such as Daily Running Mix, Daily Tabata Mix etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/148/1*PjWfl3nTvkNHtObXuSV6Sg.png" /><figcaption>Workout in top genres on search page</figcaption></figure><p><strong>Part 3</strong>: In order to make it easier to discover workout music for fitness enthusiasts, display Workout in top genres in the search section</p><h4>Solution 2: Search and Sort on Beats per Minute</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/170/1*Hvik5QSB72kJ1KT3OA5_KQ.png" /><figcaption>Spotify lists music with beats in specified range</figcaption></figure><p><strong>Part 1</strong>: Index the BPM for each song in the search database to enable users to search on BPM</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/170/1*LuIXYC2vex1iEkmA5S-leA.png" /><figcaption>Sort on BPM to play music with increasing pace</figcaption></figure><p><strong>Part 2</strong>: Add BPM to the sort options for playlists enabling users to play songs in increasing or decreasing order of BPM</p><h4>Solution 3: Song radio tailored for workouts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/146/1*nWqs9VEZWARuY27uG06ITA.png" /></figure><p><strong>Step 1</strong>: User opens the fitness app and selects the workout routine. For example, Light Jogging, Marathon, Warm-Up etc.</p><p><strong>Step 2</strong>: Based on the workout routine, the app has a pre-set duration of the workout</p><p><strong>Step 3</strong>: User plays music using the Spotify integration on the fitness app</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/146/1*AfMdxohOT4Q012VCbfF3cw.png" /><figcaption>Spotify playing song radio on the fitness app</figcaption></figure><p><strong>Step 4</strong>: Basis the duration of workout and user’s heart rate, Spotify curates the <strong>‘ideal workout’</strong> radio with songs of varying BPM — increasing (main workout) and then decreasing (cool-down)</p><h3>Prioritization:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*MjEBM3ASI0ntTzGrYC1YvA.png" /><figcaption>RICE Framework: Prioritization Matrix</figcaption></figure><p>Based on the score, I would go for the ‘<strong>Tailored Experience</strong>’ solution providing seamless music playing experience to fitness enthusiasts.</p><h4>Implementation Timeline</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*gDbLZ1BgYgrhcZ2F4SLQsw.png" /><figcaption>Implementation timeline</figcaption></figure><p>As features under each solution are overlapping, we may implement all the solutions to provide the full-fledged experience</p><h4>Metrics:</h4><h4>Product wide metrics</h4><p>These metrics will track product wide performance improvements due to the proposed solution</p><ul><li><strong>New Sign Ups: </strong>Track month-on-month change in sign-ups</li><li><strong>% Active Users: </strong>Track month-on-month change in the number of logins</li><li><strong>Time spent on Spotify: </strong>Track month-on-month change</li><li><strong>Average hrs of music played per user: </strong>Track month-on-month change</li></ul><h4><strong>Feature Specific Metrics</strong></h4><p>These metrics will track feature specific usage statistics</p><ul><li><strong>% users opening workout playlists from homepage</strong>: Track day-on-day change</li><li><strong>% users playing workout songs from homepage</strong>: Track day-on-day change</li><li><strong>% users using ‘bpm’ in their search term</strong>: Track month-on-month change</li><li><strong>% users sorting their song queue on ‘bpm’</strong>: Track day-on-day change</li><li><strong>% users invoking Spotify from fitness apps</strong>: Track day-on-day change</li></ul><h3>Potential Pitfalls:</h3><ul><li>The recommendations based on BPM may not be precise enough and may require additional parameters such as bass to be added to the algorithm</li><li>The workout music recommendations may overwhelm the user and hinder regular music discovery</li><li>The indexing and storing of BPM for each song may slowdown the search</li><li>The fitness apps may not share data regarding length of workout and heart rate leading to delay in implementation of the feature</li></ul><h3>Product Strategy:</h3><p>In order to gain traction, acquire and retain more customers, Spotify can:</p><ul><li>Post beta testing, launch the workout feature in collaboration with other sports apparel brands such as Puma, fitness start-ups such as cure.fit etc.</li><li>For future growth, Spotify can also look at creating shared experiences around workouts by launching buddy workout radio where users can listen to the same song radio while exercising together and therefore improving customer engagement</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3be8b775f709" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/product-improvement-spotify-for-fitness-enthusiasts-3be8b775f709">Product Improvement: Spotify for fitness enthusiasts</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Design: A bicycle renting app for tourists (Incomplete)]]></title>
            <link>https://medium.com/a-case-for-humanity/product-design-a-bicycle-renting-app-for-tourists-incomplete-88d6c638004f?source=rss----94bf092ba90c---4</link>
            <guid isPermaLink="false">https://medium.com/p/88d6c638004f</guid>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Soumya Gupta]]></dc:creator>
            <pubDate>Wed, 13 Jan 2021 11:46:05 GMT</pubDate>
            <atom:updated>2021-01-13T11:46:04.917Z</atom:updated>
            <content:encoded><![CDATA[<p>Designing a bicycle renting app for tourists using the CIRCLES framework.</p><h3><strong>Comprehend</strong></h3><ul><li>Where is it located? <em>Europe</em></li><li>Who is it for? <em>Tourists who visit for 2–3 weeks or so</em></li><li>Why do they need it? <em>Convenient, economical, private, without a license — mode of travel</em></li><li>How do they use it? <em>Flexible plans, day plans as well as 1–2 weeks long</em></li></ul><h3><strong>Identify</strong></h3><h4><strong>Persona 1: Solo traveller</strong></h4><ul><li><strong>Demographics:</strong> 18–35 years, educated, single</li><li><strong>Behaviors:</strong> explorer, curious, adventurous, price-sensitive, don’t have a plan, young energy (informal, unaffected by society)</li><li><strong>Needs and goals:</strong> Explore the city and culture, talk to people, economical but good quality plans, flexibility in plans</li></ul><h4><strong>Persona 2: Friends trips</strong></h4><ul><li><strong>Demographics: </strong>22–35 years, educated</li><li><strong>Behaviors:</strong> here to have fun, adventurous, spending time with friends, away from monotony, it’s a small time-bound experience</li><li><strong>Needs and goals:</strong> want to have fun in limited time, high amount of convenience — smooth onboarding procedure, a planned experience — along with trip</li></ul><h4><strong>Case 3: Middle aged tourists</strong></h4><ul><li><strong>Demographics:</strong> 30–45 years,</li><li><strong>Behaviors: </strong>a little more sedate, experimental, time-bound, not for long distances, recreational, time-bound</li><li><strong>Needs and goals: </strong>short, planned, and guided trips, high amount of convenience, fun in limited time</li></ul><h4><strong>Case 4: Family</strong></h4><ul><li><strong>Demographics:</strong> 4 adults, parents above 50+, children 18+</li><li><strong>Behaviours:</strong> here to spend time with family, recreational</li><li><strong>Needs and goals:</strong> high amount of convenience, short day trips for family bonding exercise</li></ul><h3>Report the needs</h3><ul><li>As a <strong>solo traveler</strong>, I want<strong> a safe, private, economical, independent, flexible mode of travel</strong>, so that <strong>I may explore the city at my own pace</strong></li><li>As a <strong>traveler on a friends’ trip</strong>, I want<strong> a convenient, planned, novel, and fun mode of travel</strong>, so that <strong>I may have an unforgettable experience on this journey</strong></li><li>As a <strong>person on a family trip</strong>, I want<strong> a convenient, guided, planned, recreational, intimate mode of travel</strong>, so that <strong>I may explore the city while spending quality time with my family</strong></li></ul><h3>Cut, through prioritization</h3><p>The biggest segments/market size would be from Solo travelers and friends’ trips.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*JCPQiTmMVp3ryLINPZq6xQ.png" /></figure><h3><strong>List the solutions</strong></h3><p>User journey:</p><p>Entice: Interact through social media, hostel receptions, offline advertising, planning itinerary, vlogs from influencers.</p><p>Enter: Download the app, <strong>register (validate ID card), </strong>security fee is optional</p><p>Engage: find the nearest offline bike station from the app maps, check the number of free bikes, complete registration, scan QR code at main dock, pay security, take off!, look for audio guided tours or other quests.</p><p>Exit:</p><p>Extend</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88d6c638004f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/a-case-for-humanity/product-design-a-bicycle-renting-app-for-tourists-incomplete-88d6c638004f">Product Design: A bicycle renting app for tourists (Incomplete)</a> was originally published in <a href="https://medium.com/a-case-for-humanity">A case for humanity</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>