Skip to content
RED SAGSkills

Product Management interview questions and answers

Product management questions test how you decide what to build: discovery, prioritisation, metrics and strategy.

Below are 60 Product Management questions with the correct answer and a short explanation, grouped from fresher to experienced level. Try each one before you open the answer.

What Product Management interviews usually check

  • ✓Product discovery and customer problems
  • ✓Prioritisation frameworks
  • ✓Roadmaps and strategy
  • ✓Metrics and success measures
  • ✓Working with engineering and design

Product Management interview questions for freshers easy

1. A good problem statement

Which is the best problem statement to start discovery with?

  1. A.We need to build a dark mode
  2. B.Our app should have more features than competitors
  3. C.Small shop owners spend about 3 hours a week matching payments to invoices by hand, which delays their month-end close
  4. D.Users want AI
Show answer

Answer: C. Small shop owners spend about 3 hours a week matching payments to invoices by hand, which delays their month-end close

A good problem statement names who has the problem, what the problem is and why it matters, without choosing a solution. Starting with a solution limits the team's thinking and skips the question of whether it is worth solving.

2. A Kano must-be feature

For a food delivery app, which is most likely a Kano must-be (basic) feature?

  1. A.Animated stickers in the order chat
  2. B.Being able to pay securely for the order
  3. C.A surprise free dessert on birthdays
  4. D.Choosing a theme colour for the app
Show answer

Answer: B. Being able to pay securely for the order

Must-be features are expected. Users do not praise them, but they are very unhappy if they are missing. Secure payment is basic; surprises and stickers are more likely attractive or indifferent.

3. A Kano indifferent feature

In a Kano survey, most users say they do not care whether a feature exists or not. Which category is it?

  1. A.Performance
  2. B.Must-be
  3. C.Indifferent
  4. D.Attractive
Show answer

Answer: C. Indifferent

Indifferent features do not change satisfaction either way. Building them uses effort without making users happier, so they are usually low priority unless they serve another goal like compliance.

4. Roadmap columns without dates

What is the main idea of a Now / Next / Later roadmap?

  1. A.Rank engineers by how fast they work
  2. B.Show order and confidence without fixed dates
  3. C.List exact release dates for every feature
  4. D.Show only the work finished last year
Show answer

Answer: B. Show order and confidence without fixed dates

Items in "Now" are in progress and well understood; "Next" and "Later" are less certain. Avoiding firm dates for far-off work keeps the roadmap honest and easy to change as priorities shift.

5. Technical debt

What is technical debt?

  1. A.The number of bugs reported by users
  2. B.Money the company owes to software vendors
  3. C.The future cost of shortcuts taken in code or design
  4. D.The salary cost of the engineering team
Show answer

Answer: C. The future cost of shortcuts taken in code or design

Technical debt is the extra work that builds up when quicker but weaker solutions are chosen. Like financial debt it charges "interest" in slower changes and more bugs, so it needs planned repayment.

6. Tasks on the critical path

In project planning, why do tasks on the critical path get extra attention?

  1. A.They are always the cheapest tasks
  2. B.They need no testing
  3. C.Any delay to them delays the whole project
  4. D.They can be done in any order
Show answer

Answer: C. Any delay to them delays the whole project

The critical path is the longest chain of dependent tasks. It sets the earliest finish date, so a slip there moves the end date. Other tasks have some slack.

7. Only picking easy items

A team keeps choosing easy items because they finish fast. What is the risk over time?

  1. A.Important, harder problems never get solved
  2. B.Easy items always have the highest value
  3. C.Velocity will drop at once
  4. D.The team will run out of easy items next week
Show answer

Answer: A. Important, harder problems never get solved

Easy wins are useful, but if they are all a team does, the big problems stay unsolved. Balance quick wins with work that moves key goals, even if it is harder.

8. A payment bug and a typo

Two bugs are reported: customers cannot pay by card, and a help page has a spelling mistake. Which should be fixed first?

  1. A.Whichever was reported first
  2. B.The spelling mistake
  3. C.The card payment bug
  4. D.Whichever is easier to fix
Show answer

Answer: C. The card payment bug

A broken payment stops revenue and hurts trust right away, so its cost of delay is very high. A typo on a help page is minor. Order by impact, not by report time or ease.

