Practicing standard consulting frameworks, but just bombed a mock Amazon product interview. The interviewer said I was ‘too structured’? Looking for insights from tech PMs on balancing analytical rigor with the creativity they expect. What specific adjustments work for ambiguous strategy cases?
Key difference: Tech PM cases value hypothesis-driven creativity over exhaustive analysis. Instead of 70/30 prep work to presentation ratio, flip it. I coach candidates to spend max 5 minutes structuring, then dive into prototyping. Example: For ‘Design a fridge for astronauts,’ immediately sketch 3 user scenarios rather than market sizing.
Had the same wake-up call prepping for Google! My mentor made me do ‘framework jenga’ - pull out pieces of my consulting templates until only core insights remained. Turns out they want 20% structure, 80% storytelling. Now I lead with user personas instead of profit trees.
Don’t worry! Tech cases are about vision first 
Try leading with bold ideas then backfilling logic. You’ve got the skills - just shift the order!