Five Guiding Principles for New Product Managers

As more companies shift to a product-centric focus, you may be one of the many project managers transitioning to a product manager role. There is no question project managers can fill the role, but the transfer of skills is not 1:1. As a new product manager, you may find yourself scrambling to shift your focus to a new and unique set of priorities.

What is so different about the product manager mindset? Product managers must obsess over their product and find ways to understand user behavior gleaned through analytics and direct user interaction. They must place a premium on optimizing the development team’s workflow and release capabilities—which fosters an environment of feature experimentation. These five guiding principles can speed, and hopefully ease, your transition into this new role: 1) The Product is Your Baby; 2) Customers Are Your Best Data Source; 3) Prioritize Continuous Value Delivery; 4) Find Strategic and Tactical Balance, and; 5) Develop Shared Understanding.

1. The Product is Your Baby

The project manager and product manager roles completely diverge in the outcomes each expects to realize. Project managers seek outcomes that shape the ideal execution of a project. Even when you align schedules, adhere to budgets, and meet the launch timeframe set by management, these waterfall metrics can still result in a bad product. While the project manager focuses on all the correct outcomes to deliver the product on time and on budget, it is often not enough to ensure the product solves key problems for the target customer.

Product managers must realign to a new set of outcomes. The product is your baby now, and to foster and grow it, you need to obsess over your customer. Understand their demographics and areas where they work. Find out what they like and do not like about your product. If your customer is experiencing a problem your product does not solve, figure out if/how your product can provide a solution. One insightful exercise that can bring customer problems into focus is listening to support calls. Understanding the failure points of your product is essential for improvement. Another way to gain product insight (and build rapport with the sales team) is listening in on sales calls, which will quickly highlight the value proposition your customers gravitate toward. It’s also important you learn to use the product as much as possible and directly experience what its challenges are. By taking a forward-looking approach, you’ll be better equipped to determine the new problems your product can solve and, consequently, the new customers you can target.

2. Customers Are Your Best Data Source

Users generate interactions with your product every single day, so it’s essential that product managers ensure monitoring is in place to capture the telemetry, analytics, and usage metrics from users’ behavior. Building these monitoring capabilities is as important as any user-facing product feature. Just as an engineering team determines the most prudent way to deliver a new feature, that same team should understand what metrics behind that expected feature are valuable for the product manager to track and devise a way to implement those metrics.

Ensuring some baseline usage tracking of a new feature is a good place to start because it provides a view into user adoption. Some key parameters to identify include:

• What percentage of users from the overall user base are using the feature? It’s important to define in the user story the actions for each feature that are core to understanding engagement.
• Frequency of feature usage
• What customer segments use the feature most often?
• Daily active user/monthly active user count
• Typical session duration for a user segment
• The number of user actions per session for a given feature

Pairing quantitative data with direct user feedback can serve as a powerful tool to understand the value being delivered to customers. Building customer response/comment mechanisms directly in your application helps you more easily gather this feedback.

Product-focused organizations can also implement a Voice of the Customer program—a structured approach to interviewing customers with the purpose of examining a hypothesis about your product. By targeting a broad customer segment to interview, a Voice of the Customer program can provide additional context beyond the metrics generated from the product.

3. Prioritize Continuous Value Delivery

Delivering software within an Agile framework allows for a constant flow of value delivery to customers based on your team’s development and release cadence. Each story within your backlog must serve as an independent slice of value delivered to your target customers. Your team should be able to build out that story and have it releasable at the end of your development cadence (typically 2 weeks, but this can vary based on company environment).

It’s important to optimize your development environment for this kind of workflow by prioritizing investment in DevOps and implementing automated test and code promotion capabilities. Ideally, a developer should be able to run automated tests and push a button to promote to a higher environment.

Once this type of capability is achieved the true purpose of continuous value can be realized: Experimentation. Continuous Value means you can run clearly defined experiments to determine feature viability among your user base. Releasing features to a small segment of your user base (as low as 1%) can limit the risk of a new feature not working. It can also provide valuable insight when introduced in conjunction with usage monitoring.

The goal is to shorten the feedback loop from users. As feedback comes in, you as the product manager now has the insight to adjust the planned value present in the product backlog. If an MVP feature proves not to be valuable, the team can quickly shift to other priorities and abandon the remaining stories necessary to fully build out the feature.

