Prateek Sharma

⚠️ Common Mistakes Product Managers Should Avoid ⚠️ Podcast - Career in Product Management Product management is a tough but rewarding role, and even the best product managers can stumble along the way. Here are some common mistakes to watch out for—and tips to avoid them: Neglecting Data: Decisions made solely on intuition can be risky. Always back your choices with data to validate hypotheses and track success. Ignoring Customer Feedback: Building a product without real customer insights is a recipe for failure. Stay connected to your users, regularly gather feedback, and iterate based on their needs. Lack of Clear Communication: Poor communication with teams and stakeholders can derail projects. Ensure everyone is on the same page by setting clear expectations and providing regular updates. Not Managing Stakeholder Expectations: Stakeholders may have conflicting goals, and failing to manage their expectations can create friction. Be transparent and set realistic expectations from the start. Being Inflexible: Rigidly sticking to a plan despite new information can harm your product. Stay adaptable and be ready to pivot when necessary. Underestimating the Importance of Team Collaboration: You can’t do it all alone! Successful products require input from engineering, design, marketing, and sales. Foster strong cross-functional collaboration. 🚀 Avoiding these mistakes will help you grow as a product manager and lead to building products that truly succeed in the market! Follow Dushyant Bhatt and Chaitanya Shahare for career guidance. #ProductManagement #CareerGrowth #Leadership #AvoidMistakes #CustomerFeedback #Prioritization #Teamwork #Innovation #StakeholderManagement #ContinuousImprovement

157

29 commentaren

***99% of product managers don’t understand the super effective but non obvious levers for growth. *** Growth is not just paid traffic and writing blogs and good landing pages. Some obvious and non obvious levers - 1. The basic maths says ARPU > CAC so obviously the very first lever to get channel economics work is getting your funnel conversion as high as possible to make this maths work. 2. Now let’s talk about some non obvious levers- the first big one is bundling. Build bundled offerings/build products that increase the basket size in the same transaction. What does bundling do is it increases the ARPU for users which means that you have a better chance of winning the ARPU > CAC equation. 3. Next non obvious lever is to Improve organic/direct traffic %age of your overall traffic. What this does mathematically is brings down your blended CAC across organic + paid traffic and helps you win the ARPU > CAC equation or in other words the organic traffic and orders helps you experiment with higher CAC on your paid channels. How to improve organic/direct %, well build solid products to drive repeats, invest in an SEO engine to drive organic and so forth. 4. Next non obvious lever is help your team identify users on marketing channels who tend to engage with your product more. This means defining key milestone events on your funnel - sign ups, user demonstrating intent eg add to cart etc even before the final purchase and help your team build similar audiences to these users. Relying just on the final milestone will leave you with a much smaller sample to work with and super hard to scale. 5. Finally, a key part of making the economics work is specifically working on a product strategy that heroes high ticket size products. Which means working in tandem your growth team to work out product categories where interest in those categories (either shown by search volume/potential impression volume is high) and the ticket sizes are also reasonably high. Think of a 2x2, you want products with high ticket size and reasonable interest volume. What this does is again improves ARPU while lowering CAC helping you win the equation. Follow me for high quality content, not product philosophy but practical insights https://lnkd.in/gHweK_q7 AND also here https://lnkd.in/ggUKftFq My Playbook - https://lnkd.in/gHzyN-Xc My Channel - https://lnkd.in/gs6qnNUJ

18

