JustAnotherPM

Why does everyone love Harvey Specter? Because Harvey doesn’t just win—he defines winning. He walks into a room and everyone knows it. He doesn’t second-guess. He doesn’t hesitate. He’s 10 steps ahead,playing a game that no one else even sees. And he does it all with the kind of confidence that makes you believe there’s no one better. He is what every Product Manager dreams to be! What makes him so great?!? 𝗨𝗻𝗯𝗿𝗲𝗮𝗸𝗮𝗯𝗹𝗲 𝗰𝗼𝗻𝗳𝗶𝗱𝗲𝗻𝗰𝗲 – When Harvey speaks, people listen. Why? Because he radiates certainty. He knows what he’s doing, and he knows he’s the best at it. 𝗠𝗮𝘀𝘁𝗲𝗿 𝗼𝗳 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆 – Harvey isn’t just solving today’s problem; he’s already thinking five moves ahead. He anticipates what’s coming and adapts faster than anyone else. 𝗗𝗲𝗰𝗶𝘀𝗶𝘃𝗲 𝗮𝗰𝘁𝗶𝗼𝗻 – No hesitation. No second-guessing. Harvey weighs his options and makes bold, fearless decisions—because he knows waiting around is a recipe for mediocrity. 𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 𝗿𝘂𝗹𝗲 – Harvey knows one simple truth: success isn’t just about what you know, it’s about who you know. He builds powerful and strategic alliances and makes them work for him. 𝗔𝗱𝗮𝗽𝘁 𝗼𝗿 𝗱𝗼𝗺𝗶𝗻𝗮𝘁𝗲 – When the unexpected hits, Harvey doesn’t flinch. He turns challenges into opportunities and pivots like a pro—turning every setback into a step forward. 𝗡𝗼𝘄, 𝗶𝗺𝗮𝗴𝗶𝗻𝗲 𝗛𝗮𝗿𝘃𝗲𝘆 𝗦𝗽𝗲𝗰𝘁𝗲𝗿 𝗮𝘀 𝗮 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗿. He wouldn’t just manage a product. He’d own the market. He’d see what customers need before they even realize it. He’d build a team that moves mountains. He’d create products that leave competitors scrambling—and his product wouldn’t just succeed, it would dominate. Harvey has the kind of qualities that would make him an unstoppable PM: ✅ Confidence that wins rooms ✅ Strategy that crushes the competition ✅ Decisiveness that delivers results ✅ Relationships that drive influence ✅ Adaptability that makes anything possible 𝗡𝗼𝘄 𝗵𝗲𝗿𝗲’𝘀 𝘁𝗵𝗲 𝗸𝗶𝗰𝗸𝗲𝗿—𝘆𝗼𝘂 𝗰𝗮𝗻 𝗯𝗲 𝘁𝗵𝗲 𝗛𝗮𝗿𝘃𝗲𝘆 𝗦𝗽𝗲𝗰𝘁𝗲𝗿 𝗼𝗳 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁. You can build the same mindset. The same skills. The same ability to not just play the game, but to redefine it. And that’s exactly what we're going to teach in our course. In just six weeks, you’ll gain the tools to think, act, and lead like the best. You’ll be the person who makes bold decisions, anticipates trends, and drives massive impact. Everyone can do product management. But are you ready to be the Harvey Specter of PM? Join the waitlist: https://bit.ly/4gaVeel Get all the details about the course. Be the first to know when it goes live. 𝗧𝗮𝗸𝗲 𝘁𝗵𝗲 𝗳𝗶𝗿𝘀𝘁 𝘀𝘁𝗲𝗽 𝘁𝗼𝘄𝗮𝗿𝗱 𝗮 𝗰𝗮𝗿𝗲𝗲𝗿 𝘁𝗵𝗮𝘁 𝗱𝗼𝗺𝗶𝗻𝗮𝘁𝗲𝘀.

