At a glance
What you need to know.
To make ownership, permitted use and correction of important records enforceable, start with a complete business journey and its operating constraint. This guide examines a shared identity and integration capability, then connects the design choice to an observable result. The walkthrough is illustrative guidance; targets, access and readiness must be established for the actual system.
Start with a shared identity and integration capability
Enterprise architecture can centralize identity and integration controls while several business capabilities remain independently owned. Identify the shared failure domains and policy authority. A gateway may enforce a common entry rule, but individual services still need record-level authorization and useful readiness checks. Inventory all consumers and their availability needs before changing the shared layer. Define an exception process that can be reviewed and retired. Centralization should simplify an enforceable control rather than force every business change through an unowned queue.
Enterprise scale introduces policy variation, shared infrastructure and many consumers with different priorities. Name an accountable owner for the business journey and separate local decisions from organization-wide controls. Inventory consuming teams before changing a contract. A centrally approved design still needs evidence that each intended role can complete its task. Use explicit exceptions for business units with a different requirement instead of forcing silent workarounds or multiplying nearly identical implementations without support ownership.
Choose the enterprise architecture boundary that changes the result
Make authoritative entities and permitted consumers visible in the architecture. A customer master, local projection and analytical dataset have different write and freshness responsibilities. Define the contract for corrections, schema changes and deletion across those boundaries. Avoid treating a shared database as an agreement about ownership; direct access can bypass the capability's business rules. Use traceable transformation versions and consumer inventories for important outputs. Architecture should make a governance rule enforceable in the running system, rather than merely annotate a diagram with a policy name.
Resolve the decision within this operating context
Choose the authority for records shared across business units and define the rights of local projections. Name the owner of policy exceptions and the consumer inventory for each important dataset. Verify a correction, access change and deletion request across the relevant boundaries. A global label or catalogue does not settle disagreement about meaning. Decide whether a field is genuinely common or represents separate local concepts that require a documented mapping.
Illustrative walkthrough and failure case
Trace the identifiers, source versions and approved consumers for a business capability consuming the shared identity authority. Choose which shared controls must be synchronous and which approved data can be safely projected with a documented freshness bound. Test a restricted role and a later correction across the relevant output copies. Keep disputed ownership visible until the accountable owner resolves it instead of treating a merged view as automatic agreement.
The shared authority becomes slow and every service retries aggressively. Allocate timeout and retry budgets, stop unsafe writes when authority cannot be confirmed and test the resulting degradation across consumers.
Define the acceptance metric before the pilot
Select the records that affect a real decision and identify their authoritative source, owner, approved consumers and retention rule. Measure unresolved ownership, rejected records, stale inputs and access exceptions using documented definitions. Count verified lineage coverage for the selected dataset rather than every field in the estate. A catalogue entry alone does not prove that a server enforces access or that derived copies honor deletion. Review governance with the people who create, correct and use the data so controls match actual workflows.
Test a permitted reader, an unauthorized reader, a correction and a retention or deletion request across the source and relevant derived copies. Verify API, export and background-job access in addition to the main interface. Sample the lineage from an output back to its source version and transformation. Record exceptions with an accountable owner and a resolution rule. Acceptance requires observable enforcement and usable correction procedures; assigning a steward in a spreadsheet is the beginning of governance, not the complete result.
Release a supported change and retain ownership
Record the decision, its assumptions, accepted tradeoffs and the owner responsible for revisiting it. Version the affected contract and identify consumers before rollout. Use a compatibility period or controlled cutover that the operating teams can rehearse. Review the actual deployed diagram, permissions and recovery paths after release. Architecture governance is useful when it helps a team make and maintain a decision; a reference diagram without ownership, migration evidence and an operating procedure cannot establish that the business capability is ready.
Before you start.
- Who owns the record and which derived copies must honor a correction?
- Choose which shared controls must be synchronous and which approved data can be safely projected with a documented freshness bound.
- Which restricted role, correction and dependency failure belong in acceptance?
- Who owns unfinished work and reconciliation during the pilot?
- Which baseline, workload assumptions and stop condition are recorded?
Common questions.
How should we measure improving data governance?
Begin with one decision-critical dataset. Document ownership, permitted use, lineage, access and correction, then test those rules across its consumers. A larger catalogue is useful when it helps maintain those controls, but catalogue size is not a governance outcome by itself.
What should the first pilot cover for a shared identity and integration capability?
Use one bounded journey involving a business capability consuming the shared identity authority, with its actual authority, source records and operating owner. Choose which shared controls must be synchronous and which approved data can be safely projected with a documented freshness bound. Include the failure case and confirm accepted destination state before expanding. A successful screen or resource-creation receipt is evidence of that stage, not proof that the full journey is ready.