9. Prioritisation is never one-off

Why is prioritisation treated as an ongoing activity rather than a one-time exercise?

  1. A.Priorities are set by law once a year
  2. B.Once ranked, items can never move
  3. C.Goals, data and the market keep changing
  4. D.Teams must reprioritise every hour
Show answer

Answer: C. Goals, data and the market keep changing

New evidence, customer feedback, competitor moves and results from shipped work change the value of items. Regular reviews keep the order matched to current facts without constant churn.

10. The four big product risks

Marty Cagan groups the risks a product idea faces into four types that discovery should reduce before building. Which list is correct?

  1. A.Value, usability, feasibility and business viability
  2. B.Scope, budget, schedule, quality and overall team capacity
  3. C.Design, coding, testing, release and support
  4. D.Brand, legal, hiring and investor funding
Show answer

Answer: A. Value, usability, feasibility and business viability

Value asks whether people will buy or use it, usability whether they can figure it out, feasibility whether the team can build it, and viability whether it works for the business (legal, finance, sales). Scope, budget and schedule are project risks, not product risks.

11. A hypothesis you cannot check

A teammate writes the hypothesis: "Users will love the new dashboard." What is the main thing missing?

  1. A.A list of every feature that the new dashboard will include
  2. B.The name of the designer who created the dashboard
  3. C.A full launch plan with dates for every market
  4. D.A measurable signal that would show it is true or false
Show answer

Answer: D. A measurable signal that would show it is true or false

A testable hypothesis states the expected change in observable behaviour, for example "at least 30% of weekly users open the dashboard twice in the first two weeks". Without a measure and a threshold, any result can be read as success.

12. Length of a design sprint

The design sprint process made popular by Google Ventures takes a team from problem to tested prototype in how long?

  1. A.One afternoon
  2. B.Five days
  3. C.Three months
  4. D.Two years
Show answer

Answer: B. Five days

The classic sprint runs Monday to Friday: map the problem, sketch solutions, decide, build a realistic prototype, and test it with about five customers. Some teams now use a compressed four-day version.

13. The two axes of an assumption map

In assumption mapping, the team places each assumption on a 2×2 grid. What are the two axes?

  1. A.How costly it is to build, and who suggested it
  2. B.How old the idea is, and how many people like it
  3. C.How important it is, and how much evidence you have
  4. D.How hard it is to explain, and how long it takes
Show answer

Answer: C. How important it is, and how much evidence you have

Assumptions that are important and have little evidence are the "leap of faith" ones to test first. Unimportant ones, or ones already backed by good evidence, can wait. The map turns a long list of beliefs into a testing plan.

14. Objective or key result

In OKRs, how do objectives and key results differ?

  1. A.The objective is a number; key results are tasks the team will do
  2. B.They are the same thing written in two different styles
  3. C.The objective is a qualitative goal; key results are measurable signs of reaching it
  4. D.Key results are always set by leadership, and objectives are set by each individual team member
Show answer

Answer: C. The objective is a qualitative goal; key results are measurable signs of reaching it

An objective states what you want to achieve in inspiring words, for example "Make first-time filing effortless". Key results are two to five measurable outcomes that show whether you got there, such as "Raise first-session filing completion from 40% to 60%".

15. How a marketplace earns

A food delivery platform keeps a percentage of each order's value from the restaurant. What is this revenue model usually called?

  1. A.A seat-based subscription model
  2. B.An advertising-only model
  3. C.A take rate (commission) model
  4. D.A one-time licence model
Show answer

Answer: C. A take rate (commission) model

Marketplaces often earn a take rate, a share of the gross merchandise value (GMV) that flows through them. Many add other streams, such as ads, delivery fees or subscriptions, on top of the commission.

16. A data protection law in PESTLE

In a PESTLE scan for India, where does the Digital Personal Data Protection Act most clearly fit?

  1. A.Social
  2. B.Technological
  3. C.Legal
  4. D.Environmental
Show answer

Answer: C. Legal

PESTLE stands for Political, Economic, Social, Technological, Legal and Environmental. A specific data protection law that sets rules for collecting and using personal data is a legal factor.

17. Blue ocean strategy

