As a Product Manager, how do you approach prioritizing tasks and product features?
Prioritization can be one of the most challenging aspects of your position as a Product Manager. When you and your team are faced with endless tasks and numerous product feature options, it's up to you to decide what gets tackled first. The interviewer wants to know the process you take when coming to decisions and conclusions.
Provide evidence that you are calm under pressure and that you have a reliable framework for triaging tasks and features when they may all seem urgent at first. Walk the interviewer through your prioritization process, showing that your approach is a good fit for Facebook.
Some of the most common frameworks for task prioritization include:
- The MoSCoW method, which is an acronym for Must have (vital), Should have (priority), Could have (optional), and Won't have (scratch it!).
- The RICE scoring model, which is an acronym for Reach, Impact, Confidence, Effort.
- The Kano model, which focuses on product features and how important they may or may not be (Delighters,
Performance Features, and Basic Features).
"Typically, when I am prioritizing tasks or product features, I will use the MoSCoW model. I have been trained in Agile methodology and lean toward this model because it focuses on both the project stakeholders' goals and the customer's needs. I also find it the easiest method to use when I need to explain my decision-making process to individuals outside of the technical aspects of the project. The first step is to ask if the product feature is a 'must-have,' vital feature. Then, I ask if it is a 'should-have,' which makes the feature a priority. Moving down the list, is I ask if the product feature is a 'could-have.' Perhaps it's optional or could be visited at a later time. Then, I can determine if the feature is a 'won't-have,' meaning it's time to scratch that particular idea. Then, my team will prioritize the must-have and should-have features. I am also aware of other methods such as the RICE scoring or Kano models. Could you share with me if there is a preferred prioritization model at Facebook?"
Community answers are written by other candidates practicing this set. Reading how others frame the same question is one of the fastest ways to sharpen your own.
Anonymous Answer
- The MoSCoW method, which is an acronym for Must have (vital), Should have (priority), Could have (optional), and Won't have (scratch it!).
"Typically, when I am prioritizing tasks or product features, I will use the MoSCoW model. I have been trained in Agile methodology and lean toward this model because it focuses on both the project stakeholders' goals and the customer's needs. I also find it the easiest method to use when I need to explain my decision-making process to individuals outside of the technical aspects of the project. The first step is to ask if the product feature is a 'must-have,' vital feature. Then, I ask if it is a 'should-have,' which makes the feature a priority. Moving down the list, is I ask if the product feature is a 'could-have.' Perhaps it's optional or could be visited at a later time. Then, I can determine if the feature is a 'won't-have,' meaning it's time to scratch that particular idea. Then, my team will prioritize the must-have and should-have features. Could you share with me if there is a preferred prioritization model at Facebook?"
Marcie's Feedback
Good for you - asking a question back to the interviewer in order to keep the conversation going. Nice! Your MoSCoW method sounds useful and will provide the interviewer with a clear picture of how you prioritize tasks and product features. You might also mention that you take urgency and deadlines under consideration when prioritizing projects and tasks.
Unlock all 30 Facebook questions
Unlock expert responses to Facebook's rigorous product thinking and design questions.
Get Started