<?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 Pravir Shanker on Medium]]></title>
        <description><![CDATA[Stories by Pravir Shanker on Medium]]></description>
        <link>https://medium.com/@pravirshanker?source=rss-72dc363beb89------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*LXaleaqEgtNZbJqb7t4NPw.jpeg</url>
            <title>Stories by Pravir Shanker on Medium</title>
            <link>https://medium.com/@pravirshanker?source=rss-72dc363beb89------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:45:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pravirshanker/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[A Day in the Life of a Razorpay Product Manager — Unfiltered]]></title>
            <link>https://medium.com/razorpay-unfiltered/a-day-in-the-life-of-a-razorpay-product-manager-unfiltered-7a145a21ced8?source=rss-72dc363beb89------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a145a21ced8</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager-interview]]></category>
            <category><![CDATA[product-manager-skill]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-manager-job]]></category>
            <dc:creator><![CDATA[Pravir Shanker]]></dc:creator>
            <pubDate>Fri, 19 Feb 2021 08:37:01 GMT</pubDate>
            <atom:updated>2021-02-19T11:23:38.154Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Day in the Life of a Razorpay Product Manager — Unfiltered</h3><p>Reading Time: 6 minutes</p><p>“A product manager is the CEO of the product” — one of the most advertised quotes for PMs, and I guess no PM would disagree with it.</p><p>And being the CEO you can’t expect any two days to be identically the same or in fact, there is a high chance that all of the weekdays stand way apart. This generally happens because a typical product manager does everything to build the right product for the end customer and most of the time it also depends upon what stage of the product development they are into.</p><p>It would be hard to pen down everything that a PM does on a day-to-day basis but the below schedule will give you a fair idea of general activities that all product managers at Razorpay do every day for building the right product for our customers.</p><p>Razorpay being an employee-first company, never enforces any specific login time for the employees. Still, all the Razors kick off their day max by 11:00 AM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8VqBpiRXb8zL-9Pg.jpg" /></figure><p><strong>Pulse Check on Numbers</strong> — Being a leader in the payment industry, PMs at Razorpay is surrounded by a lot of data. Every PM kick starts their day by looking into their Northstar metrics for the past day. Looker being our analytical tool, we ensure that L0, L1, L2, L3, L4 metrics are pushed on respective slack channels every day so that it’s easy to consume by anyone.</p><p>Any anomaly detected would be reported immediately to the concerned team. Sometimes it could be due to external factors for which partner or bank will be contacted for finding the root cause and resolution.</p><p>Starting the day by looking at all the metrics of the product has helped me a lot in terms of building muscle memory around numbers, this practice also comes in handy when I deal with cross-functional stakeholders and customer conversations. Due to automation from Looker and integration with Slack, it hardly takes 5 minutes to be on top of metrics.</p><p>Focussed Work — Everything related to product documentation goes into this space because you need to ensure that your PRD captures all the requirements in the crispest way so that it’s easy for engineers to consume.</p><blockquote><a href="https://razorpay.com/unfiltered/how-razorpay-is-building-great-products-by-avoiding-traditional-prd-approach/"><em>Follow this link, </em></a><em>just in case if you want to know our PRD structure. 🙂</em></blockquote><p>This slot is also used for the conceptualization of ideas that were discussed sometimes with internal stakeholders or merchants. Writing down ideas onto the paper gives clarity of thought on actual work that might be required to accomplish the task and whether it would be beneficial for the customers or not.</p><p>Completing a document gives me a feeling of accomplishment as I am the one who loves to document almost everything. And hence this is my favourite slot of the day, which I enjoy a lot. Firefighting days don’t let me work on this, but somehow I ensure that I do this at least 3days in a week.</p><p><strong>Daily Standup</strong> — A daily 15-minute team standup is conducted by EMs every day, which is generally a standard part of the agile development process. This is a common time when engineers, product managers, and designers on our team assemble to share updates from yesterday and planned tasks that would be accomplished today. Every team has its own Jira board, which is used for managing the standups.15 minutes of discussion gives a complete view of the progress the team made yesterday.</p><p><strong>Email and Slack Check</strong> — Being product manager of payment methods, my inbox and Slack is usually flooded with updates, reminders, follow-ups, and escalations. Superhuman helps me to figure out the priority emails and I ensure to address them immediately. Slack being a communication channel at Razorpay, helps to organize and set reminders on messages. This takes approx an hour or so but gives enough visibility on all things happening in and around payments.</p><p><strong>Lunch</strong> — Prior to a pandemic, in-person lunch with colleagues in the office used to be pure bliss and a refreshing session, as it was a great way to talk about something other than work.</p><p><strong>Afternoon Catchups</strong> — PM at Razorpay deals with multiple cross-functional teams on a day-to-day basis and it’s important to have regular discussions with them to have a 360-degree view of things happening in and around. These discussions can be categorized into:</p><ul><li><strong>Sprint Planning meeting with engineers and designers </strong>— PMs decide what would go into the sprint as per the priority and also, evaluate the prior sprint backlogs. EMs would get the update from the engineers, designers and conclude on the sprint performance.</li><li><strong>Huddle with the Sales team on new product launch</strong> — Launching multiple products with release notes is a common practice among PMs, but at the same time, one needs to ensure that the launched product is able to entice the sales team. Razorpay PMs create a sales pitch deck and production demo environment for all the new releases. PMs, give a walkthrough on the feature released along with key differentiators from the competition. With a pitch deck and demo environment, the sales team becomes equipped to jump into the market.</li><li><strong>PRD/Design/Tech Spec Walkthroughs</strong> — Often it’s said that once a PRD is created, it’s the engineer’s job to read them and implement the same but that ends up being more instructive work rather than a collaborative approach. At Razorpay, each document PRD/Design/Tech Spec is discussed with the entire team to get their inputs and ideas around the proposed solution. Walkthroughs provide everyone the sense of ownership towards building a product that solves end-user problems and how each one of the team members owns the success/failure of the product.</li><li><strong>Ad Hoc meetings to unblock developers, designers, and support teams </strong>— When multiple external stakeholders are involved, there are high chances that the team might hit a blocker due to the unavailability of support or resources. PMs owning the complete ecosystem at Razorpay, act as the bridge between external and internal stakeholders to unblock the product development. These meetings are valuable. Sometimes, it might be the product manager who requests them. But ad hoc internal meetings also lead to filling up the calendar quickly, leaving no time for the other essential parts of the job.</li><li><strong>Quarterly Roadmap Planning</strong> — Quarterly Roadmap is followed at Razorpay, which is frozen a month prior to the quarter start. PMs owns it completely which requires inputs from stakeholders, analyzing the impact, and prioritizing the roadmap based upon the availability of engineers. This requires multiple back and forth discussions with almost all the cross-functional teams at Razorpay.</li><li><strong>Monthly Review</strong> — We have monthly lookback discussions to see the progress of the quarter on planned vs actual. This is the common forum where everyone is able to absorb the latest updates from each team. Evaluating Product and Business metrics for the past month is also part of this forum.</li><li><strong>Zestful Evenings</strong> — Brainstorming ideas/understanding your user pain points/ solving problems all goes into this slot, and that’s what makes the evening high spirited. These many external stakeholders Razorpay deals with:</li><li>Banks</li><li>Card networks</li><li>Gateway Providers</li><li>NPCI</li><li>EMI and Pay later Providers</li></ul><p>Each of the above will have multiple providers and product managers need to work together with them in a collaborative approach to resolve the pain points of the merchant. These meetings will have some of the brightest brains of the financial sector in India and it gives immense pleasure to hear them on how different products have been conceptualized to make life easy for merchants to accept payments online and on the other hand making the infra more secure for end customers.</p><p><strong>Customer Conversations</strong> — Building a champion product is only possible when you hear out your customers quite often, in fact, make it a habit to know them closely. Customer-first is one of the core values at Razorpay and that’s the secret why it’s the preferred choice for businesses for accepting Payments online. Someway or the other, every product manager at Razorpay ensures to their customers every day, it could be via:</p><ul><li>Escalation from a frustrated customer</li><li>Cross-selling new products to existing customers</li><li>Help Sales rep to crack a new deal</li><li>Customer support tickets</li><li>Social media mentions.</li><li>Scheduled feedback sessions with key merchants.</li><li>Workshops with merchants to improvise their conversion.</li></ul><p><strong>GTM and Impact Assessment</strong> — There is a mindset prevalent in the industry that PM’s job ends with the launch of the product, which doesn’t stand true. When a product is signed up for a quarter, there is a significant cost and impact attached to it that has been agreed by all the stakeholders and owned by the entire team. Product Manager being the driver of the feature creates a go-to-market strategy with a clearly defined plan and direction for all stakeholders to drive maximum impact from the feature launch. This involves various phases of rollout with clear criteria for increasing the rollout. Metric dashboards are created upfront to monitor the data closely and take further actions. The product manager along with the help of a Product analyst does the impact assessment of every product/feature launch and the same is presented to monthly review discussions. Scenarios where the product is not able to create the expected impact are also discussed and RCA is published for the same.</p><p>One of the many reasons Razorpay consistently brings innovative, business-impacting products to market is because of the collaborative work we do in Product Management. With a clear focus on simplifying the payments, product managers closely work with multiple stakeholders to build world-class products. In order to manage the day mentioned above, a typical product manager needs to have:</p><ul><li>Customer Empathy</li><li>The data-oriented approach towards solving any problem</li><li>Decision-making power</li><li>Structured problem-solving skills.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IkRyH_v_pj7ha09t.jpg" /></figure><p>If the above schedule excites you, <a href="https://razorpay.com/jobs/#openings">do check out our current openings</a>. We are hiring for multiple PM roles at Razorpay and here is a guide which talks about <a href="https://razorpay.com/unfiltered/how-we-hire-product-managers-and-what-to-expect-in-your-pm-interviews-at-razorpay/">How we hire Product Managers at Razorpay</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/96/0*LbGBd-nG9AeYxU7R" /></figure><p><em>Originally published at </em><a href="https://razorpay.com/unfiltered/razorpay-product-manager/"><em>https://razorpay.com</em></a><em> on February 19, 2021.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a145a21ced8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/razorpay-unfiltered/a-day-in-the-life-of-a-razorpay-product-manager-unfiltered-7a145a21ced8">A Day in the Life of a Razorpay Product Manager — Unfiltered</a> was originally published in <a href="https://medium.com/razorpay-unfiltered">Razorpay Unfiltered</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Razorpay is building great products by avoiding traditional PRD approach — Unfiltered]]></title>
            <link>https://medium.com/razorpay-unfiltered/how-razorpay-is-building-great-products-by-avoiding-traditional-prd-approach-unfiltered-211138aee673?source=rss-72dc363beb89------2</link>
            <guid isPermaLink="false">https://medium.com/p/211138aee673</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[requirement-document]]></category>
            <category><![CDATA[prd]]></category>
            <category><![CDATA[pm]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Pravir Shanker]]></dc:creator>
            <pubDate>Fri, 16 Oct 2020 11:33:06 GMT</pubDate>
            <atom:updated>2021-08-19T13:39:37.131Z</atom:updated>
            <content:encoded><![CDATA[<h3>How Razorpay is building great products by avoiding traditional PRD approach — Unfiltered</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*NnMC78eWWwXtIaOhvb5nZw.jpeg" /></figure><p>Razorpay has been innovating at the top of the financial ecosystem and providing solutions to businesses since 2015. From our neobanking product — RazorpayX, to the recently launched product — Payment Buttons — all of these products have seen significant traction. Month on month, increment in the organic growth of businesses that sign up to use Razorpay, is a testimony that our products have been solving some of the key problems that were until now ignored.</p><p>In order to make sure that we always strive to continue building such solid products, there are definitely many factors that go into it. However, as a product manager, one of the most crucial elements to our success can be attributed to our Product Requirement Document (PRD).</p><p>In this article, I will take you through behind the scenes of how Razorpay has been able to conceptualize and consistently launch exceptionally high performing products. If you are into product management, you’ll definitely love this!</p><p><strong>What is a Product Requirement Document and why is it important to have one?</strong></p><p>A Product Manager (PM) is often called the CEO of a product or a customer’s advocate. Whether there’s a customer pain point to be solved or a business case to be implemented or just a fun feature to develop — all of these can be molded into simple ‘requirements’. A collection of these requirements for any product is called a PRD.</p><p>A PRD helps in easy collaboration across cross-functional teams like Design, Analytics, Engineering, Dev Ops, QA, Marketing, and Sales.</p><p><em>At Razorpay, the challenge is huge in trying to solve problems and at the same time ensure compliance with regulatory bodies such as the Reserve Bank of India.</em></p><p>Given the large number of people involved in making a particular product successful, it becomes important to document everything relevant so as to create a common understanding of the product. A PRD hence also acts as a communication tool between the Product Manager, cross-functional teams as well as other stakeholders.</p><p>Without ironing out the details and setting the right expectations in the PRD, it is very likely that what is in the mind of the Product Manager compared to what finally gets launched could be very different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/0*zpyWxintSN9ZUc-s.jpeg" /></figure><p>To avoid such mistakes a PM needs to ensure that they clearly explain requirements in a way that is easy to consume by the readers. Flowcharts and wireframes always aid in explaining complex requirements much better</p><p><strong>Challenges with traditional PRDs</strong></p><p>A traditional PRD will be a lengthy document that is focused purely on elaborating the solution in form of requirements. The solution is thought based upon the feature list that has been finalized by the PM. Many of the times, it happens that the ideation of the product is based upon what has worked upon in the past and if the same can be modified a bit for a newer set of customers. A walkthrough of the same is provided to different stakeholders, which is further broken down into the Jira tasks based upon the features and the specifications.</p><p>Traditional PRD doesn’t sell the vision of the product and fails to excite the team in terms of:</p><p><em>Why is this product important?</em></p><p><em>Who are the customers?</em></p><p><em>How is it going to solve the problem of the customers?</em></p><p><em>What benefit will the organization get post this product launch?</em></p><p>Hence it continues to be the voice of a PM rather than the voice of the customers.</p><p>Being a PM, If you don’t go deep into the problem statement and don’t understand your customers then you will never be able to build solid products, the same applies to the reviewers of your PRD. If the reviewers of the PRD are not aware of the problems faced by the customers, they would never be able to provide meaningful feedback on solving the problem in a different way, and they end up being readers rather than reviewers.</p><p><strong>How is a PRD at Razorpay different from others?</strong></p><p>At Razorpay, we not just emphasize on ‘What’ but also on the ‘Why’ part of the product requirements. So the deal is like — Why does this product need to be built and what problem is it going to solve? A few questions to be answered are:</p><ul><li>Do we know about the customer’s pain point?</li><li>Do we have the right customers for this product?</li><li>Is this the right time to build this product?</li><li>Is this inline with the vision of Razorpay?</li></ul><p>One of the most common mistakes made by PMs is to directly jump to provide a solution without completely defining the problem statement. In order to avoid such situations, we have divided the PRD into two parts — a Concept Note and User Stories.</p><p>A concept note is supposed to elaborate on the purpose of the product and get an internal buy-in on the concept — problem statement, customers, impact, and a high-level overview of the proposed solution.</p><p>Think of a concept note as an executive summary of a business plan or a VC pitch. This concept note can come in from any stakeholder and having this handy helps a PM prioritize a particular requirement among the many others in the product backlog. A PM can then introduce wireframes, workflow diagrams etc to explain the above points in the concept note. It’s not necessary that all concept notes written will see the light of the day as post writing a concept note, one could have a better insight on the “Why” part.</p><p>User Stories on the other hand are specifications that act as input for other members of a cross-functional team. These are further broken down into Epics and Stories, based upon the granularity required for the product. Each story is focused towards providing a deliverable feature to the end customer. It is always important that these stories be as granular as possible because it would help in getting realistic estimates in planning for a sprint.</p><p><strong>Key Sections in a Concept Note</strong></p><p>Building a concept note will help you get the buy-in from your business and tech stakeholders, but still the same can’t be used for the implementation. The next piece is to break down the proposed solution into requirements so that it can be consumed by various teams for implementation.</p><ul><li><strong>Project Summary</strong> — A project summary is meant to inform the reader about the idea and key highlights of the product. The project summary is one of the most important parts of the proposal. It is likely to be the first thing a reviewer will read and this is your best chance to grab their attention, have them show their interest, and probably convince them of the importance of the product before they even read the entire document.</li><li><strong>Goal and Success Criteria</strong> — This section carries the exact goal that we would achieve post launching of the product. Success Criteria should be well defined, as every stakeholder would want to keep an eye on this metric to see the value add that this is going to bring to the organization. Post-launch this becomes more critical for stakeholders as it helps to measure the success or failure of a product.</li><li><strong>Objective and Key Results (OKR) mapping</strong> — Another key line item that we add to this section is “OKR Mapping ‘’ which helps the PM to understand that whatever they are building is aligned to and shall impact the organization’s OKR. This is a topic of an article in itself if you haven’t already started using this technique to help prioritize.</li><li><strong>Problem Statement</strong> — Current problem faced by the customers in the absence of the proposed product. A good problem statement not just contains a description but is also backed by data. Data helps in highlighting how big the problem is. Most of the PMs make the mistake of defining a problem statement with just descriptive text, assuming that the stakeholders are already aware of the problem statement. Sometimes you may not find the right data for your product. In those cases, it is very important to start doing customer research or user interviews to understand how big the problem is. A well-defined problem statement is the core of building the right product for the right customer.</li><li><strong>Customer Persona </strong>— Razorpay has a Customer-first philosophy that emphasizes a lot on defining the personas. Who are you building this product for? What are the key pain points of these sets of users? There are multiple scenarios where you will find that there are different sets of customers and each set has a unique behavior. Do NOT make the mistake of putting all your customers into a single bucket! This way your product will never be able to find a market fit. Either you are very very sure of the segment for which you are solving a problem or you pick your segment for whom you would be solving that problem.</li><li><strong>Current Alternate</strong> — We are working in an era where technology is evolving every day and product improvisation is born to happen. There are high chances that your team or stakeholders aren’t aware of how customers are currently working in the absence of the problem to be solved. When you uncover this portion you may encounter, more areas of customer pain points, you could get more clarity of thought on what to build and what not to build.</li><li><strong>Assumptions</strong> — This is an optional section, but it is recommended to add all the assumptions you have taken towards conceptualizing the product. This helps all the stakeholders to be on the same page and leaves no room for misunderstanding.</li><li><strong>Recoverable / Reversible in case of failure without impacting Customer experience</strong> — Disaster management, something that most of us might have heard of, is least likely to be implemented when we are building a product. There is no silver bullet in software engineering and there could be a scenario where your product might be dead on arrival or it might have severe impact on other modules that could impact overall customer experience. This section would cover the solution we are proposing is reversible/recoverable in terms of failure and steps to mitigate the same. This would help the team to shut down the feature in terms of failure.</li><li><strong>Unknown/Future similar problem</strong> — Zoom out and think of, what could be the similar problems that might arrive in the future, list those downs to get a fair idea on, how proposed solutions can be leveraged to incoming future solve the problem that doesn’t exist as of now.</li><li><strong>Solution consideration</strong> — As I mentioned earlier, a typical mistake which is made by PMs is to come up with a solution and not elaborate on the problem statement enough This has also led to thinking of just one way of solving a problem and in most of the cases, PMs might have already thought of a solution. Do not do a rookie mistake over here — open your mind and think of at least 3 ways to solve a problem. These solutions could be very lame and may look hackish but still jot down every solution with pros and cons. This would give you a clear picture of your own thoughts and you would be able to surprise yourself too on what the mind can achieve when put to think before acting. At Razorpay, PMs are able to propose a minimum of 3 different approaches to solve a problem, each approach having its pros and cons. This helps the stakeholders to evaluate the solutions and also provide a view of why a solution is being proposed like this.</li><li><strong>Solution Summary </strong>— Once you have the different approaches listed down with their pros and cons, you are now clear with what approach could be chosen to solve the said problem. Mention a high-level summary of your proposed solution so that the reader gets a sense of the bigger picture of the solution before going deep into it.</li><li><strong>Happy Flows</strong> — Maybe a wireframe or workflow diagram, use your preferred way to explain the happy flow of the proposed solution. How customers interact with the system, end to end? It will make the readers comfortable and they can visualize how you are proposing to solve the problem.</li><li><strong>Un-Happy Flows</strong> — Similarly like Happy Flow, you need to explain all the edge cases in form of wireframe or workflow diagram, these are very important and do not ignore even if you are building a smaller feature as well. If you are not defining this section very well, you are surely going to miss some of the system behaviors and these would be voided during the implementation, and eventually, it might lead to poor customer experience.</li><li><strong>Detailed Solution</strong> — By the time you reach this section, you have already uncovered all the possibilities in terms of the problem and it’s solution, your mind can now focus on elaborating each and every moving piece that would be required to build the product. Uncover each component and blocks, layer by layer, and explain your solution. The easiest way to do this, jot down all the blocks of the solutions and within blocks, capture the component interaction of the system. After reading this section, readers should be well aware of the proposed solution and different pieces that would be required to build this product. Most teams should be able to provide rough estimates based upon this section.</li><li><strong>Impact assessment and Metrics </strong>— Define the metrics that you would use post-launch, to measure the impact of the product and ensure its success or failure. This section should be in line with the Goals and Success Criteria mentioned in the starting of the concept note.</li><li><strong>Internal Dependencies (optional) </strong>— Optional section to help you collate all the internal dependencies you might have for executing the product implementation, it could be as small as getting additional data from someone or maybe it could highlight cross-functional team dependency.</li><li><strong>External Dependencies (optional) </strong>— Differentiating external dependencies with internal one so as the team has clarity of thought on whom to approach for what. It could be something like a UAT testing environment or sandbox environment. Any blocker you feel you might have from an external party, mention about the same here.</li><li><strong>Competitive landscape (optional) </strong>— Every business has its own competition, make sure you have done enough research on how they are solving this problem statement and highlight the same. It need not be in detail, just the summary with few external reference links will give a fair idea of how soon this problem should be addressed.</li><li><strong>Risk assessment (optional)</strong> — The solution which you are proposing, will it impact other modules or cannibalise any other product or it might cause drop off in the user base? If yes, then assess the risk associated with the same and highlight it in this section, so that stakeholders are aware of the risk associated with building this product.</li><li><strong>Release strategy and milestones</strong> — Callout your phase-wise release strategy on how you are going to take this product to the market and roll out the feature/product slowly. For bigger projects, I would recommend carving out a separate Go to Market (GTM) plan. Your strategy should start from Production testing → Alpha Release(1 customer) → Beta Release(4–5 Customers) → Phased wise release. Every phase will have the release criteria based upon which you would be increasing the rollout.</li><li><strong>Future scope</strong> — High chances are that you are not building a full-fledged product and focused towards building in a phased wise approach. Carve the future scope of this product into a summary paragraph.</li></ul><p>User Story is broken down further into EPIC and Stories. A single EPIC can have multiple stories and a product can have multiple EPICs.</p><ul><li><strong>EPIC</strong> — An epic is a large user story that cannot be delivered as defined in a single sprint or single iteration. This typically contains the key components of the product which needs to be developed by implementing smaller stories inside it. While writing EPIC, please ensure you write down the project summary along with relevant links to the reference documents like — Concept Note, Mocks, Integration Docs etc. EPIC should also contain the benefit, the end-user will get post-go-live of the project.</li><li><strong>User Stories</strong> — Set of features that you would have planned to have in your product. Each feature to be explained in such depth that developers should be able to understand user interaction with the system. Below is the framework that we had implemented at Razorpay, to carve out the user stories.</li><li><strong>Summary of the story</strong> — 1–2 liner explaining the feature that is being addressed with this story.</li><li><strong>Benefit</strong> — End customer impact that it will have post-development of this story. Teams who would be picking this story for implementation will be well aware of the impact that this is going to happen post-launch.</li><li><strong>Acceptance Criteria</strong> — The expected outcome for a user for the corresponding solution being proposed. A good user story contains acceptance criteria at the Product solution level and stays away from drafting Engineering and Design solutions towards the proposed product solution.</li><li><strong>Analytics Requirement</strong> — Metrics that you must have planned to track post-go-live, may not even exist, hence every story should be backed by the analytics requirement, these could be in the form of events or data points that you would like to capture.</li></ul><p><em>Tip: User Story format is compatible with Jira importer, post writing your stories in the excel, you can upload the same on Jira, it would create all the stories in no time. You can also add as new columns as per your project configuration and it will work flawlessly.</em></p><p>As you can see from the above sections, we at Razorpay document, every minute details and moving pieces of a product. The objective is pretty simple — easy collaboration and informed decision making across cross-functional teams. Beautiful ideas are often badly executed due to a lack of clarity or wrong expectations which in turn result in disastrous products.</p><p>Do try out writing a concept note next time with your user stories, here is the handy template of <a href="https://docs.google.com/document/d/1AFiWRZXOYrifuELpINIJQzqJv3xH94YF1Ub1L_57t1w/edit?usp=sharing">Concept Note</a> and <a href="https://docs.google.com/spreadsheets/d/10QajYsYAJF-2hnDHRcRAJgG186eeNCmZj5TG_SEawuE/edit?usp=sharing">User Story</a>, that will help you to get started right away.</p><p>We would love to hear other best practices around writing better product requirement specifications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/96/0*Ywrog7tCCIpgABVM" /></figure><p><em>Originally published at </em><a href="https://razorpay.com/unfiltered/how-razorpay-is-building-great-products-by-avoiding-traditional-prd-approach/"><em>https://razorpay.com</em></a><em> on October 16, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=211138aee673" width="1" height="1" alt=""><hr><p><a href="https://medium.com/razorpay-unfiltered/how-razorpay-is-building-great-products-by-avoiding-traditional-prd-approach-unfiltered-211138aee673">How Razorpay is building great products by avoiding traditional PRD approach — Unfiltered</a> was originally published in <a href="https://medium.com/razorpay-unfiltered">Razorpay Unfiltered</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>