What does a "blue ocean" strategy aim to do?

  1. A.Beat rivals on price in a crowded, established market
  2. B.Copy the market leader's features faster than anyone
  3. C.Create new demand where competition is not yet relevant
  4. D.Sell only to government buyers who face no rivals
Show answer

Answer: C. Create new demand where competition is not yet relevant

Blue ocean strategy means creating uncontested market space, often by combining value elements in a new way, so the old competition matters less. A "red ocean" is an existing market where firms fight over the same demand.

18. A good discovery question

Which question is the best open-ended discovery question?

  1. A."Do you use Excel for your month-end reporting?"
  2. B."Would you like a 20% discount if you sign now?"
  3. C."How does your team handle month-end reporting today?"
  4. D."Can I send you our brochure and price list?"
Show answer

Answer: C. "How does your team handle month-end reporting today?"

Open-ended questions invite the buyer to explain their situation in their own words, which reveals problems and priorities. Yes/no questions give little detail. Good discovery uncovers what matters before you present a solution.

19. What they tried before

Why is 'What have you already tried to fix this?' a useful discovery question?

  1. A.It tells you which competitor to criticise during the demo next week
  2. B.It lets you skip the questions about their problem
  3. C.It shows the buyer that you already know the answer
  4. D.It shows past attempts, why they failed and what to avoid
Show answer

Answer: D. It shows past attempts, why they failed and what to avoid

Past attempts reveal how serious the problem is, what the buyer has learned and what they distrust. You can then position your approach against what did not work. It also avoids pitching something they already rejected.

20. Spot a problem question

Which of these is a problem question in the SPIN model?

  1. A.Which accounting software do you use today?
  2. B.How many people are in your finance team?
  3. C.Are you happy with how long month-end closing takes?
  4. D.Would faster closing help you report to the board?
Show answer

Answer: C. Are you happy with how long month-end closing takes?

Problem questions probe difficulties, dissatisfaction or gaps with the current way of working. Asking about software or team size gathers situation facts, and the last one is a need-payoff question. Problem questions open the door to deeper implication questions.

Product Management intermediate interview questions medium

21. Talking to customers every week

A product trio sets a habit of interviewing at least one customer every week. What is the main benefit compared with one big study per year?

  1. A.Decisions stay informed by fresh, ongoing customer input
  2. B.It makes large studies completely unnecessary
  3. C.It ensures every result is statistically significant
  4. D.It lets the team skip writing notes
Show answer

Answer: A. Decisions stay informed by fresh, ongoing customer input

Continuous discovery keeps learning close to decisions, so assumptions are tested as they arise. Big studies still have a place for deep or broad questions, but small, regular contact prevents long gaps where the team guesses.

22. Working out ICE scores

Your team scores ideas with ICE = Impact x Confidence x Ease (each 1 to 10). A: 8, 6, 5. B: 6, 9, 6. C: 9, 4, 7. D: 7, 7, 4. Which idea ranks first?

  1. A.B, with 324
  2. B.C, with 252
  3. C.A, with 240
  4. D.D, with 196
Show answer

Answer: A. B, with 324

A = 240, B = 324, C = 252 and D = 196. B is not the most impactful, but high confidence and ease lift it. ICE is fast but subjective, so agree on what each score means before comparing.

23. How big a launch

Your team ships about 20 changes a month, from small fixes to a major new product. How should you handle go-to-market for them?

  1. A.Give every change a full press release and event
  2. B.Never announce anything
  3. C.Use launch tiers: big launches get full marketing, sales training and press; medium ones get blog posts and in-app notes; small ones go in the changelog
  4. D.Let each engineer decide how to announce their change
Show answer

Answer: C. Use launch tiers: big launches get full marketing, sales training and press; medium ones get blog posts and in-app notes; small ones go in the changelog

Tiering matches effort to impact, so marketing and sales can focus on what matters. It also keeps customers informed without flooding them with noise.

24. GMV or revenue

A travel marketplace processed ₹200 crore of bookings and kept ₹18 crore in commissions. In its financial statements, what is its revenue usually reported as (when it acts as an agent)?

  1. A.₹200 crore
  2. B.₹18 crore
  3. C.₹218 crore
  4. D.₹182 crore
Show answer

Answer: B. ₹18 crore

