A public-health records compliance officer insists the Product Vision should be 'be compliant.' How should the Product Owner reframe it?
Select an answer to reveal the explanation.
Short Explanation
'Be compliant' is the speed limit, not the road trip. You still need a destination — healthier residents, records they can actually use. Rules constrain the drive; they are not why the car exists.
Full Explanation
Compliance and regulation typically constrain how value is delivered; they rarely constitute a complete Product Vision. A vision of 'be compliant' does not tell the Scrum Team which citizen outcomes to maximize when two compliant options differ in value. The Product Owner should keep a citizen-value vision and make compliance an explicit constraint, often through Done, risk items, and non-negotiable backlog work. Separating compliance into a second product usually fragments accountability.