The city publishes an OKR to cut childhood vaccination gaps by 15 percent. The Product Owner of the public-health clinic portal is asked to support the OKR with more portal features. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A city OKR is the scoreboard; a product hypothesis is the play you think might move the score. Slapping vaccination gap on every ticket is decoration. Pick a few portal bets you can actually test against that number.
Full Explanation
Organizational OKRs do not automatically become Product Backlog items. The Product Owner should form product-level hypotheses—changes the clinic portal could make that might move the vaccination-gap OKR—and inspect evidence. Labeling existing work, forcing the OKR into a Sprint Goal, or substituting the city metric for a product goal all create strategy theater. Hypotheses keep the connection between product bets and city strategy empirical.