In just 2 minutes, I will make you understand: the true meaning of 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗦𝗲𝗻𝘀𝗲 As a PM, problems are ambiguous and vague. The information is limited 2+2 is not always 4. Hence, there is no way to know the “right” answer Yet some PMs always do 𝘳𝘪𝘨𝘩𝘵 𝘵𝘩𝘪𝘯𝘨 Despite the ambiguity 𝗧𝗵𝗶𝘀 𝘀𝗸𝗶𝗹𝗹 (𝗼𝗳 𝗸𝗻𝗼𝘄𝗶𝗻𝗴 𝘄𝗵𝗮𝘁 𝘁𝗼 𝗱𝗼 𝘄𝗶𝘁𝗵 𝗹𝗲𝘀𝘀 𝗶𝗻𝗳𝗼) 𝗶𝘀 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝘀𝗲𝗻𝘀𝗲. In other words, it is the ability to find the right solution for the users and the business, despite limited and ambiguous information. There are 5 steps to go from ambiguous problem to a set of concrete solutions. 1. Create/clarify the overall goal 2. User Discovery: Identify users, pick 1 or 2 3. Problem discovery: Identify top user problems 4. Solution discovery: Brainstorm and select solutions 5. Alignment with larger goals ------------------------------------------------------- 6. Building and delivering the solution 7. Measure success and collect feedback (Step 6 and 7 are not part of “product sense”, but are important for success) This week (on Saturday) we're doing a 90-minute Masterclass on Product Sense. In this session, we will focus on: • A deep dive into the 5 steps [10 mins] • Best practices for Product Sense [10 mins] • Solve real problems together [20 mins] • 5 Tricks to improve product sense [20 mins] • Q&A [30 mins] Masterclass Details: • 𝗪𝗵𝗲𝗻: Saturday 24th August | 4:30 PM IST / 12PM BST • 𝗪𝗵𝗲𝗿𝗲: https://lu.ma/z47zcduj • 𝗣𝗿𝗶𝗰𝗲: FREE for the first 60 people; $15 afterwards Seats are filling fast. We only have 35 free slots left. Sign up before they are gone too!

Why do so many Product Managers (even the good ones) still struggle to deliver complex and projects? The main reason: They don't understand the role (and importance) of Project and Program Managers.  Here is the simplest way to understand the three roles and the differences (so you can execute and deliver flawlessly every time!) 𝗧𝗟;𝗗𝗥: 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗿: WHY and WHAT for a product 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗿: WHEN for a 𝘴𝘪𝘯𝘨𝘭𝘦 project 𝗣𝗿𝗼𝗴𝗿𝗮𝗺 𝗺𝗮𝗻𝗮𝗴𝗲𝗿: WHEN for a 𝘨𝘳𝘰𝘶𝘱 of related projects 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗿𝘀: 𝗙𝗼𝗰𝘂𝘀: create solutions that solve problems for customers and create impact for the business. 𝗣𝗿𝗶𝗺𝗮𝗿𝘆 𝗧𝗮𝘀𝗸𝘀: • Identify the right users • Identify and prioritize their problems • Prioritise solutions to solve them and create impact • Work with eng, design, other teams to deliver solutions • Measure success and keep improving    𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗖𝗿𝗶𝘁𝗲𝗿𝗶𝗮: products meets user needs and achieves business goals 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗠𝗮𝗻𝗮𝗴𝗲𝗿𝘀: 𝗙𝗼𝗰𝘂𝘀: focus on achieving short-term goals with concrete deliverables, ensure timely delivery and smooth execution of tasks. 𝗣𝗿𝗶𝗺𝗮𝗿𝘆 𝘁𝗮𝘀𝗸𝘀 • Understand how project ties to larger goals • Create detailed plans with timelines, deliverables • Identify interdependencies • Communicate with teams to ensure alignment • Identify and mitigate risks • Coordinate across teams to ensure timely delivery • Monitor progress, address any issues or delays • Measure progress, course correct when needed • Act as central point of progress, issues, deadlines 𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗖𝗿𝗶𝘁𝗲𝗿𝗶𝗮: Project is delivered on time, within budget, and meets defined goals. 𝗣𝗿𝗼𝗴𝗿𝗮𝗺 𝗠𝗮𝗻𝗮𝗴𝗲𝗿𝘀 𝗙𝗼𝗰𝘂𝘀: oversee multiple related projects, ensure they align with business goals, enable on-time and effective delivery of projects 𝗣𝗿𝗶𝗺𝗮𝗿𝘆 𝗧𝗮𝘀𝗸𝘀: • Create programs which include multiple projects • Ensure programs align with the strategic goals • Coordinate different project teams to ensure alignment • Monitor overall program progress • Manage and unblock interdependencies • Address risks and issues that affect multiple projects    𝗦𝘂𝗰𝗰𝗲𝘀𝘀 𝗖𝗿𝗶𝘁𝗲𝗿𝗶𝗮: All projects within the program are delivered successfully, contributing to the overall strategic goals. -- P.S. Of course this is an over simplification of the roles. All of them are complex, challenging, and include hundreds of moving parts. This mental model is meant to help you identify the main differences. P.P.S Do let me know how you define the three roles.