Most intro to tech for product managers - let's talk APIs, what about its very close cousin SDKs? :) Every one seems to have memorized the restaurant and butler example for APIs. If SDKs sound like an out of syllabus question.. let's set it right. What is an API - well the most simplistic but clear explanation is it is a URL/endpoint that gives you raw data that you can munge as per your requirement. What is an SDK then? - SDK stands for software development kit, basically an SDK is a packaged piece of code for a particular platform to enable a certain functionality - For eg. you will have different SDKs - a Javascript SDK for web, an Android SDK for Android platform, so on. At this point you are like Anurag not getting this at all, what the f*** are you trying to convey. Let's take a concrete example - let's talk Facebook login So, let's say you are trying to enable Facebook login on your website and your Android/iOS app Now, Facebook offers different SDKs to enable Facebook login for different platforms, so like I said earlier a Javascript SDK for web, Android for Android apps, iOS for iOS Apps. Eg. FB SDK for Android https://lnkd.in/gtnCn_BT What it does is allows the Android developer to quickly get up and running, doesn't have to worry about many details - eg. how should I create user screens for FB login, the SDK comes with pre-built login button Don't have to worry about writing code for hitting FB server with user credentials & receive the access token, manage token still live etc, the SDK provides you this pre-built functionality which you just use. Think of it like boilerplate/starter code that FB has provided for your specific platform to make your life easy. Ok let's talk API now, well I can always say that hey I don't want to use the SDK & I want to implement the same via APIs Remember API involves hitting URLs so here is how you would hit FB servers to invoke the login dialog through the raw API https: //www.facebook. com/v18.0/ dialog/oauth? &redirect_uri={"https: //www.domain.com/login"} &state={"{st=state123abc,ds=123456789}"} GET the access token GET https:// graph.facebook. com/v18.0/oauth/access_token? &redirect_uri={redirect-uri} &client_secret={app-secret} &code={code-parameter} This approach will work on any platform because you are just hitting URLs and managing the response. Now when would you use an API & when would you use an SDK. Well sometimes your hand is forced, for eg. let's say FB doesn't offer an SDK for building apps on Windows platform - well your hand is forced you have to use the API. Sometimes you want to keep size hit to a min an SDK can often be big, use an API, sometimes you want to build functionality server side, eg. get ads from multiple sources server side and then pass the best ad to your website, use API, in most other cases use SDK. My Channel - https://lnkd.in/gs6qnNUJ My Playbook - https://lnkd.in/gHzyN-Xc Follow me https://lnkd.in/gHweK_q7 AND https://lnkd.in/ggUKftFq

18

The Ken has an empathetic article on the role of PMs in India. Highly recommended weekend read. However, I think the article goes beyond just empathy and romanticizes the role of a PM. For two reasons: 1. PMs must deliver measurable outcomes and healthy ROI. As must sales, finance, and operations folks. It’s foolish to assume that there is space in this hypercompetitive world for romanticizing Jobsian visions of the next iWhatever. 2. Almost all tech product companies in India are a copy of something that has worked in developed markets. The PMs job is to contextualize and optimize it for the Indian customer, regulations, and operating environment. A Product Marketer role, oversold as a Product Manager role. Two things we need to change: (1) Set realistic expectations with new hires. Don’t over-promise the role just to hire a rockstar. She’ll leave in a year’s time, and you’re back to square zero. (2) as PMs be prepared to do the hard grind in the initial years to figure out whether this is really for you. The Ken Praveen Gopal Krishnan Rohin Dharmakumar #productmanagement #productmarketing #expectations #careerchoices #careerpaths #metrics #ROI #stevejobs #reality

21

I recently completed Shreyas Doshi "Improving Your Product Sense" course. Attending this course was one of the best use of both time and money. If you are serious about product thinking, this is the course you should plan to attend. #ProductSense #ProductThinking #ContinuedLearning

40

5 commentaren

This event wouldn’t have been the same without the enthusiasm and participation. It’s always amazing to learn with and from such a vibrant community. Let’s keep the momentum going! Until next time, let’s continue to connect, learn, and grow. 🚀 GrowthSchool #ProductManagement #BrunchWithAnkur #GrowthSchool #Networking #LearningTogether

42

1 commentaar

#TechnicalWriters, have you ever wanted to ask a #ProductManager about their take on #documentation? In this episode, I am in conversation with Mrityunjay Kumar who has owned products in organizations such as Microsoft and Zenoti about software products and the role of documentation in their success. https://lnkd.in/dTh5yUaf #DocumentorsUnplugged #podcast

28

2 commentaren

