Book SummaryCracking the PM Career, by Jackie Bavaro and Gayle Laakmann McDowell

1-Page Summary1-Page Book Summary of Cracking the PM Career

Core Concepts and Abilities for Product Managers

This section introduces the foundational elements of product management and presents a comprehensive overview of the essential skills needed to excel in a product management role. It explores the core responsibilities of the PM role, emphasizing the importance of adapting to various environments and effectively managing a product's entire life span. Furthermore, it provides practical guidance on building valuable relationships with designers and engineers so that you're prepared to manage a team.

Defining a Product Manager's Responsibilities

The product manager position is dynamic and complex. Bavaro and McDowell explain that no single definition exists, and the exact responsibilities vary across industries and companies. Within a single organization, responsibilities may vary widely across various teams. This makes it a uniquely challenging role both to enter (how do you prepare for such a wide-ranging career?) and to get right (what exactly is your job supposed to entail?).

Understanding the Scope of Responsibilities As a PM

While the position of a PM is hard to define, there are some core responsibilities that all product managers share, regardless of their level, industry type, or company size. The authors describe the PM's role as entailing selecting the correct problems to pursue, determining how to measure success, and directing their team toward achieving positive results. To truly nail this, you need a profound comprehension of your customers, be able to translate your insights into effective solutions, and lead a team to execute well.

Other Perspectives

• Selecting the correct problems is subjective and depends on the company's strategic goals, which may not always align with the product manager's perspective.
• Some aspects of success are qualitative and may not be easily measurable, such as customer satisfaction or brand perception.
• Relying too heavily on customer feedback can lead to incremental improvements at the expense of breakthrough innovations that could be more impactful in the long run.
• Insights must be continuously validated and tested against real-world scenarios, as initial insights may not always lead to effective solutions without iterative development and user feedback.
• While leading a team to execute well is important, it is not the sole determinant of a product manager's success; strategic vision and decision-making are equally critical.

Navigating White Space and Adapting to Environments

The authors use the term "whitespace" to describe areas where there's an organizational shortfall in a company or team. Bavaro and McDowell's approach for working in whitespace is to "act like an owner," and not just an "employee," which means you oversee your product's success as a whole, even in the areas that are not directly under your control. For instance, a gap could appear as something that's missing (like a team without a dedicated user researcher or tester), or it could be that a needed function is being poorly handled by the people who are currently responsible.

Many companies and teams have processes, structures, templates, and philosophies that were implemented to address issues or enhance work efficiency. Over time those processes can become dated, misaligned with the organization's goals, or even counterproductive. An important part of acting as an owner is to identify opportunities to improve those systems, and to then take the lead on enacting those improvements so that all of your teams can do their best work.

Other Perspectives

• The focus on "whitespace" might divert attention from other important aspects of organizational health, such as culture, employee engagement, or leadership effectiveness.
• Not all employees have the influence or authority to oversee the success of the product as a whole, which could render this approach impractical for some.
• Assuming that all gaps are negative ignores the possibility that some whitespace could provide creative freedom, allowing team members to innovate and find new solutions without being constrained by rigid roles or functions.
• Templates and philosophies that seem outdated might still be effective due to their simplicity and ease of understanding, which can be advantageous in certain situations.
• The concept of acting as an owner may not align with the cultural or operational realities of all organizations, particularly those that are rigidly structured or bureaucratic.
• The concept of taking the lead on improvements might not be feasible in environments where there is resistance to change or where the existing processes are deeply entrenched and protected by those in power.

The Engineering, Design, and PM Team

A great way to comprehend a PM's duties is to examine the other roles in a product team, as each member is accountable for a distinct aspect of a product launch. The authors explain that the core product team at most modern companies is called the "triad"-the engineer (or tech lead), designer, and product manager. At the best companies, all three work in close collaboration.

Each person on the team handles a different part of the solution: engineers manage the technical implementation, designers focus on the user experience, and the PM ensures everything works together and that the whole solution delivers value to customers and the business. The product manager identifies which problem to solve, defines success, and guides the team toward the solution that works best. These boundaries between roles are not rigid, however, and the way work is shared between team members can vary significantly. For instance, a senior designer could play a bigger role in defining the problem and need more independence, while a less experienced designer might want the PM to provide them with highly detailed instructions. It’s beneficial to directly discuss this with each new team member so...

Cracking the PM Career Summary Skills for Execution and Delivery

This section covers the skills that PMs need to launch high-quality products quickly, efficiently, and successfully.

Running Projects Effectively

Here you'll learn about project management—what a PM does during the "Develop" and "Deliver" stages of a product's lifecycle. The authors present a number of different approaches for organizing work (such as Agile, Kanban, and Scrum), and how to guide your team in making effective decisions and collaborating successfully. Good project management not only cuts down on wasted work, it also improves team morale, as teammates feel a sense of clarity and accomplishment.

Project Manager Duties: Agile and Scrum Methodologies

The authors explain how agile methodologies such as scrum and kanban are great tools for breaking down large releases into multiple, smaller phases and launches where the team’s engineers can focus their energy on the most important pieces, and the PM can start incorporating learnings early in the process. Scrum is a good place to start, as it introduces a number of helpful terms and processes, but the exact process a PM should use will vary depending on what the team requires.

Other Perspectives -...