Frequently Asked Questions
These common questions and their short answers are taken from Julia Barham’s book The Project Management Playbook: Create, Ship, and Optimize Winning Products (2026). You can find longer answers to each in your copy of the book, either printed or digital version.
- What makes this book different from other product books?
Most product books today do one of two things: they stay at the level of theory and principles, or they plant a flag on a single topic and go deep. Both have value, but few acknowledge the reality for everyday practitioners: managing a portfolio of features in different stages of maturity, trying to balance discovery and delivery simultaneously, working without durable design and data partners, and dealing with needy stakeholders.
This book is meant to give you something you can use on Monday morning when a new problem hits your inbox. Wherever you are in the product life cycle, Chapters 3–10 have a playbook method that can help focus your team and help you march forward with confidence. - I’m not a product manager—is this book still for me?
Absolutely. “Product manager” is a title, but product thinking often shows up in dozens of roles across companies because it spans five critical domains, which are covered in Chapter 1, “The Truth About Product Management.” Designers, engineers, strategists, product owners, business analysts, and founders are all doing product work to some degree. Even teams that don’t follow the product operating model still need to define problems, create solutions, and achieve product-market fit.
This book uses the term PM as shorthand, but it’s written for anyone building technology-enabled solutions to meet customer needs and business goals. If that’s the work you do, this book is for you. Plus, if you plan to interview for product manager roles, Chapter 12 “The Future of Product Management and You” includes interview strategies and resources. - I’m an experienced product manager. Do I need to read this?
Yes, for three reasons. First, the field of product management is a moving target. Experience doesn’t equal longevity. This book covers enduring principles and modern technologies, tools, and ways of approaching product craft today. Everyone has to stay current.
Second, thousands of experienced product managers have blind spots. Many were stuck in delivery roles for years and then expected to become strategists overnight. Chapters 3–7 will help them level up discovery skills, strategic thinking, and stakeholder influence techniques. Other folks spent years cooking up “strategy,” but don’t have enough execution experience to know how the two connect. Chapters 6–10 will help these readers go deep on the importance of using data and technology as a strategic lever, how to lead delivery teams, and how to assess product-market fit.
Third, if you want to move into product leadership, you’ll be expected to coach less-experienced PMs. To do this, you can use the skills assessment in Chapter 2, “The Effective Product Manager’s Toolkit,” to evaluate your team and develop individualized coaching plans. You can also use the principles in Chapter 11, “Mastering Leadership and Influence,” to help teammates build a strong brand and prepare for promotion. - Does this book cover AI tools and AI product management concepts?
Yes! Throughout the book, I encourage teams to supercharge the product development process using AI productivity tools, with one critical caveat: AI tools should supplement, not substitute core product thinking. Chapter 6, “How: Defining the Approach,” takes a deeper dive, covering the key technology concepts every PM should understand about AI today, including five specific technologies and six skills every product manager should develop when working on AI-based products. Notably, this book also addresses two emerging areas that every product manager and business leader should understand: how to evaluate third-party AI solutions and how to practice responsible AI standards. - Is there a single methodology that works best in product management?
No. Product management varies greatly by company, team size, product maturity, culture, and org design. A PM working for a large enterprise will have a different experience than a PM operating at a five-person startup. That said, Chapter 2 covers four competencies that are required in almost every context (strategic thinking, discovery skills, delivery skills, and leadership behaviors) and common methodologies used by product teams today.