How do #technicalwriters get a seat at the table? Listen to Mrityunjay Kumar talk about how product documentors can be more relevant to the success of a product. #DocumentorsUnplugged #Podcast

7

1 commentaar

Is Product Manager a generalist or a specialist ? Curiosity is mother of all inventions !! Thinking on the above lines motivates anyone to start building new ♾️ But more often than not, one out of 150 gets the approval of testing times to bring their subject a life. Considering new software products as a subject, my observations are below. 1. Asking right questions provides depth into thoughts 2. Does changing perspective of users could be reshaped by a jack of all trades? 3. Improvements are brain tanks of a PM 4. Growth mindset might not affect the overall user base perception 5. Combined skill level of a team brings thoughts to life 6. Technical know how brings scalability to platform 7. Approach of onboarding new users to a product determines long-term value 8. Often updates to the most used channel in the portfolio is a no-show 9. Teams are the strongest parlayed in the entire product user journey 10. Cultural shifts distorts the whole idea of creativity

3

2 commentaren

I recently took Shreyas Doshi's product sense course where we learned the secret to building winning products: There are no secrets Most of us are doing it wrong :D But you can get much, much better at it than you realized If you learn to think correctly The course was dense, intense, and I learned more in 30 hours than in many years of doing product. Fundamentally it taught me what it means to treat making correct product decisions as an actual skill. But you have to jump in the pool and swim - there's no framework that can do it for you. Perfect for product people, founders (there were several great ones in my cohort) and senior Engineers https://lnkd.in/e8KDhv5c

10

I found Punit Sethi's jargon free introductions to various web concepts. Concise & Useful. I recommend checking them! I checked where he explains Hydration https://lnkd.in/dsjRQzNf #frontend

1

***How to ramp up quickly in any product role and bring fresh insights to the table*** 1. Start with a beginner's mind. Don't start with a pre-conceived mindset. Meet and greet relevant folks and make copious notes. Now is the time to ask all questions, clarify all pieces of jargon. Ask a lot of questions around what are the top themes/focus areas for the org at this point of time. 2. Understand the org structure, it helps in understanding the flow of information, who are your key stakeholders and who to go to for insights in a specific area. Understand the org DNA, when there are conflicting goals what does the org prioritize. 3. Do lots of customer calls - get an outside in perspective. Dogfood your product. See this talk on why - https://lnkd.in/gtGsxcEp Otherwise the echo chambers of your organization will surface the same kind of information and noise. 4. Get access to all important dashboards and also build a way forward for new dashboards for key metrics that you feel are missing. 5. Always aim for a good mix of functional areas and levels - senior and junior folks while speaking to folks.. Junior folks in the trenches will give you rich info on building blocks, how things happen at ground level. Senior folks will be able to give you a zoomed out view. Both views are super imp. Follow me for high quality content https://lnkd.in/gHweK_q7 or https://lnkd.in/ggUKftFq

22

2 commentaren

Unlock the Secret to Powerhouse Team Performance 🚀🔐 Building a high-performing team isn't rocket science 🧪. But it does require mastering team dynamics 👥. Let's deconstruct this with a magnifying glass 🔍 for a moment. Imagine a Ferrari 🏎️ without an expert driver. All that horsepower, yet no trophies 🏆. That's an impeccable team with poor dynamics. Now, think of an average car 🚗 but with Lewis Hamilton at the wheel. Trophies galore! That's what we call excellent team dynamics 👌. The question is - How do you get your team to perform like Lewis Hamilton? 🤔 The answer? You master Team Dynamics 🎯. Find out more in my latest document – 'Mastering Team Dynamics.' 📚 Dive in today! See your team transform from a 'good enough' group into a championship-winning powerhouse 💪. Share your thoughts once you've unpacked it 💭. Can't wait to hear your success stories!

3