When a marketplace acts as an agent, it reports its commission as revenue, not the full booking value. GMV (₹200 crore) shows scale, but calling it revenue would mislead investors about the size of the business.

25. Ranking jobs by WSJF

Using WSJF = cost of delay / job size, which job should go first?

Job   Cost of delay   Job size
A     21              13
B     13               3
C      8               8
  1. A.A, with WSJF about 1.6
  2. B.B, with WSJF about 4.3
  3. C.C, because its numbers are equal
  4. D.A, with the highest cost of delay
Show answer

Answer: B. B, with WSJF about 4.3

WSJF: A = 21 / 13 ≈ 1.6, B = 13 / 3 ≈ 4.3, C = 8 / 8 = 1. B goes first because it delivers a lot of value per unit of time. Highest cost of delay alone is not the answer.

26. Confidence for a hunch

A PM has a strong hunch about an idea but no data, research or tests. Which confidence level is most honest in RICE?

  1. A.50% or lower
  2. B.It should be left blank
  3. C.80%
  4. D.100%
Show answer

Answer: A. 50% or lower

Intercom's guidance is 100% for strong evidence, 80% for some support and 50% for low confidence; anything below is a "moonshot". A hunch with no evidence belongs at the low end.

27. Shrinking a job to raise WSJF

A job has cost of delay 20 and size 8 (WSJF 2.5). A thin first slice keeps cost of delay 16 with size 3. What is the slice's WSJF?

  1. A.About 5.3
  2. B.2.5
  3. C.About 6.7
  4. D.2.0
Show answer

Answer: A. About 5.3

16 / 3 ≈ 5.3, more than double the full job. Splitting out the most valuable slice lets it ship sooner, and the rest can be scored again on its own.

28. Splitting capacity into buckets

A team splits capacity 70% core improvements, 20% new bets and 10% experiments. What is the main benefit?

  1. A.It removes the need to prioritise inside buckets
  2. B.It ensures all bets succeed
  3. C.It protects time for each type of work
  4. D.It means stakeholders never disagree
Show answer

Answer: C. It protects time for each type of work

Without buckets, urgent core work often eats everything. Fixed shares keep room for innovation and tech health. Inside each bucket, items are still ranked with a method that fits that type.

29. Fixing a leading question

Which is the best rewrite of the leading question "Don't you find bank reconciliation frustrating?"

  1. A."How frustrating is reconciliation, on a scale of 1 to 10?"
  2. B."Would a tool that automates reconciliation help you?"
  3. C."Walk me through the last time you reconciled your bank account."
  4. D."Most people hate reconciliation. Do you?"
Show answer

Answer: C. "Walk me through the last time you reconciled your bank account."

The rewrite asks for a neutral, concrete story and lets the participant show whether frustration exists. A 1–10 scale still assumes frustration, the "would a tool help" question is hypothetical and pitches a solution, and the last one adds social pressure.

30. A feature that annoys

In a Kano survey, most users of a meditation app say they would be dissatisfied if it had a public leaderboard and satisfied if it did not. How is the leaderboard classified?

  1. A.Reverse
  2. B.Attractive
  3. C.Must-be
  4. D.Performance
Show answer

Answer: A. Reverse

A reverse feature is one whose presence lowers satisfaction for a segment. Kano surveys pair a functional question ("if it had X") with a dysfunctional one ("if it did not have X") to reveal this, which a simple "do you want X?" survey would miss.

31. Calculating an opportunity score

Outcome-driven innovation scores an opportunity as importance + max(importance − satisfaction, 0), using 1–10 ratings. An outcome has importance 9 and satisfaction 3. What is its score?

  1. A.12
  2. B.6
  3. C.27
  4. D.15
Show answer

Answer: D. 15

The gap is 9 − 3 = 6, so the score is 9 + 6 = 15. Scores above about 10 suggest under-served needs worth pursuing. If satisfaction exceeded importance, the gap term would be 0.

32. Sizing a market from the bottom up

There are about 2,00,000 small clinics in India. You can realistically serve the 30% in the cities you cover, and you charge ₹24,000 a year. What is your serviceable market (SAM) per year?

  1. A.₹480 crore
  2. B.₹14.4 crore
  3. C.₹144 crore
  4. D.₹1,440 crore
Show answer

