A housing-assistance Product Owner needs to estimate Unrealized Value beyond people who already finish applications. Which signals should they use?
Select an answer to reveal the explanation.
Short Explanation
Unrealized Value is the housing help people never got — the survey that says they never even tried, and the application they started and quit. Approved-applicant smiles are Current Value. Overtime and leftover roadmap items are busywork, not unmet demand.
Full Explanation
Unrealized Value is estimated from unmet needs and non-consumption, not from the happiness of people already served. For housing assistance, unmet-demand surveys and abandoned applications are direct UV signals: intended civic value that never occurred. The Product Owner should instrument non-user and abandonment evidence to size the UV gap beyond people who already finish applications.
Using only the satisfaction score of approved applicants confuses Current Value with Unrealized Value and invents no valid 'plus ten percent' rule. Developer overtime hours are an Ability to Innovate or cost smell, not unmet demand. The count of roadmap features not yet started is an output wish list, not evidence of resident need. Housing help the public never received is the Unrealized Value gap a Product Owner must size before celebrating the served.
Exam caveat: PSPO II Unrealized Value distractors often swap CV of served users, team effort, or unstarted features for true non-consumption signals.
Operational check: quantify abandoned housing applications and survey non-applicants about barriers; put those UV figures next to approved-applicant satisfaction before ordering the next backlog slice.