A town parking product team is drafting a Product Vision. Which statement should the Product Owner prefer?
Select an answer to reveal the explanation.
Short Explanation
'Build an app' is a shopping list. 'Stop people circling the block' is a vision. The app, sensors, and QR codes might help — or a better curb policy might — but the outcome is what the town actually wants.
Full Explanation
A strong Product Vision for a town parking product describes the citizen outcome—reducing downtown congestion so residents can find and pay for a space without circling the block—rather than prescribing solutions. Native apps, QR codes, sensors, and a new payment vendor this fiscal year are solution choices that belong in backlog options, not vision. Twelve parking epics and a public dashboard before the next election are a delivery contract dressed as vision. A parking microservice platform other city apps can reuse is an architecture goal, not the resident job to be done. Exam caveat: prefer outcome language over solution or project lists when selecting vision statements on PSPO II. Operational check: test candidate vision sentences by asking whether they help say no to popular but off-outcome ideas; keep the congestion and find-and-pay outcome, and evaluate QR, sensors, and platforms as ordered backlog experiments inspected at Sprint Review. Outcome-oriented parking vision enables saying no to fashionable sensors and vendors that do not reduce circling or payment friction. Evaluate those technologies as backlog experiments measured against congestion and find-and-pay outcomes, not as vision text.