I am going to say this (again): Product Owner is a set of responsibilities whereas Product Manager is a role Still, most companies treat these as two different roles. The main reason? They don't understand the difference. That leads to confusion, inefficiencies, overheads, subpar products. With just two images, I show you the meaning and the difference. (If you're a visual learner, skip directly to the images) 𝗠𝗔𝗜𝗡 𝗗𝗜𝗙𝗙𝗘𝗥𝗘𝗡𝗖𝗘𝗦: 𝗥𝗼𝗹𝗲: Product Manager: is the role of a person who is responsible for all stages of the product lifecycle (planning, alignment, execution, measuring) Product Owner (PO): is a set of responsibilities that the PM takes on when she is in the execution stage of the product lifecycle (image 1.) 𝗚𝗼𝗮𝗹: PM: Responsible for overall success of product -- by creating value for the users and impact for the business PO:Responsible for on-time, high-quality solution delivery 𝗥𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝗶𝗲𝘀 / 𝗱𝗮𝘆 𝘁𝗼 𝗱𝗮𝘆 𝘁𝗮𝘀𝗸𝘀 PM: should think holistically about the product, users, business, technology, market because they are required to lead--planning, alignment, execution, and success of the product PO: Execution related tasks (sprint planning, testing, delivery, etc.) 𝗠𝗮𝗶𝗻 𝗳𝗼𝗰𝘂𝘀 / 𝘁𝗶𝗺𝗲 𝗵𝗼𝗿𝗶𝘇𝗼𝗻 PM: is focused on the future by aligning today's work to long term vision and goals PO: is present-focused, ensuring daily tasks and immediate goals are met. 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿𝘀: PM: has a large and diverse set (like leaders, sales, CS, eng, design, marketing, etc.) including customers PO: primary stakeholders are  engineers and other technical teams. No interaction with customers 𝗠𝗲𝘁𝗿𝗶𝗰𝘀 𝗮𝗻𝗱 𝘀𝘂𝗰𝗰𝗲𝘀𝘀: PM: uses business goals and product metrics to gauge success PO: is focused on delivery metrics like sprint velocity, burn-down charts, and backlog health. -- What am I missing?

