Answering: “You started measuring product feature usage in your last release. You are surprised to learn that a sizable percentage of the features you thought were very important are never or rarely used.”

All four actions help explain why features you thought were important are rarely used. Talking to users, switching off unused features, running experiments and checking whether features solve the problem all produce evidence.

Exam Question

You started measuring product feature usage in your last release. You are surprised to learn that a sizable percentage of the features you thought were very important are never or rarely used.
Which of the following actions could you take to further evaluate this unexpected result?
(choose all that apply)
A. Spend more time talking to Users to identify the impact they seek.
B. Disable the features that have never been used and listen for feedback.
C. Run experiments to increase your understanding of what customers find valuable.
D. Examine whether the rarely used features solve the intended problem.

Correct Answer

A, B, C and D.

Why This Is the Correct Answer

Usage data showing that expected high-value features go unused is a signal that assumptions about value were wrong. The Product Owner’s next step is to learn why, using empiricism. Talking to users (A) uncovers the outcomes they actually want. Disabling unused features and listening for complaints (B) is a cheap test of whether anyone needs them, and it can also reduce maintenance cost. Running experiments (C) tests new ideas about what customers find valuable. Examining whether features solve the intended problem (D) checks whether the idea was sound but the build missed. Each option gathers evidence instead of relying on opinion.

Exam Tip

When a PSPO II question says “choose all that apply” and every option is a way to gather evidence, it is likely that all are correct. Watch for any option that relies on opinion alone.

Key Takeaways

• Unexpected usage data means your value assumptions need testing.
• Removing unused features is a valid experiment.
• Talking to users explains what the numbers cannot.