Answer: C. ₹144 crore

Serviceable clinics are 2,00,000 × 30% = 60,000. Revenue is 60,000 × ₹24,000 = ₹1,44,00,00,000, which is ₹144 crore. ₹480 crore would be the total market across all clinics.

33. Top-down or bottom-up sizing

Why do investors and leaders usually trust a bottom-up market size more than a top-down one?

  1. A.It always gives a bigger number to show investors
  2. B.It is built from countable customers and real prices
  3. C.It comes from published industry reports
  4. D.It avoids having to choose a target segment
Show answer

Answer: B. It is built from countable customers and real prices

Bottom-up sizing multiplies the number of reachable customers by what they would actually pay, which forces you to state assumptions you can check. Top-down figures ("1% of a huge market") hide those assumptions.

34. Working out an ICE score

Using ICE scoring where each factor is rated 1–10 and multiplied, an idea has impact 8, confidence 5 and ease 6. What is its score?

  1. A.19
  2. B.240
  3. C.48
  4. D.400
Show answer

Answer: B. 240

ICE = impact × confidence × ease = 8 × 5 × 6 = 240. Some teams average the three instead (6.3 here), so always state the method. ICE is quick, but subjective ratings make it easy to bias.

35. Organising a roadmap by theme

Why do many product teams organise roadmaps around themes such as "Faster month-end close" instead of feature lists?

  1. A.Themes keep focus on problems while leaving room to choose solutions
  2. B.Themes allow the team to avoid setting any priorities or making trade-offs at all
  3. C.Feature lists are not allowed in agile frameworks
  4. D.Themes make the roadmap longer and more detailed
Show answer

Answer: A. Themes keep focus on problems while leaving room to choose solutions

A theme names a customer problem or goal. It aligns stakeholders on why work matters, while the team keeps freedom to discover the best features. Feature lists lock in solutions before they are validated.

36. An integration that brings customers

A small expense app builds a deep integration with a widely used Indian accounting software and gets listed in its marketplace. Strategically, what is the main benefit?

  1. A.It removes the need for any marketing at all
  2. B.It taps a large existing customer base and fits their workflow
  3. C.It makes the expense app the owner of the accounting data
  4. D.It guarantees the partner will never build a rival feature
Show answer

Answer: B. It taps a large existing customer base and fits their workflow

Integrations with popular platforms can be a powerful distribution channel, because they meet customers inside tools they already use. The risk is dependence: the partner may change terms or build the feature themselves.

37. Why the backlog is ordered

Why is a product backlog kept as an ordered list rather than grouped as "high, medium, low"?

  1. A.Groups make the backlog too short to read
  2. B.Ordering is needed only for tooling reasons
  3. C.High, medium and low are not allowed in Scrum
  4. D.A single order forces clear choices about what comes next
Show answer

Answer: D. A single order forces clear choices about what comes next

With priority buckets, most items end up "high" and the team still has to guess. An ordered list means item 1 beats item 2, which forces trade-off discussions and tells the team exactly what to pull next.

38. Choosing from an audit list

An audit lists 120 issues. The dev team has two days a month for SEO. How should you order the work?

  1. A.High impact and low effort first, then bigger projects
  2. B.Fix issues in the order the tool listed them
  3. C.Start with the lowest-impact items as warm-up
  4. D.Fix every warning before any errors
Show answer

Answer: A. High impact and low effort first, then bigger projects

An impact vs effort view puts quick wins, like a broken canonical template, first and schedules big, valuable projects next. Many tool warnings have little impact and can wait. This builds momentum and trust with developers.

39. Predicting a rival's response

Before cutting your price, you want to predict how the market leader will react. What should you study most?

  1. A.Their goals, past reactions and how much the segment matters
  2. B.Their logo, brand colours and recent ad designs
  3. C.The number of employees listed on their website
  4. D.Only their founder's posts on social media
Show answer

Answer: A. Their goals, past reactions and how much the segment matters

Competitor response profiling looks at a rival's objectives, assumptions, capabilities and history of reacting. A leader that depends on that segment and has matched prices before is likely to retaliate, which could start a price war.

40. Symptom or root cause?

