Articulate Your Personal Product Management Principles and Show One in Action

How would you describe your philosophy of product management? Lay out the few principles that guide how you decide what to build and how you work with your team, and show one of them at work in a real decision. ```hint Principles need proof Settle on two or three beliefs you genuinely act on, and for each, recall a decision where holding it changed what you did. A principle with no decision behind it sounds like a slogan. ``` ### Clarifying Questions - Should I describe the philosophy I hold today, or also how it changed from earlier roles? - Are you most interested in how I choose what to build, in how I lead engineers and designers without formal authority, or in both? - Should the principles be framed for a particular kind of product, such as enterprise software where the buyer and the daily user differ, or stay product-agnostic? ### What a Strong Answer Covers - A short set of distinct, opinionated principles rather than a textbook definition of the PM role - Evidence for each principle: a concrete decision or trade-off where it changed the outcome - How the candidate resolves tension between principles, such as speed versus quality or customer requests versus strategy - How the philosophy shapes collaboration with engineering, design and stakeholders - Self-awareness about where the philosophy came from, how it has evolved, and its limits ### Follow-up Questions - Tell me about a time one of your principles led you to the wrong call. What did you change afterward? - If a senior leader asked you to ship something that conflicts with one of your principles, what would you do? - Which part of your philosophy would need to change for a product whose buyer is not its everyday user?