<?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 Rajesh Mukherjee on Medium]]></title>
        <description><![CDATA[Stories by Rajesh Mukherjee on Medium]]></description>
        <link>https://medium.com/@rajeshmukherjee?source=rss-b174d209e345------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*3USn1-8w8IgP2xlw.</url>
            <title>Stories by Rajesh Mukherjee on Medium</title>
            <link>https://medium.com/@rajeshmukherjee?source=rss-b174d209e345------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 19:49:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rajeshmukherjee/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[Three Lessons from Managing Product at an Emerging Tech Company]]></title>
            <link>https://medium.com/@rajeshmukherjee/three-lessons-from-managing-product-at-an-emerging-tech-company-88d3c5e191a9?source=rss-b174d209e345------2</link>
            <guid isPermaLink="false">https://medium.com/p/88d3c5e191a9</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Rajesh Mukherjee]]></dc:creator>
            <pubDate>Mon, 06 Jan 2020 12:21:49 GMT</pubDate>
            <atom:updated>2020-01-17T16:14:17.258Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pW4XH_3DI4LU-2PbSEcfPw.jpeg" /></figure><h3>What is this post about?</h3><p>Most organizations today are developing their “product” team to build better products. These organizations, I would call them “emerging Tech companies”, meaning tech is sometimes mistaken as IT here, face several challenges building a product first culture. In this post, I am going to share some of the challenges and lessons I learned in the process of managing products in such an “emerging Tech company”.</p><h3>Background</h3><p>Organizations are fundamentally built on three things —Values, People, and Processes.</p><p>Organizations that are still growing into a “product first” company faces biggest challenge in changing the existing <em>culture and values</em>. Which is responsible for attracting the people it employs. Which in turn drive the quality of the products they build.</p><p>It might take a while for “Emerging Tech companies” to truly carve out product leadership and understand the nuances between product owner, product manager, and UX researcher.</p><p>The beauty of Software products is the quick iterations it can go through, but “emerging Tech companies” might have legacy processes that might be a hindrance to follow such Agile development. PM’s you’ve been warned!</p><p>For example, they can have a ‘Wagile’ framework — a mix of waterfall and agile framework due to legacy reasons.</p><h3>Learnings</h3><p>I am going to discuss three main challenges and lessons I learned.</p><p><strong>Challenge #1: Conflicting Cultures</strong></p><p>When you are jumping ship from well-established software companies to non-software companies, there is a definitely a culture shock. The implication is the way people communicate.</p><h3>Learning #1: Learn to read people</h3><p>I learned that “open debate” style of work is not particularly appreciated everywhere. As an eager and ambitious PM, you might want to learn everything about your product and its ecosystem. Your eagerness and style might get mistaken for <em>Aggressiveness.</em></p><p>Try taking a step back and observe the behaviors of key stakeholders. A good way to grasp style is by observing the focus, depth, and tonality of problem discussions. A book I recommend for this is <a href="https://www.amazon.com/Influence-Without-Authority-Allan-Cohen/dp/1119347718/ref=sr_1_1?crid=SXZYXD80MHFT&amp;keywords=influence+without+authority&amp;qid=1579275335&amp;sprefix=influence+withou%2Caps%2C368&amp;sr=8-1">Influence with Authority</a></p><p><strong>Challenge #2: Unquestioned status quo</strong></p><p>While every organization wants to improve and innovate constantly, but change is often resisted.</p><p>I tried to implement an OKR process to improve execution but failed utterly.</p><h3>Learning # 2: Win Trust first</h3><p>The number one metric leader gets measured on is <em>Trust</em>. I learned that changing a process as a new PM can sometimes be both a bad idea and hard because your team doesn’t trust you yet. Further, while working in the weeds with your team, it sometimes gets hard to understand how the entire Machinery works.</p><p>As a new PM execute and show results first before implementing change. Yes, there are cases when a PM has the flexibility to introduce a quick change but those changes must be Tops-down. For example, if you can present the idea of the change to the Director and implement the change through her. Bottoms up changes work when the process is impacting you or only a few team members (less than 4)</p><p><strong>Challenge #3: Speed</strong></p><p>Moving fast in “emerging Tech companies” is hard. You might be constantly shot down in the backlog grooming meetings due to competing priorities or resources unavailability or your engineers working part-time on bug fixing due to lack of QA. Consequently, you have to cut scope, delay launch timelines and your product won’t meet its goals.</p><h3>Learning #3: Don’t be frustrated</h3><p>PMing is stressful, and it is important to manage stress. It can be frustrating when your launch timeline is approaching and your product is not 50% ready.</p><p>Cut features ruthlessly and communicate potential returns to each stakeholder personally. Be an opportunist, other products release might get delayed or rolled back, jump on it to push your development through. End of the day, a PM needs to be resourceful.</p><h3>Concluding thoughts</h3><ul><li><strong>Find your fit:</strong> Be true to yourself about what work environment brings out the best in you? It might be attractive to choose smaller organizations and startups but consider their culture. Remember, most organizations have <em>core values</em> for their wall, while some have them have it in their hearts.</li><li><strong>Learn to navigate company politics:</strong> While PM’s should be inherently good at building relationships, but be prepared to work well both with your supporters and adversaries. Leadership roles are inherently political since it is apparently seen as a position of power.</li><li><strong>Leverage your strength: </strong>Don’t forget you are the product and every product has a key value proposition. Identify your key strength and use it wherever possible. You and your customers will immensely benefit from the long term impact of it.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88d3c5e191a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you should work for Amazon (if you are hired)]]></title>
            <link>https://medium.com/@rajeshmukherjee/why-you-should-work-for-amazon-if-you-are-hired-fa1581ca963a?source=rss-b174d209e345------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa1581ca963a</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[hiring-strategy]]></category>
            <dc:creator><![CDATA[Rajesh Mukherjee]]></dc:creator>
            <pubDate>Wed, 05 Jul 2017 00:16:11 GMT</pubDate>
            <atom:updated>2017-07-15T17:19:00.587Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Prologue: </em></strong>This post is geared towards non-engineering professionals who want to get an insider scoop about career growth at Amazon.</p><p>Mechanical engineering didn’t interest me much, so I decided to learn all I could about business, not by earning an MBA, but rather by doing it. Back in 2009, when I started my first job at ZS Associates, I thought all I was going to do is attend high profile business meetings with c-suite executives wearing power suits. I mean that’s the rosy picture of a “management consultant” I had. But to my horror, I had to build ETL pipelines, run SQL queries and send out around 120 weekly reports without really knowing why or how it impacted the business.</p><p>In December 2012 the universe granted my wish, Amazon wanted me to join their marketplace team as a Business Analyst. I was absolutely thrilled to be a part of the company that is making history, but I really didn’t have much of an idea what working for this juggernaut would be like. Looking back, I realize it was an incredible opportunity that set the foundation of my career, thus I wanted to share what I learned from my personal experiences during my two and half year of stint at Amazon</p><h4><strong>Thinking Like a Leader</strong></h4><p>If someone reads Jeff’s letter to the shareholders, it becomes evident that how much he emphasizes on long term thinking.</p><p>Coming from a management consulting background, where gala lunches/dinners at 3–5 star hotels for new employees is the norm, I found it very strange to receive a bunch of black &amp; white printed NEO pages and some bare minimal snacks during my orientation. It was fairly disorienting actually! My manager brought me a sandwich at Whole Foods instead of a grand lunch buffet I was expecting; this was “Frugality” — a principle at Amazon — in practice. While I was upset about the RSU’s vesting distribution and Amazon’s frugality at that time, looking back it makes sense; Amazon never invests on short-term returns.</p><p>Strangely a lot of Valley start-ups haven’t learned from this simple principle. They tend to overspend on things that do not matter. No amount of perks or lunches will retain top-notch employees, unless they are working on something fulfilling, growing every day, and getting rewarded accordingly.</p><h4><strong>Learning How to Swim in a Whirlwind</strong></h4><p>There are numerous articles that criticize the intense work culture (sometimes untrue) at Amazon, but Amazon doesn’t expect an average employee. You will have to bring out your A-game every day.</p><p>On my first day, I was sitting at a weekly business review (WBR) meeting with the director of Amazon Marketplace and 20 other senior managers. For a rookie like me, my position provided me with an incredible learning opportunity. I was the “data-guy” with the responsibility to report product KPI’s to a room full of intimidatingly smart people asking probing questions to one another and debating to the death. During my first 60 days, while I was supporting a team of four Senior Product Managers, I had zero training. It was up to me to find the right resources and right people to reach out to and learn from. Either you find your survival strategy or you sink.</p><h4><strong>Developing Leadership Communication</strong></h4><p>All great leaders from history have one common trait among them that is the ability to communicate very very well.</p><p>At Amazon, anything that is spoken or written gets challenged to the point where the 5- why’s gets answered (read about “ 5 whys” here). During our Annual Planning Ritual, or lovingly known as “Opportunity Planning,” I witnessed this practice first hand. There was no hierarchy in the discussions. Anyone can challenge anyone during these meetings and dig deep to their heart’s content. It can be a humiliating and stressful experience for a lot of people, but it is good for business. Every idea is challenged, called out on its flaws, and most corner cases are covered, resulting in the creation of world-class products. Amazon also taught me how to read and write the infamous “1-pagers”and”6-pagers”. This is the single most important skill one can learn at Amazon. I can vouch that no other company in the world puts such rigor in reading and writing skills. Many new MBA grads struggled with their “6-pagers” because words such as “many,” “most,” “less,” and “much” didn’t exist in Amazon’s dictionary. They are always replaced with cold hard numbers.</p><p>The effect of such rigor was excellence. There was clarity in what we did and why we did it. This is one of the reasons why Amazon executes so well and so fast. (“Get Big Fast” — some of you may remember.)</p><h4><strong>Ingraining Values for Life</strong></h4><p>A real Amazonian will always carry the Amazon values into other workplaces or other future endeavors for good or bad. (Sometimes the cultures are a misfit)</p><p>Most senior managers live and breathe Amazon’s famous Leadership principles. Initially, I didn’t understand the importance of those principles or how do they make an impact on business. Those principles may seem to be just superficial business jargons to an outsider. However, as you grow with Amazon, it becomes apparent how these principles are the commandments to success; not only in business but also in one’s personal life. No Amazonian, (expect for Jeff maybe) excels at all the Leadership principles. Thus, they are constantly improving through practice (it’s always Day 1). The execution of these values is what separates the Amazonians.</p><h4><strong>Partying with the “Amazing Amazonians.”</strong></h4><p>This was the fun part. I worked with some amazingly smart people. We “nerded out,” paid homage to Wheelhouse coffee, and randomly got drunk from time to time. I made some great connections for life and learned a lot from them both professionally and personally.</p><p>A lot of people go to top B-school to build a network. Amazon provides an opportunity to build that network while having a job. You are challenged every day, you learn every day, and you grow every day. Amazon’s talent pool consists of not only smart but also friendly people. In all my interactions across engineering and business, I didn’t come across any snobby egoists. Everyone I met was very humble and helpful.</p><h4><strong><em>What are the exit opportunities after Amazon?</em></strong></h4><p>I don’t want anyone to take my word for it, so I wanted to get some to data to back up the some of the above claims. I looked at the data from Linkedin and used that data to analyze what are potential exit opportunities of Amazonian. Here is what I found</p><h4><strong>Microsoft, Google and Facebook are top employers of “ex-Amazonians”</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*VwJeSQs4Z1_XPLz0QSEZgw.png" /><figcaption>Note: Data is only for a sample of employees who left Amazon</figcaption></figure><p><em>MBB* — Mckinsey &amp; Co, BCG and Bain&amp;Co.</em></p><p><em>Unicorns* — Airbnb, Uber and Snapchat</em></p><p>Next, I wanted to see if there is a correlation between tenure at Amazon and exit opportunities. Based on a random sample of 30–40 employees, I found there is a trend between the two.</p><h4><strong>Employees who stays longer at Amazon have a good chance of making it to Google or Facebook, while employees who jumps ship early, goes to Microsoft</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*8GNucYGfaes-WZPQTlX81A.png" /></figure><h4><strong>Chicago, Boston, D.C and Austin are options too!</strong></h4><p>Although Seattle might be a reason to move out of Amazon, interestingly most employees who leave Amazon stays in Seattle,(Microsoft is here) followed by Bay Area, New York City, and Los Angeles. Other than this big cities Chicago, Boston, D.C, and Austin are also top destinations for ex-Amazonians. (not bad if you can keep the same base pay!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/493/1*oIvfdOeRolJGFIGnTVal5A.png" /><figcaption>Where do ex-Amazonians live?</figcaption></figure><h4><strong>Over 1,500 M-7 school alums works at Amazon</strong></h4><p>Finally, I wanted to see how “amazing” the current Amazonians are. So I looked at how many M-7 schools grad with MBAs are currently employed by Amazon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*F4JOr-SUQGZIWv1TuEidSQ.png" /></figure><p><strong><em>Epilogue : </em></strong>Jeff is simply one of the greatest business leaders of our time, and working at Amazon for a couple of years is practically the same as graduating from a B-School that is run by him. You start thinking like him by reflecting those leadership values wherever you go. While it is not for everyone, otherwise it will not be Amazon. If I could rewind time, I would happily do it all over again.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa1581ca963a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>