Peter Yang’s Post

Product release is not about slide shares. It's not about setting weekly calls It's not about PMs grilling the product team It's about timely execution of the much need solution. And record-speed execution on the feedback.

Improving product sense is a two step process. The first step is to make a habit of creating a log of product decisions you made/ are making. Looking at the impact of these decisions over time helps you assess how good/bad is your product sense. It serves as a feedback loop. The next step is analysing this feedback loop well to identify your weaknesses and blind spots. While you can do the analysis yourself, it’s far more effective when done with another trusted PM with strong product sense. Now this isn’t to say that doing both steps is as easy as it sounds, but one has to at least start doing them first to get initiated on their journey to improve their product sense.

🤔 Did you know, it just takes a simple framework to explore and understand any product? 🎯 That is exactly what I am uncovering in the next edition of PJ's Perspective (my blog). 🤩 📌 If you are new to Product Management or want to get into Product Management, don't miss this one. 👍 📌 It will help you build a strong Product Mindset and improve at Product Management. 👌 👉 I have started this blog series ✒️ to help build and strengthen a strong Product Mindset. Get all the knowledge nuggets directly in your mail and it's completely FREE. 🎁 #ProductManagement #ProductManagers #LearnProductManagement #ProductOwner #Agile

Here's a list of some of the "must-reads" for PMs and aspiring Product Managers out there. How many of these have you read already?

94% of PMs fail at Product Discovery. Don't be one of them. PMs who don't do Discovery lack the clarity to create any impact. That's why we have written a complete guide of the '11 lesser-known mistakes PMs make during Discovery' PS: Some of these are hots take. Please proceed with your own risk. 🚨 Want it? Comment 'Discovery' and we will send it your way! 📥 #product #productmanagers #productmanagement

'A release schedule is not agile enough; it's too rigid.' Consistency goes beyond routine — it's a game changer. Here are 4 benefits of having a release schedule within your organization: 🎯 Unified direction — Everyone's on the same journey. It maps out goals, ensuring everyone's energies converge. 🕑 Build trust — When customers know what to expect and when, their loyalty deepens. 💡 Nurture growth — Consistent releases mean constant learning. Every new release is an opportunity to adapt and refine. 🔄 Stay connected — Regular updates provide more chances to engage with users, really getting to the heart of their needs. It's not about getting it perfect every time; it's about — progress, — adaptation, — always pushing forward. A release schedule is a compass guiding you through today's fast-paced digital landscape. — I'm Tom Sieron. Passionate about product excellence and innovation. Let's connect! 🚀 — #ProductManagement #ReleaseSchedule #ContinuousImprovement

"So you don't care about hitting our annual goal then?" This was in response to a product manager raising concerns about their current focus not having the necessary leverage to move their outcome as much as we initially thought. Instead of engaging in a helpful conversation about what we've learned and the given constraints, this question put everyone on their heels. Of course the PM wanted to hit the goal. It is completely unreasonable to think that because they recommended changing course, based on recent evidence, that somehow meant they weren't bought in to the goal. This strict adherence to decisions made before new understanding or information is found cripples product teams. It becomes more about what we said we were going to deliver than figuring out how to achieve our outcomes. It's an easy trap because what we ship has immediate, binary feedback. Did we deliver it or not? Versus results are lagging and very rarely can be tied back explicitly to the work. Products are dynamic things used by messy, complicated humans. That's why our process needs to be dynamic and messy too!

Fast follow... MVP... These are common terms Product teams use all the time. I believe we have it wrong. We are abusing the terms, the work, and the people by using them. We need reframing. MVP + Fast follow = Iteration Iteration is what we are truly striving for. Create the most basic version of an idea. Release it. Learn from its use. Iterate. The term MVP needs to go to the graveyard, with Fast Follow right behind it. Let's just iterate.

A great reality check for your Product Team. Answer these questions in a scale from 1 to 5 (1 = Never / 5 = Always). 👇 HOW OFTEN DO YOU EXPERIENCE THE FOLLOWING? 🤔 a) Work towards an output over an outcome b) Motivations are opinions and not evidence (data) c) Roadmap is prescriptive instead of allowing you to embrace the unknown d) Concern is to meet a deadline instead of reaching goals e) Priority is to implement a solution, not to solve a problem Once you finish, calculate the average of your grades. The lower your final score is, the better. Have a good day. This exercise is from the great book "Untrapping Product Teams"

What sets apart an average product manager from an exceptional one? Many individuals often focus on acquiring a plethora of frameworks and processes to elevate their skills. In my upcoming blog post, I argue that it's the nuanced quality of product sense that truly makes the difference and should be prioritized.