Your stance on design thinking and how you would use it day to day as a PM

Would you want to use design thinking in the product role you are interviewing for? Give your honest view of the approach and explain how you would put it into practice on the job. ```hint Show it on a real problem Rather than listing the stages, pick one problem that buyers or sellers on a vehicle marketplace actually face and show how starting from their needs would change what the team builds. Be ready to say when you would not run the full process. ``` ### Clarifying Questions - Would the role focus on buyers searching for and comparing vehicles, on private sellers and dealers creating listings, or on the marketplace as a whole? - Will I work with dedicated UX researchers and designers, or would the PM run most discovery work alone? - Are you mainly interested in my opinion of the method, or in evidence of how I have used it before? - Does the team have room for discovery before scope is committed, or does it work from a fixed roadmap? ### What a Strong Answer Covers - A clear position on design thinking, including where it adds value and where it is too heavy - How understanding users, framing the problem, exploring options, prototyping and testing would fit the team's real delivery cadence - Application to both sides of the marketplace and the tensions between buyers, private sellers and dealers - How qualitative insight is combined with funnel data and A/B tests rather than replacing them - Evidence from past work that the candidate has practiced the approach, not only read about it ### Follow-up Questions - Engineering wants to start building next week and sees discovery as a delay. How do you respond? - What would you do if interviews with sellers pointed one way and the listing funnel data pointed the other? - After some months of working this way, how would you tell whether it had improved the team's results?