A parks-recreation booking product is thriving as its own mobile app with a separate login. City strategy now requires one resident account across permitting, transit, and parks. Local usage looks strong, but the standalone login undermines the citywide channel. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A packed local diner is still a problem if the city is trying to run one kitchen. Parks bookings can look like a win while they wreck the one-account strategy. Surface the conflict upstairs instead of optimizing the side door.
Full Explanation
Local product success can conflict with enterprise strategy. A parks app that grows on a separate login may improve recreation metrics while blocking the city's unified resident channel. The Product Owner should make that strategic conflict visible to leaders rather than optimizing locally in silence. Ignoring the citywide account, chasing downloads, or handing strategy to a vendor leaves the organization with two incompatible bets.