Most product case frameworks, including my S.U.S.S. framework, require the candidate to prioritize user segments before proceeding to pain point identification.  

Some people have three criteria and then a five point scale for those three criteria. Just stating the structure makes me scream K.I.S.S. please! (Keep it Simple Stupid) 

I advocate a simple two criteria framework with a L, M, H grading system. My approach requires no complex averages to be calculated while under extreme stress.  

How you deliver your prioritization varies depending on the company you are interviewing at: Meta/Facebook requires more obvious structure (clear framework) to be displayed while Google is looking for comfort with the concept that is better displayed through concise verbal communication. 

I recommend always prioritizing in your notes, even if you don’t show your work. It helps you present your ideas clearly. BUT if you don’t show the visual, don’t painstakingly read each line and ranking one-by-one. Present your conclusion and then share the logic. 

Here are what my prioritization grids look like: 

Remember, the grids help you maintain structure and clarity of thought. But don’t sound frameworky or robotic. It is a tool not a crutch.