A store manager says, 'Our staff are always rushing at closing time.' What should a consultative rep do next?

  1. A.Ask what causes the rush and what it leads to
  2. B.Pitch the staff scheduling module straight away
  3. C.Offer a discount on the full suite
  4. D.Agree and move to the next topic
Show answer

Answer: A. Ask what causes the rush and what it leads to

The first thing a buyer says is often a symptom, not the real problem. Asking 'why' and 'what happens then' uncovers the root cause and its business cost. The solution you propose should fix the cause.

Product Management interview questions for experienced candidates hard

41. Time criticality near a deadline

In SAFe, cost of delay = user-business value + time criticality + risk reduction or opportunity enablement. A compliance job has low business value but a regulator deadline in six weeks. What usually lifts its WSJF?

  1. A.A higher job size
  2. B.A high time criticality score
  3. C.Removing business value from the formula
  4. D.A lower risk reduction score
Show answer

Answer: B. A high time criticality score

Time criticality captures how value falls as time passes, such as fines after a deadline. As the date nears it rises, which pushes the job up the order even when user value is modest.

42. Big bets never get picked

A team always ranks by value / effort. A year later, they have shipped many small tweaks but no big strategic bets. What is a common fix?

  1. A.Set capacity buckets, such as a share for big bets
  2. B.Only allow items that take under a week
  3. C.Remove effort from the formula
  4. D.Pick items at random each sprint
Show answer

Answer: A. Set capacity buckets, such as a share for big bets

Ratio scoring favours small, low-risk items. Allocating capacity by investment type, such as core, growth bets and tech health, keeps some room for large bets judged against each other.

43. Improving a feature again

Version 1 of a faster checkout cut drop-off a lot. The team wants version 2 to make it faster still. What should they expect when scoring it?

  1. A.Higher impact, since users now trust it
  2. B.The same impact as version 1, for the same effort
  3. C.No impact, since checkout is solved
  4. D.Lower impact than version 1, due to diminishing returns
Show answer

Answer: D. Lower impact than version 1, due to diminishing returns

The easiest gains usually come first. The next step often costs more and moves the metric less. Re-estimate impact from current data, not from version 1's results.

44. Estimates are often off

History shows the team's big items take about 3 times longer than estimated, while small items are close. How should this change prioritisation?

  1. A.Ignore it since every team is wrong
  2. B.Only accept items estimated at under one day
  3. C.Triple every estimate, small or large
  4. D.Adjust big-item effort up, or split them smaller
Show answer

Answer: D. Adjust big-item effort up, or split them smaller

If large items are routinely underestimated, ratio scores favour them unfairly. Use history to adjust estimates for big work, or split large items so estimates become more reliable.

45. A forecast with a range

A Monte Carlo forecast based on past throughput says the 30 must-have items will finish by 15 June with 50% confidence and by 10 July with 85% confidence. The launch is fixed on 20 June. What should the PM do?

  1. A.Ignore the forecast since it is a model
  2. B.Ask the team to work weekends with no change
  3. C.Cut or re-rank scope to raise confidence for 20 June
  4. D.Tell everyone the work is done by 15 June
Show answer

Answer: C. Cut or re-rank scope to raise confidence for 20 June

A 50% date is a coin toss. To meet a fixed launch with reasonable confidence, reduce or re-order scope so the most important items finish first, and share the risk openly.

46. "It is just a small change"

A stakeholder says a request is "just a 10-minute change". Why should the PM still look at it carefully?

  1. A.Small changes are never worth doing
  2. B.Testing, review, support and upkeep add hidden cost
  3. C.The team should always say yes to small asks
  4. D.Small changes do not need any tracking
Show answer

Answer: B. Testing, review, support and upkeep add hidden cost

Code time is only part of the cost. Testing, review, release, docs, support and future upkeep add up, and many small asks can fill a sprint. Track them and judge them like other work.

47. A must-be item with no deadline

A Kano survey says reliable sync is a must-be feature, but its cost of delay looks low because users are not yet complaining. How should you read this?

  1. A.Kano and cost of delay must always agree
  2. B.Dissatisfaction may build quietly, so watch for churn
  3. C.Low complaints prove the feature is unimportant
  4. D.Must-be items never need prioritising
Show answer

Answer: B. Dissatisfaction may build quietly, so watch for churn

