<?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 Prashant Agrawal on Medium]]></title>
        <description><![CDATA[Stories by Prashant Agrawal on Medium]]></description>
        <link>https://medium.com/@prashantagarwal272?source=rss-cc8cf2c721a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*X2wEbGVK58ptbwbl91W7Cw.jpeg</url>
            <title>Stories by Prashant Agrawal on Medium</title>
            <link>https://medium.com/@prashantagarwal272?source=rss-cc8cf2c721a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:07:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@prashantagarwal272/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[Future of World is in the hands of better APIs and not better Products]]></title>
            <link>https://medium.com/swlh/future-of-world-is-in-the-hands-of-better-apis-and-not-better-products-2a113e969820?source=rss-cc8cf2c721a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a113e969820</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Prashant Agrawal]]></dc:creator>
            <pubDate>Sun, 19 Apr 2020 11:21:46 GMT</pubDate>
            <atom:updated>2020-04-24T22:02:07.085Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atEsHK44oe_AWQhJKIy_KA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/kBUfvkbFIoE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Tomasz Frankowski</a> on <a href="https://unsplash.com/search/photos/future?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The above statement might sound quite ambitious and highly optimistic from API’s point of view, but if you realize the way people are building their products these days, it might not be too far from the truth.</p><h3>The current state of the APIs</h3><p>Today, a product without application program interfaces (APIs) that allow software programs to interact with each other is like the internet without the World Wide Web. Just as the World Wide Web opened up the internet’s potential for use by billions, APIs — specifications or protocols for how to exchange information or request online services from an organization — are allowing companies to grow businesses at unprecedented rates by sharing services with external firms.</p><blockquote>A product without APIs that allow software programs to interact with each other is like the internet without the World Wide Web</blockquote><p>The monolithic infrastructure and applications that have powered businesses over the past few decades are giving way to distributed and modular alternatives. These rely on small, independent, and reusable <a href="https://opensource.com/resources/what-are-microservices">microservices</a> that can be assembled relatively easily into more complex applications. As a result, developers can focus on their own unique functionality and surround it with fully functional, distributed processes developed by other specialists, which they access through APIs. Products today are straightforward to customize, and they easily integrate pretty much with any other product (thanks to Zapier, IFTTT, etc.).</p><p>There is a rising wave of software innovation in the area of APIs that provide critical connective tissue and increasingly important functionality. There has been a proliferation of third-party API companies, which is fundamentally changing the dynamics of how software is created and brought to market. Major credit towards this rise, in my opinion, goes to the fact how developers have grown better in <a href="https://medium.com/better-practices/design-apis-like-you-design-user-experience-a7adeb2ee90f">building better APIs by treating them as products</a>. Organizations today have taken this one step further by taking an API first approach towards building applications. An API first approach essentially means that developers are now building their APIs first for products rather than building APIs as side effects to product requirements. They are spending more time designing their API, thinking about business value it will offer, and the developer experience around it.</p><p>APIs enable companies to accelerate their digital transformation in a straightforward manner that allows for greater partnership opportunities, both upstream and downstream of their products or services. They enlarge one’s customer base by tapping into companies in adjacent markets and connecting products and services to theirs so that everyone’s customers win. Companies exposing APIs can earn a direct or indirect fee for allowing the use of their assets. <a href="https://hbr.org/2015/01/the-strategic-value-of-apis">Salesforce.com generates 50% of its revenue through APIs, Expedia.com generates 90%, and eBay, 60%</a>.</p><p>On the other hand, developers can capitalize on the resources already created by another party, without the need to create them from scratch. This spurs creativity and innovation at their end as they can combine several APIs from different sources and create a new service. Such a strategy of building services proves to be faster, cheaper, and more efficient as compared to the strategy of everything in-house, because of the huge amount of time and financial resources the latter requires. But more importantly, it allows companies to focus on their core capabilities and develop differentiated functionality, their “secret sauce,” at higher velocity.</p><blockquote>APIs help companies to focus on their core capabilities and develop differentiated functionality, their “secret sauce,” at higher velocity.</blockquote><p>‘Build or buy’ has always been a key strategic consideration while creating new products and businesses. In the API era, this choice will expand to ‘build or buy or API’!</p><h3>The Big Shift</h3><p>While the ecosystem for API startups is attractive today, I believe it will only become stronger. <a href="https://blogs.gartner.com/rene-buest/2018/10/22/explore-the-api-economy-of-infrastructure-services/">By 2023, 65% of global infrastructure service providers’ revenue will be generated through services enabled by APIs, up from 15% in 2018.</a> Over the last decade, there’s been a broadening of interest in enterprise-oriented technologies like SaaS, Big data, microservices, and AI. APIs are the nexus of all four of those areas.</p><p>Before buying or subscribing for a product, a lot of businesses today evaluate them not only based on the features it offers but also how well it integrates with their existing products, infrastructure, and workflows. APIs play a major role in achieving that. Hyper-globalization and remote work opportunities in today’s world have greatly impacted our choices of products. People want to be flexible in how they use a product and its offerings, and to facilitate that companies have started investing a lot more in APIs. <a href="https://api-university.com/blog/the-api-mandate/">Jeff Bezos was one of the first people to realize this shift back in around 2002.</a></p><p>The increase in the number of people who are now accessing the internet has also raised concerns over the security of user’s data. Companies are now much more concerned about giving access to their entire data to 3rd party applications. Therefore, they are leveraging APIs to provide this data in a transformed manner and on-need basis. This approach also ensures that they have more control and visibility on the data they are sharing.</p><p>APIs are also a key ingredient in building Integrations. Using different types of integrations is turning out to be the fastest-growing and most common way of leveraging a Product. Tools like Slack have amplified their usage by providing a single platform from where people could interact with these integrations and in the most basic way, “Chat messages”. We are now seeing more and more products following similar footsteps by allowing other products to integrate and increase the provided value. Going forward, this trend will ensure that companies will think about integrations as a core part of their business and hence will invest a lot more in APIs to enable these workflows.</p><p>Tools like <a href="https://www.postman.com/">Postman</a> have already made it easy to fiddle with APIs, and if you look at some of their blogs, you will see some interesting use-cases already being solved by just using simple 3rd party APIs (ref <a href="https://blog.postman.com/building-a-restaurant-discovery-service-with-postman/">1</a>, <a href="https://blog.postman.com/wondering-about-air-quality-postman-can-help/">2</a>, <a href="https://blog.postman.com/librarian-building-a-serverless-slack-app-using-postman-and-airtable/">3</a>, <a href="https://blog.postman.com/how-to-make-money-using-postman-chaining-requests/">4</a>). Internet of Things (IoT) is another field that has benefitted a lot from this transition towards API-first ideology. <a href="https://iot.do/global-internet-of-things-iot-market-2017-12">The worldwide IoT market is predicted to touch approximately $1.6 trillion by 2024, indicating a strong 21.1% annual growth from $346.1 billion in 2016</a>. APIs being the backbone of IoT means that this growth will also accelerate a lot of innovation and investment for it and be crucial in creating a much brighter future for APIs.</p><h3>Welcome to the Future</h3><p>To reason better about what the future holds for APIs, we need to first understand it’s future users. Today, developers are the primary users for the APIs, using it to either communicate between services, build integrations, or provide it for 3rd party consumers. But the future will have fewer developers and more “Builders”. One of the most frictional points, when someone wants to build something, is the ability to code it out. But our future generations will probably not know how to code, and that’s what excites me. They will be intelligent and would be more focused on the outcomes expected from a product rather than the effort it takes to build one. In the future, there will be more applications that will allow you to drag and drop business logic, and spit out the most optimized code with far fewer bugs. It might be hard to believe but look just a few years back, how many designers you knew could build their portfolio websites. Those barriers are now being broken with tools like <a href="https://webflow.com/">Webflow</a>.</p><p>Over time, our product tooling is going to get a lot better as well. We will see APIs take the shape of LEGO blocks, and builders will mostly have to put together the right blocks to build a product. Products will get intelligent to automatically visualize the API response, which will kill the need to build User Interfaces. At most, what a builder might need to do is to perform some minor configurations to enable those.</p><p>We will see a rise in newer API protocols that will associate themselves more closely with products. GraphQL was invented to optimize data fetching on mobile devices, fetching only the information that is required by the product. We will see more such innovations to support wearable devices, IoTs, and future breed of applications. <a href="https://www.ibm.com/watson">IBM Watson</a> was just the beginning, allowing developers to use NLP and ML capabilities over the API, we will soon be able to leverage <a href="https://developer.ibm.com/dwblog/2017/quantum-computing-api-sdk-david-lubensky/">Quantum computing as well using APIs</a>, and that will open doors to a completely different dimension of products.</p><p>Future generations will be much more critical of the applications that they want on their devices, and they would favor a more integrated end-to-end experience. Which means product integrations are bound to take center stage, and this will mean that people will stop looking for a new product to solve their needs. They will rather search for an add-on on their existing application. I realized this when I gave up on flight aggregators once I discovered <a href="https://www.google.com/flights">Google Flights</a>. Rather than waiting on products to support a necessary feature, people will start feeling more comfortable in taking actions and building those features for themselves.</p><h3>This is just the beginning…</h3><p><a href="https://techcrunch.com/2019/09/06/apis-are-the-next-big-saas-wave/">Several companies like Stripe, Twilio, Segment, etc. are already riding the API-first wave and are the real success stories of this change</a>. And believe it or not, the world will be driven by APIs. If you still haven’t started moving towards the API-first approach, then I would recommend you give it a serious thought.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a113e969820" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/future-of-world-is-in-the-hands-of-better-apis-and-not-better-products-2a113e969820">Future of World is in the hands of better APIs and not better Products</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An engineer’s guide to Product Management]]></title>
            <link>https://medium.com/@prashantagarwal272/an-engineers-guide-to-product-management-f9c7b7758cad?source=rss-cc8cf2c721a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9c7b7758cad</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Prashant Agrawal]]></dc:creator>
            <pubDate>Sun, 12 Apr 2020 13:16:54 GMT</pubDate>
            <atom:updated>2020-04-12T13:16:54.843Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJS1cx_AZsfkYiYleIqZYg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@campaign_creators?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Campaign Creators</a> on <a href="https://unsplash.com/s/photos/meeting?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>After I decided to transition to Product Management from Engineering, the road towards becoming a Product Manager was not so straight forward. There were a lot of unanswered questions in my mind, even before I started on this journey. Mostly around if this is the right decision for my career, will I be able to create more impact as a Product Manager rather than a Senior Engineer or an Engineering Manager, will this transition bring awkwardness among my peers, what if I fail in this new role, etc.</p><p>That being said, it has been a journey full of new learnings, challenges, and lots of exciting discoveries, most of which I will try to share here. As I progressed as a Product Manager, I met several people who wanted to understand my motivation behind the transition as a Product Manager and were looking to move to Product Management at some point in time.</p><p>With this blog post, I will try to provide my perspective of Product Management, what are the key differences that you would have to embrace as you make the transition, and what are the core skills that you might have to acquire to be an impactful Product Manager.</p><h3>So you want to be a Product Manager, really?</h3><p>Product management as a field has boomed in recent times, and I believe that’s why there are a lot of different opinions on Product Management and what is a Product Manager’s actual job.</p><p>That is why I also feel I should first clear some air around it, and make sure that Product Management is something that you are excited about and that you are not motivated by the myths associated with the job. I have also seen that people selectively only process the amazing aspects of the role. Things like, “<em>You’ll get to be the CEO of a product!</em>” “<em>You get to manage many different teams!</em>” “<em>You get to come up with ideas for features and new products all day long!</em>”. But whenever something sounds too good to be true, always remember the words “There’s no such thing as free lunch.” Some of the most common misconceptions about product management are</p><h4>I get to be the CEO of a product!</h4><p>Let’s get one thing straight. As a Product Manager, you’re going to have to learn to throw away any ego and remember that you own the failures while your team owns the successes. The best teams work well because everyone feels ownership over the product, and it’s your job as a PM to guide your team towards a product vision and give them all the credit. Ideologically, your role will be closest to that of a sports team <strong>coach</strong>. If you win, your team will get celebrated, but if you fail, you might get fired.</p><h4>Being a PM lets me do different types of work in various fields!</h4><p>A lot of people think that being a PM means you get to work directly on all aspects of building a product like engineering, design, marketing, finance, strategy. Depending on the size of your company, there likely will be dedicated teams for each of those functions, and your role will be communicating, planning, and coordinating with each of these teams. As a PM, you should focus on being a champion for your users and understand their needs, so that you can work with your dedicated teams to come up with the right solutions.</p><h4>There’s a ton of satisfaction in shipping the product!</h4><p>Product management is a job that does not have immediate, concrete satisfaction. You’re going to be scrambling around making tons of decisions, and it will take a long time before you see a final product or feature launch. There is no moment of clarity where you find and fix broken code, design the perfect user flow, or have an ideal product that requires no more work because shipping a product is like an infinite game. With every release you learn something new, you then iterate on it to make an improvement and then release again.</p><h4>The PM role is well-respected!</h4><p>Product management may be the one job that the organization would get along fine without (at least for a good while). Without engineers, nothing would get built. Without salespeople, nothing gets sold. Without designers, the product looks like crap. But in a world without PMs, everyone simply fills in the gap and goes on with their lives. It’s important to remember that — as a PM, <strong>you’re expendable</strong>. Now, in the long run, successful product management usually makes the difference between winning and losing, but you have to prove it.</p><p>Now that you have understood what not to expect from the Product Manager role, I want to make sure that you have the right motivation to be the Product Manager and that you are making the right career choice. What I primarily want you to do is take some time off from your busy schedule and ask your self these three questions:</p><p><strong>Q: Why do you want to become a PM? What’s your motivation?</strong></p><p><strong>Q: Do you like thinking about Problems or thinking about their Solutions?</strong></p><p><strong>Q: Why do you believe you will be able to create more impact as a Product Manager as compared to your current role?</strong></p><p>I could have given you my answers to these questions, but that would have prevented you from self-evaluation and probably would have made you force-fit your answers towards your biasing.</p><p>What I would instead recommend you is that you discuss these with the Product Manager in your organization. They have worked with you closely and would help you in understanding the role of a PM better. If you don’t have a PM in your company, feel free to connect with me over <a href="https://www.linkedin.com/in/prashantagrawal1/"><strong>LinkedIn</strong></a><strong>,</strong> and we can discuss this in more detail.</p><h3>So what does a Product Manager actually do?</h3><p>Great PMs do whatever it takes to amplify their team’s impact on the customer experience and business. Product management can sometimes be an unglamorous job, but ultimately there is no greater joy than seeing your product launch and provide value to your users.</p><blockquote>Great PMs do whatever it takes to amplify their team’s impact on the customer experience and business.</blockquote><p>Like most jobs, product management involves more of an attitude than a set of skills. Great product managers:</p><ul><li>Execute impeccably. They say what they’ll do, and then do what they say. Their follow-through is impeccable, and they don’t let details slip. When they join a team, quality and pace seem to dramatically improve overnight as they deal with ambiguous tasks and immediately adapt to get stuff done.</li><li>Voraciously seek out insights about customer needs and pain points through research, experiments, and cross-functional partners. They course correct constantly.</li><li>Always try to fine-tune and build product strategy<strong> </strong>to maximize business impact, so their teams never worry about whether their hard work will matter. They don’t care about accolades from peers, Apple design awards, or press write-ups.</li><li>Talk well and listen even better. Product Managers infuse urgency, foster collective creativity, and build great relationships with all teams they work. They establish consensus by default but can drive hard decisions when they have to. They establish enough credibility to rally a team around a product strategy</li><li>Define and track the key metrics that matter and align the whole org around them. They know how to design and analyze reliable experiments — and know when hill-climbing isn’t worth it.</li><li>Immerse themselves in research, feedback, data, discussions, and the market. They craft thoughtful, inspiring narratives for where the product should go — and the best path to get there.</li><li>Maintain a framework for prioritization as well as make the right product trade-offs</li></ul><p>If you have started doing your research about Product Management, then this is one of the most common representations that you will find about the job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d0iVWMpQYtlbXoqr.png" /><figcaption>Originally from <a href="http://www.mindtheproduct.com/2011/10/what-exactly-is-a-product-manager/">http://www.mindtheproduct.com/2011/10/what-exactly-is-a-product-manager/</a></figcaption></figure><p>This intersection is the minimalistic way to define the different kinds of hats that a Product Manager might have to wear. This in no way means that you need to have in-depth experience of all these three fields, but what you might be expected to have abstract knowledge about, to steer through the different roadblocks, decisions, prioritization while building a product. You can read more about the things that you need to know from every circle <a href="https://blackboxofpm.com/mvpm-minimum-viable-product-manager-e1aeb8dd421">here</a>.</p><p>As a Product Manager, you don’t have to write code, create mockups, sign deals, but your job is to help your team ship the right product to your users that will create more value.<strong> </strong>This also brings me back to the myth that I mentioned above, <em>You’re not the CEO of the product, </em>but you <strong>are a team leader.</strong></p><p>Now that you know what a Product Manager is and what they are job they are supposed to do, it is equally vital that you understand about the things a PM should be very cautious of not doing</p><h4>Thinking you are the customer</h4><p>You’re in the business of building products for customers, and you have to remember that you are not the end-user in the development-use cycle. Learn to take yourself out of the equation and focus on the real facts and data that support creating something people want. Stay away from planning based on the idea that “this feature will be cool to have.” No matter how “cool” it is, this doesn’t mean it will make your customers happy. Know who your target is, and build for their delight.</p><h4>Building your roadmap strategy by your intuition alone</h4><p>This goes back to thinking a feature will be cool to have. You may have an intuition when it comes to creating an excellent product, but you also need to back that gut feeling with some data. The desired end result is customer happiness, which leads to sales, which keep the lights on. Implement A/B testing strategies, feature requests based on valuable user stories, and feedback from your team. Then build the roadmap based on that plus your intuition.</p><h4>Assuming the vision is all yours</h4><p>You are there to support your team, remove roadblocks, and give them the freedom to build. Stay humble and empathetic. Don’t prioritize a feature over another just because it was your idea. Let your developers tell you how they can add features and what they have in mind, and don’t be afraid to work with a team that is smarter than you. This will go a long way when it comes to getting everyone on board with your product and influencing your stakeholders.</p><h4>Using fancy tech jargon and over-the-top designs to get to your point</h4><p>Your job is to tell the product story, explain how much the user experience will improve, and the end results of the new feature or addition, such as more sign-ups, in-app purchases, better retention rate, etc.… In the art of storytelling, we know it’s essential to be clear and concise, and be able to explain the “why” well enough to express how the action will drive business results.</p><h4>Doing everything your CEO, customers, team, and mother ask</h4><p>You should probably do most everything your mother asks, but when it comes to building your roadmap, it’s important to take ideas into account, then back up suggestions with data. Get comfortable with saying “no.” If you accept every task or additional feature suggested, you’ll never have a finished product. Often in product management, done is better than perfect, so leave space to have a finished product, A/B test potential features, then make version 2.0 or updates based on intelligent qualitative and quantitative data.</p><h3>What will be different from your existing role</h3><p>Of all the things that I had to do to prepare myself for the transition, the most challenging one was to drop my engineer’s mindset. Now that doesn’t mean unlearning the skills of an engineer, but to work as a successful Product Manager without being influenced by the engineer in you. During the transition, it might also be expected from you to fulfill your current role and that of a PM. But sooner you detach yourself from your existing role, more impact you will be able to create as PM. Some of the things that have helped me in achieving this transition are:</p><h4>Redefine Success</h4><p>Most of the time, people start considering the effort they put into something as their success. To be a great Product Manager, you need to redefine the way you measure success by calculating the impact that you create for the users, product, and the organization.</p><p>It doesn’t matter if you ship 100 new features unless it either generates more revenue, improves retention, or solves a common pain point of the user. The rest of the organization might consider shipping a new feature as their success, but for you, as a Product Manager, it might be just a waste of resources if it was not able to create an impact.</p><h4>Ship early</h4><p>When teams ship a significant release, you hope to get an immediate hit of value. Even operating on the assumption that you release the perfect solution with no technical issues first time (spoiler alert: it’s unlikely). There has been a massive investment made by your team (in terms of time) that has not returned anything (left diagram).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a459v6NabCSMWH-S.png" /></figure><p>By releasing small and often, you’re shipping incremental pieces of work. It begins to pay off because you can realize value sooner and learn from mistakes faster. Value trends above effort almost consistently in the second graph, and this is what teams should be striving for.</p><h4>There is no “Done”</h4><p>Your job is never done, and the product is never finished. In reality, no product will ever be quite right for everyone. It’s an ongoing process of continued development and iteration to make it better. As a PM you constantly Build, Measure and Learn in a loop</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/397/1*eprQ15NugjAjAZ_lD2eC8g.png" /></figure><p>One other challenge that you might run into while adopting this ideology is to keep your team motivated towards making those small but impactful changes. Engineers love to get challenged by working on larger and meatier features, but as a PM, this is your job to communicate to the team that why these small improvements are way more important than that next upcoming feature.</p><h4>Become obsessed with problems, not solutions</h4><p>It’s straightforward to get attached to a novice solution, which you believe is the perfect answer to the user problem that you are trying to solve. Imagine after three months you released a feature that, according to you, is a groundbreaking feature for your product, but when you looked at your growth numbers, there was no much impact.</p><p>Being obsessed with the solution will make it very tough to do an honest retrospection because you were 100% certain in your mind that it’s going to work. On the other hand, if your entire focus is on the problem in hand, then it’s a fair thing to assume that you would have multiple hypotheses to solve that. And even if one of them fails, you can always try other ones to solve that problem.</p><h3>Core Product Manager Skills</h3><p>Over the past year, I talked to a lot of PMs, trying to understand the essential skills which they see in successful Product Managers. PM role might have different responsibilities in different organizations, but some of the skills that are must for an effective Product Manager are:</p><h4>Communication</h4><p>PMs are information conduits and context builders, and therefore communication is everything. As a PM, it’s your job to communicate vision and strategy for the product in order to persuade people towards the objective rather than asking them to do stuff. Therefore brevity and clarity are your two most important rules to follow when it comes to communicating as a product manager. Don’t use jargon, but instead, make sure you’re speaking the language of whoever it is you’re talking too. Successful PMs are concise, structured, thorough, and persuasive.</p><h4>Prioritization</h4><p>The time of your team is the most precious resource at your disposal, and it’s your most important job to direct that in the right direction. There will always be hundreds of things that people will expect you to do in the product. You will have requests from your CEO, team, customers, etc. but as a PM, it’s your job to choose. Once you grow in this role, you will have your own way/framework of prioritizing things, but remember that core of all those should always be the impact and value that you are creating for your customers. You should be <a href="https://blackboxofpm.com/ruthless-prioritization-e4256e3520a9">ruthless and rigorous in your prioritization</a> and always choose the most impactful thing that you should be doing at that time. How to identify that most impactful thing is where your other skills as a PM will come in handy, such as talking to customers, gathering insights from data, user research, etc.</p><h4>Analytical thinking</h4><p>Great product managers should have the ability to get your hands dirty with analyzing data. While technical skills like coding aren’t mandatory, the ability to analyze data and provide recommendations/insights for the rest of your team is crucial for measuring success. For every feature you push or course of action taken through the life cycle of your product, there should be measurable results that can determine success or impact.</p><h4>Empathic thinking</h4><p>Empathy is the ability to walk in someone else’s shoes, to see and understand the world from their perspective. It is the sentiment of curiosity about who other people are in themselves. If you’re building something for someone else, you’ll be more successful if you can identify with their needs first.</p><p>But empathy is also essential to leading a team, especially for PMs who tend to have responsibility without authority and must earn respect and support of others. If you can see the world through your engineer’s eyes, or from the perspective of your VP of sales, you can understand what motivates them, what frustrates them, and what you can do to help.</p><h4>Decision making</h4><p>Product managers have to make many decisions every day, including product prioritization decisions, product design decisions, bug triage decisions, and many more. But deciding how important a decision is, is the most important decision you can make. In <a href="https://www.amazon.com/p/feature/z6o9g6sysxur57t">Amazon’s 2016 shareholder letter</a>, Jeff Bezos touches on this concept.</p><p>When you are racing against the time to ship out a product, the pace at which you take decisions becomes critical. It might feel great to you to be at the center of every decision that’s being made, but please understand that it’s not going to scale. PMs should be the facilitator of decisions and should care about getting to the right decision, not whether they are right. As a PM, you should layout well-researched trade-offs, set timetables, and structure great discussions. Only in rare situations should you actually “make the call.”</p><p>So finally, If you’ve gotten this far, and you’re brimming with excitement, then maybe it’s time to button up, roll up your sleeves, and start your own product manager journey.</p><h3>FAQs</h3><ul><li><strong>Do I need an MBA degree to become a Product Manager?<br></strong>Well, it depends. If you are transitioning to Product Management in your existing company, then you might not require it. But if you are looking to make the switch to a new company as a PM, then having an MBA degree helps. Also, if you really ask me, people who are looking for PMs with an MBA degree are just looking for their credibility because that’s the only data point these companies have about you. So if you can establish your credibility as a PM, then you don’t need an MBA.</li><li><strong>How much Technical a PM should be?<br></strong>A PM is never required to write code, but what is expected from a Product Manager is that they can understand the system architecture at a high level and can converse with engineers about technicalities of building a new feature.</li><li><strong>What should the initial few weeks of a new PM look like?<br></strong>One of the common mistakes that I have seen new PMs making is trying too hard to establish their credibility a PM by jumping too fast into things that they don’t completely understand. I would say start by meeting your team, conducting 1:1 meetings, understanding the problem space, constraints, understanding about the initiatives that the team had tried before you joined, making sure that you have data available to get insights from, etc. Believe me; it’s ok to take some time to get comfortable rather than starting quickly but off on the wrong foot.</li></ul><h3>References</h3><ul><li><a href="https://medium.com/swlh/6-diagrams-i-use-to-explain-product-management-concepts-b9d9e79880bf">6 diagrams I use to explain Product Management concepts</a></li><li><a href="https://medium.com/@johnpcutler/pm-tip-30-seconds-answers-to-common-questions-2c8a33b6643c">PM Tip: 30 Seconds Answers (to Common Questions)</a></li><li><a href="https://blackboxofpm.com/making-good-decisions-as-a-product-manager-c66ddacc9e2b">Making Good Decisions as a Product Manager</a></li><li><a href="https://blackboxofpm.com/applying-leverage-as-a-product-manager-ffad4a99db24">Applying Leverage as a Product Manager</a></li><li><a href="https://blackboxofpm.com/the-first-principles-of-product-management-ea0e2f2a018c">The First Principles of Product Management</a></li></ul><h3>Books</h3><ul><li><a href="https://www.amazon.com/gp/product/0679762884">High Output Management</a> <em>by Andrew Grove</em></li><li><a href="https://www.amazon.com/gp/product/0307887898">The Lean Startup</a> <em>by Eric Ries</em></li><li><a href="https://www.amazon.com/gp/product/0062060244">The Innovator’s Dilemma</a> <em>by Clayton Christensen</em></li><li><a href="http://amazon.com/gp/product/0981690408">Inspired</a> <em>by Marty Cagan</em></li><li><a href="https://www.amazon.com/gp/product/1591847788">Hooked</a> <em>by Nir Eyal</em></li><li><a href="https://www.amazon.com/Measure-What-Matters-Google-Foundation/dp/0525536221">Measure What Matters</a> <em>by John Doerr</em></li></ul><p><em>P.S: Special note of thanks to </em><a href="https://www.productmanagerhq.com/"><em>Product Manager HQ</em></a><em>, </em><a href="https://www.productschool.com/"><em>Product School</em></a><em> and </em><a href="https://www.mindtheproduct.com/"><em>Mind the Product</em></a><em> for providing a wonderful community for Product Managers, some of the content is inspired from the conversations with the PMs in this community and their resources. I would definitely recommend joining their Slack communities</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9c7b7758cad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build better APIs by establishing API Design Guidelines]]></title>
            <link>https://medium.com/@prashantagarwal272/build-better-apis-by-establishing-api-design-guidelines-ed745d631144?source=rss-cc8cf2c721a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed745d631144</guid>
            <category><![CDATA[api-design]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Prashant Agrawal]]></dc:creator>
            <pubDate>Tue, 07 May 2019 09:10:38 GMT</pubDate>
            <atom:updated>2019-05-07T09:25:34.281Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VaLXoygWcjz_dRPM-AoeZw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/cqkbESEkhjk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mia Baker</a> on <a href="https://unsplash.com/search/photos/design-guidleines?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>In one of my previous article, I talked about how developers can <a href="https://medium.com/better-practices/design-apis-like-you-design-user-experience-a7adeb2ee90f?source=friends_link&amp;sk=cfe63a472d0365ab086e6c09f6f13073">design better APIs using concepts and processes which are used to design beautiful User Experiences.</a> One important point that I touched in that article was how building a <em>design guideline</em> can help you and your organization build quality, consistent and easy to use APIs.</p><p>Most of the organizations already use Design Systems to build UI for their products, but I think it is equally important that we start doing this for APIs as well. As your organizations will scale and will have several services exposing APIs, enforcing consistency will become hard and it might harm the User Experience that developers have with your APIs.</p><p>I understand that building your own <strong>API Design Guidelines</strong> might seem like a daunting and resource consuming task and that’s why to give you a bit of headstart I have published an API Design Guideline template on <a href="https://www.getpostman.com/downloads/"><strong>Postman</strong></a>. You can just import it and start referring it or modify it according to your need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FYgwkcL7GvhxIzTeiyKbsQ.gif" /><figcaption>Importing API Design Guideline template</figcaption></figure><p>Some of the things that this guideline covers are:</p><ul><li>How to name your API URLs</li><li>Which HTTP methods to use and when</li><li>Using the right status codes</li><li>How to support Pagination, Searching, Filtering and Sorting in your APIs</li><li>API Versioning</li><li>How to handle errors and return a response that helps developers debug the issue.</li></ul><p>I hope you would find this useful in designing your next set of APIs. If there is anything more you would want to see as part of this API Design Guideline, please let me know.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed745d631144" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design APIs like you design User Experience]]></title>
            <link>https://medium.com/better-practices/design-apis-like-you-design-user-experience-a7adeb2ee90f?source=rss-cc8cf2c721a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7adeb2ee90f</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Prashant Agrawal]]></dc:creator>
            <pubDate>Thu, 21 Mar 2019 10:07:18 GMT</pubDate>
            <atom:updated>2020-04-19T15:35:04.675Z</atom:updated>
            <content:encoded><![CDATA[<h4>Learn to design better APIs using concepts and processes which are used to design beautiful User Experiences</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G3Pxy90SG5jZHuc8hZcybQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/a2VqhP3d4Vg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong><em>Update</em></strong><em>: This article is now available in </em><a href="http://doublem.org/Design-APIs-UX/"><em>Korean</em></a><em> as well. Thanks to </em><a href="https://www.linkedin.com/in/jae-yeoul-ahn-a01626108/"><em>Jay Yeoul Ahn</em></a><em> for the contribution.</em></p><h3>What is User Experience?</h3><p>User Experience (UX) is the value that you provide to your users when they are using your product. It is a term that is mostly associated with beautiful looking User Interfaces. But, by principle, <a href="https://en.wikipedia.org/wiki/User_experience_design"><strong><em>User Experience Design</em></strong></a><strong><em> (UXD or UED) “is the process of enhancing user satisfaction with a product by improving the usability, accessibility, and pleasure provided in the interaction with the product.”</em></strong><em> </em>Designers spend a decent amount of time to make sure that they make every interaction, every UI element as delightful as possible.</p><p>Producing the best type of UX is mainly processes — the processes that Design/UX teams use to make sure that their design is valuable, desirable, and usable to the community. It is not just about providing a beautiful UI. They make sure that in the design process all stakeholders are involved so that there are no sudden surprises towards the end. They also do enough research, user testing and prototyping to make sure that all the ideas or designs they are generating, those resonate with the target users.</p><blockquote>Design is not just what it looks like and feels like. Design is how it works.</blockquote><blockquote>— Steve Jobs.</blockquote><h3>Why you should care about API Design?</h3><p>The way we see an API’s lifecycle at Postman, it contains stages like Designing, Debugging, Automated testing, Documenting the API, Monitoring and Publishing the API so the end users can start consuming it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*IOixL_dpklhfKJuHdLHvEg@2x.png" /><figcaption>API Lifecycle</figcaption></figure><p>“Designing and Mocking an API” is the first and most important step of this lifecycle. Any good engineer can tell that if you start with a shaky foundation or bad bedrock, you’re going to collapse, and the same is true for APIs. If you haven’t done a good job in designing the API, it will have cascading effects on other steps in the lifecycle.</p><p>When APIs have already been built, changes are difficult, expensive and time intensive. Even worse, the changes to published APIs might break any client using the API. The design allows for planning all the details, iterating over several proposals and perform what-if analysis. Moreover, <a href="https://medium.com/postman-engineering/api-first-software-development-for-modern-organizations-fdbfba9a66d3">changes made to the API in the designing stage are easy and cheap to perform</a>.</p><blockquote>API Design helps us to avoid building the wrong API, or API in the wrong way</blockquote><p>Still, you will find developers spending more time on developing and coding their APIs rather than designing them. APIs are considered to be consumed by machines and not a user-facing entity, as a result of which many organizations don’t spend enough attention and resources to set up a design process for APIs. But today, when the microservice architecture is taking the world by storm, APIs are starting to look more like a product rather than a technology. They should be seen as a way to provide the functionality to end user.</p><blockquote>In the API space, we build something on a machine for a machine to use and this is wrong because there are people on the other side of API clients.</blockquote><blockquote>— <a href="https://twitter.com/mitraman">Ronnie Mitra</a>, Director of Technology at Publicis Sapient</blockquote><h3>Designing a better UX, but for APIs</h3><p>Many RESTful APIs that are designed today are nothing more than object browsers delivering internal representations of the domain/business objects over HTTP/S as a transport layer. So, how can you get better in designing APIs, how can you make sure all the APIs that you design follow consistent patterns, how can you make sure that new people joining the team do not reinvent the wheel of making design decisions about API that rest of the organization has learned over time. If you read those above questions again what you will find missing is a process of API design similar to the one UX designers employ and these are the kinds of problems that are being solved by them every day.</p><p>A great UX should ideally follow the usability rules defined by <a href="https://semanticstudios.com/about/">Peter Morville</a> known as <a href="https://semanticstudios.com/user_experience_design/">UX Honeycomb</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*-YcF_LjLY5SDq14isGDx-Q.png" /><figcaption>The UX Honeycomb</figcaption></figure><p>In order to design an API with a great UX, you should answer these questions while designing it:</p><ol><li><strong>Useful</strong>: Is the API useful from an end user’s point of view?</li><li><strong>Usable</strong>: Can the API be quickly used by a developer and provide easy-to-use functionality?</li><li><strong>Desirable</strong>: Is the functionality provided by the API something that generates desire in developers and end users?</li><li><strong>Findable</strong>: Can the API documentation be found easily, and can developers start using it immediately?</li><li><strong>Accessible</strong>: Can the API provide functionality for end users who have technical constraints/limitations in consuming it?</li><li><strong>Credible</strong>: Is the data provided by the API trustworthy?</li><li><strong>Valuable</strong>: Does the API contribute to the company’s bottom line and improve customer satisfaction?</li></ol><h3>Defining a Design Process for APIs</h3><p>The strength of a design lies as much in the steps taken to create it as in the final result. A design process helps you to remain transparent and efficient while designing a solution. It sets a clear expectation and decreases the risk of delivering unwanted results.</p><p>The <a href="https://www.designcouncil.org.uk/news-opinion/design-process-what-double-diamond">Double Diamond</a> design process by the<em> </em><a href="https://www.designcouncil.org.uk/">British Design Council</a> is one of such many design processes. It allows people to make intentional design decisions by exploring various options (divergent thinking) while validating stronger ones and weeding out the weaker ones (convergent thinking).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1QxeZfAl9MCFWKNShtu1YA.png" /><figcaption>The Double Diamond design process</figcaption></figure><p>This approach will help you in achieving two of the most important things in any design process:</p><ol><li>Designing the Right Thing</li><li>Designing the Thing Right</li></ol><h4>Designing the Right Thing</h4><p>This phase is split into <em>Discover/Research</em> and <em>Define/Synthesis</em>. While designing something new it is very easy for people to blow the actual scope of the problem and put all their effort into designing something that no one actually wants or will use. This phase of designing keeps us grounded and makes sure we are designing for the right thing by doing diligent research and defining the right problem statement to solve.</p><p><strong>Discover/Research: </strong>When you are building a new Product, Feature or an API you are trying to solve a problem. In order to provide a solution, you need to first understand the problem. Always start by acquiring the <em>Domain Knowledge</em><strong><em> </em></strong>about the problem. Try to understand what problem you are trying to solve, who is this being built for etc. Clarify on the use-cases and the requirements. Research on existing solutions to understand how they are solving the same problem and what you can learn from their architectural/technical decisions. Talk to all the teams inside/outside your organization that are stakeholders for this new API which might include Product Team, Design Team, Security Team, etc. Their different perspective will give you a broader view to think about your API and the technical decisions that you are planning to take from that point onwards.</p><p>You can also leverage the <a href="https://www.getpostman.com/api-network/">Postman API Network</a> for your research or reference to find out how different organization’s APIs looks like. Postman’s API Network contains a diverse list of APIs which are published by organizations from a lot of different domains and industries. For example, if you are building the API in FinTech space, for your research you can check some of the APIs published by other organizations in the Financial Services section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zqNNlpY3wjt70woh0WO5jg.png" /><figcaption>API Network inside Postman app</figcaption></figure><p>This step will result in a lot of unstructured information, overlapping and conflicting use-cases/requirements. So in the next step, structure this information so that you can make better design decisions around your API.</p><p><strong>Define/Synthesis: </strong>From the raw data, find trends and insights that span across different users and scenarios. Try to pin down exact use-cases and requirements you are planning to cater. This stage of the process is also the right time to flag off any dependency that your API might have on another service, which is quite common in a microservices architecture. Define your Resource Models and relationships between them, which will help you in identifying all the Resources for which you would need to expose APIs. You should also clearly outline the behavior and expectations of the API so that consumers don’t have to make any assumptions while using your APIs. Doing this will help you identify the amount of business logic that will be part of the service or the client.</p><h4>Designing the Thing Right</h4><p>This phase is split into <em>Develop/Ideation</em> and <em>Deliver/Implementation</em>. This phase will ensure that whatever you decide to design, it’s designed the right way to ensure that you are not compromising with quality, consistency, security and the best practices outlined by the organization/industry.</p><p><strong>Develop/Ideation: </strong>Once you are clear on ‘what needs to achieved’ using APIs, it’s time to design those APIs so that you can communicate on what you as API provider intent to ship. API Description Languages such as OpenAPI/Swagger, RAML, etc are a great way to express important aspects of an API. Especially the frontend design decisions and architectural design decisions, which are visible to the consumer, can be captured by API description languages. But one drawback with these API description languages is that they can get way too technical, verbose and difficult to collaborate upon. So alternatively what you can do is import <a href="https://learning.getpostman.com/docs/postman/collections/data_formats/#importing-swagger">Swagger</a>, <a href="https://learning.getpostman.com/docs/postman/collections/working_with_openAPI/">OpenAPI</a> or <a href="https://learning.getpostman.com/docs/postman/collections/data_formats/#importing-raml">RAML</a> specification files into <a href="https://learning.getpostman.com/docs/postman/collections/intro_to_collections">Postman Collection</a>.</p><p>If you have worked closely with a UX/Design team before you would have noticed that some of the outcomes at the end of their designing process are documentation around all the features and interactions, representation of various states of UI (error states, empty states, etc) and a prototype which demonstrates the exact interaction with the UI and what should be the expected outcome.</p><p>Using Postman collections you can also achieve the same outcome for your APIs and provide total transparency to all the stakeholders around it.</p><ul><li><strong>API Documentation: </strong>You can <a href="https://learning.getpostman.com/docs/postman/api_documentation/intro_to_api_documentation/">document your collection, folders, requests</a>, up to the granularity of documenting headers, query parameters, etc in the request. Along with this, Postman also <a href="https://learning.getpostman.com/docs/postman/api_documentation/publishing_public_docs">generates beautiful looking documentation</a> out of the box which can be shared with anyone.</li><li><strong>Different API scenarios/states: </strong>You can design different <a href="https://learning.getpostman.com/docs/postman/collections/examples">Examples</a> for every API so that consumer knows what request to send and what response to expect. Generally, it’s recommended that you add examples for all different request/response scenarios possible for the API, including error responses, empty responses, etc.</li><li><strong>Prototype: </strong>You can create a <a href="https://learning.getpostman.com/docs/postman/mock_servers/intro_to_mock_servers">Mock server</a> that will return the designed examples as a response. This is very helpful because it immediately enables your API consumers and they can start prototyping /testing their use cases even though the actual API is not ready.</li></ul><p><strong>Deliver/Implementation: </strong>After you have successfully designed your APIs now is the time to start implementation. But before you start coding your APIs you should establish a <a href="https://medium.com/postman-engineering/consumer-driven-contract-testing-using-postman-f3580dba5370">Contract Test</a> for your API which will ensure that if anything changes during development in the agreed API request/response design, these Contact tests will start failing. Then you can either update your code or inform all the affected teams. Also, it is very easy in <a href="https://learning.getpostman.com/docs/postman/launching_postman/collaboration">Postman to collaborate </a>with your entire team. You can constantly receive feedback using <a href="https://learning.getpostman.com/docs/postman/collections/commenting_on_collections">comments</a> while you are actually developing your APIs and any changes that you make will instantly be made available to everyone involved in the process.</p><h3>Building a Design Style Guide, but for APIs</h3><p>When you are working in a growing team with new people joining in every now and then, after a certain point of time it becomes very difficult to ensure the quality, consistency, and security of the APIs. Imagine what would happen if every new developer will start following their own convention of naming endpoints, using Authorization, headers query parameters, success and error response structure, etc while developing an API.</p><p>Design teams face a similar challenge when creating a new UI. They solve this by building Design Style Guides which make sure that everyone in the team uses the same UI component, colors, typography, etc. Using Design Style Guide it becomes easy to communicate between teams, keep UI consistent in the long term and bring agility in the design and development processes.</p><p>So, why not have a <a href="http://apistylebook.com/">Design Style Guide for APIs</a> itself? Companies like <a href="https://cloud.google.com/apis/design/">Google</a>, <a href="https://github.com/Microsoft/api-guidelines">Microsoft</a>, <a href="https://github.com/CiscoDevNet/api-design-guide">Cisco</a>, <a href="https://github.com/paypal/api-standards/blob/master/api-style-guide.md#version">Paypal</a>, and many more rely on these API Styleguides to make sure their APIs remain consistent, look cohesive and intuitive. The benefits of consistency accrue in aggregate as well; consistency allows teams to leverage common code, patterns, documentation and design decisions. It will also ensure to make the developer experience as smooth as possible, for both API producer and consumer. Some of the important things that should be part of an API Style Guide are:</p><ul><li><em>URL Structure: </em>How should a URL format for a given resource look like, what should be the path, query parameters, etc.</li><li><em>Request methods: </em>Define a list of request method and define when to use which request method. This will make sure that request methods have the same behavior across your APIs.</li><li><em>Request/Response Headers: </em>List of headers that should be used with the API while requesting to service and responding back.</li><li><em>Response status codes: </em>Create a list of allowed status codes for your API and clearly set the guidelines on when to use a specific status code.</li><li><em>Errors: </em>Design a common error response format that all other developers can use. A good error response should let a developer recognize, diagnose and recover from errors.</li><li><em>Versioning: </em>Establish guidelines on how to version an API and points to keep in mind while versioning an API.</li><li><em>Filtering/Pagination/Sorting: </em>How to support filtering and pagination in your APIs which returns a collection of data, what should the response JSON look like with filtered/paginated/sorted result.</li></ul><p>To help people quickly get started, I have published a collection as a template that you can import and start fiddling around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FYgwkcL7GvhxIzTeiyKbsQ.gif" /></figure><h3>A final thought</h3><p>Like all other design processes, the API design process also needs to be an iterative process. Publishing an API to your users is not the end of an API’s lifecycle. You have to keep the channel of constant feedback from API consumers always open and make sure that you keep accommodating suggestions using the same design process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7adeb2ee90f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-practices/design-apis-like-you-design-user-experience-a7adeb2ee90f">Design APIs like you design User Experience</a> was originally published in <a href="https://medium.com/better-practices">Better Practices</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Snapshot testing  for APIs using Postman]]></title>
            <link>https://medium.com/better-practices/snapshot-testing-for-apis-using-postman-7f9f26295d6b?source=rss-cc8cf2c721a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f9f26295d6b</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[postman]]></category>
            <dc:creator><![CDATA[Prashant Agrawal]]></dc:creator>
            <pubDate>Wed, 13 Feb 2019 11:38:16 GMT</pubDate>
            <atom:updated>2019-04-11T22:30:46.713Z</atom:updated>
            <content:encoded><![CDATA[<h3>Snapshot testing for APIs using Postman</h3><h4>Test your APIs without breaking a sweat using saved API responses as Snapshots.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Yds6zVJfyTISChkNeofMA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/8Zt0xOOK4nI?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dietmar Becker</a> on <a href="https://unsplash.com/search/photos/comparison?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Writing tests, most of the times is not a breeze. <a href="https://hackernoon.com/common-excuses-why-developers-dont-test-their-software-908a465e122c">Writing good tests with acceptable code coverage takes time, effort, practice, and patience</a>. Probably that’s why you would find “Write Tests” as the last to-do item in most developers’ task list. This situation gets worse in the case of startups or early-stage companies because the time, effort and resources spent on writing tests are not justified by the business.</p><blockquote>Writing good tests with acceptable code coverage takes time, effort, practice, and patience</blockquote><p>In this blog post, we will try to address this for APIs. We will talk about <strong>Snapshot Testing, </strong>a style of testing which removes much of the manual coding and boilerplate, leaving the test runner to compare the produced result against a saved <em>snapshot</em>. Snapshot testing became a major thing for UI tests, thanks to <a href="https://jestjs.io/docs/en/snapshot-testing">Jest test runner</a> by Facebook that includes it by default. Before starting on how to get this working in Postman, let us first understand what is Snapshot Testing in principle.</p><h3>What is Snapshot Testing?</h3><p>Imagine a unit test.</p><pre>const add = (a, b) =&gt; a + b</pre><pre>it(&#39;adds numbers&#39;, () =&gt; {<br>  expect(add(2, 3)).toBe(5)<br>})</pre><p>The test computes a value using a call to add(2, 3) and compares it to a hard-coded value of 5. How did we get this expected value 5? Well, I (the human developer) took a piece of paper and a pencil and added 2 + 3. Easy.</p><p>Imagine a real-world unit test. Would computing the expected value be as simple as adding two small numbers? No. A more complex algorithm would generate a large object as a result, not a single number. For example, if we are unit testing an API response that response could be a really big nested JSON object.</p><p>Ideally, you would either write tests for each and every individual property of the response or write a huge schema that this response will validate against. This sounds good if you have 2–5 requests but imagine doing this same tedious task for 100s of requests.</p><p>Now imagine what if you could test this something like</p><pre>it(&#39;returns top seller item&#39;, () =&gt;<br>  api.get().then(item =&gt;<br>    expect(item).toMatchSnapshot()<br>  )<br>)</pre><p>The item returned from the API should match its saved snapshot. Here a snapshot is nothing but just the <strong>Gold Standard</strong> of how your item should look like.</p><h3>Snapshot testing strategies</h3><p>Ideally, a snapshot should be exactly equal to the result that you are trying to test but in reality, this might not be true (especially in the case of APIs). Therefore, based on your specific needs and type of responses that you are trying to test, you can choose any of the following snapshot testing strategies for your APIs:</p><ol><li><strong>Response should exactly match the saved snapshot.</strong> This strategy is useful if your API response is static and doesn’t change often. The downside of this approach is that it is too rigid, any small change (even the one that you are not worried about) will cause the test to fail.</li><li><strong>Response should have a snapshot as its subset. </strong>This strategy makes sure that if new properties get added to the response, it doesn’t affect your test. This strategy is not helpful if your response consists of properties whose values are dynamic.</li><li><strong>Response should match the JSON Schema generated from the saved snapshot. </strong>This strategy generates a basic schema from your save snapshot and check the validity of the API response against this generated Schema. If you want more control on how this Schema should look like then you can create the Schema manually and save it as a snapshot, rather than saving the expected API response. This requires a bit of effort when creating a Schema but it will make sure that it establishes a defined contract about the structure of response with the author of the API.</li></ol><h3>Snapshot Testing in Postman</h3><p>Now that we have seen what is a Snapshot and what Snapshot Testing is about, let us build it out for the requests inside Postman. <a href="https://www.getpostman.com/">Postman</a> is an <strong>API Development Environment</strong> <strong>(ADE)</strong> which means it comes with all the building blocks that we would need to achieve snapshot testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qF63WnZI4LabqE6AJ5QnRw.png" /><figcaption>Setting up snapshot testing collection</figcaption></figure><ul><li><a href="https://learning.getpostman.com/docs/postman/collections/creating_collections/">Create a collection</a> and save a request in that collection. This will be the request for which we will be saving as a snapshot.</li><li>As we saw in the previous section, snapshots are nothing but an ideal representation of how the result should look like. We will save our request and its response as <a href="https://learning.getpostman.com/docs/postman/collections/examples/">Example in Postman</a>, which in essence will behave as a snapshot of this request. This is very helpful because rather than a separate place, your snapshots can exist alongside the request you want to test. This makes it really easy to debug in case of failing tests. So, now we go ahead, send the request and save the response as an example.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QiCSQdyl5KcPq-uzIoHyuA.gif" /><figcaption>Save response as an example</figcaption></figure><ul><li>In the previous step we saved our snapshot, but how will we use them in our <a href="https://learning.getpostman.com/docs/postman/scripts/test_scripts/">Test Scripts</a>?? Well, Postman allows you to create <a href="https://learning.getpostman.com/docs/postman/mock_servers/intro_to_mock_servers">Mock Servers</a> on top of your collection and the response of these Mock requests is the response that you saved in the Example. So let’s create a mock server on the collection.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h4rVTNmzxsFCqdX4W7eWTA.gif" /><figcaption>Create a mock server</figcaption></figure><ul><li>Now what we need to do is fetch the snapshot from the Mock server that we created, inside our test script so that we can compare it against the actual API response. We need to first <a href="https://learning.getpostman.com/docs/postman/mock_servers/setting_up_mock">create the Mock</a> endpoint from where we will be fetching the snapshot and then use <a href="http://blog.getpostman.com/2017/10/03/send-asynchronous-requests-with-postmans-pm-api/">pm.sendRequest()</a> to fetch the snapshot.</li><li>I recommend adding this <a href="https://learning.getpostman.com/docs/postman/scripts/pre_request_scripts/#adding-a-pre-request-script-to-a-collection-or-folder">script at the collection or folder level</a> so that whenever you add any new request, all you need to do is save its response as an Example and you will get a snapshot test for that request out of the box. Also updating the Test becomes as simple as updating the Example response with the updated snapshot.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6KBL5RbCgu1OBHcUS8pE9Q@2x.png" /><figcaption>Snapshot testing workflow using Postman</figcaption></figure><p>So as you can see how simply we created our very own snapshot testing framework using Postman. It also fits very well with other testing strategies like <a href="https://medium.com/postman-engineering/consumer-driven-contract-testing-using-postman-f3580dba5370">Consumer-driven Contract Testing</a>. To help you get started with snapshot testing I have already published a <a href="https://documenter.getpostman.com/view/1372588/S1ENxJFZ">Postman collection</a> with all the above strategies. Alternatively, you can also import this collection from Postman Templates. Just follow the steps mentioned in that collection to get it running and you will be all set to test your APIs using snapshots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8TLLr4XPd90I0pHBifsllw.gif" /><figcaption>Import snapshot testing collection from Postman Templates</figcaption></figure><p>For more interesting workflows and testing strategies, follow <a href="https://medium.com/postman-engineering">Postman Engineering</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f9f26295d6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-practices/snapshot-testing-for-apis-using-postman-7f9f26295d6b">Snapshot testing  for APIs using Postman</a> was originally published in <a href="https://medium.com/better-practices">Better Practices</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building XPATHs for React apps]]></title>
            <link>https://medium.com/@prashantagarwal272/building-xpaths-for-react-apps-7126247f020c?source=rss-cc8cf2c721a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/7126247f020c</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[postman]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Prashant Agrawal]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 17:44:19 GMT</pubDate>
            <atom:updated>2018-10-22T17:44:19.735Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently at Postman we decided to build “In-app Lessons” to provide our users with an unique on-boarding experience. The objective of the lessons is to skill up our users on different features inside Postman.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Z3zyG1xJKVd72B6qYElwA.gif" /></figure><p>One of the major part of building this on-boarding system was to have the capability to reference parts of UI so that we can attach popovers while running a lesson.</p><p>But the problem here is that these lessons exists separately on a service and Postman app just fetches the required lesson and run it. So we needed to create a way that this service can reliably use to create lesson steps (popovers that are attached to an UI element).</p><p>We couldn’t use traditional query selectors or <a href="https://developer.mozilla.org/en-US/docs/Web/XPath">xpaths</a> because they are tightly coupled with the DOM and the way how components are structured. Also there is always this risk that some attributes or elements could be removed during refactoring or implementing new features.</p><p>After some brainstorming and POCs we built our own flavour of <strong>XPATHS</strong> by leveraging React and its <a href="https://reactjs.org/docs/context.html">context</a> API.</p><p>The idea here is to wrap all the components that you want to make referenceable with <strong>XPATH </strong>Component. What this enabled us to do is create a skeleton structure of our entire app which can be referenced and also allowed developers enough flexibility to build new features without worrying about removing or changing these XPATHs.</p><pre>&lt;XPATH identifier=&#39;app&#39;&gt;</pre><pre>  //...<br>  <br>  &lt;XPATH identifier=&#39;sidebar&#39;&gt;<br>  <br>  //...</pre><pre>  &lt;/XPATH&gt;<br>  &lt;XPATH identifier=&#39;main&#39;&gt;<br>  <br>  //...</pre><pre>    &lt;XPATH identifier=&#39;requestSection&#39;&gt;<br>  <br>      //...</pre><pre>    &lt;/XPATH&gt;<br>  &lt;/XPATH&gt;<br>&lt;/XPATH&gt;</pre><p>So from above you can see that now we have 4 sections that we can reference and also now developers can add/remove any code that they want without touching these XPATHS. Lets say a lesson step needs to show popover on “requestSection”. The way to reference it is <strong>app/main/requestSection</strong>.</p><p>We used <em>context</em> from React to provide parent’s path to its children. The XPATH components down in the React tree just compose on top of the paths provided by the parent and then again pass down this composed path. Now whenever an XPATH component is mounted, it registers the DOM node it is wrapping against its final path. Below I have added a codesandbox which shows a trimmed down version of the XPATH that we implemented inside Postman.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodesandbox.io%2Fembed%2Fzk2w1w6x5x&amp;url=https%3A%2F%2Fcodesandbox.io%2Fs%2Fzk2w1w6x5x&amp;image=https%3A%2F%2Fcodesandbox.io%2Fapi%2Fv1%2Fsandboxes%2Fzk2w1w6x5x%2Fscreenshot.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codesandbox" width="1000" height="500" frameborder="0" scrolling="no"><a href="https://medium.com/media/aef09cbaf911f48ee0b71ccb8d84d516/href">https://medium.com/media/aef09cbaf911f48ee0b71ccb8d84d516/href</a></iframe><p>Along with this, for more seamless orchestration of lessons, XPATH component inside Postman app emit <em>registered</em> and <em>unregistered</em> events so that the on-boarding system knows that the XPATH is ready and can be used for attaching Popovers. Also rather than just mounting and unmounting, developers can control when they actually want to make this XPATH register/unregister by passing a prop. A use case for this was that inside our app there were certain sections of UI which are always mounted but are made hidden using CSS and we don’t want it to be made available for reference until it is actually visible on the UI.</p><h3>Future ahead…</h3><p>With these XPATH now we have the capability to create on-boardings for ideally anything inside the Postman app. This also enables our developers to very easily make new features on-boarding ready by just adding XPATH around their components. In future we want to build more flexibility around using these xpaths like we have in traditional query selectors or xpath.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7126247f020c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>