Human judgment is infrastructure: Incorporating responsible AI into actual work environments.

Responsible AI is not simply about having accurate prompts. Human judgment, verified sources, provenance, approval boundaries and accountable workflows are essential components of responsible AI in real world applications.

Human judgment is infrastructure: Incorporating responsible AI into actual work environments. — abstract systems diagram by Free the Line

AI is capable of conducting research, summarizing, classifying, drafting, comparing, analyzing, and generating rapidly. This rapid capability presents an enormous opportunity.

However, it also enables organizations to produce polished errors, distribute unreliable data, and automate incorrectly understood decisions at a pace never seen before. Responsible AI isn't simply a disclaimer at the bottom of the screen; it must be built into the system surrounding the technology. The system includes trustworthy data, defined responsibilities, transparent data sources, approval processes, recovery mechanisms, and individuals who comprehend the goal of their work. Human judgment is not an obstacle preventing AI from achieving efficiency. It is an integral component of the system's infrastructure. An AI system can create a response, but it cannot assume responsibility for what occurs after that response is utilized. The AI system doesn't manage the client relationship. It doesn't encounter the ramifications of publishing a false assertion. It cannot be professionally responsible for a negative recommendation, an ill-advised message, a broken promise, or a decision based on incomplete data. An individual or entity bears the responsibility. That responsibility cannot be eliminated by stating that AI produced the outcome. An organization selects the tool, provides its data, establishes its role, publishes or utilizes its output, then the organization is accountable for its decision.

As a result, responsible implementation of AI commences with identifying who is accountable for each significant event.

Proofreading vs. Human Review

Proofreading is often viewed as the final review of spelling and grammar. Proofreading is far too restrictive. A reviewer may be required to assess whether: The source data is valid. Context is absent. The conclusion logically follows from the evidence. The tone is appropriate for the target audience. The output adheres to the organization's standards. Private or confidential data has been released. An assertion necessitates qualification. An exception should take precedence over the general principle. The requested action is approved. The outcome could result in financial, legal, operational, or reputational damage. The work is truly beneficial. These assessments require experience, knowledge, accountability, and sometimes subjective taste. A reviewer is not present solely to enhance AI-generated work to appear more human-like. A reviewer safeguards the authenticity of the work.

AI Output Quality Relies on the System Surrounding It

People typically evaluate an AI tool through the evaluation of its individual responses. Organizational value is greatly dependent on a broader environment. Where did the tool obtain its data? What were the allowable data sources? Was the data up-to-date? Can the user differentiate between factual data and AI-generated interpretations? Is the output stored with its corresponding sources and historical data? Who reviews it? What transpires if the model expresses uncertainty? Can the action be reversed? A single model may be valuable in one environment and detrimental in another. An AI assistant grounded in authorized records, constrained to a clearly defined task, and associated with a visible review process differs significantly from an unrestricted generator that operates on copied fragments from unknown sources. Responsible AI is a systems-design challenge.

Source Quality Prior to AI-Generated Answers

Since AI can transform ambiguous data into seemingly comprehensive answers, source quality is vital. Before an organization requests AI to summarize, transform, compare, or publish data, it must define which records are authoritative. Which biography contains the accepted facts? Which product record dictates pricing and availability? Which policy is currently active? Which customer record serves as the standard? Which file serves as the approved master? Which source defines ownership and usage rights? Which version of a process should employees follow? Which public assertions have been validated? If these inquiries cannot be addressed, the organization has an information-governance issue that AI may exacerbate. The system should facilitate AI's ability to locate trustworthy data.

Additionally, it should enable people to identify where that data originated.

Trust Inspection Via Provenance

Provenance is the history of origin for data, media, or decisions. Provenance may encompass the original source, author, owner, date, permissions, alterations, approvals, and relationships to other records. Provenance is important because a refined result may mask an uncertain origin. An image may appear suitable while lacking clearly defined usage rights. A paragraph may appear knowledgeable while relying on outdated biographical data. A customer response may incorporate a detail copied from an incorrect account. A recommendation may synthesize verifiable facts with AI-generated assumptions. When provenance is preserved, reviewers can examine the foundation of the work. Reviewers can inquire which source supported a statement, whether it received approval, when it was updated, how AI modified it, who evaluated it, where it was published, and what adjustments must be made if the initial record is revised. Trust becomes demonstrable by the system rather than assumed by the user.

Review Levels Vary Based on Risk