Fostering this type of environment can lead to challenges in clearly defining product roadmaps for the business. Releasing features incrementally and quickly reprioritizing based on user feedback makes it difficult to provide hard project delivery dates to leadership. This necessitates an adjustment to one’s communication style:

• Keep the roadmap high level and let leaders and team members know that priorities can shift. Keep the content to broad feature categories and ensure your time windows are generous when discussing potential releases. Ensure your team understands the full value of Agile metrics vs. Waterfall metrics, allowing for the flexibility necessary for continuous delivery.
• Ensure OKRs are set to reflect the business value delivered. Avoid having metrics tied to an arbitrary number of releases or the number of story points delivered per sprint. Prioritize defining what business value means in your specific context (X% churn reduction, X% increase in transactions within the app, X% increase in time spent on the app as examples) and report this to leadership.
• Provide updates to your stakeholders on a reliable and frequent cadence (at least monthly). Transparency in this regard will ensure stakeholders are not blindsided with updates to the features delivered/roadmap.

4. Find Strategic and Tactical Balance

The responsibility of a product manager is taxing. Some people find it difficult to let go of the team’s day-to-day tasks and focus on the long-term strategic vision of the product. Others are too removed from the specifics and may not be aware of the core challenges their teams face. It’s essential to balance the strategic priorities that are at the core of the product manager role while still being grounded and engaged with the daily team effort.

According to a 2019 study that surveyed 2,500 product managers, 73% of the respondent’s time was spent on tactical issues related to daily business activities. The remaining 27% was spent on strategy. Yet, respondents reported preferring a 50/50 split between time spent on strategic vs tactical activities–with strategy gaining a larger share of this split the higher one’s position in the leadership chain.

While it is important for a product manager to be connected to daily business activities, especially activities related to their development team, they must also make time for strategic activities, such as studying the market, determining the next evolution of an existing product, or developing new product ideas. Maintaining focus on your core responsibilities is key to successful product management. Engaging in work outside your professional skillset could lead to potential product issues, so if you find yourself doing work outside of your primary responsibilities (UX as an example), quickly make an effort to offload that work to the correct person on the product team.

That said, product managers do need to understand the development team’s challenges, dynamics, story estimation approaches, and QA processes. It’s easy to throw feature ideas at the team, but if capacity isn’t there or technical challenges are impeding the work, it becomes difficult to ensure the team can continuously deliver valuable functionality. If the product management responsibilities are split between multiple people—including product owners (not ideal as it’s more effective to have a centralized authority)—putting in place a regular cadence for team-wide discussions is critical to staying in sync. Another way product managers can align with the development team: Attend product demos and ask for early versions of the product to do some exploratory testing. You may also add value by ensuring the team has some capacity to allocate toward technical debt and resolving/optimizing issues that affect existing product performance.

5. Develop Shared Understanding

Good products are built on an understanding of overall business objectives and value delivery to the end customers. Any team can build a new modal, integrate with a new API, or make the overall experience less buggy. It’s when your product team has the strategic context for the market it is serving—namely specific customer usage and feedback data that drives product decisions—that your work becomes more meaningful and directly connects to your company’s overall goals.

One strategy for developing shared understanding requires communicating to the team the Who, What, and Why of the product. By doing so, they will become empowered to make decisions that drive better product outcomes:

• The Who: Customer personas must be socialized and explained in detail. By discussing customer personas, the team better understands the individual context of the user stories they are working and can make better choices to implement a feature in a way that specifically serves the target user.
• The What: The team must understand the core problems faced by the target user. What are the key product value propositions for them? How does the product materially make their lives easier? What does our product currently not do well? Openly addressing your product’s shortcomings helps the team prioritize the work better and properly sort the backlog by the value contained in each story.
• The Why: Make your team aware of the outcomes the business seeks to realize and how the product fits into the overall vision. It’s not valuable for teams to be given blanket mandates without context or explanation. By sharing what the business wants to achieve, you empower your teams to surface ideas that support the end goal.

These five principles not only provide valuable guideposts on your journey as a new product manager, but can also speed and simplify your transition to a mindset focused on product-specific outcomes that deliver business success and customer satisfaction.

If you’re a project manager transitioning to a product team role, I’d love to hear how you’re doing—what’s easy, what’s hard, and if you find these five guiding principles helpful.  Reach out to me on LinkedIn.