A city Product Owner for resident services can fund either a splashy parks-reservation skin or a shared resident identity-and-payments platform that would later unlock permit fees, transit passes, and clinic copays. Strategy wants several self-service outcomes next year. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Think of a city keycard that opens the pool, the permit desk, and the clinic—once. A shared identity-and-payments layer is that keycard: not flashy, but it unlocks a bunch of later doors. Strategy sometimes means sequencing the enabler that makes many outcomes cheap, not the prettiest single feature.
Full Explanation
Advanced Product Ownership includes sequencing enabling bets—shared capabilities such as identity and payments—when those capabilities unlock multiple strategic outcomes. Ordering a thin, releasable enabler first is a product-strategy choice: later permit, transit, and clinic flows ride the same platform instead of each inventing its own checkout. Cosmetic channel work and unrelated split products do not create that leverage, and freezing a capital feature list substitutes a project plan for empirical strategy.