Not all tasks require identical levels of review. A responsible AI workflow should reflect the potential implications of being incorrect.

Low-risk assistance

AI may assist in brainstorming ideas, organizing notes, proposing alternatives, or preparing preliminary drafts privately. Low-risk assistance typically does not necessitate extensive review since the output is neither authoritative nor publicly available.

Moderate-risk preparation

AI may prepare website copy, summarize research findings, categorize records, compose customer correspondence, or recommend modifications to workflow processes. A qualified individual should review the results and confirm key facts prior to their use.

High-risk actions

AI may contribute to financial decisions, legal obligations, security authorizations, sensitive correspondence, public assertions, or substantial decisions regarding individuals. High-risk actions demand explicitly defined authority for review and source validation, documented review processes, and often explicit human authorization. The objective is not to impede productivity for every task. Rather, it is to allocate careful judgment to situations where errors carry significant consequences.

Approval Boundaries Need to Be Explicitly Defined

AI systems frequently blur the distinction between suggesting an action and executing it. The distinction must be discernible. An assistant may conduct research on available data, identify discrepancies between data sources, prepare a draft, propose a categorization scheme, recommend an update or collect necessary materials for a decision-making process.

However, the assistant may not be authorized to publish without review, eliminate vital records from storage systems, change access permissions for files or databases, send sensitive communications electronically, grant approval for financial commitments to third parties (vendors), modify canonical information or make highly impactful decisions regarding individuals. The specific delineation between these types of actions depends on an organization's mission and goals as well as the particular task at hand. The key requirement is that the boundary between these types of actions is established intentionally. Capability does not imply authorization.

Human Judgment Should Occur Throughout Workflow Stages

Human judgment may be necessary at numerous points within a workflow process including defining problems or challenges encountered by workers; selecting relevant sources of information for use by AI systems; establishing constraints on AI systems' operation (e.g., limits on access to certain types of data); recognizing exceptions to rules established by AI systems; evaluating AI systems' performance against benchmarks; authorizing actions taken by AI systems; monitoring AI systems' performance against benchmarks; correcting errors made by AI systems; improving workflow processes implemented by AI systems. Distributed judgment makes AI systems more reliable. Employees should not be required to approve work completed by AI systems when those systems conceal their sources of information; assumptions made during data processing; transformations applied to data during processing; and/or unresolved uncertainties associated with data processing.

Designing for Uncertainty

AI systems should be able to express uncertainty. When AI systems are required to produce complete-appearing answers regardless of uncertainty present in underlying data sources; employees may perceive confidence in presentation as confidence in factual accuracy. A responsible workflow can differentiate among verified information; reasonable inference based on available data sources; AI-generated suggestions; missing information; conflict between data sources; unresolved questions; and pending actions awaiting approval. In some cases; the most useful result is not a completed draft but rather a clear statement indicating that two authoritative records contradict one another and an employee must resolve the contradiction.

Failure Visibility

AI-enabled workflows will fail. A source of data may become inaccessible; an integration may lose authorization; a response generated by an AI system may be incomplete; or an automated action may succeed in one system but fail in another. A dependable workflow should preserve original requests submitted by employees; original sources of data used by AI systems; what was attempted by AI systems; visible failures caused by AI systems; avoidance of duplicate attempts at completing actions; support for safe retries of failed actions by AI systems; notification of appropriate employees regarding failed actions by AI systems; provision for manual recovery paths for failed actions by AI systems; retention of sufficient history data to allow diagnosis of why failed actions occurred by AI systems. Invisible failure creates false confidence among employees using AI-enabled workflows. Responsible AI systems make uncertainty and interruptions understandable for employees using those workflows.

Enabling Employees to Override AI Systems

Automation should not confine employees to making decisions that AI systems cannot comprehend. Employees nearest to the work frequently recognize unusual circumstances before software does. AI systems should enable authorized employees to stop; correct; redirect; or override a process executed by AI systems. Overrides should be recorded when they represent important decisions made by employees. Repeated overrides may indicate that a rule implemented by an AI system is incomplete; that source data used by an AI system is inadequate; or that a workflow implemented by an AI system no longer accurately reflects real-world conditions. Human intervention does not necessarily represent a failure of automation. It can indicate where AI systems' boundaries lie.

Avoiding Illusions of Human Review

