Davies Meyer – home
    AI3 min read

    Automated Decision-Making

    Automated decision-making means that a system makes decisions using data and rules or models. Examples include assigning a task or selecting an ad delivery. It differs from decision support, where a person meaningfully reviews a suggestion and makes their own decision.

    Automated Decision-Making explained

    Describe the decision first: what triggers it, which information does it need and what changes as a result? Even a simple rule can decide automatically; AI is not required. A model may help with ambiguous patterns but adds evaluation and operational requirements. Choose the approach according to the task and possible consequences.

    Set the scope of action. A media-budget allocation system, for example, needs spending limits, reliable inputs and a way to stop when anomalies occur. A proposed amount is not an executed change. Check whether the action actually occurred in the destination system and record the rule or model version used.

    Personal data can bring specific requirements. Article 22 GDPR concerns solely automated decisions with legal or similarly significant effects. Restrictions, legally specified exceptions and safeguards apply. A merely formal human confirmation does not replace meaningful review. Assess the actual use case before deployment.

    Creative Engineering connects the usable workflow with appropriate control. We take responsibility for the concept and quality. First test the logic on known cases and, where suitable, in suggestion mode. Compare correct decisions, errors and total effort. Executing an incorrect decision faster is not an improvement.

    Examples

    Hypothetical application

    A team wants to assign incoming requests to departments automatically. It first tests rules using previously handled requests. Clear cases are later assigned automatically, while ambiguous ones enter a shared review queue. The team checks misrouting and handling time; sorting does not decide whether the request is accepted or rejected.

    Key Points

    • Distinguish decision support from an executed decision.
    • Specify inputs, boundaries and exceptions.
    • Assess correctness and consequences alongside effort.

    Practical application

    Describe a concrete decision, its data and consequences. Test boundaries and exceptions, establish the required review and check the actions actually executed.

    Useful measures

    Decision quality

    Check correct decisions and consequential errors in context.

    Executed action

    Compare intended changes with those actually implemented.

    Consequences and effort

    Record error consequences, manual handling and ongoing operation.

    Common mistakes

    • Describing a suggestion system as an automation already taking action.
    • Allowing interventions without clear limits or traceable feedback.
    • Equating formal approval with independent review.

    Sources and context

    Frequently Asked Questions about Automated Decision-Making

    No. Defined if-then rules can also automate decisions. A learning model is one possible implementation.

    Loading related terms…

    All Terms