The public-health department claims a huge records-overhaul project is required for compliance value, but much of the scope is gold-plating beyond the regulation. What should the Product Owner do first?

Compliance can be real value for public-health records, but it does not justify maximal gold-plated scope. The Product Owner should seek the smallest valuable compliant outcome first, then inspect whether more scope is still justified. Funding the entire overhaul as one release so auditors see maximum effort optimizes optics over learning and delays any compliant Increment. Converting the regulation into a multi-year project plan and pausing empiricism until it finishes recreates waterfall. Rejecting all compliance work because civic products should optimize only resident delight ignores real constraints that still apply inside a citizen-value vision. Exam caveat: minimal valuable compliance plus inspection beats gold-plated compliance projects. Operational check: extract the regulation's must-haves, deliver a Done compliant slice, review residual risk with compliance stakeholders, and only then order further records scope that still shows Unrealized Value. Minimal valuable compliance for health records beats gold-plated overhauls that pause empiricism; delight-only rejection of compliance is also wrong. Deliver the must-have Done slice, inspect residual risk, then decide whether more scope still pays.