<?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 Akash Verma on Medium]]></title>
        <description><![CDATA[Stories by Akash Verma on Medium]]></description>
        <link>https://medium.com/@akash4?source=rss-61254db88978------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*noC9xdunXvRcbzxRh0g3Dw.png</url>
            <title>Stories by Akash Verma on Medium</title>
            <link>https://medium.com/@akash4?source=rss-61254db88978------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:45:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@akash4/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How do API product managers work with developers while aligning vision and code?]]></title>
            <link>https://medium.com/design-bootcamp/aligning-vision-and-code-api-product-managers-working-with-developers-364025388cfc?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/364025388cfc</guid>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Wed, 22 Jan 2025 17:51:20 GMT</pubDate>
            <atom:updated>2025-01-24T16:52:17.651Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5ZhQeNzRRJkvHNBR5XO3LA.jpeg" /><figcaption>Pixabay on Pexels</figcaption></figure><p>While developers bring the technical expertise to bring APIs to life, API Product Managers ensure these APIs align with business goals and user needs. However, the key to success is how effectively these two roles collaborate. Misalignment between these roles can lead to delays, confusion, or product failure. This article focuses on what an API manager should do to make sure the developers are motivated to produce quality APIs that very well align with the vision.</p><p>API PMs (or PMs in general) need to use their PM skills to avoid conflicts of requirements from different stakeholders, especially developers, to make sure the business needs are well-informed and always aligned while you look for a middle ground to ensure everybody gets a piece of what they wanted as the desired outcome. Is there a solid plan to ensure this? Well, not always. Alignment between the PMs and developers seems to be the only option a PM has, and they must manage this pretty well. While there is no absolute way to avoid conflicts, I can assure you that this can be managed well.</p><h4>Know Your Customer</h4><p>As an API PM, you need to have a list of customers who should be important to define your APIs and what values they can provide. Different customers/consumers have different needs and understanding your market is the holy grail of the success of your APIs/product. Because the market is so competitive and there are multiple solutions for the same problem out there, you need the following list to make a better proposition that will take you a long way.</p><ul><li>Developers who create and maintain APIs, including adding new features and fixing issues.</li><li>Internal developers who consume private APIs to integrate business systems.</li><li>Partner developers who consume APIs restricted to use within strategic business relationships.</li><li>Third-party developers with access to public APIs.</li><li>Internal end-users who rely on APIs to enable business processing spanning multiple applications to run smoothly.</li><li>Consumers rely on APIs to conduct online business efficiently.</li><li>The business unit leaders that own the APIs.</li></ul><p>So, now we know what offers will have the biggest impact on the business and end-users, what values to target, and what problems we are going to solve, it is time to build the solution.</p><h4>Define Roles</h4><p>While this looks different from team to team there can be Product Designers or Engineering Managers involved in this process to build. But let us just consider API Developer and API PM here as to what the roles should look like. The below details are what I have found very helpful so make a note.</p><p><strong>API Developer:</strong></p><ul><li>Implementation, adherence to standards</li><li>Technical design decisions</li><li>Developer Evangelism</li></ul><p><strong>API Product Manager:</strong></p><ul><li>Understand and articulate user goals, needs, and pain points</li><li>Define and document API contracts and roadmaps</li><li>Define value through a language common to both business and technology</li><li>Create a great developer experience by<br>-&gt; Giving the business context.<br>-&gt; Listening to the community.<br>-&gt; Knowing when to stop. (not adding functionalities, making APIs super bloated)</li></ul><h4>Improve Tech Partnerships</h4><p>The following steps can be used to enhance the tech relationship at your work when working in a close partnership with your developers to build the APIs/product:</p><ol><li>From defining the goals of the APIs to discussing how to achieve those goals, there is a regular feedback call cycle has to be established. The discussion mainly remains on scoping where we define what needs to be built, what are the different components required to build it, and how are we going to build it.</li><li>Now that we have all the information available on how to build the feature, we define the goals. And then, break down the goals into smaller steps or specific activities.</li><li>Each activity is assigned to each individual in the team dividing the responsibilities and coming to an agreement. This ensures that everybody picks their task and focuses on completing it without any clash. There could be subsets where both the PMs and Devs will have to discuss together on multiple calls, but the other activities must be divided across the team.</li><li>Have bi-weekly retrospective meetings to check on your technical partners where we discuss if there are any blockers and if some things do not seem to work in the roadmap that’s decided.</li></ol><h4>API Development Best Practices</h4><p>As an API PM, it is very crucial to maintain a guideline list when starting the development of an API product. You must provide some kind of guardrail to the developers so that they know what is expected and what are the API industry standards that make them the best in the market. So make sure you have the following information laid out and keep it handy for your developers:</p><ul><li>Modern API standards (REST/HTTP)</li><li>Treat them as products rather than just code</li><li>Security &amp; governance, performance, and scale</li><li>Streamlined software development lifecycle (SDLC)</li><li>Good documentation for consumption and versioning</li></ul><h4>Resolving a Conflict</h4><p>Struggles with working in a team to lead them to focus on the main thing and yet handling everyone’s query becomes difficult. As an API PM, you interview the consumers and figure out the solutions for the new challenges by collaborating with your engineers, but there can be times when there are differences in priorities or a new team coming together. It is bound to happen when there are situations where there would be some negotiations and discussions that have to be had, but always keep in mind that your main goal in a conflict is to bring everybody back to what the goals are that everybody started building the APIs in the first place. Make sure you try to reach a middle ground where we are true to our goals but also getting what each of us wants. This is the best way to avoid conflicts when working with developers &amp; engineers, or even external stakeholders.</p><p>I highly recommend you read the “<a href="https://akash4.medium.com/api-product-manager-fundamentals-a6f89c887e2f">Mastering the Basics: API Product Manager</a>” article to understand the basics of an API product manager.</p><p>I hope this article has been helpful to those of you starting your journey in the world of API Product Management.</p><p>If you appreciate reading stories like this and wish to read more such articles please comment your queries and I should answer them either with a comment or a blog. Please leave a clap and follow to support this account.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=364025388cfc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/aligning-vision-and-code-api-product-managers-working-with-developers-364025388cfc">How do API product managers work with developers while aligning vision and code?</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering the basics of an API product manager]]></title>
            <link>https://medium.com/design-bootcamp/api-product-manager-fundamentals-a6f89c887e2f?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6f89c887e2f</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[api-product-management]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[api-development]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Tue, 21 Jan 2025 09:25:48 GMT</pubDate>
            <atom:updated>2025-01-25T07:58:18.946Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re wondering why an API product manager is a role in itself? How are they different from the typical PMs, or why does one even know the difference? You have come to the right blog to learn about an API product manager. I’m maintaining an approachable and straightforward tone for newcomers, while still being engaging and relatable for seasoned product professionals. This blog will have a sequel for the other things that could not be covered here and all the queries that will be asked in the comments.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fV63nwsepv-nXRQbJ33MzQ.jpeg" /><figcaption>Stanislav Kondratiev on Pexels</figcaption></figure><p>APIs (Application Programming Interfaces): Software that allows two applications to talk to each other (eg: microservices). APIs have always existed on the Internet but have become the most popular in the last decade. It is the most important concept in modern software development practices especially when the scaling is done in millions and billions of connections where the traditional client-server architecture no longer works.</p><h4>How Did the APIs Become So Huge?</h4><p>Cloud computing is the reason why APIs have gained so much popularity. You want to grow quicker, push regular updates to your product, develop rapidly, and enable instant revenue for your company. You want your developers to focus on the business needs and develop the high-priority feature while integrating an API to handle the basics sounds like the right thing to do. <br>Eg: using a payment gateway API or authentication mechanism, you wouldn’t want your valuable developers to write lengthy codes to develop these functionalities as there are some amazing API providers in the market already that have nailed these services.</p><p>Yes, companies allow you to use their APIs and make money. I encourage you to do a quick Google search on how the following companies make billions of dollars by exposing their APIs:<br>Amazon, Google, Salesforce.com, eBay, Twitter, and Expedia are just a few of the companies.</p><h4>API Product Managers vs Typical Product Managers</h4><p>While this could be an entire blog on its own, let me cover the basics to get you started.</p><ol><li>A typical product manager mostly works with the research team and the design team at the ideation stage of a product and spends a lot of time on Figma and sharing insights before the developers pick the feature. Whereas, an API product manager sits between the API producers (developers who develop APIs) and the consumers (mostly developers).</li><li>Typical PMs manage customer-facing/internal products, focusing on user needs and business goals. API PMs manage APIs as products, focusing on integration, usability, and developer experience.</li><li>Typical PMs&#39; concern is how the end users (mostly non-technical) will use their product and what the product lifecycle will look like, while as an API PM, you need to be a little technical as their end users are the developers who will integrate your APIs, so the developer experience is the key to your success as an exposer (PMs who expose their APIs for others to use). You don&#39;t have to code but you must know how your APIs will be consumed across different platforms.</li><li>Typical PM would generally not look at things that are happening under the hood as far as the technical challenges are concerned, but an API PM would have to get a little bit into the depts of how the components interact with each other.</li></ol><h4>Role of an API Product Manager</h4><p>Let&#39;s break it down into phases to highlight the most common tasks of an API PM. It depends on the APIs you’re working with but the following covers it all for you (or at least almost).</p><p><strong>Phase #1:</strong> At the beginning of the API lifecycle, you are creating business and product requirements based on all stakeholder needs and you’re understanding the technical specifications of your API that your developers need to adhere to.</p><p><strong>Phase #2:</strong> An API manager needs to ensure the developers follow common best practices around standards, naming conventions, design principles, and also some consistent development methods. This is where you work closely with the developers to make sure you get their feedback as well which helps create an excellent developer experience. And these practices will be included in the tech specs when you write epics or user stories.</p><p><strong>Phase #3:</strong> Once you have developed the API or are in the process of the development, you determine how you monetize your APIs. Who has access and how do you expose it? How do you make access easy for developers?<br>This could include creating mockups or prototypes for testing or providing sandbox environments (a testing tool for consumers to quickly test your APIs in a controlled environment).</p><p><strong>Phase #4: </strong>Creating a feedback loop where you learn how your consumers are using your APIs and get their feedback and their experience into your next iteration. Any required changes that you get from the consumption data should be part of your future release backlog.</p><p>There is not much difference in what an API PM does when compared to the other PMs, it is just that they go a little deeper in understanding the API performances and how each component behaves with each other while closely working in partnership with the developers.</p><h4>API PM Toolkit to Cover the Basics</h4><p>As a product manager, you must answer these questions when working with an API as a product or any other product as well. Trust me, keep this handy:</p><ol><li>What problem is your API solving and for whom? <br>Stick to the problem your API is solving and do not do not make the mistake of adding multiple functionality to your APIs.</li><li>How do you advertise and market your service?<br>Is there a marketing strategy that can be leveraged? How do I want to make it visible to my end customers?</li><li>How do you grant access to your APIs?<br>Do I want this to be freely available or there has to be a Signup/Register? Or invite selective people to use your APIs and their feedback would be valuable for you.</li><li>How do you package the service you plan to deliver?<br>Are providing a single API or a set of multiple APIs? Is the API a point product on its own or is it a part of another product?</li><li>What’s your Quality of Service and how do you measure and ensure it?<br> Figure out an analytics system to learn how your APIs perform through regular monitoring</li><li>What should your product lifecycle look like? <br>How would you handle new changes? Do you have CICD pipelines in place to take care of new development? How much of automation is required?</li><li>What are the technical requirements?<br>Do I need an API management platform right away or is my API small enough to take care of itself? What solution would I use for the correct policy enforcement, security, how important are these at this point in time? Make conscious decisions here.</li><li>What are scale and performance requirements?<br>Do you expect high adoption right away? Not super important when launching an API but should be considered in the later stages of the lifecycle.</li></ol><p>I hope this article has been helpful to those of you starting your journey in the world of API Product Management.</p><p>If you appreciate reading stories like this and wish to read more such articles please comment your queries and I should answer them either with a comment or a blog. Please leave a clap and follow to support this account.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6f89c887e2f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/api-product-manager-fundamentals-a6f89c887e2f">Mastering the basics of an API product manager</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beginner Tools So Good, Even Senior Product Managers Swear By Them!]]></title>
            <link>https://akash4.medium.com/beginner-tools-so-good-even-senior-product-managers-swear-by-them-a4643804d029?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4643804d029</guid>
            <category><![CDATA[product-management-tool]]></category>
            <category><![CDATA[pm]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Wed, 11 Dec 2024 17:23:35 GMT</pubDate>
            <atom:updated>2024-12-11T17:23:35.922Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EH9HtDVSJ5QbxqrD-aqcvg.png" /></figure><p>In the fast-paced world of product management, the right tools can significantly enhance efficiency and decision-making. From road mapping to user research, here are some of the most widely-used tools, with examples of how they can be applied to a SaaS product like TaskFlow, a team collaboration app.</p><h3>1. Roadmapping and Planning Tools</h3><h4>Aha!</h4><p>Aha! helps product managers outline their product vision and align it with business goals. For TaskFlow, a PM can use Aha! to create a high-level roadmap, showcasing features like “AI-Powered Task Suggestions” for Q2 and “Voice Commands” for Q3. These timelines ensure stakeholders are aligned and development teams stay focused.</p><h4>Productboard</h4><p>Productboard centralizes feature prioritization based on customer feedback. TaskFlow PMs might collect input from users requesting improved notification systems and use Productboard to rank this feedback against internal priorities, ensuring the most impactful features are tackled first.</p><h3>2. Collaboration and Communication Tools</h3><h4>Slack</h4><p>Slack enables seamless communication within cross-functional teams. TaskFlow’s PMs can create channels like #Feature-Ideas to gather input from designers, engineers, and marketers, fostering transparency and collaboration.</p><h4>Confluence</h4><p>Confluence is excellent for documentation. TaskFlow PMs can maintain a centralized repository of product specs, meeting notes, and retrospectives, ensuring all team members have access to the latest updates.</p><h3>3. User Research Tools</h3><h4>UserTesting</h4><p>UserTesting allows PMs to gather direct feedback from real users. For TaskFlow, PMs can test a new “Shared Calendar View” feature by observing how users interact with it and identifying pain points to address before launch.</p><h4>Hotjar</h4><p>Hotjar provides heat maps and session recordings. By analyzing TaskFlow’s homepage heatmap, PMs might discover that users struggle to locate the sign-up button, leading to actionable UI improvements.</p><h3>4. Analytics and Metrics Tools</h3><h4>Google Analytics</h4><p>Google Analytics tracks website and app engagement. TaskFlow’s PMs can monitor metrics like bounce rates on the pricing page, enabling data-driven optimizations to improve conversion rates.</p><h4>Mixpanel</h4><p>Mixpanel provides insights into user behavior within an app. TaskFlow PMs can track feature adoption, such as how many users utilize the “Task Ownership Indicator,” and refine features based on these insights.</p><h3>5. Design and Prototyping Tools</h3><h4>Figma</h4><p>Figma enables collaborative design. TaskFlow’s PMs and designers can co-create wireframes for a new “Mobile Task Creation” feature, ensuring alignment before development begins.</p><h4>InVision</h4><p>InVision facilitates interactive prototyping. TaskFlow PMs can create click-through prototypes of the “Team Progress Dashboard,” allowing stakeholders to visualize and provide feedback before development.</p><h3>6. Workflow and Agile Tools</h3><h4>Jira</h4><p>Jira is a go-to for agile project management. TaskFlow PMs can use it to create sprints for developing the “Slack Integration” feature, tracking tasks from “To Do” to “Done.”</p><h4>Trello</h4><p>Trello’s Kanban boards are perfect for visualizing workflows. For TaskFlow’s marketing launch, a PM might use Trello to track tasks like content creation, social media posts, and email campaigns.</p><h3>7. Competitive Analysis Tools</h3><h4>Ahrefs</h4><p>Ahrefs helps analyze competitors’ online presence. TaskFlow PMs can research keyword rankings for competitors like Trello, enabling strategic improvements to their SEO and content strategy.</p><h4>G2</h4><p>G2 provides reviews and competitor comparisons. TaskFlow PMs can monitor feedback on competing tools to identify gaps or opportunities for differentiation.</p><h3>8. Customer Feedback and Support Tools</h3><h4>Zendesk</h4><p>Zendesk streamlines customer support. TaskFlow PMs can analyze tickets to identify recurring issues, such as confusion with task assignments, and prioritize solutions accordingly.</p><h4>SurveyMonkey</h4><p>SurveyMonkey helps collect structured feedback. TaskFlow’s PMs can survey users post-launch of the “Dark Mode” feature to gauge satisfaction and gather improvement suggestions.</p><p>By leveraging these tools, product managers can streamline workflows, make data-driven decisions, and deliver features that truly resonate with users. What tools are in your PM toolkit? Share your favorites below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4643804d029" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Frameworks That Make Product Management a Piece of Cake]]></title>
            <link>https://akash4.medium.com/frameworks-that-make-product-management-a-piece-of-cake-79a5b3938833?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/79a5b3938833</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[junior-product-manager]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[framework]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Wed, 11 Dec 2024 16:30:16 GMT</pubDate>
            <atom:updated>2025-01-21T09:27:28.839Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*FA-a8i9yCUs1aa8fB7Jg4w.png" /></figure><p>In the world of SaaS product management, frameworks serve as invaluable tools to drive discovery, prioritize effectively, and deliver value to users.</p><p>I’ve provided a brief overview of the frameworks along with an example. For further details, you can easily find comprehensive information about each framework online.</p><p>Here, we explore essential frameworks with examples using a hypothetical SaaS product, <strong>TaskFlow</strong> — a productivity app for team collaboration.</p><h3>1. Product Discovery</h3><h4>Design Thinking</h4><p>Design Thinking emphasizes empathy, ideation, prototyping, and testing. For example, TaskFlow PMs might conduct user interviews to understand why team members miss deadlines. They discover that task ownership could be clearer. Through brainstorming and prototyping, they design and test a “Task Ownership Indicator” feature, which assigns clear accountability. After multiple iterations, the feature is validated by beta users and rolled out to all customers.</p><h4>Double Diamond Framework</h4><p>This framework separates problem exploration and solution development. TaskFlow PMs begin by identifying a broad issue: teams struggle to coordinate schedules. In the first diamond, research reveals the problem: no central view of deadlines. In the second diamond, they brainstorm solutions and develop a “Shared Calendar View.” Prototypes are refined based on user feedback, resulting in a user-approved feature.</p><h3>2. Prioritization</h3><h4>RICE (Reach, Impact, Confidence, Effort)</h4><p>Using RICE, TaskFlow PMs evaluate a Slack integration. They estimate it will Reach 50,000 users, have a high Impact (9/10), Confidence of 80%, and require 5 weeks of Effort. The RICE score (50,000 × 9 × 0.8 / 5 = 720) helps prioritize it over other features like minor UI improvements, ensuring resources focus on high-value initiatives.</p><h4>MoSCoW Method</h4><p>TaskFlow’s roadmap uses MoSCoW to align priorities. “Task Notifications” are Must-haves to improve engagement. “Dark Mode” is a Should-have for user satisfaction. “Custom Emojis” are categorized as Could-haves for personalization. Features with negligible impact, like seasonal themes, are dropped entirely (Won’t-haves).</p><h4>Value vs. Effort Matrix</h4><p>TaskFlow’s team plots features on a Value vs. Effort matrix. “Automated Task Assignment” ranks high in value and low in effort, making it a quick win. Conversely, the “Advanced Reporting Dashboard” is deprioritized due to its high complexity and moderate value.</p><h3>3. Roadmapping</h3><h4>Now-Next-Later Framework</h4><p>TaskFlow’s roadmap uses Now-Next-Later to communicate priorities. “Slack Integration” is in the Now bucket with development underway. “AI-Powered Task Suggestions” are Next, requiring further research. “Voice Commands” are in the Later category due to low demand and technical challenges.</p><h4>Gantt Charts</h4><p>TaskFlow PMs use a Gantt chart to map timelines for the Slack integration. The chart shows the development phases: API research (2 weeks), integration (4 weeks), and testing (2 weeks). This helps visualize dependencies, like testing starting only after integration.</p><h3>4. Customer/User-Centric Frameworks</h3><h4>Jobs to Be Done (JTBD)</h4><p>For TaskFlow, a JTBD might be: “When I’m managing a remote team, I want a tool that lets me see all tasks in one place so I can track progress easily.” This insight inspires features like “Team Progress Dashboard,” which consolidates task statuses in a single view.</p><h4>Empathy Maps</h4><p>A TaskFlow empathy map might include: Thinks: “Are all tasks on track?”; Feels: stressed when progress is unclear; Says: “We need a better way to manage deadlines.” frequently checks and updates spreadsheets. This guides the creation of features like “Deadline Alerts.”</p><h3>5. Metrics and KPIs</h3><h4>AARRR (Pirate Metrics)</h4><p>A five-step framework to help companies understand their user’s journey.</p><ul><li><strong>Acquisition</strong>: 10,000 sign-ups/month through marketing campaigns.</li><li><strong>Activation:</strong> 60% of users create their first project within a week.</li><li><strong>Retention</strong>: 40% remain active after 3 months due to ongoing feature updates.</li><li><strong>Referral:</strong> 20% of users invite colleagues using referral incentives.</li><li><strong>Revenue:</strong> $500,000 in annual recurring revenue (ARR).</li></ul><h4>North Star Metric</h4><p>TaskFlow’s North Star Metric is “Tasks Completed Per User Per Month.” By focusing on increasing this metric through features like “Quick Add Task,” the team ensures higher engagement and satisfaction.</p><h3>6. Strategy and Goal Setting</h3><h4>OKRs (Objectives and Key Results)</h4><p>Objective: Increase team collaboration.</p><ul><li>Key Result 1: Launch “Shared Calendar View” with 90% adoption within 3 months.</li><li>Key Result 2: Achieve 80% positive feedback on collaboration features in user surveys.</li><li>Key Result 3: Increase retention rate by 15%.</li></ul><h4>Lean Canvas</h4><p>TaskFlow’s Lean Canvas example:</p><p>Problem: Teams struggle with task coordination.<br>Solution: Unified task and deadline management.<br>Key Metrics: Tasks completed, team engagement.<br>Customer Segments: Remote teams and SMEs.</p><h3>7. Agile and Workflow Management</h3><h4>Scrum</h4><p>TaskFlow’s team uses Scrum for iterative development. In a two-week sprint, they develop “Task Completion Notifications.” Daily standups keep the team aligned, and sprint reviews gather feedback. Retrospectives reveal areas for improvement, such as clearer backlog refinement.</p><h4>Kanban</h4><p>Using a Kanban board, TaskFlow tracks tasks through the “To Do,” “In Progress,” and “Done” stages. For example, “API Testing” moves from “In Progress” to “Done” after successful validation, ensuring visibility and flow.</p><h4>SAFe (Scaled Agile Framework)</h4><p>TaskFlow’s large-scale initiative, like “Q4 Analytics Update,” uses SAFe. Cross-team alignment is achieved through shared goals and regular Program Increment (PI) planning sessions, ensuring seamless coordination.</p><h3>8. Competitive and Market Analysis</h3><h4>SWOT Analysis</h4><p>TaskFlow’s SWOT:</p><ul><li><strong>Strengths</strong>: Intuitive interface.</li><li><strong>Weaknesses:</strong> Limited reporting capabilities.</li><li><strong>Opportunities:</strong> Remote work trend.</li><li><strong>Threats:</strong> Competitors like Asana and Trello.</li></ul><h4>Porter’s Five Forces</h4><p>TaskFlow’s analysis reveals:</p><ul><li>Threat of New Entrants: Low due to brand loyalty.</li><li>Bargaining Power of Customers: High, given abundant SaaS options.</li><li>Threat of Substitutes: Moderate, with many task management tools.</li><li>Bargaining Power of Suppliers: Low, as most dependencies are commoditized.</li><li>Industry Rivalry: High, with established players.</li></ul><h3>9. Retrospectives and Process Improvement</h3><h4>Start, Stop, Continue</h4><p>For TaskFlow’s retrospective:</p><ul><li><strong>Start:</strong> Conduct post-launch surveys for major features.</li><li><strong>Stop:</strong> Overloading the sprint backlog.</li><li><strong>Continue:</strong> Bi-weekly syncs to align priorities.</li></ul><h4>4Ls Framework</h4><p>TaskFlow’s 4Ls:</p><ul><li><strong>Liked:</strong> Team collaboration improved with “Shared Calendar View.”</li><li><strong>Learned:</strong> Users demand deeper analytics.</li><li><strong>Lacked:</strong> Early involvement of the QA team.</li><li><strong>Longed For:</strong> Faster iteration cycles.</li></ul><p>These frameworks not only help structure processes but also foster a shared understanding among teams, ensuring TaskFlow delivers maximum value to its users. What frameworks do you use? Share your thoughts below!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79a5b3938833" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customers use our products in a world of distractions]]></title>
            <link>https://akash4.medium.com/customers-use-our-products-in-a-world-of-distractions-1c960437e5db?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c960437e5db</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-management-2023]]></category>
            <category><![CDATA[customer-design]]></category>
            <category><![CDATA[improve-products]]></category>
            <category><![CDATA[product-mistakes]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Mon, 22 May 2023 09:51:34 GMT</pubDate>
            <atom:updated>2023-05-22T09:51:34.697Z</atom:updated>
            <content:encoded><![CDATA[<p>Most PMs focus on a customer’s pain point. But few learn about their environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qa7GtQ4r3rrkPq5gso-y4A.jpeg" /></figure><h4>Brief</h4><p>Several years ago, a recruitment product customer (let’s call him Larry) invited the PM (let’s call him Ved) to his office. <br> <br>Larry showed how he used the product &amp; had suggestions. Ved observed him closely during that visit.</p><blockquote>While Ved was there:<br>- Larry was interrupted by 3 phone calls.<br>- His Whatsapp chimed every other minute.<br>- His email notification tray constantly played hide &amp; seek.<br>- A couple of colleagues dropped by to run something by him.<br>- He shared how he uses the mobile app when he goes to pick up his kid from school.</blockquote><p>It led Ved to extrapolate 3 realizations:</p><p><strong>✔<em> </em></strong><em>Customers use our products in a world of distractions.</em></p><ol><li>The product wasn’t used linearly. It was hardly the step-by-step flow that Ved imagined in his user stories.</li><li>What’s funny is that Ved used to suspect UX flaws when he would see higher time-on-page metrics. But seeing Larry stall on one screen while attending a call made him think otherwise.</li><li>Sometimes, customers complete their aha moments in installments.</li></ol><p><strong>✔ </strong><em>Customers may use the product differently than how you designed it.</em></p><ol><li>Larry proudly showed Ved how he would “print screen” our dashboard visuals &amp; copy-paste the pie charts on his leadership presentation.</li><li>Ved also noticed that instead of using the nav or breadcrumbs, he was using browser bookmarks to leap to different sections of the product.</li><li>Customers have their own mental models of using your product. They’ll skip steps, ignore functions &amp; use it out of order.</li></ol><p><strong>✔</strong> <em>Customers don’t have an intrinsic motivation to learn best practices &amp; new features.</em></p><ol><li>Larry asked Ved about a couple of features Ved had talked about the last time they talked. Interestingly, those features had been launched for a while. Larry confessed that he wasn’t reading the product update mailers.</li><li>As he logged in, their NPS survey popped up. He casually dropped a rating to “dismiss” it.</li><li>He wasn’t aware that he could format his job post using shortcut keys (admittedly, the UX didn’t make it apparent either).</li><li>Customers don’t have the motivation to learn about your product unless there’s a necessity.</li></ol><h4>My Take on this:</h4><ol><li>Design for distraction <br>- How long does it take to figure out what to do next on a screen? <br>- How can the product copy be simplified to say the same thing? <br>- How can the user save their progress seamlessly?</li><li>Create ziplines to value <br>- How can you make decisions on their behalf? <br>- How can you cut down their input efforts? <br>- How can you reduce friction inflows?</li><li>Educate when needed <br>- When’s the best time to educate a user about a feature? <br>- What would you tell them if they responded with “So what?” <br>- What happens if they miss your update?</li></ol><p>Customer discovery questions focus a lot on pain points (&amp; rightfully so). But without learning more about their environment in operation, PMs will end up with sub-optimal solutions.</p><p>That’s it, thanks</p><p>If you appreciate reading stories like this and want to help me as a writer. Please leave a clap/tip, and follow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c960437e5db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tick off the To-do list as a PM]]></title>
            <link>https://akash4.medium.com/tick-off-the-to-do-list-as-a-pm-in-shreyas-doshis-style-a8c61fda9c6d?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8c61fda9c6d</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Sat, 15 Apr 2023 18:11:21 GMT</pubDate>
            <atom:updated>2023-04-16T06:08:05.911Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ab6MHuwoQifM9cVlZjm7WQ.jpeg" /><figcaption>Image credits: Product Growth</figcaption></figure><p>Isn’t it cool to tick off tasks from your to-do list as you progress? But it might also get overwhelming when you take up more responsibility as work and lose track of what to finish next. Working as a PM it has been a tough job to prioritize my tasks when having too much on my plate to deliver and I end up misjudging the importance of having a framework.</p><p>We can not go on ticking off tasks as we go. A strategy is really needed and I recently came across this framework that I’m going to share with you all that has made a drastic change in my productivity. I don&#39;t just get my tasks done within the deadline but I also know how much effort is needed for each task. You will see what I’m talking about in a minute.</p><p><a href="https://medium.com/u/8ce50828f1">Shreyas Doshi</a> is the coach you might be looking for when starting/stuck in a career as a PM. He has been the reason behind Stripe’s success working as the first PM ever for them. He’s also behind many successful products at Twitter, Google, Yahoo, and a few more.</p><h4>So here we are to learn about his LNO framework</h4><p>Start fresh. be it a book that you use, sticky notes or notion, or something else. Start off by taking down your task list. No matter how many of them are yet to be picked up.</p><p>Now divide your tasks into the following tags:</p><ol><li>Leverage Task (L): They are the most high-priority tasks and add the most value to the team. Give all your focus while working on these. Give your best shot.</li><li>Neutral Tasks (N): These tasks have to be done but you do not need to stress out much. Do a good job in completing these tasks. Nothing more than a good job is needed.</li><li>Overhead Tasks (O): Just get them done. No need to spend a lot of time doing a good job. The only goal should be to complete this job.</li></ol><p>Classify all your tasks under these 3 labels and allocate hours to each.<br>You can see which ones are going to take the maximum time to complete and require your undivided attention.</p><h4>Example:</h4><p>If I had 3 tasks as follows, I would tag/label them like this:</p><ul><li>Discussion with the Backend team to fix latency on dashboard (L)</li><li>Briefing the Design team regarding a new feature (N)</li><li>Following up with the Marketing team on a change requested by you on a blog they posted on your website (O)</li></ul><p>I would block my time for the day for the L label task as it required my undivided attention. For label N, I would try to complete it as soon as I get done with L and try to wrap it up asap. Label O would not take me more than a minute, you see how easy it is for me now to sweep the slate clean!</p><p>I have been very successful with this framework and I hope this will help you the same.</p><p>That’s it, thanks</p><p><em>If you appreciate reading stories like this and want to help me as a writer. Please leave a clap/tip, and follow.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8c61fda9c6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Product Management Anyways?]]></title>
            <link>https://akash4.medium.com/what-is-product-management-anyways-ba2e312edf10?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba2e312edf10</guid>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[product-lifecycle]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Mon, 12 Sep 2022 19:49:47 GMT</pubDate>
            <atom:updated>2022-09-12T19:49:47.636Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jOPrQW9-ljWkkfV1zw5RnA.png" /></figure><p>The most debatable question for decades now. Often I think to myself what do I understand of the role? What makes it so crucial for a company/product? Bringing in the stakeholders together is essential to build a product, and I get it.. but what are they trying to accomplish with this? Some say a PM’s job is to manage the product while some talk about the tech and design skills a PM uses to make a better product for the end users. So what is Product Management anyways?</p><p>I’ll try to answer this based on what I’ve learned from my own experiences. There are some amazing Product Persons out there and I’m not going to talk about what they think a PM does, I’m covering my thoughts on this and you can share yours in the comments.</p><h4>Basics</h4><p>Let’s understand the Product Team first. In general, the Product Team consists of UX Researchers who research user needs &amp; behavior, analyze data, compare the competition, etc. Then there is a UIUX Designer who takes care of the wireframes, designs of the screen/website/app/dashboard, etc based on the user personas and feel of the requirements. Then we have the Developers who develop the screens/website/app/dashboard. A Tester, that does all the testings before we take the code (coded by dev) live. Last but not the least, a PM. PM guides each one of them from building the product from scratch to Positioning and Pricing. Their main goal is to bring value (profits) to the company by building what users want and what’s technically or operationally possible. That’s a pretty good explanation for the basics.</p><h4>Product Lifecycle</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/963/1*AphwMDpZKPhL_Jhq2tvioA.jpeg" /><figcaption>Investopedia / Xiaojie Liu</figcaption></figure><p><em>What does a PM focus on at each stage of the Product? </em>Let’s talk about it.</p><ol><li><strong>Lifecycle Phase 1: Introduction</strong></li></ol><p>Be it a new product of Google or from an unknown Startup, every product starts somewhere. The challenge that a company faces in the introduction phase is Demand Generation. The Product gets tested for Product-Market fit. If the Product even has any skin in the game. And if users have started using it which feature is being used the most, and what type of users are using it the most? This is where a PM determines what changes can be prioritized for the next release. Though a PM does not make direct decisions on the price change or marketing strategies, they serve as an important resource to the Marketing and Sales Teams. As a PM, their job is to stress the benefits of the product and what are the Aha-moments of using it.</p><p><strong>2. Lifecycle Phase 2: Growth</strong></p><p>The Product has proved its market and is growing as users start to use it more. I consider Introduction and Growth phases to share an invisible line between them, though Growth is usually the longest phase when compared to Introduction. Marketing has a way of promoting the Product as they know by this phase what campaigns worked and which channel got them more users to use the Product. PM must keep the profit margins feasible as other companies bring their features to the market. PM will also prioritize which feature is the key feature of the Product and what to eliminate from the product. This is where the concept of a Roadmap begins to take its shape. PM must make sure that a part of the revenue should also be invested in the development to improve the product.</p><p><strong>3. Lifecycle Phase 3: Maturity</strong></p><p>In simple words, most who wanted to invest in the Product already have used it, and attracting new users becomes difficult. The growth phase is where the company makes a decent profit, but in the Maturity phase, the profits slow down. PMs take care of the cost-cutting by keeping the operations and development team lean, while still focusing on differentiating the product from the other companies. PM is very selective in which feature to focus on and how to bring a value proposition that customers are ready to invest more on. Their focus will be to create unique add-ons or create a feature that has its new market to keep floating. Collaboration with the Customer Success Manager of a PM plays a crucial role here as they both aim at retaining as much customer base as possible while fighting churn and attrition.</p><p><strong>4. Lifecycle Phase 4: Decline</strong></p><p>Every Product hits the Decline. Product has no more demand in the market, or there are better replacement solutions for the users. Could be any reason for a Product to wind up. As I mentioned in the Maturity phase, a PM will look for alternatives to keep floating by creating a feature/new product that has a new market.</p><blockquote>Apple switched from making desktop computers to making mobile devices</blockquote><p>This is one of the most inspiring examples out of many other companies which excelled in the Decline Phase.</p><h4>Project Management</h4><p>PMs also take care of the tasks and tickets to keep the development of the Product on track. They also coordinate with other teams to make sure there is no blocker for the release of the Product. Breaking down the whole roadmap into weeks/2 weeks/4 weeks sprints is the approach PMs take to complete the tasks effectively. This gives a broader picture of the roadmap. Sprint planning also includes having a backlog where features/tasks not so important are diverted, to be picked up later.</p><h4>Product Requirements</h4><p>Product requirements or product specs, serve as a guide to everyone involved in the product/new feature. PMs create this document to serve as a very useful communication tool across the different stakeholders. It helps designers understand guideposts in the features, helps developers know what exactly the experience should be and helps the testers to understand how the feature should behave. Beyond them, PRD is also consumed by other stakeholders like Marketing, for example, to take away the capabilities of the product to market it to the target audience.</p><h4>Team’s OKRs</h4><p>PM is a leadership role and one has to be inspiring and drive the focus of the Product team. Objectives &amp; Key Results (OKRs) are one of the most useful frameworks a PM uses to make their team outcome-oriented. When everyone in the team knows what priorities are given to which tasks, what should be the result, what time the task is expected to be finished, and who is going to be responsible for what task, it makes the chances of success even stronger.</p><blockquote>Be Stubborn on vision, but flexible on details -Jeff Bezos</blockquote><p>To end this blog, I could not have used any better quote. A PM is a visionaire, yet adaptable with the approach to achieving the desired outcome.</p><p><em>If you appreciate reading stories like this and want to help me as a writer, please leave a clap, and follow. Tips are always loved that you guys leave to support me and this channel.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba2e312edf10" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customer Support to Product Management, My Transition]]></title>
            <link>https://akash4.medium.com/customer-support-to-product-management-my-transition-6723810987d5?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/6723810987d5</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[pm]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[transitions]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Wed, 24 Aug 2022 19:18:10 GMT</pubDate>
            <atom:updated>2022-08-24T19:18:10.242Z</atom:updated>
            <content:encoded><![CDATA[<p>I started my career as a PM a year back for a start-up. Working on a SAAS Product has helped me understand how software is built. But before I ever knew anything about PM roles, my experience was limited to support or other customer-facing positions. And I was damn good at it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*7yZriVQISqrY4lRv2DSJIA.png" /></figure><p>To be good at customer support one needs to develop empathy for the customer’s issue. I started with Amazon, the most prominent institute in the world to learn about customer satisfaction. Working as a Customer Support Executive I learned some critical things about delighting customers. Though spending each minute of my shift on calls was daunting, I became obsessed with resolving customers’ issues. And I’d be lying if I didn’t mention the days I felt frustrated because of the product (or whoever was responsible for it) for causing silly issues to the customers who’d connect with us. I always thought I’d fix the product so much better if I had the chance.</p><p>Not just that, I wanted to resolve customers’ issues on a broader level. Not just 30–40 customers a day. Hence, I started looking to get into a product role.</p><p><em>Here’s what worked for me</em></p><h4>I was already empathetic towards the customers</h4><p>Though this is the most common thing you might have heard from a PM who was a former support guy, this is the reason why most of the great PMs are from a Support background. When in Support, you understand the customer’s issue and resolve it for a good review, as a PM you understand the true pain points of your customers and improve the NPS (Net Promoter Score) of your product. Keeping it really simple here. But it’s not as easy as it sounds. You provide a holistic perspective on what to build and how it should be carried out. You learn it as you progress in the role.</p><h4>I had more time on my hand</h4><p>When I was in Support, I used to handle calls and tickets almost every minute once I logged in. I would hardly get any time to even talk to the person sitting next to me. But as a PM, I had no non-stop calls, no tickets to handle. At least in the start. This left me with an enormous amount of free time on my watch and I took good advantage of this. I could focus on one thing at a time, uninterrupted. I also befriended the Dev people. The most crucial thing to do if you’ve time is to connect with the developers. Ask them all you want about how things work, PRDs (Product Requirement Doc) for the product/features, ask the to explain HLD (High-Level Design), etc. I also did a PM course on Linkedin. Use this time wisely as I did.</p><h4>I never took my colleagues for granted</h4><p>No matter where I worked, I always had a strong bonding with my team. Though it sounds like a stressful job to maintain relationships, it’s worth it. And that’s coming from a person who is shy. Being a people person is easily the <em>top 3 things</em> to have when working as a PM anywhere. It involves you handling their feedback properly, giving constructive feedback to the team, attending the meetings regularly, showing concern for the team by action, attending team events and parties, etc. Your designer knows better about how to create a new design, and your QA person knows more about the product than you do. See why this can work in your favor? The secret is to show up for success in anything, and I take it literally in this aspect of my work life.</p><h4>More about the team</h4><p>It’s very important you know how you make the best use of other teams. I made it a habit to connect with the Marketing team at least once a week on a call. The same goes for the Support team. This helps me keep track of who’s working on what and what needs to be fixed on the product’s end. Though the customers are not right always, you get a basic understanding of what the Support team is expecting from the product. You can then prioritize the features and start building. When I worked in support I always had one feature request from at least one customer a day. Though all would not be needed, one can still prioritize the product requirements out of it. A simple trick to prioritize a feature is to find out what age group has raised the same feature most, if your product targets that age group, then go for it. The same goes for the industry type or business type, or country that your product targets. You get the picture.</p><h4>Don&#39;t be shocked by open tickets in the backlog</h4><p>While working in Support, my job was to close all the tickets before leaving for the day. I was amazed to learn this will not be the case always when working as a PM. Do not bother about those open tickets in the backlog simply because not all the tickets/issues raised has to be resolved. You will prioritize the high-value tickets or bugs first. Most of these tickets do not affect the users at all. When working in Support, you handle the high-priority tickets first, it’s the same here. Leave the rest for now. What I do to prioritize is check the frequently used section of the product by the users and fix the issues raised for it first.</p><h3>Now for the parting words</h3><p>Though the journey has been tough, I’m still learning each day. You face a new challenge every new day working for the same old product. if you love the product you will make it something lovely that’s worth it for a customer to have. So if you’re somebody who is obsessed with making a customer happy, then this can be a great step for you to make better product decisions for your customers.</p><p><em>If you appreciate reading stories like this and want to help me as a writer, please leave a clap, and follow.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6723810987d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Job’s effect on my personal life]]></title>
            <link>https://akash4.medium.com/product-jobs-effect-on-my-personal-life-5c951d954a1e?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c951d954a1e</guid>
            <category><![CDATA[faang]]></category>
            <category><![CDATA[work-life-personal-life]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Mon, 18 Jul 2022 15:56:30 GMT</pubDate>
            <atom:updated>2022-07-18T15:56:30.908Z</atom:updated>
            <content:encoded><![CDATA[<p>I started my Product Management career last year. My current role has been thoroughly rewarding, though it comes with a new challenge to solve every day. I have evolved as a person with this role which is mindblowing when I think about it, but the changes are subtle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*5SHFJ8rLgH-jX8-ePe7xBQ.jpeg" /></figure><p>Reflecting on my start in this role I can see an immediate impact it has made on my day to day life. Persistence is the key factor in any task you perform and product management is no different. You will have to manage your task schedules in such a way that you get to work effectively. And I have always believed no matter what we do it always has a lot to do with our personal lives too. So without further a do, let me mention some important lessons a product role has taught me.</p><h4><strong>Feedbacks</strong></h4><p>There’s no space for denial in product management. You get feedbacks from all over the teams, fellow PMs, designers, engineers, CPOs, etc. It’s your job to listen what every other person has to say. And most of the times it’s constructive feedback if you think about it. It can only make you better if you know what needs to be changed. I have been in denial about certain habits I had in my life and my loved ones always tried to tell me to do the right thing. Now that I can take feedbacks pretty well, I have realised how important it is to listen to others who are involved and invested in you (friends &amp; family).</p><h4>Every Hour Matters</h4><p>There’s no doubt that Product management is a fast paced role, you have to be on your toes. Get things done, prepare for up coming meetings, make road map, make sure everybody is aware about their tasks, and what not! You know what is the most frustrating thing, yet crucial? Feeling like the day was not productive at all. As a PM its important to feel productive, and that is possible by managing your time. This is no different from our personal life.</p><p>I always thought that the things we love to do, and things we love to do for a loved one should have no timings. Do as you wish. No! Completely wrong I was. Everything needs to be timed. Like meeting friends on weekends, a night out on a Saturday, quality time with parents and siblings. Not to mention, dates. Your people will soon know that you are on a schedule and they will not bother you when you’re working, as they know you will be available for them for the rest of the day.</p><h4>Invest in Better Products</h4><p>A good product is not only better in quality but it lasts longer. Be it a belt, shoes, bed, laptop, a service, an app, a TV show subscription. As a product person you realise so much about a product and it takes for it to stand out. I see so many products out in the market which are lame and I use to be a consumer of most. Now I don&#39;t mind spending extra on a better product. It goes without saying, everybody should start making better purchase decisions and see it as an investment.</p><h4>Respect for MAANG and Others</h4><p>I recently started reading about Products that made it in the market and I was surprised to read about success stories. Every PM has a dream to take their product to the top. And to do it a level like MAANG did is phenomenal. Everybody is copying what they did already. They take the first step and others simply follow. Be it a design, architecture, product feature, marketing, they are big and I recently realised how big exactly.</p><p>I interact and work with some of the smartest engineers and PMs in my current role, and it is a start up. One can only imagine about the talent of the team that took top notch big tech companies right to the top.</p><h4>Able to Recognise a Great Design</h4><p>Lastly, I am going to admit that a couple years ago a great design would have gone right pass me and I wouldn’t have noticed it. Ideally, that&#39;s what a great design is supposed to be, go unnoticed. But now I’m able to recognise and appreciate amazing designs, apps, websiteand ofcourse, products. Cred is one example of such designs, it’s bold move of using black amazed a lot of the other designers. Black is a hard personality to crack in design. You understand different components and elements of designs in the product and websites. There are so many amazing UI designers out there who are taking the products to a whole another level. Design in tech has never been so exciting and full life, ever.</p><p>That’s it, thanks</p><p>If you appreciate reading stories like this and want to help me as a writer. Please leave a clap, and follow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c951d954a1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Own any one of these 2 skills to get started with a PM role]]></title>
            <link>https://akash4.medium.com/own-any-one-of-these-2-skills-to-get-started-with-a-pm-role-ae21ae9a423?source=rss-61254db88978------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae21ae9a423</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[pmp-certification]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager-skill]]></category>
            <dc:creator><![CDATA[Akash Verma]]></dc:creator>
            <pubDate>Wed, 13 Jul 2022 17:15:19 GMT</pubDate>
            <atom:updated>2022-07-13T17:15:19.335Z</atom:updated>
            <content:encoded><![CDATA[<p>All the beginners who are fascinated by PM jobs and considering switching to one should read this for ease of mind. This is going to be a great switch btw, as it is going to be one hell of an experience to carry and I assure you that.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/746/1*_dAyrpSIbglnNroX3pBGWw.jpeg" /></figure><p>Though I’m not really sure what inspired you to look to get into a product role, I surely know that some of you are looking for some simple answers to questions like, “What does a PM do?”, “What experience do I need to have?”, or “How can I start with no relevant college degree or past work?”. Well, it’s pretty simple and I talk about stuff like these here. No past experience is required and doesn&#39;t matter what college degree you carry. For now, I’m only going to talk about skills you should be focusing on, or you already have, just to get started.</p><p>This is in my opinion and how I started. You can get into any product role, or be an APM or PM. Works for any type of Product Role for Saas. I will keep it painless.</p><p>The 2 skills I’m talking about are :</p><blockquote><strong>#1. Technical skills</strong>, or let’s say to have a basic understanding of how the software works.</blockquote><blockquote><strong>#2. UX UI</strong>, how a user will interact with your product.</blockquote><p>Yes, don&#39;t get it twisted. These 2 only. Precisely, only 1 of these 2. This is how I started and got my first experience ever in PM. You can start as an intern and work your butt off to convert it into a full-time role (and it’s fun). Or you can begin as an APM in any start-up. This is all that’s there tbh, but let me try to break this further down.</p><p>So let’s say you have the technical skills, you are from a CS background and you already are familiar with the tech world. Congrats! You’re already a preferred candidate for the role. This skill takes time to build when you’re from a non-technical background. It’s important to know how the tech works for a Product guy as they would be handling/working with a pack of engineers to build one solid product. But, what are you going to build? Who are you building it for? How would you know what your users&#39; pain points even are?</p><p>You’re in the role, started strong with the tech knowledge you already have. Now you need to get in touch with the UX designer to understand the basics of design. As a PM, your job will be to make sure the Product(starting from scratch)/new feature is going to solve the problem for the end users. So you will have to finalize a feasible UX UI solution for the Product, which the developers can build with the resources they have. I hope this makes sense. <em>This is a major responsibility and that’s why you learn the UX side of the product simultaneously when you begin in the role.</em></p><p>When I started, I had a decent amount of knowledge in UX and hence why I got the internship. Apart from that I also began to read about top-notch products in the business and how they work, fairly before the interview. The tool most UX designers and even PMs use is <a href="https://www.figma.com/">Figma</a>. It’s a web-based interface designing tool that is used to make app screens, websites, wireframing, and prototyping. Start learning about each word I just mentioned, thank me later. Wireframing is very important, as a PM you will make wireframes of an upcoming feature, which will later take shape as you progress with the feature. And while I was managing the UX UI side of the product, I would also spend an hour or 2 on informal calls with the developers to understand tech, shamelessly. You have to be shameless when you’re an intern and eager to learn. Though I still struggle sometimes with tech, I have acquired the basics of it.</p><p>Not to mention, you also need to get familiar with other teams and their goals like marketing, Customer Success, and Sales. You should know how you’re company earns money, and what’s the budget for it to function. Everything is a tool based now, so you need to be able to make smart decisions on the tools you’re going to opt in for. Do you need a full-time developer for the product, or an intern would serve the purpose better? And most important of all, you should be able to communicate with your team. You’ll learn this too.</p><p>So, to conclude. One of these 2 skills is enough for you to step in. In my experience, this can work for anyone who carries any of the 2 skills. And if you carry both skills, then do not waste your time searching for “the skills required as a PM” on the internet. This is all there is, to at least get started. The rest you can learn as you grow in the role.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae21ae9a423" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>