<?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 Akshayaa Govindan on Medium]]></title>
        <description><![CDATA[Stories by Akshayaa Govindan on Medium]]></description>
        <link>https://medium.com/@akshayaag?source=rss-7d699eb0c467------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5NmezNHjiVef48dvbNBtZQ.jpeg</url>
            <title>Stories by Akshayaa Govindan on Medium</title>
            <link>https://medium.com/@akshayaag?source=rss-7d699eb0c467------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:30:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@akshayaag/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[My least favourite part of being a Product Manager]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://akshayaag.medium.com/my-least-favourite-part-of-being-a-product-manager-7297e76a5496?source=rss-7d699eb0c467------2"><img src="https://cdn-images-1.medium.com/max/720/1*FSGG6EKe4-mwEECHkmlPFg.png" width="720"></a></p><p class="medium-feed-snippet">The good and the bad of product management</p><p class="medium-feed-link"><a href="https://akshayaag.medium.com/my-least-favourite-part-of-being-a-product-manager-7297e76a5496?source=rss-7d699eb0c467------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://akshayaag.medium.com/my-least-favourite-part-of-being-a-product-manager-7297e76a5496?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/7297e76a5496</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Thu, 24 Feb 2022 01:05:41 GMT</pubDate>
            <atom:updated>2022-02-24T01:05:41.780Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[5 things to consider when you say ‘No’ as a Product Manager]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/5-things-to-consider-when-you-say-no-as-a-product-manager-613fb6681a79?source=rss-7d699eb0c467------2"><img src="https://cdn-images-1.medium.com/max/740/1*ertmhw13MwUD7X_a332HmA.png" width="740"></a></p><p class="medium-feed-snippet">How to go about doing it successfully without damaging relationships or hurting your product strategy</p><p class="medium-feed-link"><a href="https://medium.com/swlh/5-things-to-consider-when-you-say-no-as-a-product-manager-613fb6681a79?source=rss-7d699eb0c467------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/5-things-to-consider-when-you-say-no-as-a-product-manager-613fb6681a79?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/613fb6681a79</guid>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[saying-no]]></category>
            <category><![CDATA[empathy]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Tue, 16 Nov 2021 02:31:27 GMT</pubDate>
            <atom:updated>2021-11-16T02:31:27.271Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[3 Things That Helped Me Manage My Roadmap As A New Product Manager]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/3-things-that-helped-me-manage-my-roadmap-as-a-new-product-manager-64b66e4c97f3?source=rss-7d699eb0c467------2"><img src="https://cdn-images-1.medium.com/max/719/1*yOFLEOr16sTC2Ia2ZRXAnA.png" width="719"></a></p><p class="medium-feed-snippet">Strategies to think through when taking over a roadmap at a new role</p><p class="medium-feed-link"><a href="https://medium.com/swlh/3-things-that-helped-me-manage-my-roadmap-as-a-new-product-manager-64b66e4c97f3?source=rss-7d699eb0c467------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/3-things-that-helped-me-manage-my-roadmap-as-a-new-product-manager-64b66e4c97f3?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/64b66e4c97f3</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[roadmaps]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Thu, 19 Aug 2021 01:46:00 GMT</pubDate>
            <atom:updated>2021-08-19T01:46:00.590Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[First 30–60–90 day guide for Product Managers]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/first-30-60-90-day-guide-for-product-managers-6020a25c229f?source=rss-7d699eb0c467------2"><img src="https://cdn-images-1.medium.com/max/1280/1*rNuyN06g_T2r_QqNJKvj8w.jpeg" width="1280"></a></p><p class="medium-feed-snippet">Spend time observing, evaluating and acting in the first 90 days to succeed in the long run</p><p class="medium-feed-link"><a href="https://medium.com/swlh/first-30-60-90-day-guide-for-product-managers-6020a25c229f?source=rss-7d699eb0c467------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/first-30-60-90-day-guide-for-product-managers-6020a25c229f?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/6020a25c229f</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[guides-and-tutorials]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[new-job]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 01:19:31 GMT</pubDate>
            <atom:updated>2021-07-06T01:19:31.881Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Hardware Engineer to Product Manager]]></title>
            <link>https://medium.com/getting-started-in-product/hardware-engineer-to-product-manager-4d39837cdc77?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d39837cdc77</guid>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[breaking-into-product]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[patience]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Thu, 20 May 2021 12:48:05 GMT</pubDate>
            <atom:updated>2022-05-05T07:33:53.316Z</atom:updated>
            <content:encoded><![CDATA[<h4>It wasn’t straightforward but some courage and patience helped</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w3sRfUbyMmoTnrb0" /><figcaption>Photo by <a href="https://unsplash.com/@les_photos_de_raph?utm_source=medium&amp;utm_medium=referral">Raphaël Biscaldi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>“How can I break into product management?”</strong></h3><p>It’s a question that I’ve heard a lot lately and a question I’ve done some reflection on in the past few months. No career journey is straight or easy; it’s an iterative, often confusing journey. The same goes for product management.</p><p>My journey to product wasn’t straightforward. There were a lot of bumps, turns and some trenches. I wanted to share key parts of my transition to help others understand that it is achievable with a bit of <strong>courage to explore</strong> their interests, some <strong>extra effort</strong> and a lot of <strong>patience</strong>.</p><h3><strong>My start as a hardware engineer</strong></h3><p>As someone who graduated with a degree in engineering, the easy and obvious path forward was to find a job as an engineer. That’s exactly what I did. I started off as an electro-optical engineer in the med-tech field. I’ve always been a tinkerer and loved math so this was perfect for me. Or so I thought…</p><h3>Realizing I didn’t want to just be an engineer for the sake of it</h3><p>Now, this wasn’t easy to identify or accept. When I was working as an engineer, I was always asking myself “Why this feature? Why am I not exploring a different more advanced piece of technology?” and the why questions bubbled up quite often. I realized in order to be able to build <strong>useful </strong>technology, I needed to understand the “Why?” behind every problem I solved.</p><p>I started talking to a lot of people, in different companies, industries, career paths (engineering, product, project, software, HR — you name it) to understand where the “why?” is decided and by whom. Something I realised about myself from these conversations was that:</p><ol><li>I didn’t want to<strong> just</strong> pursue the problem-solving (I wanted to learn more about the problem identification and definition)</li><li>I wanted to work with different types of people (not just other engineers)</li></ol><h3>Figuring out what it is that I wanted to do</h3><p>This was probably the toughest part. From my conversations, I had found some common threads but I didn’t know exactly what to do with them. The one thing I learned I lacked was business acumen. My degree and jobs had focussed heavily on the technology and a lot less on the value to the user &amp; business delivered by that technology. I had to find a way to get all that under my belt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bCq0UWJ6PxjUQfdYv8WwzQ.jpeg" /></figure><h3><strong>Winding Path into Product — Set goals, reflect and re-assess</strong></h3><p>I went from being a hardware engineer in a Medtech company to a contract role as a project manager and finally into a rotational program in the financial industry. Switching from one career path to another, or from one industry to another isn’t easy, so I put in the extra effort and networked with individuals in industries I was very interested in. I pursued each opportunity with the goal of learning in mind and regularly reflected on my goals. I assessed my learnings, potential learnings to come and other opportunities I have yet to consider and using this I pursued paths that would help me build up my business acumen.</p><p>During my time in the rotation program, I worked closely with product managers and that’s when I came to the realisation that this was the path that would address all my “why?” questions and increase my exposure to strategy and problem-identification, while staying close to technology and problem-solving. I immediately took action:</p><ul><li>I networked with the various product managers on my team to assess my strengths &amp; weaknesses</li><li>I expressed interest in product to my own manager</li><li>I took on small opportunities alongside product managers to understand the role and demonstrate the value I brought</li><li>I sought mentorship from product managers to understand the areas I needed to further improve</li></ul><p>My team recognized my passion for product management and my drive to succeed as one so when a role opened up, I was immediately considered for it. I was finally in a place where I was tackling the challenge I always strived to decipher as an engineer!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EBDVgZDQUNKKXryp" /><figcaption>Photo by <a href="https://unsplash.com/@gpthree?utm_source=medium&amp;utm_medium=referral">George Pagan III</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Explore, Put in the Effort and Be Patient</h3><p>Once I left my job as a hardware engineer, it was tough not to go into the next thing that came across my plate because it was a job I was comfortable with. Three key themes played a HUGE part at the time.</p><ol><li><strong>Explore </strong>— early in your career is likely when you have a lot of flexibility and so you should try to take full advantage of that. I have worked as a hardware engineer, a project manager, and a product manager. before I figured out what I wanted to do and all within the first 2 years of my career. I have worked in the electronics, MedTech, and Fintech industries before I started in e-commerce. I took this time to explore roles and industries to see what else was out there. I leveraged my network to help me understand my interests and still do to this day.</li><li><strong>Put in the Effort</strong> — figure out which of your skills are relevant to the role and the areas you lack in. Put in the extra effort to build up your skillset in the areas you lack (either through taking on additional small features alongside product teams at work or by building a case study to showcase how you would tackle a specific user problem).</li><li><strong>Patience</strong> — it’s always easier said than done. I had to be very patient with myself and with the job market at this time. It was tough dealing with rejection or having to reject another engineering role. However, I stayed patient because I believed the return on my investment would pay off and I would be able to pursue what I wanted to do.</li></ol><h3>What’s next?</h3><p>I am a Product Manager today and I’m still learning. I still set goals, reflect and assess myself to understand myself to now find the specific problems I want to pursue and how I can improve my skill set as a Product Manager. I don’t expect it to be an easy challenge to undertake, but one definitely worth my time to understand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d39837cdc77" width="1" height="1" alt=""><hr><p><a href="https://medium.com/getting-started-in-product/hardware-engineer-to-product-manager-4d39837cdc77">Hardware Engineer to Product Manager</a> was originally published in <a href="https://medium.com/getting-started-in-product">Getting Started in Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building your Network in a Remote World]]></title>
            <link>https://akshayaag.medium.com/building-your-network-in-a-remote-world-5c107b86ef33?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c107b86ef33</guid>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[connection]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Fri, 16 Apr 2021 01:38:47 GMT</pubDate>
            <atom:updated>2021-04-16T01:38:47.413Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K0jxaW4_-FPZ1qWcS5xn3w.jpeg" /><figcaption>Image by <a href="https://source.wustl.edu/2018/07/six-tips-networking-for-professional-success/">The Source </a>at<a href="https://wustl.edu/?_ga=2.157155067.1918935519.1618088797-496546242.1618088797"> Washington University in St. Louis</a></figcaption></figure><p>It’s been over a year of remote working and even if it may not be here to stay, it definitely opened me up to re-evaluating and expanding my approach when it came to networking. Why limit yourself to those in your company, your industry, or your geography? Isn’t this the best time to meet &amp; learn from others across borders while still confined to the boundaries of our homes?</p><p>I took the last few months to assess how the pandemic helped me grow my network and meet diverse individuals across the globe to improve my communication skills and develop a deeper understanding of different challenges from different viewpoints.</p><p>If you are someone looking to build your network in a remote world or just someone looking to improve your approach, you’ve come to the right place.</p><h3>1 — Online professional communities are now your best friend</h3><p>This one is quite straightforward: if you’re looking to network outside your company, build up your presence on websites like LinkedIn, Twitter, Clubhouse, industry-specific Slack groups and more. Leverage the powerful search capabilities of these platforms and find a company, a recruiter or a person and engage with them.</p><p>Participate in webinars/online conferences and connect with individuals on those platforms. <strong>It’s up to you to ensure you get the most out of these sessions and that should not just stop at the content from the speakers.</strong> Don’t be shy when it comes to connecting with an attendee who asked an insightful question or a speaker who left an impression on you. Now you have a point to reference when sending out that connection request.</p><p>Familiarize yourself with tools like <a href="https://calendly.com/">Calendly</a>, <a href="https://lettucemeet.com/">LettuceMeet</a> to set up quick conversations and make that first meeting all the less awkward.</p><p>Check out the following websites/companies to find events that could be of interest to you:</p><ul><li>Webinars: <a href="https://elearningindustry.com/webinars">https://elearningindustry.com/webinars</a></li><li>Webinars: <a href="https://www.eventbrite.ca/d/online/webinar/">https://www.eventbrite.ca/d/online/webinar/</a></li><li>Hackathons: <a href="https://devpost.com/hackathons">https://devpost.com/hackathons</a></li></ul><p><strong>Pro Tip:</strong> If you want to go the extra mile, maintain an active presence on these platforms. This has helped me connect with people all over the world on a more meaningful level than just a dormant connection/one-way relationship.</p><h3>2 — Reach out, Follow up</h3><p>When connecting with anyone new, always ensure you send a note with the connection request → goes to show you put in the effort of actually learning about them and also gives them a chance to see what you are hoping to gain out of this.</p><p>If you want to speak with 3 people, send out requests to 9. Be aware that the response rate is around 30% (at least in my experience). Instead of looking at this as a hurdle, be aware of it and make it work for you.</p><p><strong>Most importantly, follow up!</strong> Give the person some time (5 days to a week) and send a follow-up message checking in. In my experience this has pushed that 30% response rate up to ~70%. Just like yourself, people are busy and often forget or get distracted. Do not be discouraged.</p><h3>3 — Ask questions (the right ones)</h3><p>Walk into the conversation with an objective and the right questions. I like to write down the objective of my chat and list out my questions. I start by introducing myself, explain why I reached out to them in the first place and ask about their experiences &amp; background. From there on, I drive the conversation with questions I have related to that goal.</p><p>As a Product Manager, it’s easy for me to put my PM hat on and prioritize my questions based on my goal and the relevant part of my connection’s experience. It does not have to be too extensive, just directed to a specific area.</p><p>Be sure to ask if they have any questions for you, since they may be looking to learn something out of the conversation as well, and thank them for their time.</p><p><strong>Finally, if you feel a synergy, don’t be afraid to ask if you can reach out again in the future with questions.</strong> Just as easily, you have now managed to convert that dormant connection to an active one.</p><h3>Ready.. Set.. Network!</h3><p>So go out there and start networking. Keep in mind, it’s not a one-size-fits all and each connection, each platform and each individual is a bit different. As I mentioned before, be aware of these differences and morph your tactic to work for you. If the person you are reaching out to prefers a text conversation over a phone call, list out your questions over an email. If Twitter is the place to be for your industry, get on there and start finding interesting people to follow. The worst that can happen is you try and learn something out of it — and is that really so bad?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c107b86ef33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working from home as a Product Manager]]></title>
            <link>https://medium.com/swlh/working-from-home-as-a-product-manager-c8c7c30d2cf0?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8c7c30d2cf0</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[wfh]]></category>
            <category><![CDATA[adapt]]></category>
            <category><![CDATA[priorities]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Wed, 24 Feb 2021 18:45:21 GMT</pubDate>
            <atom:updated>2021-02-24T18:46:27.892Z</atom:updated>
            <content:encoded><![CDATA[<h4>Actionable areas of improvement to effectively WFH as a PM</h4><p>Over the last year, we have all had to adapt to working from home and depending on the type of work you do, that could have been really easy or brought up some new challenges you had to get used to. A large part of my role as a product manager revolves around communication — with my team, my stakeholders, my management. I know my job can be done remote but adapting to doing it in this manner had its challenges initially. <strong>It’s not just about doing your job remotely but being able to do so effectively without a loss in productivity. </strong>Over the last year I’ve spent some time identifying tactics/tips that helped me work from home effectively as a product manager and I’ve included them in this article.</p><p>I’m not going to go into the best practices of working from home &amp; the best tools to use (there are a ton of articles about this out there, a few of which I’ve included at the end). This article assumes you already have your team set up to work from home with all the tools necessary and is more geared towards tweaking your remote work approach to get the job done effectively as a product manager. <strong>The most important takeaway is actually taking the time to evaluate your approach and determine what works best for you.</strong></p><h3>1 — Ask lots of questions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eR-lPzw2ROlPDfgm" /><figcaption>Photo by <a href="https://unsplash.com/@iamfelicia?utm_source=medium&amp;utm_medium=referral">Felicia Buitenwerf</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Why is this important?</strong> As a PM my job involves talking to many different people on different teams. When I had conversations with users or stakeholders, I relied on their facial expressions and body language heavily — after all, about <a href="https://ubiquity.acm.org/article.cfm?id=2043156">90% of communication is nonverbal</a>! With remote work, these conversations have been reduced to audio or video calls; the same user research that would have been done in person is now done via a screen share and the same conversations with stakeholders is now an audio call with only some people choosing to share their video. Often times people’s faces are not visible clearly. This means you’re missing out on important facial cues that could help understand a person’s point of view, and we are definitely giving up any learnings that could come from body language. As a product manager, I had to find a way to operate with this forced gap in my knowledge.</p><p><strong>How can I fix it? </strong>To bridge the gap of information from nonverbal cues, I’ve learnt to ask more questions — it’s that simple. If I can’t “see” the information in our conversation and I feel it’s an important point of learning, I just ask to bridge the gap in my knowledge. Just remember that each person’s time is valuable therefore ensure you’re making the most of it by asking:</p><ul><li>relevant questions</li><li>questions that have not already been asked before</li><li>targeted questions that address a gap in your knowledge</li></ul><h3>2 — Be adaptable (even more so than before)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KxQDzNBEQXg62PIyQjDlBQ.jpeg" /><figcaption>from <a href="https://clarkeandroskrow.co.uk/2020/05/01/good-news-you-are-adaptable-to-change/">Clarke &amp; Roskrow</a></figcaption></figure><p><strong>Why is this important? </strong>At the office it’s quite easy to approach a team member with a question or nudge them for an update on something. Context switching probably already comes to you naturally since you’re juggling multiple stakeholders and moving pieces as a product manager. Now that you’re working from home, you’re not going to be able to “nudge” that co-worker anymore. <strong>Asynchronous conversation is the norm now</strong>, with that Slack message going un-answered for hours and your co-worker unavailable for a quick call. You’re going to miss out on the short conversation exchange that could go a long way in helping you get the answers you are looking for.</p><p><strong>How can I fix it? </strong>If you’re a product manager, you’re likely already comfortable with context switching. Leverage this key skill and adopt a more flexible approach to your work so that you’re not creating hurdles for yourself while your coworkers may be busy with other work/calls and not responding to Slack messages. Take some time to evaluate the following:</p><ul><li>How urgent is it? Is there any other way you can get this info — another team member or Google perhaps? Evaluate your need and the urgency to ensure you’re reaching out about the most pressing item</li><li>What is each team member’s communication preference and working style? Work as a team to figure this out and try and respect them as much as possible to ensure you are reaching them via the best method but also not interrupting their work</li><li>Document notes not only from meetings but also important learnings from conversations in a centralized location where anyone can access it. This avoids duplication of questions and often means questions get answered before you even fully formulate them in your mind</li><li>Approach any decision-point with a user-focused mindset (this should come easy as a product manager but sometimes it can escape you when things seem dire)</li><li>Group questions for the same individual together so you’re making the most use of the limited time you may have on a call with them</li></ul><h3>3 — Prioritize your day, own it &amp; stick to it</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*jX7d0thLiAHd7PRK-PBhiw.jpeg" /><figcaption>by Adisai Chaturapitr from <a href="https://www.farmmanagement.pro/3-ways-to-prioritize-tasks/">farmmanagement</a></figcaption></figure><p><strong>Why is this important? </strong>While working from home, distractions are everywhere. It can be as small as a delivery you have to tend to or something much bigger like your pet running amok and leaving a mess behind them. There’s always something to deal with in addition to work. Therefore, it’s important to apply the same ruthless prioritization you would apply to your product requirements, to your own work.</p><p><strong>How can I fix this?</strong> I treat my day like a mini sprint that lasts one day and prioritize 2 to 3 key non-negotiable tasks I want to complete for that day. If possible I try to assign “effort estimates” to each item — the goal isn’t to time box an activity, but rather ensure I’m properly evaluating the activity I’ve set out to achieve for the day and made sure it’s a realistic piece of work I can complete. I usually set 10 mins aside to complete this right when I log on (before I get distracted by emails or messages because we all know that’s happening sooner or later).</p><h3>Understand what works for you</h3><p>This isn’t a “one-size-fits-all” situation. The one biggest thing that helped me was to assess my situation/needs and see where I lacked or where inefficiencies were introduced. <strong>The most important thing is to actual take time to evaluate your approach. </strong>You need to reflect on your work habits, your team preferences, the tools you have available and your goals to figure out an approach that works best for you. The more you actively evaluate this and adapt, the more you start getting creative with your approach and your work!</p><p>A huge thank you to <a href="https://medium.com/u/d2e9355ae522">Hicham Abou-Jaoude</a> for inspiring this article!</p><h4>Some more resources…</h4><p>Here’s some more interesting reads on remote product management:</p><ul><li><a href="https://www.productfocus.com/distilling-11-years-of-working-as-a-remote-product-manager-product-focus/">Working as a remote product manager | Product Focus</a></li><li><a href="https://www.productplan.com/6-remote-product-management-strategies/">6 Strategies for Remote Product Management Teams</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8c7c30d2cf0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/working-from-home-as-a-product-manager-c8c7c30d2cf0">Working from home as a Product Manager</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Product Manager’s Guide to APIs]]></title>
            <link>https://medium.com/swlh/a-product-managers-guide-to-apis-c5fffff0e5e0?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5fffff0e5e0</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Fri, 05 Feb 2021 20:15:28 GMT</pubDate>
            <atom:updated>2021-04-27T02:35:16.006Z</atom:updated>
            <content:encoded><![CDATA[<h4>What are they and why are they important</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/0*3mAAsy0vAab-jUxf.jpg" /><figcaption>Image by <a href="https://fiverr-res.cloudinary.com/images/t_main1,q_auto,f_auto,q_auto,f_auto/gigs/132560890/original/1d48e15e7b67d13e4721d03918d36485ec25494a/integrate-api-in-website-app-api-integration-and-development.jpg">Fiverr</a></figcaption></figure><p>We live in a world where technology reigns and data presides at every corner. As users of many different products, we’re no longer looking for the best product to get the job done, we’re now looking for the product that gets the job done AND works seamlessly with all other products we use. Therefore, it has become increasingly important to understand tools that simplify workflows and integrate components to provide a seamless user experience for our customers. Since data has become abundant, innovative teams have grown exponentially better at forming these links and connections to simplify workflows via APIs.</p><h3>What is an API?</h3><p>An Application Programming Interface, or API, is in its simplest sense a technology that connects two systems.</p><p>Here’s an analogy explaining it:</p><p>You go to a large library and are looking for ‘The Da Vinci Code’ by Dan Brown. But the library is huge and you have no clue where to find this book. Luckily for you, you see the librarian at their desk and a catalog with the types of books you can borrow. You request for ‘The Da Vinci Code’ from their fiction list. The librarian walks through the labyrinth of shelves to find the book and brings it to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Go1-sHZi2R1obKrO" /><figcaption>Photo by <a href="https://unsplash.com/@jzamora?utm_source=medium&amp;utm_medium=referral">j zamora</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In this analogy</p><ul><li>the library is the <strong>database </strong>— one of the systems involved</li><li>the books are the <strong>data</strong></li><li>you are the <strong>requestor </strong>— the application/system looking for information</li><li>the librarian is the <strong>API </strong>— they take the request back to the database and return information back to the requesting application</li><li>the request for the book is the <strong>call </strong>made to the API</li><li>the catalog represents the <strong>specific format the request has to follow </strong>so the API understands it</li><li>the book you received from the librarian is the <strong>response</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/0*91BYade60eqZKGYA.png" /><figcaption>By <a href="https://bytenbit.com/best-guidelines-design-restful-api/">Sachin Jain</a> for <a href="https://bytenbit.com/">ByteNBit</a></figcaption></figure><p>In the simplest of terms, that is what an API does: it acts as the interface between two applications and facilitates information transfer while ensuring speed and security.<strong> </strong>It is a developer-centric tool<strong> </strong>—<strong> APIs are built by and for developers as part of the application code, however, this doesn’t mean they can’t drive value for the end user.</strong></p><h3>How do they work?</h3><p>Let’s take a real life example.</p><p>You are on LinkedIn and you are trying to find some companies in the fintech space. You type out your keywords (industry, location, etc.) and LinkedIn executes the search to display relevant results from its database of thousands of companies in less than a second. This request to look up all the relevant companies almost instantaneously is likely facilitated by LinkedIn’s <a href="https://developer.linkedin.com/docs/v1/companies/company-search">Company Search API</a> (which is also available for use by external applications).</p><p>This type of request-response interaction can occur within a product or with external products and is used to facilitate information transfer ranging from financial payments data to location data, in order to provide a seamless experience for the end user.</p><h3>Why are they important to product managers?</h3><p>APIs open up a world of opportunities to build a more-integrated product to provide more value for your users. As a product manager, it <strong>helps to understand the benefits and the constraints that also come with the technical solutions built/leveraged by the product team, so you can make and communicate product decisions and strategy effectively.</strong> I’m not saying you have to understand APIs to the point where you can dig right into the code — instead you should be able to understand the value it provides your user and business so that you can identify and test if there is a need for it and communicate WHY this is necessary to all stakeholders/partners of your product.</p><p><strong>Using APIs built by others</strong></p><p>I’ve created a really simple, short list of the ‘Good’ and the ‘Bad’ items to consider when thinking about using APIs built by others.</p><p>The Good:</p><ul><li>It can provide a well-integrated and simple experience for the user</li><li>If you leverage other APIs, you can focus on building features that address the core need for your product, while maintaining a simple and complete flow for the user</li><li>It can reduce the effort to implement specific features</li></ul><p>The Bad:</p><ul><li>Some cost money (based on the volume of requests you’re making)</li><li>You create a dependency on another system — if the other system changes their API call, you have to make changes on your end to ensure your user experience isn’t interrupted</li></ul><p><strong>Building an API for others to use</strong></p><p>There are a few key items to consider before undertaking this:</p><ul><li>Is this something users want or need? If so, are they likely to use it? This can be validated quickly by talking to customers or even with landing pages to evaluate the demand</li><li>What value is this driving for our business? Are we expecting an increase in revenue? or a higher conversion rate? It’s also important to ensure that we are targeting metrics in line with our product strategy and our organizational goals</li><li>Can we even do this? Is our business ready to support the cost of building it out and also the cost of maintaining the infrastructure to provide this service for our users?</li></ul><h4><strong>Implementation</strong></h4><p>Once you’ve identified the need for leveraging or building an API, it’s also important to understand how you break this down into user stories for implementation while maintaining focus on your user persona’s goal. It may help to split the user story into two — one for the API and one for the UI functionality/piece. However, you could include it all in a single user story and call out the API criteria specifically in the Acceptance Criteria. The approach should be discussed with the product team to see what works best for them.</p><p><strong>Who is the user?</strong></p><p>This could be developers, testers of an application or technical folks on specific internal teams. It is important to really understand and isolate your user and have a clearly defined persona for each type of user to provide context on their specific needs and goals.</p><p>For example — if your user is a developer, make sure you either define the specific type of developer (front end/back end/developer looking to incorporate payment functionality) or have a clearly defined user persona the team can refer to.</p><p><strong>What is their need and their goal?</strong></p><p>For this portion, you need to understand the functionality that is expected (create, read, update, delete) by the user and tie that back in to what the user is trying to achieve.</p><p>Your final user story could go something like this:</p><p>As a <em>developer working on payment systems</em>, I want to <em>fetch the customer’s relevant financial data when I send a customer identifier</em>, so that <em>I have the information from the customer to process the financial transaction</em>.</p><p><strong>Acceptance Criteria</strong></p><p>I’d include any mandatory fields that need to be a part of the API requests and the key fields that you need from the API response. If this connects in to the front end, it’s also important to call out those elements here to ensure its tackled by the team. If you’re integrating with an existing API then it’s best to read all the API documentation upfront and ensure it’s attached to the stories for everyone’s reference.</p><p>Another section to include would be API criteria that is not directly associated with the actual function of what the API is trying to achieve, but could impact the end customer. This could include the number of requests to be handled per unit of time, the time it takes to send out/receive a response, any authentication/authorization information expected by the API, limits on the volume of data sent in a single API call — it’s best to call this out explicitly and tackle this with the technical team, especially if these items can impact the end customer experience.</p><h3>Few more things to learn about APIs…</h3><p>Now this section includes more details that you could say are teetering on the edge of the more technical side of things. I’ve used this section to detail areas I’m familiar with through work and also explore areas new to me.</p><h4>Public vs Private</h4><p>APIs largely fall into 2 buckets: Public and Private.</p><p><strong>Public</strong> — these are APIs open for use external to a company. Key examples are the Google Maps API to leverage Maps functionality in your product, Braintree API to leverage payments functionality in your product or the LinkedIn Company Search API to add company search functionality in your product. The goal is to be able to share information for use cases being tackled by other companies, that can end up benefitting your end user (eg. <a href="https://akshayaag.medium.com/open-banking-what-can-it-solve-8edd6e64eaf3">Open Banking</a> in the world of financial data)</p><p><strong>Private </strong>— these are APIs developed for internal use for developers/applications with specific access. Key examples are customer information APIs within a company that can be used by different business functions within that company for obtaining customer information pertaining to the problem they are tackling.</p><h4>Types of APIs</h4><p>I’ve only listed the two key types (there are other older formats that are not used as commonly today)</p><ol><li><strong>REST (Representational State Transfer)</strong> — this is currently the most common type of API. REST represents a specific API architecture and these APIs generally use HTTP functions to make/receive requests (with information typically being sent/received via <a href="https://www.json.org/json-en.html">JSON</a> files). A key thing to note about REST APIs is that they are <strong>flexible in terms of the types of data they return/take and have a low bandwidth</strong>. There are 4 key HTTP functions these APIs are based on: POST, GET, PUT, DELETE (performing create, read, update and delete functions respectively)</li><li><strong>SOAP (Simple Object Access Protocol)</strong> — this is an actual protocol. SOAP APIs generally use HTTP and XML. These APIs are often <strong>heavier in terms of bandwidth and payload</strong>.</li></ol><h4><strong>Webhooks</strong></h4><p>Webhooks get a special mention because they can be considered a special type of API — the simplest way to describe them is a “reverse” API. With APIs, the data transfer will not happen unless a request is made explicitly; webhooks on the other hand trigger the data transfer based on an event (such as a payment being received, an update to a user’s feed, etc.) which can be really beneficial to automatically trigger a downstream set of events.</p><h3><strong>Where do we go from here?</strong></h3><p>This was just a short intro into the world of APIs and how it could play into conversations with your stakeholders as a Product Manager. Hopefully, it’s equipped you to identify opportunities to optimize your product and also understand the numerous items the product team has to consider when dealing with APIs.</p><p>There’s still a lot more that comes into play when building or using APIs, ranging from understanding API documentation to figuring out how you authenticate users of your API, and this means there’s a lot to be learnt if you’re interested. Time to dive right into it!</p><h4>If you want to build an API…</h4><p>I took the last two days to build a simple REST API based on Python and Flask that leverages the GET and POST request methods. I’ve listed out some great resources below that should definitely help you get up and running and experimenting on your own!</p><ul><li><a href="https://programminghistorian.org/en/lessons/creating-apis-with-python-and-flask#introducing-apis">Creating Web APIs with Python and Flask</a></li><li><a href="https://rapidapi.com/blog/rest-api-vs-web-api/">REST API vs Web API (vs SOAP API) [What&#39;s the Difference?] | RapidAPI</a></li><li><a href="https://blog.miguelgrinberg.com/post/designing-a-restful-api-with-python-and-flask">Designing a RESTful API with Python and Flask</a></li><li><a href="https://flaviocopes.com/http-curl/#perform-an-http-put-request">The curl guide to HTTP requests</a></li><li><a href="https://flask.palletsprojects.com/en/1.1.x/quickstart/#">Quickstart - Flask Documentation (1.1.x)</a></li></ul><h4>Additional great reads</h4><ul><li><a href="https://www.smashingmagazine.com/2019/01/api-based-platforms-product-managers/">Understanding API-Based Platforms: A Guide For Product Managers - Smashing Magazine</a></li><li><a href="https://www.departmentofproduct.com/blog/apis-explained-for-product-managers/">APIs Explained for Product Managers - Department of Product</a></li></ul><p><strong>References</strong></p><ul><li><a href="https://www.cleo.com/blog/knowledge-base-what-is-an-api">What is an API? Everything you need to know</a> — Adam Hughes</li><li><a href="https://rapidapi.com/blog/rest-api-vs-web-api/">REST vs Web (vs SOAP) API</a> (Sep 2020)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5fffff0e5e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/a-product-managers-guide-to-apis-c5fffff0e5e0">A Product Manager’s Guide to APIs</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Banking: What can it solve?]]></title>
            <link>https://akshayaag.medium.com/open-banking-what-can-it-solve-8edd6e64eaf3?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/8edd6e64eaf3</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[customer-focus]]></category>
            <category><![CDATA[fintech]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Sun, 24 Jan 2021 21:21:03 GMT</pubDate>
            <atom:updated>2021-01-24T21:22:47.266Z</atom:updated>
            <content:encoded><![CDATA[<h4>A quick intro to the open banking paradigm and a look into how this can help optimize customer experience with their financial products</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AZjwA8Rb_LV1JPYL.jpg" /><figcaption>Image from <a href="https://blog.withplum.com/the-banking-revolution-in-the-making-and-why-you-should-be-excited-about-it/">Elise</a> via <a href="https://blog.withplum.com/">The Plum Basket</a></figcaption></figure><p>What if I told you there was a problem with the way banking works in today’s world? Especially around the breakdown in information flow that occurs between our bank and all other organizations who need information from our banks. We are expected to provide so many other trusted financial service providers &amp; merchants with information from our banking products, yet we have to act as the middle man for almost all of these requests. As a customer, I want to be able to have an instantaneous, secure flow of information from my bank to other trusted third-party companies and vice versa, so that I save time and obtain the most value from all my financial products.</p><p>How can we solve this problem for our customers? Working at a bank, I do understand the amount of beneficial information they have on a customer. As a data enthusiast, I can’t help but fantasize about the kinds of problems one can solve by leveraging the data if they have access to it. What if there was a way to make banking more accessible and efficient in a secure manner? What potential opportunities to enhance the customer experience does this unlock?</p><p>Enter open banking.</p><h3>What is Open Banking?</h3><p>Open banking is the concept of allowing third-party companies secure access to data associated with a customer’s financial products and banking services, to enable them to build products/services that enhance the customer experience.</p><p>The current proposed solution is to do this by establishing <a href="https://medium.com/@perrysetgo/what-exactly-is-an-api-69f36968a41f#:~:text=Application%20Programming%20Interface%20%28API%29&amp;text=JSON%20or%20XML%E2%80%9D.-,The%20API%20is%20not%20the%20database%20or%20even%20the%20server,that%20can%20access%20a%20database.&amp;text=APIs%20allow%20our%20sites%20to%20alter%20data%20on%20other%20applications%2C%20too.%29">APIs</a> (Application Programming Interfaces) that registered third-parties can use to access customer financial data from a bank’s systems. They can be provided with read and write privileges to a financial institution’s systems, with the requests covering consumer account data, transaction data or even payments data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*ivfRdseJrjSERkOb" /><figcaption>Image by <a href="https://unsplash.com/photos/466ENaLuhLY">Marcus Spiske</a> via <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>If you have any more questions on how exactly it works, its benefits and its drawbacks, here is a great <a href="https://medium.com/datadriveninvestor/the-future-of-banking-what-is-open-ban-b1ad510b37ab">article</a> written by Kalana Wijethunga explaining it.</p><h3>What problems can you solve with Open Banking?</h3><p>This is the question that interests me the most. Banks can learn from tech giants like Amazon or Uber when it comes to leveraging this data to benefit the customer. Both Amazon and Uber provide a platform on which they connect their customers and a specific customer need — physical goods in the case of Amazon and car rides in the case of Uber. With open banking,<strong> banks could act as the platform that connects their gargantuan customer base with financial service providers</strong> <strong>(insurance providers, merchants, lenders, etc.) to allow customers to benefit not just from the core banking products they hold, but also an entire suite of financial tools built by others.</strong> Open banking introduces a secure flow of information, both into and out of a financial institution’s systems, with the ultimate focus being on the customer. What problems can this solve?</p><h4>Payments</h4><p>Today when you make a purchase, you use a card as a token to identify your account and rely on a payment processor (like Visa or Mastercard) to facilitate that transaction between the merchant’s bank account and your bank account, which can take somewhere between a few hours to a few days (that’s why we see pending charges on our cards).</p><p>With direct access to a bank’s systems via open banking, the merchant bank &amp; your bank can facilitate that transaction themselves via API calls on real-time payment rails (instead of the traditional card rails). The payment could be initiated by the you via a mobile app, instead of a card, at the time of purchase and the transfer of funds carried out in real-time, saving you time and unnecessary pending charges.</p><h4>Third Party Financial Services</h4><p>Lenders, brokers and insurance providers all rely on your banking data to be able to provide you with a service. Today you have to authorize use of your information and either transmit it yourself (literally send statements over) or initiate the transmission from bank to third-party and wait for processing on either end.</p><p>This is a transmission flow that can be simplified with open banking. Third party financial service providers could directly interface with the banks’ systems to obtain the necessary data and analyze this data to provide you with the best possible service or product. The bank acts as the platform where you gain access to a world of financial services built to best suit your needs as a customer, while other financial service providers use it as a platform to obtain data to best shape the products/services they build for you as their customer.</p><h4>Aggregate View of all Financial Product Data</h4><p>Today many customers have multiple bank accounts with different banks, multiple insurance providers, multiple lines of credits with different lenders. As a customer, you have no consolidated view of all your finances.</p><p>With open banking, you could build a solution that does just that — communicates with the various banks to obtain and present that information in one consolidated real-time dashboard. A single view of all your finances (maybe even with detailed analysis) so you can best understand it all.</p><h3>All this sounds great, when can we start?</h3><p>Technically, the open banking paradigm has been set in motion in different parts of the world already. In UK and Australia, the government set it in motion by passing laws mandating banks comply with open banking. In the US there isn’t a standardized framework in place, but new players like Plaid and Finicity are acting as the trusted intermediaries between banks and third-parties to provide these services.</p><p>In Canada, there are a few frameworks and tools that allow customers to consent to the use of their financial information by third-parties, however, banks have not yet made moves to adopt this paradigm completely and likely will not do so till regulation mandates them to.</p><p>In a world, where people rely on multiple apps and tools, and stand to save time and effort if provided with an integrated, connected workflow all the way through, open banking can pave that benefit for us in the financial space. It’s not a matter of if but when this future becomes a reality, unlocking the world of possibilities with it.</p><p><strong>References</strong></p><ul><li><a href="https://www.openbankingexpo.com/features/due-north-is-canada-ready-for-open-banking/">Open Banking Expo</a> (2019)</li><li><a href="https://www2.deloitte.com/content/dam/Deloitte/au/Documents/financial-services/au-fsi-deloitte-open-data-banking-payment-060120.pdf">Deloitte — Open Banking </a>(2019)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8edd6e64eaf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Product Management Bible: Inspired (Review)]]></title>
            <link>https://akshayaag.medium.com/the-product-management-bible-inspired-review-a31f9cd525f6?source=rss-7d699eb0c467------2</link>
            <guid isPermaLink="false">https://medium.com/p/a31f9cd525f6</guid>
            <category><![CDATA[marty-cagan]]></category>
            <category><![CDATA[problem-solving]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[inspired]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Akshayaa Govindan]]></dc:creator>
            <pubDate>Tue, 22 Dec 2020 17:20:59 GMT</pubDate>
            <atom:updated>2020-12-22T17:20:59.241Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I now know why many call Marty Cagan’s masterpiece the Product Management Bible. In my opinion, it’s a great book for anyone who has an idea and wants to understand an effective way to bring it to fruition.</em></p><p>I bought my copy after it came up in almost every virtual coffee chat I had and every “Must Read” list for PMs. True to every piece of advice I received, Inspired taught me what it means to be a good Product Manager and how best to work with the team of individuals — from Product leaders to Product team members — to deliver value to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/0*6uNW6gI2996aCWhs.jpg" /><figcaption>Image from <a href="https://amzn.to/37FfOlH">Amazon</a></figcaption></figure><p>Beyond understanding the ideals of Product Management, I also learnt the following 5 key points:</p><p><strong>Focus on the value you drive with your features and not the specific features you ship</strong></p><p>Marty drives this point home with constant examples of how building teams who actively participate in the problem discovery &amp; solution ideation, with a focus on outcome, will outperform teams who do as they are told &amp; fight to deliver output. It’s all about value to the customer &amp; the business NOT about the number/type of features that are delivered within a specific timeframe.</p><p><strong>A product succeeds because everyone did what they should. A product fails because the PM did not do what they were supposed to.</strong></p><p>This is something I’ve read in multiple books, blogs and articles. If the idea fails, it likely isn’t addressing a problem properly and if that’s the case, it’s because the product manager did not successfully comprehend the user’s problem. Keep in mind, we’re all human and we make mistakes, however, it’s a commendable skill to admit those mistakes and actively improve.</p><p><strong>The distinction between leadership &amp; management. Leaders drive the vision &amp; Management focuses on execution</strong></p><p>In discussing how to empower a product team to deliver on a vision &amp; execute a strategy, Marty adds a key point in differentiating between leadership &amp; management. To many leaders across organizations this may seem obvious, however, it’s a point of learning for those aspiring to reach that level one day. It is a learning curve one must go through as a Product Manager — starting as an executor and slowly growing to develop the vision.</p><p><strong>Product Discovery has to address 4 key risks: value, usability, feasibility &amp; business</strong></p><p>Understanding the company goals &amp; product vision is key in being able to identify the order in which these 4 risks need to be addressed for the problem at hand. This ties back very closely with the first point: driving value for the user/business.</p><p><strong>Customer Misbehaviour can be a great learning tool</strong></p><p>As a PM still growing my skillsets, this was an interesting new approach to me. The idea is as follows: during testing just let your customers use the product without much interference. You can learn a great deal about a problem and the usability of your solution from a customer “misusing” it. I’m excited to try this out during sessions with my users and see the slew of solvable problems I uncover just by letting the customers “misuse” the product.</p><h3>Anyone interested in problem solving should read it</h3><p>Overall, it is a must read for anyone in this profession but also a great recommendation for those looking for a refreshing approach to understanding the “Why?” behind how product teams select features to implement. That was me a few years ago as a product developer and this is a great lesson for me as a product manager.</p><p><strong>Reference:</strong> Inspired (2017) <em>Marty Cagan </em>(Get it <a href="https://www.amazon.com/INSPIRED-Create-Tech-Products-Customers/dp/1119387507">here</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a31f9cd525f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>