A city's 'digital transformation' slogan is being used as the Product Vision for a resident-services portal. What should the Product Owner put in a usable Product Vision?
Select an answer to reveal the explanation.
Short Explanation
'Digital transformation' is a bumper sticker, not a vision. A real vision names who you are helping and what gets better — fewer midnight trips to city hall, faster benefit decisions. If the audience and the outcome are missing, the team is just decorating a slogan.
Full Explanation
A usable Product Vision for a resident-services portal states who the product is for and what change in citizen outcomes would count as success. A city's digital transformation slogan is branding, not vision: it does not guide backlog trade-offs. Listing platforms, vendors, and departments to be transformed in the next budget cycle describes a technology program, not citizen outcomes. A three-year Gantt of every digital project the CIO has funded is a portfolio schedule, not a Product Vision. A slogan-refresh workshop that makes the same buzzwords sound newer still fails to define users and success. Exam caveat: PSPO II expects visions that enable ordering decisions, not slogans or solution laundry lists. Operational check: rewrite the vision to name primary resident personas and the measurable life or service change that would mean the portal succeeded, then test whether backlog debates can be resolved by referring to that statement during refinement. Resident-services vision must name who benefits and what success looks like so backlog debates have a filter; transformation slogans do not. After rewriting, test the vision by using it to reject at least one popular but off-outcome request in refinement.