Users may not complain about expected features until they leave. Check churn reasons, reviews and support data for hidden cost of delay. Frameworks look at different sides and should be read together.

48. A test with no way to fail

A PM designs a test: "If anyone signs up, the idea is validated." Why is this a poor experiment?

  1. A.It does not include a large enough number of users
  2. B.Almost any result passes, so the team learns nothing
  3. C.It should measure page views instead of sign-ups
  4. D.Sign-ups are never a valid signal in discovery
Show answer

Answer: B. Almost any result passes, so the team learns nothing

A useful test must be able to fail. Set a threshold tied to what makes the idea worth pursuing, for example "at least 8% of targeted visitors join the waitlist", based on the economics you need. Otherwise the result simply confirms what the team wanted.

49. Marketing a feature everyone has

Your app's homepage still sells "Dark mode!" as its key differentiator. Interviews show every rival has it and users now just assume it. What does Kano analysis suggest?

  1. A.It is still a delighter, so promote it even more strongly in every campaign
  2. B.It is now a reverse feature, so remove it from the app
  3. C.It is indifferent, so stop maintaining it altogether
  4. D.It has become a basic; keep it but stop treating it as a differentiator
Show answer

Answer: D. It has become a basic; keep it but stop treating it as a differentiator

Once everyone offers a feature and users expect it, it no longer differentiates. Removing it would cause dissatisfaction, so keep it. Positioning should focus on attributes that still delight or that you perform clearly better on.

50. A real problem, but not worth solving

Interviews confirm that hotel owners find yearly fire-safety paperwork annoying. It takes them one hour a year, and they would not pay to avoid it. What is the right call?

  1. A.Deprioritise it: low frequency, low pain and no willingness to pay
  2. B.Build it right away, since the problem has been confirmed
  3. C.Run a large survey to prove the problem exists
  4. D.Build it as a free feature to drive sign-ups
Show answer

Answer: A. Deprioritise it: low frequency, low pain and no willingness to pay

A confirmed problem is not automatically worth solving. Weigh frequency, severity, current cost and willingness to pay. An hour of annual annoyance with no budget behind it rarely justifies a product, unless it unlocks something bigger.

51. Two segments, one roadmap slot

Interviews reveal two strong opportunities: freelancers want faster invoice payment, and agencies want team time tracking. You can pursue one this quarter. What should decide it?

  1. A.Which one best serves your target outcome and strategy
  2. B.Whichever opportunity came up in the most recent interview
  3. C.Whichever solution the engineers find more interesting
  4. D.Building half of each so neither segment feels left out
Show answer

Answer: A. Which one best serves your target outcome and strategy

Opportunity choice should follow the desired outcome and the company's target segment, then size, severity and your ability to win. Splitting effort across both usually delivers neither well, and recency or team interest are poor guides.

52. Stretch goals that are always met

A team rates every aspirational OKR at 1.0 for four quarters in a row. What does this most likely say?

  1. A.The team is the best in the company and needs no change
  2. B.The targets are not real stretches and should be set higher
  3. C.OKRs are working perfectly and need no review
  4. D.The scoring system is broken and should be dropped
Show answer

Answer: B. The targets are not real stretches and should be set higher

If moonshots are always hit, they are not moonshots. Either targets are sandbagged or the team is under-reaching. Leaders should review how targets are set, while making sure missing stretch goals is not punished, which causes sandbagging.

53. A rival copies your best feature

A larger competitor launches a near-copy of your flagship feature and offers it free. What is the strongest strategic response?

  1. A.Copy their entire product and also make yours free
  2. B.Drop the feature quickly, since a small company cannot win against a bigger rival
  3. C.Sue the competitor for copying the feature
  4. D.Double down on what is hard to copy, such as segment fit and relationships
Show answer

Answer: D. Double down on what is hard to copy, such as segment fit and relationships

Features are easy to copy; deep fit with a specific segment, data, integrations and trust are not. Talk to customers about what they value, strengthen those advantages, and price on value. A blind price war usually favours the bigger player.

54. Chasing every competitor feature

Sales keeps losing deals and asks for a "feature parity" roadmap that matches all 40 features of the market leader. What is the main risk?

  1. A.You become a weaker copy with no reason to choose you
  2. B.The roadmap will finish too quickly
  3. C.Customers always dislike products that have many features
  4. D.It makes positioning far too sharp
