A municipality wants MDM for every entity at once—parties, assets, vendors, employees, and more—before any domain is mastered. What sequencing guidance fits best?
Select an answer to reveal the explanation.
Short Explanation
Trying to master everything on day one is like renovating every city building in the same weekend—chaos wins. Pick a high-value domain such as parcels or locations, prove the pattern, then expand. Roadmaps beat ocean-boiling.
Full Explanation
Wanting MDM for every entity at once—parties, assets, vendors, employees, and more—before any domain is mastered should be tempered by sequencing high-value domains such as parcel/location first and avoiding boiling the ocean. Civic programs win by delivering usable masters in priority domains. Delaying all MDM until every source is rewritten to one vendor platform fails by coupling identity governance to an improbable mega-replacement. Starting only with rarely used reference codes while postponing party and location indefinitely fails prioritization against operational pain. Mastering every entity in one release so stewards never prioritize fails capacity and quality. Exam caveat: domain sequencing and prioritization beat enterprise-wide big-bang MDM. Operational check: rank domains by citizen impact and duplicate pain, charter the first domain with owners and metrics, deliver, then expand. Put the sequence in the municipal roadmap so sponsors cannot force an unstaffable all-entities go-live. 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.