PM guesstimate practice plan for consulting-style interviews
Build skill with PM guesstimates by practicing structured decomposition, explicit assumptions, and basic calculations. Focus on clarity, not speed. Use realistic scenarios, check your math, and reflect on reasoning quality to avoid common missteps in consulting-style interviews.
PMMockr.comStart with a common guesstimate decision
Imagine you’re asked: 'Estimate how many electric scooters are rented daily in a mid-sized US city.' The temptation is to throw out a quick number. But strong candidates pause and break the problem into manageable components. This habit is essential for consulting-style PM interviews, where clarity of thought outweighs quick guesses.
A common mistake is to dive into calculations without explaining the logic. For example, simply multiplying city population by a guessed adoption rate skips the opportunity to show structured thinking. Instead, interviewers look for a clear decomposition and explicit assumptions at every step.
Why structure matters more than speed
Rushing through mental math or skipping steps leads to errors and unclear reasoning. Structured breakdowns signal to interviewers that you can tackle ambiguous problems methodically. Consulting-style interviewers want to see how you approach uncertainty, not just your arithmetic skills.
A strong structure also makes your logic easier to follow and corrects. If you’re off track, it’s much easier for someone to jump in and challenge an assumption than to untangle a chain of opaque calculations.
Choose a decomposition approach
There are many ways to break down a guesstimate, but for most PM problems, starting with a population or usage funnel is simplest.
For the scooter example, one approach is: - Estimate total city population - Segment by adults likely to use scooters - Estimate the fraction who use scooters daily - Multiply by likely average rides per user per day
Choosing a familiar, logical structure reduces cognitive load and reduces the risk of missing key steps.
Make explicit, reasonable assumptions
Interviewers expect you to invent plausible numbers, but each assumption should be stated clearly and justified if possible. For example, if you assume a city population of 500,000, state why: perhaps you’re modeling a city similar to Atlanta or Sacramento.
For segments, clarify your thinking: if you estimate 60% of residents are adults, explain your reasoning. Don’t just say 'let’s assume 20% use scooters'—give a rationale, such as 'based on urban density and public transit use, I’ll assume 20% of adults try scooters at least once a month.'
Worked example: Estimating daily scooter rentals
Let’s walk through the electric scooter example fully, making and explaining each assumption:
Assumptions: - City population: 500,000 (modeled after a mid-sized US city) - Adults (18-65): 60% = 300,000 - Urban dwellers more likely to use scooters: assume 70% of adults = 210,000 - Fraction who have tried scooters in the last month: 20% = 42,000 - Fraction who use them daily: 10% of those = 4,200 - Average rides per daily user: 1.5 (assume some round trips)
Calculation: - Daily users: 4,200 - Total rides: 4,200 x 1.5 = 6,300 rides per day
Competing approach: Instead of focusing on daily users, you could estimate based on total scooter fleet size and utilization, e.g., city has 2,000 scooters, each used 3 times/day = 6,000 rides. Both approaches converge, which can be a useful cross-check.
Risk: If you overestimate the proportion of daily riders, you may overshoot the total. To validate, you could check against public data from similar cities or news reports. If you found evidence that the average is only 2,000 rides/day, you’d revisit your user segmentation, perhaps lowering your estimate of daily users or average rides per user.
In real interviews, stating, 'If I saw reliable city reports showing only 2,000 rides/day, I would adjust my daily user assumption downward and recalculate,' demonstrates flexibility and self-correction.
Common weak reasoning and a stronger alternative
Weak reasoning: 'I think about 10% of the population uses scooters every day, so that’s 50,000 rides.' This skips segmentation, doesn’t explain why 10% is reasonable, and ignores ride frequency per user.
Stronger alternative: 'I’ll segment by age, focus on likely urban users, estimate how many have tried scooters recently, then estimate what fraction ride daily and how often.' This approach is transparent and easier to adjust if challenged.
Testing your estimates and knowing when to revise
After reaching an estimate, sense-check your answer. Does it seem plausible compared to known benchmarks, such as public transit ridership or similar city data? If your number is wildly higher or lower, revisit your key assumptions and see which one might be off.
In the scooter example, if the fleet size is only 500 scooters, your daily ride estimate probably needs to be lower. Always articulate what evidence would change your recommendation and be specific about what you’d do differently.
Build a sustainable practice routine
To make steady progress, aim for two or three guesstimate questions per week. Rotate through different domains (transportation, tech devices, retail, etc.) and occasionally revisit the same type of problem with new assumptions or decomposition methods.
After each session, review your steps: Did you clearly state all assumptions? Was your math correct? Did you reflect on alternative approaches and potential errors? Practicing with a peer or using tools like PMMockr can help, but solo practice with self-review is also effective if you’re deliberate.
Timed practice and self-review checklist
Set a timer for 10 minutes and answer: 'Estimate the number of cups of coffee sold each day in a city of 1 million people.' Write out every step, assumption, and calculation. When time’s up, review using this checklist: - Did I structure the problem clearly before calculating? - Did I state and justify each assumption? - Did I complete the math accurately? - Did I consider at least one alternative approach or cross-check? - Did I explain what evidence would make me revise my answer?
A realistic cadence is to do this exercise every few days, focusing on clarity and completeness, not just speed.
FAQ
How detailed do my assumptions need to be in a PM guesstimate?
Your assumptions should be stated explicitly and justified with real-world logic or a relatable analogy. You don’t need precise data, but each step should be clear enough that someone else could follow and challenge your reasoning.
What if my final estimate is way off from reality?
If you realize your answer is unrealistic, identify which step or assumption likely caused the error. Explain how you would adjust it and recalculate. Interviewers value your ability to self-correct and reason transparently.
Should I prioritize speed or completeness when practicing?
Focus on completeness and clarity first. Speed will improve with practice, but a rushed answer with unclear logic is less impressive than a slower, well-structured response.