Show answer

Answer: A. You become a weaker copy with no reason to choose you

Matching every feature takes years, by which time the leader has moved on, and you end up an inferior clone. Find out which gaps actually cost deals, close the critical ones, and invest in differentiation for a segment where you can lead.

55. Cascading OKRs from the top

Leadership writes every team's key results and hands them down. Teams complain they have no say. What approach balances alignment and autonomy better?

  1. A.Leaders set company goals; teams propose OKRs that ladder up to them
  2. B.Leaders keep writing every key result for every team
  3. C.Each team sets any OKRs it likes, with no link to company goals
  4. D.Remove OKRs and let teams pick work each sprint
Show answer

Answer: A. Leaders set company goals; teams propose OKRs that ladder up to them

Alignment comes from shared company objectives; autonomy comes from letting teams decide how they will contribute. A two-way process, where teams draft OKRs that ladder up and negotiate with leaders, builds ownership and better plans.

56. "Everything is a must-have"

A department head says every one of 40 requirements is critical and refuses to rank them. What is an effective approach?

  1. A.Mark all 40 as must-have and plan for all of them
  2. B.Rank them yourself without telling the stakeholder at all
  3. C.Drop the stakeholder from the project
  4. D.Force trade-offs, such as ranking within half the budget
Show answer

Answer: D. Force trade-offs, such as ranking within half the budget

When everything is a priority, nothing is. Constraints such as "we can deliver 15 in the first release" force real choices. Forced ranking, buy-a-feature or linking each item to a business goal makes the trade-offs visible.

57. Is the SMB push worth it?

A proposed small-business segment has an average contract of $6,000 per year, 75% gross margin and a CAC of $9,000. What is the CAC payback period?

  1. A.18 months
  2. B.12 months
  3. C.24 months
  4. D.36 months
Show answer

Answer: C. 24 months

Annual gross margin = 6,000 x 0.75 = $4,500, or $375 per month. Payback = 9,000 / 375 = 24 months. Small customers often churn faster, so a 24-month payback is risky; a lower-cost motion such as self-serve, inside sales or partners is usually needed.

58. Signs your market is commoditising

Which pattern most strongly suggests your product category is becoming a commodity?

  1. A.Customers keep asking for more advanced, specialised features
  2. B.New premium brands enter the category and grow fast
  3. C.Switching costs between vendors rise year after year
  4. D.Buyers choose mainly on price and features look alike
Show answer

Answer: D. Buyers choose mainly on price and features look alike

Commoditisation shows up when products converge, buyers treat them as interchangeable and price drives choice, so margins fall. Responses include moving to services, building switching costs, niching or becoming the cost leader.

59. How durable is a licence moat?

Your fintech holds one of only a few payment licences in a market. How should you judge the durability of this advantage?

  1. A.Check how likely regulators are to open more licences
  2. B.Assume it is permanent, since licences are rare
  3. C.Ignore it, since licences never matter
  4. D.Judge it only by how much the licence cost
Show answer

Answer: A. Check how likely regulators are to open more licences

A regulatory moat lasts only as long as the rules stay the same. Regulators often open licensing to boost competition, as with new payment and digital bank licences in India and the Gulf. Use the window to build other moats like brand, data and switching costs.

60. "It's budget" — or is it?

A customer cancelling says, "It is just budget." Data shows they never finished onboarding and only 3 of 25 users are active. What is the best approach?

  1. A.Accept the reason and process the cancellation
  2. B.Offer a 50% discount right away
  3. C.Blame the customer for not onboarding
  4. D.Gently share what you see, ask whether lack of results made the budget hard to justify, and offer a focused plan to deliver value quickly, perhaps at a right-sized scope
Show answer

Answer: D. Gently share what you see, ask whether lack of results made the budget hard to justify, and offer a focused plan to deliver value quickly, perhaps at a right-sized scope

Budget is often the polite reason when value was never proven. Addressing the real cause, with data and a concrete short plan, may save the account or at least give honest learning. A blind discount does not fix low adoption.

Ready to test yourself?

Take a 15-question Product Management MCQ test with a score at the end, or practise the full Product Management question bank and earn points on the leaderboard.