I used to believe that the Best Product Managers had a unique skill-set that was out of reach for average PMs. But after observing the top 1% for years, I realized their secret is surprisingly simple: Just 10 habits they do consistently Anyone can copy them 𝗛𝗮𝗯𝗶𝘁 # 𝟭: 𝗥𝗲𝗹𝗲𝗻𝘁𝗹𝗲𝘀𝘀 𝗳𝗼𝗰𝘂𝘀 𝗼𝗻 𝗶𝗺𝗽𝗮𝗰𝘁 Creating impact is the most important focus for great product managers. • they always know the goals • work on things that contribute to them • eliminate tasks that do not contribute    𝗛𝗮𝗯𝗶𝘁 #2: 𝗗𝗲𝗲𝗽𝗹𝘆 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝘁𝗵𝗲𝗶𝗿 𝘂𝘀𝗲𝗿𝘀' 𝗻𝗲𝗲𝗱𝘀 Understanding user needs, not at a surface level, but the core jobs-to-be-done, is non-negotiable for Great PMs • get close to users • understand their needs • don't assume what they need • use it to inform product decisions 𝗛𝗮𝗯𝗶𝘁# 𝟯: 𝗞𝗲𝗲𝗽 𝘂𝘀𝗲𝗿𝘀 𝗳𝗿𝗼𝗻𝘁 𝗮𝗻𝗱 𝗰𝗲𝗻𝘁𝗲𝗿 GREAT PMs prioritize users in every aspect of product development (even if that means saying NO many times) • they represent user needs in decisions • foster empathy • they ask "How does this benefit our users?"    𝗛𝗮𝗯𝗶𝘁 #4: 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝘁𝗵𝗲 𝗽𝗿𝗼𝗱𝘂𝗰𝘁, 𝗺𝗮𝗿𝗸𝗲𝘁, 𝗮𝗻𝗱 𝗶𝗻𝗱𝘂𝘀𝘁𝗿𝘆 Great PMs deeply understand their product, market, competitors, industry • they're aware of market and competitors • know product's strengths/weaknesses • use it to inform product strategy    𝗛𝗮𝗯𝗶𝘁 #5: 𝗔𝗹𝘄𝗮𝘆𝘀 𝗯𝗮𝗹𝗮𝗻𝗰𝗲 𝘀𝗽𝗲𝗲𝗱 𝗮𝗻𝗱 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 Great PMs deliver products efficiently without sacrificing quality • prioritize rapid iteration when needed • set clear goals with quality checks • focus on research, testing for high-quality outcomes    𝗛𝗮𝗯𝗶𝘁 #6 𝗞𝗻𝗼𝘄 𝗵𝗼𝘄 𝘁𝗼 𝗲𝘅𝗲𝗰𝘂𝘁𝗲 𝘄𝗲𝗹𝗹 The drive successful execution of initiatives • collaborate with teams to minimize risks • build accountability and transparency • establish clear communication channels    𝗛𝗮𝗯𝗶𝘁 #7 𝗨𝘀𝗲 𝗱𝗮𝘁𝗮 𝗮𝗻𝗱 𝗶𝗻𝘁𝘂𝗶𝘁𝗶𝗼𝗻 𝘄𝗲𝗹𝗹 Great PMs know when to use data to inform their decisions (vs when to use intuition/gut feel) • they leverage data to understand users • trust instincts for guiding product vision • ground decisions in data, but trust their gut 𝗛𝗮𝗯𝗶𝘁 #8: 𝗥𝗲𝗱𝘂𝗰𝗲 𝗮𝗺𝗯𝗶𝗴𝘂𝗶𝘁𝘆 𝗮𝗻𝗱 𝘀𝗶𝗺𝗽𝗹𝗶𝗳𝘆 Great PMs don't fear ambiguity, and are good at simplifying open ended and complex problems. • identify uncertainties • get necessary info to act accordingly • break complex problems into actionable chunks 𝗛𝗮𝗯𝗶𝘁 #9: 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗲 𝘄𝗲𝗹𝗹 They're masters of communication. Their messages are clear, concise, and impactful • tailor communication to audience • actively listen and seek feedback • use feedback to get better 𝗛𝗮𝗯𝗶𝘁 #10: 𝗕𝘂𝗶𝗹𝗱 𝗮𝗻𝗱 𝗹𝗲𝘃𝗲𝗿𝗮𝗴𝗲 𝘀𝘁𝗿𝗼𝗻𝗴 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 They know that relationships enable ambitious visions and impactful execution • invest in understanding stakeholders • nurture honesty, trust, respect • leverage relations to drive results

In the coming 10 days, I will dive deep into 10 crucial documents every product manager should master. I will talk about what each document includes, why it is important, and what you should do to master it. Here's what's coming up:  1. OKRs and KPIs  2. Product Roadmap  3. Product Proposal / One Pager  4. Product Requirements Document (PRD)  5. User Stories  6. Project Pages  7. Progress Updates  8. Release Notes  9. Internal training / Go-to-Market Plan 10. Results and Measurement of Goals From OKRs and KPIs to release notes and training materials, we'll cover it all! These aren't just any documents—they form the backbone of what product managers do every day, quarter, and year. They inform the product strategy, keep you on track, and keep pushing you in the right direction. Let's embark on this learning journey together! 💼💡 All you need to do: - follow me Sid Arora - stay tuned - like and share so more people can learn In tomorrow's post, we talk about OKRs and KPIs

The tough part about product management is not... creating the solution or fighting HIPPOs or convincing 100 others The toughest and the most important part is understanding THE USER and the USER'S PAIN Get these two right, and you're already better than 90% of products in the world.

If you want to become a good product manager, it is important to understand: 1. What does "good" mean in this context 2. what can you do today so that you become "good" Siddharth Arora will be covering both these topics in his upcoming workshop: What does it mean to be a "Good" product manager The good news -- it is FREE to attend. Date/time: Mar 2, 2024, at 12:00 pm GMT Registration: link in comments