Leaders want enterprise-wide governance in the first quarter across every dataset. What success factor should temper that plan?
Select an answer to reveal the explanation.
Short Explanation
Trying to govern the entire planet before lunch usually ends in a nap, not results. Pick one high-visibility domain, show a win, then grow. Scoped starts beat ocean-boiling every time.
Full Explanation
Enterprise-wide governance across every dataset in the first quarter is rarely realistic; success factors temper that plan by starting with one high-visibility priority domain, proving value, then expanding. Civic programs build credibility with visible operational wins before boiling the ocean. Attempting to cover every domain on day one so no one feels left out fails by diluting stewardship capacity and delivering shallow results everywhere. Skipping quick wins to wait for a complete multi-year tooling suite fails by delaying learning and sponsor confidence. Publishing hundreds of policies before selecting any pilot domain fails by creating unread rulebooks without operating proof. Exam caveat: pilot-then-scale is a standard governance success pattern on professional exams. Operational check: select a priority domain with clear pain (for example permitting party or parcel), define owners and a few standards, deliver a measurable improvement, then expand the charter. Report the pilot outcome to the city data council before funding the next wave so expansion is evidence-based, not slogan-based. Keep verification evidence with the municipal runbook so audits can prove the chosen control was applied as designed and that rejected alternatives would have left city services exposed to the failure modes described above.