Simply adding a reviewer does not render a workflow responsible if the reviewer cannot realistically complete their review responsibilities. Meaningful review requires sufficient time; relevant expertise; access to evidence supporting statements made by AI systems; clear accountability for review responsibilities; authorization for reviewer to reject or revise work completed by AI systems; understandable explanations of revisions made by reviewers to work completed by AI systems; manageable volume of work assigned to reviewers. If employees consistently authorize AI output without reviewing it; human review exists only on paper.

Supporting Judgment with AI Rather Than Eliminating It

AI can collect relevant records; compare versions of documents; reveal inconsistencies between documents; summarize lengthy histories; identify missing fields in records; explain anomalies in records; prepare multiple potential approaches for completing tasks. This can provide employees with better context and more time for tasks that require employee experience. The objective is not to protect manual labor for its own sake but to automate preparatory work while preserving accountability.

Mission HQ and Governed AI Assistance

Mission HQ is being designed around these tenets. Mission HQ establishes authoritative records for artists; releases; assets; websites; playlists; merchandise; articles; and other related information. Mission HQ preserves provenance and relationships between various types of records; supports destination-specific content creation; and separates drafting activities from approval activities and publishing activities. AI can facilitate research activities; comparison activities; categorization activities; writing activities; and workflow preparation activities. The surrounding system defines which information is considered trustworthy; what remains unresolved; which destination is being served; and where human review is required. Governance does not restrict creativity; rather it provides creative and operational work with a reliable basis for performing that work.

Responsible AI as an Operational Practice

Responsible AI cannot be completed once and forgotten. Models; information sources; organizations; and risks associated with AI-enabled workflows continually evolve over time. An ongoing practice related to responsible AI includes evaluating access and permissions granted to employees for accessing data sources used by AI systems; evaluating quality of data sources used by AI systems; monitoring failures experienced by employees using AI-enabled workflows; updating requirements for approving actions taken by AI systems; testing workflows implemented by AI systems; documenting capabilities provided by AI systems; evaluating overrides made by employees to actions taken by AI systems; confirming responsibilities assigned to employees for supervising actions taken by AI systems; eliminating inappropriate automation implemented by AI systems; evaluating whether AI-enabled workflows improve their intended outcomes.

Inquiries Prior to Implementing AI in Workflow Processes

What specific capability should AI provide? Which information will it utilize? Which sources are authoritative? What private or restricted information is involved? How will generated or modified output be distinguished from original output? What transpires when sources conflict? Who reviews the result? What expertise does a reviewer require? Which actions require explicit approval? What is the consequence of making an error? Can an action be reversed? How will failures become evident? What history and provenance must be retained? Who remains accountable? How will the workflow be monitored and enhanced? These inquiries do not serve as impediments to innovation; rather they enable organizations to transform an experimental initiative into a reliable capability that can be utilized confidently.

Enhancing AI Value Through Human Judgment

The most effective AI systems do not eliminate employees indiscriminately. Rather they eliminate repetitive processes that employees perform unnecessarily; organize vast quantities of complex information for employee reference; prepare difficult tasks for employee completion; and assist employees in directing their attention towards crucial decisions that employees must make themselves. AI systems render sources visible; acknowledge uncertainty present in underlying data sources; preserve history related to data processing performed by AI systems; establish clearly defined boundaries for approval processes related to actions taken by AI systems; enable authorized employees to intervene in processes executed by AI systems; and connect speed with accountability for actions taken by AI systems. Human judgment does not represent a temporary safeguard that will eventually become irrelevant once models used by AI systems mature beyond current capabilities. Employees must still define purposes for performing tasks using AI systems; interpret context surrounding tasks performed using AI systems; recognize potential harm resulting from tasks performed using AI systems; interpret ambiguities present in data sources utilized by AI systems; protect relationships between employees and clients/customers; exercise subjective judgment related to aesthetics/taste; make ethical determinations related to tasks performed using AI systems; and accept accountability for actions taken by employees using AI systems. These functions are not external to technical systems utilized by organizations implementing AI-enabled workflows; they are integral components of those systems. For additional reading on implementing responsible AI within your organization and developing custom software solutions that meet your organization's unique requirements please refer to Read Before You Automate Anything and When Custom Software Is Worth Building – And When It Isn’t to further explore Free the Line philosophy. For discussions regarding implementing responsible AI within your organization; designing workflows that incorporate responsible AI principles; or designing connected business systems that integrate responsible AI principles please reach out to info@freetheline.com