Pod Insights The Agile Daily Standup - AgileDad How To Be A Rockstar Product Manager? About this episode How To Be A Rockstar Product Manager? You should join a rock band of course... Or you could listen to these helpful tips. How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 I got a question from a longtime listener, John. So John, thank you for submitting the question. He asked, "What are some practical things that you can do to become a rock star product manager?" And I thought it was a brilliant question, but at the same time, I had a question. My question was, "What does a product manager mean to your organization?" Because here's what I discovered. A product manager oftentimes means different things for different businesses, depending on the size, the type of business, even a role itself. So when you're thinking about the project manager or product manager role, you'll need to know what it can mean and that it means different things to different people. But that being said, that's set aside.
0:59 Speaker 00 The majority of roles follow same characteristics of a role. And I tried to put together, piece together, a simplified version of what a product manager focuses on. So they understand the market and opportunities. This means identifying potential opportunities related to a new feature, or a change in the product, or any of those types of things. Next, they define a solution. So this includes engaging with stakeholders to understand their needs, gathering requirements, identifying limitations, detailing what's possible. The product manager creates the necessary documentation to begin in the design, initiate, and evaluate things. They look for factors such as feasibility, cost reduction,
1:43 Speaker 00 business model impacts, value proposition of the product. Those are the things that drive them. And when a product solution is defined, and the product manager is created in Epic, and define all the requirements... The product manager then has to closely collaborate with the design team and have conversations with the development team to validate, is it technologically feasible? And also find ways to reduce costs related to product development. So the designer is the main person who leads the design phase, meaning that the product manager is there to support the designer and share their knowledge. So that is a big step. And this is where I came up with the whole, I don't know if you remember from training, John, but the POBA FATA, where a business analyst, functional analyst and technical analyst
2:27 Speaker 00 support the product owner in making these decisions. And oftentimes, this is where it becomes fuzzy because the product manager could also be the product owner where the FA or BA could be what the perceived product owner is. I think you see where I'm going with this. And this is where organizations really get hung up and confused. So when the design solution is done, the product manager then has to ensure the requirements and epic align completely with designs, meaning that changes may be necessary or updates or whatever the case may be. Once the design phase is completely done, then the product manager starts conversations with the team to ensure they fully understand the solution and are ready to start their delivery or development phase.
3:08 Speaker 00 During the delivery phase, the product manager can lead and help with meetings, provide additional information to developers, support removing impediments or distractions and ensure the timely delivery of what's happening. So in many cases, organizations designate someone like a program manager or another project manager to do this role. So this is where a lot of people have been talking about the recent Agile Alliance and PMI joining forces. This is where this comes into play because now there's been so much muddying of the waters. And I'm not blaming Agile, I want to be clear here, but there's been muddying of the waters with all the different roles, accountabilities, title, who does what.
3:52 Speaker 00 If you were listening last week, we had a great episode about understanding and aligning roles and responsibilities and titles as part of a team working agreement. But it's one of these things where A product manager needs to focus on ideation phase, initiation, kicking off a project, making sure we have what we need and if the idea is a good idea and in fact it aligns with where we're trying to go with our North Star. They're also responsible for research or discovery phase, understanding the market, identifying opportunities, clearly outlining the solution by definition, figuring those things out, identifying our personas, getting to the point where we're prepared for kickoff. Then the product manager can push it into product launch, which is where you'll often
4:37 Speaker 00 see product owners and actual scrum roles take over so that they can focus on getting this product or service to market and defining how everything's going to work and how people are going to collaborate with each other and coordinate the work in such a way that teams can easily swarm to get the work done. This is where you start talking about limiting WIP and understanding the right set of features that need to have, that need to be completed and having that work prepared so that the team can easily consume those features. It's about pursuing the opportunity and expanding the, taking advantage of the ability to be successful as a company. And those are the things that the product manager takes on as their main responsibility.
5:22 Speaker 00 So in a way, I guess you could say a product manager is more focused on a feature or solution and not necessarily the overall holistic roadmap. The roadmap is the vision of the product and that's often the same and done in collaboration with senior product managers or directors of a leadership team or, or anybody who's a key stakeholder in the organization. But the product manager is the first one who has to translate it and see how it leads those conversations down a path so that leadership feels informed about the opportunities and the product managers and developers and designers are all on the same page. So if you can get to that point where you have this level of alignment where you're defining and understanding the problem, making sure you do the, the due diligence of
6:07 Speaker 00 Writing an elevator statement for our target customer that is struggling with this problem. Our product or service is this type of product or service that provides this key benefit of compelling reason to buy it. Unlike our competitors' product or service, ours is different or better for this reason. What are we trying to solve? Ask yourself the questions. What are we trying to solve? Where does the problem start? What are the symptoms of the problem? Who's affected by the problem and how big is the impact? Why is this problem difficult to solve? If the problem is solved, what would happen? What would the main result be? What is something that we can track? Then you can define how it works, how it works now, what its limitations are and how it should work in the future. So it's a present identification of limitations and a future of how the product
6:52 Speaker 00 should behave or the service should behave going forward. We can gather information from stakeholders as part of discovery and this could be using focus groups, social media sentiment, figuring out what's going on and talking to the people involved so we can gather that information. When a product manager has a general idea of the problem and they understand it, then they can have better facilitated discussions with stakeholders to understand the requirements, needs and expectations. And that just makes everything kind of map together. Those conversations often begin with open-ended questions like, can you describe a problem and why it's happening now? Or help me understand how this is taking place? How do you imagine the solution to look? If you ask these types of open-ended questions, it gives people an opportunity to really dig
7:34 Speaker 00 deep and figure out beyond just the high-level symptoms, what's happening inside of the organization. Once you've asked those initial questions, then you can get more specific. Do you imagine this happening like this or like that and why? So from what I'm hearing, the issue is this and the expectation is this so that you can eventually be able to do this. These seem to be really important requirements and I want to make sure I didn't miss anything.
8:02 Speaker 00 How do you envision these laying out? All these things seem incredibly important. Do any of these have extended urgency or additional urgency about some of the others? These are the questions you can ask to help get alignment and help identify what things need to be done, when, in a practical way. You can also then evaluate solutions. So this is your initial evaluation of the solutions. And you can ask yourself, right? When you're gathered with the team and you're looking at potential approaches, you can start asking critical questions such as, is this feasible now? Do we have any dependencies? Will the solution adapt to all the use cases we discovered? Will it accommodate future iterations and changes to the platform? Is it cost efficient? What can be removed if we hit time constraints?
8:45 Speaker 00 What is the core to solution that solves the problem? What requirements haven't been written yet but seem necessary in order for the customer to have success? During this period, that's where all the questions arise. It's normal. And a product manager may need to contact stakeholders to confirm and evaluate assumptions. This is all completely normal. It's essential for the product manager to take notes on what the stakeholder says so that they can prioritize and weigh the urgency of everything that's coming in. If you can do these steps and get to the point where you're gathering requirements, sketching out mockups, visualizing what you're trying to do, evaluating alternatives and costs and feasibility, and making sure your timing is in line, these are all the things
9:29 Speaker 00 that are going to help you as a product manager be incredibly successful. It's going to make you stand out as a rock star. That's going to do it for this episode. John, I hope that helped. If you have a topic you want us to discuss, learn more at agiledad.com. We would love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care.
Previous The 15-Minute Worry Hack Next Now Is The Time For Customer Delight! Page updated November 7, 2026 · transcript and summary are machine-generated