Alright, folks, I'm gonna let you in on a little secret. I've recently experienced Product Management for Beginners with GrowthSchool by Arnav Sharma, and it has seriously blown my mind. The mentor is amazing, and the content is so good that I can't get enough. I feel like I've levelled up my skills and knowledge every single session. If you're ready to kick some serious career butt, you need to check this program out. Link for the Program: https://growthschool.io Trust me, you won't regret it!

8

1 commentaar

💡 Designing B2B Products is no easy ! In B2B, there are multiple user personas, each solving different problems. Plus, the buyer and user are often not the same. 💡 Are you also curious about how design makes a product stand out? In my latest podcast with Dhwani Shah,Product Designer at Happay we discussed about various topics like 🎨 What is Product Design and UI/UX Design? 🔄 The difference between UI, UX, Product, and Visual Designers 🛠️ Skills needed to become a UI/UX Designer 🧰 Tools used by UI/UX Designers and the Product Designer toolkit 🗺️ A step-by-step roadmap to becoming a Product Designer 📚 Free resources to learn design 📁 Building a Product Designer portfolio 📊 UI/UX Designer case studies 🎤 Interview rounds for UI/UX Design roles 💼 Designing B2B products Watch the full podcast here: https://lnkd.in/g8weg4D6 #userexperience #uiux #ux #fintech #design

32

2 commentaren

Explore the dynamic world of React Native app development with our curated list of 18 top examples that chose RN for their business apps in 2024! From innovative startups to industry-leading enterprises, discover how React Native is revolutionizing the mobile app landscape and driving business success. Gain insights into the advantages and disadvantages of using React Native for app development and learn from real-world case studies that showcase its versatility and effectiveness. Whether you're considering React Native for your next project or looking to optimize your existing apps, our comprehensive guide has everything you need to make informed decisions and stay ahead in today's competitive market. Ready to uncover the potential of React Native? Let's dive in: https://lnkd.in/ggAJH8Aq #ReactNative #AppDevelopment #MobileApps #BusinessApps #TechTrends #DigitalInnovation #BacancyTechnology

15

🍳🚀 What Cooking Can Teach Us About Innovation 🚀🍳 Ever noticed how top chefs and product managers share similar tricks up their sleeves? Just like making a delicious dish, innovation needs a mix of careful planning, creativity, and a focus on making customers happy. Take Chef Vikas Khanna, who’s known for his attention to detail and sourcing the best ingredients, just like how product managers pick the best features for users. Every small change matters, whether it’s in a recipe or an app update, to make things great. Then there’s Chef Sanjeev Kapoor, who’s always surprising us with new flavors and ideas, much like how tech companies bring out new gadgets that change the game. Making a meal that people remember is a lot like creating products that users love. So, whether you’re in the kitchen or at work, remember—being precise, thinking creatively, and keeping customers in mind are key to cooking up something awesome in both food and innovation. 🌟 #innovation #productmanagement #creativity #customerexperience #leadership #techtrends #businessstrategy #startup #foodforthought #inspiration

1

You are a PM and you love building new products/features. But most of your past launches looked promising on paper, had early beta users lined up but the product never really took off beyond early beta users. You iterate and you spend months agonising over why your product failed. Still you don’t see a clear answer. 😥 If you want to debug your scenario, sharing top 4 dysfunctions of early stage product teams(as experienced first hand across startups/Meta), which often lead to product failure: 1. Ship early/Fail fast: Your team focussed on the mantra ship-early and iterate, fail fast and other intelligent sounding jargons, rather than doing rigorous product thinking required in finding key underserved customer needs, which your team is uniquely positioned to build. 2. Let’s build for who we can reach: Your team focused on building for every customer you can reach easily, not for customers who really need something differentiated from you. 3. Lack of user segmentation:Your team had no in-depth understanding of who precisely you should build for and which needs you can address for them. 4. Falling in love with the solution, not the problem: If your team doesn’t obsess over solving real user pain points, the product will flop—no matter how cool the tech is. So next time, spend more time thinking about who you should really build for and why. And then think some more, as PMF is always attained for specific segments of customers having unmet needs not for everyone. #productmanagement #producteams

20

1 commentaar