What untrusted ERP data does to operations

Name the decision criteria

Examine the process delays, manual checks, conflicting definitions, and consumer workarounds created when ownership and data qualifications are unclear. Data quality becomes actionable when a consumer can see ownership, freshness, provenance, conflict policy, and known gaps. A copied record with no qualification often moves the uncertainty rather than resolving it. For What untrusted ERP data does to operations, the first useful artifact is a bounded statement of the consumer outcome, the current dependency, and the decision owned by data leader.

What must be explicit

Start with the two inputs shown in the decision aid: Focus: data quality and Audience: data leader. Then identify the system that remains authoritative, the consumer that relies on the result, and the exception that would make the design unsafe or misleading.

The expected scope output is A bounded problem and named owner. That output is specific enough for an owner to accept or reject. It also prevents data quality from becoming a label for unrelated work.

Compare the operating boundaries

Data quality becomes actionable when a consumer can see ownership, freshness, provenance, conflict policy, and known gaps. A copied record with no qualification often moves the uncertainty rather than resolving it. Cost management starts by naming variable and fixed drivers. Model usage, infrastructure, engineering, review, support, security, and customer acquisition behave differently as volume changes. The boundary for this review is governance operations, with cost management treated as the change under evaluation.

Review point	What to record for data quality
Consumer promise	The fields, operation, freshness, and failure behavior the consumer can rely on
Source authority	The system responsible for each material value or action
Qualification	The limits, provenance, policy, and exceptions that must remain visible
Change control	The owner, version rule, test evidence, and consumer notification path

A diagram is useful only when it makes these decisions inspectable. For What untrusted ERP data does to operations, reviewers should be able to follow a request from the consumer boundary to each dependency and back to the qualified result.

Record the tradeoff

The design is incomplete until a team owns access, change, failures, review evidence, and retirement. Governance becomes useful when policy is attached to the interface consumers use and when operators can see the source path, consumer, decision, and failure involved. Assign the operating decision to cto and use stable as the review condition captured in the article scenario.

In the review for What untrusted ERP data does to operations, the decision record should name access ownership, monitoring evidence, failure handling, and the retirement path. If one team owns the consumer contract while another owns a source dependency, the handoff and escalation path need to be written down. This matters most when the decision spans more than one system or consumer.

Questions for the design review

• Which consumer outcome makes data quality worth standardizing or governing?

• What material source difference would be hidden by the proposed governance operations boundary?

• Which evidence lets cto distinguish a contract failure from a source failure?

• When cost management changes again, which consumers should remain insulated and which must be notified?

• What condition would cause the team to reject this approach and choose a narrower design?

For What untrusted ERP data does to operations, a useful review can end with a qualified no. The aim is to make the decision, dependency, and ownership clear enough that another team can understand what was chosen and why.