Demonstrating “product sense” or “product thinking” in an interview setting can be challenging because these are ambiguous concepts with expectations and success criteria that vary significantly across companies and individuals. But, meeting these criteria can be essential to breaking into product management, which is often quite difficult. One opportunity to definitively check this box is the case study interview, where the interviewer proposes a problem and the candidate works through how they would address that problem. 

I have laid out a simple, structured framework below. These steps and questions are also fairly relevant to current product managers exploring a problem space. 

1. Clarify the Problem
2. Define Success
3. Connect Success Metric with Company Goals
4. Consider a Range of solutions
5. Consider Follow-On Effects
6. Outline Assumptions / Areas of Uncertainty

1. Clarify the Problem. When facing a large or ambiguous problem, it is critical to cut to the core to identify the true problem. Focusing on symptoms could lead to a misdiagnosis. Consider using some form of the Five Why’s Framework to better understand the true nature of the problem. This also demonstrates curiosity and robust discovery habits, and the interviewer will likely have additional information to share if probed.

2. Define Success. After deepening our understanding of the problem, we can define what success looks like. Articulate an outcome that would be considered successful and an accompanying metric to quantify results and measure progress. 

3. Connect Success Metric with Company Goals. This is more of an optional step that I think would be helpful for more product managers to consider. Does focusing on and building for this outcome align with the company’s objectives? Should we invest in addressing this problem now (versus later)? Product managers (and other functions) should take time to periodically zoom out and ensure projects make sense in the big picture context.

4. Consider a Range of Solutions. Creativity and quick thinking are rewarded, as interviewers expect several possible solutions. Brainstorming can be tough under stringent time constraints, but try to develop at least three possible solutions. You can then compare the options and demonstrate the ability to analyze trade-offs. Consider the solutions from a Return on Investment (ROI) perspective, and select the solution with the highest ROI (all else equal). 

5. Consider Follow-On Effects. In practice, this should probably be done before a solution is selected. Product managers should review how a potential solution affects other parts of the product and the overall customer journey. Will this solution create confusion in the customer journey? Do existing features conflict in any way with the potential solution? Does the potential solution require changes to the product’s data model or infrastructure? This is a more specific version of seeing the big picture. 

6. Outline Assumptions / Areas of Uncertainty. Finally, it is useful to note major assumptions or areas of uncertainty that should be investigated further. Given the limited timeframe of an interview, there should be several to identify. I would also recommend calling these out along the way as much as possible. 

These areas are helpful to review when analyzing a problem space, and following this structure should allow anyone to demonstrate a “product mindset” in an interview setting.