A new mayor wants the 311 Product Vision rewritten every week to match that week's press cycle. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Rewriting vision every press cycle is like changing the destination city every Monday because a new billboard went up. Teams need a hill they can actually climb. Change the vision when the evidence changes — not when the podium does.
Full Explanation
A 311 Product Vision must be stable enough for focus; changing it every week to match a mayor's press cycle destroys shared understanding and turns strategy into messaging. The Product Owner should change the vision only when evidence shows the environment shifted, not when the news cycle shifts. Adopting weekly rewrites for political alignment makes backlog ordering impossible. Freezing the vision permanently until the next election refuses legitimate evidence-based adaptation. Hiding the current vision from the mayor's office while the team uses old wording creates dual truths and fails transparency. Exam caveat: stability with evidence-based change beats both churn and permanent freeze. Operational check: document the evidence bar for vision change, brief the mayor on how press themes map to backlog communication without rewriting vision weekly, and update vision only when resident need or product environment measurably changes. 311 vision that chases weekly press cycles cannot order a backlog; evidence-based change is allowed, news-cycle churn is not. Offer the mayor messaging hooks tied to the stable vision instead of rewriting the vision to match each headline. Offer press-office talking points that map headlines to the stable 311 vision without rewriting the vision text each week, and log any vision change with the environmental evidence that justified it.