Header Banner
TRACE Framework: Five Questions for Using AI Wisely
AI and Work AI in Education Ethics Human Experience of AI

TRACE Framework: Five Questions for Using AI Wisely

TRACE™️: Five Questions for Using AI Wisely


Artificial intelligence has quietly changed the kinds of decisions people make each day. That change is easy to miss because many of the visible activities remain familiar. People still write emails, summarize meetings, search for information, brainstorm ideas, and solve problems. On the surface, the work often looks the same. What has changed is the relationship between the person doing the work and the system participating in it.

Consider how easily an ordinary question becomes a negotiation. A student asks an AI system to explain a difficult concept. A manager requests a summary of a lengthy report. A physician asks for possible differential diagnoses before meeting with a patient. None of these examples removes the human from the process, yet each redistributes part of the cognitive work that was previously performed without technological assistance. The interaction is no longer simply one of using a tool. It becomes a negotiation over evidence, judgment, interpretation, and responsibility.

Much of the public conversation about AI continues to focus on capability. Can the system write well enough? Can it reason? Can it replace particular kinds of work? Those are understandable questions because new technologies are often evaluated according to what they can accomplish. They tell us relatively little, however, about what happens after those capabilities become ordinary. Once AI participates in everyday work, the more interesting question may not be what the technology can do but how people begin adapting around it.

That shift in perspective is where TRACE™️ begins. Rather than evaluating AI as a technology, TRACE examines the conditions created when intelligent systems become participants in human decision-making. The framework is less concerned with whether AI should be used than with understanding the kinds of questions that become increasingly important once its use becomes commonplace. Those questions recur across workplaces, classrooms, hospitals, governments, and homes because they arise from the structure of the interaction itself rather than from any particular application.

TRACE organizes those recurring questions into five domains: trust, reality, agency, cognition, and exposure. Together, they provide a way of examining not only individual decisions but also the broader human adaptations taking place as AI becomes part of everyday life.

Each domain represents a different way AI participates in human decision-making. Although they can be considered individually, they are most useful when viewed together. A trustworthy response may still influence how we understand a problem. An efficient workflow may reduce opportunities for independent thinking. A helpful recommendation may leave important questions about responsibility unanswered. TRACE is therefore less a checklist than a set of perspectives that reveal different aspects of the same interaction.

The Five Domains of TRACE

Trust

How much confidence should I place in this response?

Trust is often treated as though it were a property of technology. We ask whether an AI system is trustworthy in much the same way we ask whether a bridge is structurally sound or whether a calculator produces the correct answer. Yet trust has never worked that way. It is not a characteristic that exists independently of either a person or a machine. It is a relationship that develops between them, shaped by repeated interactions, previous experience, institutional reputation, and the consequences of being wrong.

AI complicates that relationship because it produces something humans are particularly susceptible to mistaking for evidence: fluency. A response that is coherent, confident, and immediate often feels more reliable than one that is hesitant or incomplete. That impression persists even when the underlying information contains errors, omits important context, or presents speculation alongside fact without clearly distinguishing between them. The challenge is rarely that people trust AI absolutely. More often, trust becomes miscalibrated. Confidence gradually becomes attached to presentation rather than evidence.

The purpose of the Trust domain is therefore not to encourage skepticism for its own sake. Distrusting accurate information is no more useful than believing inaccurate information. Instead, Trust asks whether our confidence is proportional to the quality of the evidence supporting the response. The central question is not whether AI can be trusted, but how trust should be calibrated as these systems become routine participants in everyday thinking.

Reality

How might this shape my understanding?

We often imagine that information changes our minds by adding new facts. Just as often, however, it changes our understanding by changing what receives our attention. Every explanation foregrounds certain relationships while leaving others in the background. Every summary decides what deserves emphasis and what can be safely omitted.

This matters because most people encounter AI not as a database but as a conversational partner. The system does not simply retrieve information. It selects examples, establishes tone, chooses analogies, and determines which perspectives appear relevant to the question being asked. Those decisions influence what becomes visible and what remains outside the frame. Over time, repeated interactions can narrow the range of possibilities a person routinely considers without that narrowing ever becoming obvious. Reality, therefore, asks readers to pay attention not only to accuracy but also to framing. A technically correct response may still guide attention toward one interpretation while obscuring others. The question is less "Is this true?" than "How is this response shaping the way I understand the situation before me?" Recognizing that distinction makes visible one of AI's quieter forms of influence.

Agency

Who remains responsible?

Responsibility has always been easier to assign when the boundaries between people and tools are clear. A spreadsheet performs calculations without creating uncertainty about who made the financial decision. A search engine retrieves information without claiming ownership of the conclusions drawn from it. AI occupies a more ambiguous position because it increasingly contributes to judgments that have traditionally been understood as human work.

That ambiguity creates conditions in which responsibility can become surprisingly difficult to locate. Individuals may defer to algorithmic recommendations because the system appears objective. Organizations may attribute undesirable outcomes to the technology rather than to the choices surrounding its design, deployment, or oversight. As decision-making becomes distributed across people and intelligent systems, accountability risks becoming similarly diffuse.

Agency asks readers to resist that diffusion. The question is not whether AI participated in the decision. Increasingly, it will. The more important question is whether human responsibility remains visible once that participation occurs. Technology may redistribute work, but responsibility does not disappear simply because it has become easier to overlook.

Cognition

What thinking am I outsourcing?

Every technology redistributes cognitive work. Writing externalized memory. Calculators reduced the need for mental arithmetic. Search engines transformed information retrieval. AI represents another step in that longer history, but with a notable difference. Rather than supporting isolated cognitive tasks, it increasingly participates across many forms of thinking simultaneously. It summarizes, synthesizes, critiques, brainstorms, drafts, plans, and evaluates. Activities that once required sustained intellectual effort can now be completed collaboratively with a conversational system.

The question, however, is not whether these changes are good or bad. Humans have always developed technologies that extend cognitive capacity. The more interesting question concerns what happens when delegation becomes habitual. Human abilities develop through repeated use. They also decline through repeated delegation. The question is not whether AI changes cognition. It clearly does. The more important question is which cognitive capacities we gradually stop practicing because the technology performs them well enough.

The Cognition domain is concerned with the relationship between efficiency and dependence. Delegating routine work may create opportunities for deeper thinking, but only if the capacities being preserved remain intentional. Otherwise, convenience quietly becomes substitution, and the distinction between assistance and replacement becomes harder to recognize.

Exposure

What information am I sharing?

Privacy is often mistaken for secrecy, as though it matters only when someone has something to hide. Everyday life suggests otherwise. People routinely decide what to reveal, to whom, and under what circumstances. Those decisions make social life possible because they preserve the ability to manage the boundaries between different relationships.

AI systems expand those opportunities for disclosure because they invite interaction in unusually conversational ways. Users describe problems in detail, upload documents, explain workplace processes, and reveal uncertainties that might never appear in a traditional search engine query. Even when individual exchanges seem insignificant, repeated interactions contribute to larger patterns of data collection and inference. What appears to be a series of isolated prompts may also become part of a broader informational portrait.

Exposure encourages readers to think beyond the narrow question of whether a particular prompt contains confidential information. Instead, it asks how participation in AI systems gradually reshapes the boundaries between what remains private, what becomes observable, and what is ultimately available for analysis. Privacy, in this sense, is not merely the protection of information. It is the ongoing ability to decide what parts of ourselves, our organizations, and our thinking remain under our own control.

Why TRACE Matters

Frameworks become useful when they provide language for changes that are otherwise difficult to notice while those changes are still unfolding. AI is introducing new habits of working, learning, deciding, and communicating so gradually that many of its most significant effects appear ordinary by the time we recognize them. TRACE does not attempt to predict every consequence of artificial intelligence. Instead, it offers a way of observing those consequences while they are still emerging.

The five domains are not independent categories, nor are they questions to answer once and set aside. Trust influences how people construct reality. Reality shapes perceptions of agency. Agency affects the kinds of cognition people delegate to intelligent systems. Each interaction also produces new forms of exposure. The domains overlap because they describe different dimensions of the same process: the ongoing adaptation of human thinking, judgment, and social life to increasingly capable AI systems.

For that reason, TRACE is best understood as a practice of attention rather than a checklist. Returning to these questions over time makes it easier to notice how AI is changing not only the work we do, but the conditions under which that work takes place. The technology will continue to evolve. Human adaptation will continue alongside it. The value of TRACE lies in giving us a vocabulary for observing those changes before they become so familiar that we stop seeing them.




Tags: 

AI Ethics, TRACE Framework, Human-Centered AI, AI Literacy, Human-AI Interaction, Trust in AI, Human Adaptation





 

Read more
Trust & Affect System Model (TASM)
AI and Work

Trust & Affect System Model (TASM)

 

Why AI Quietly Fails Before the Metrics Notice

Dr. Kristine Ketel

The Quiet Failure Problem

Most AI-enabled systems do not fail because they are inaccurate. They fail because people quietly stop using them. This pattern is visible across industries but systematically misdiagnosed.

Long before performance metrics show a decline, users hesitate. They overcheck outputs. They build informal workarounds. They restrict use to low-stakes situations or disengage altogether. From the outside, the system appears functional. Inside the system, trust has already begun to erode.

These failures are rarely dramatic. There is no single breaking moment, no obvious error event, no clear line where confidence suddenly collapses. Instead, adoption thins over time. Reliance becomes conditional. What looks like "successful deployment" on a dashboard increasingly resembles quiet avoidance in practice.

When leaders notice low uptake or inconsistent use, the explanation often turns toward users. They lack training. They resist change. They do not understand the system's value. At other times, attention shifts to the technology itself, arguing that models need refinement, interfaces need improvement, and accuracy needs to increase.

Yet these explanations struggle to account for a familiar contradiction: why technically sound systems remain underutilized even after training, iteration, and demonstrated capability.

What is missing from these accounts is time.

Quiet failure unfolds gradually, through everyday interaction. It is not triggered solely by major errors or obvious harms. It emerges through small moments of friction: a recommendation that feels opaque, an automated judgment that feels unfair, a system decision that removes agency without explanation. Each moment on its own appears trivial. Together, they reshape how people relate to the system and what they expect from it.

This is what makes quiet failure difficult to detect and even harder to reverse. Traditional success metrics (accuracy, speed, task completion) often remain stable long after the underlying relationship between people and the system has degraded. By the time performance declines or ethical concerns surface, legitimacy has already been lost in practice.

Importantly, this pattern is not unprecedented.

Organizations have long struggled with systems that appear effective on paper but fail in lived experience. Disengagement precedes turnover. Resistance takes the form of compliance without commitment. Ethical breakdown rarely begins with overt misconduct; it begins with loss of trust, erosion of meaning, and rational withdrawal.

AI-enabled systems are now reproducing these same dynamics. This happens not because users are irrational or fearful, and not because the technology is inherently flawed, but because these systems increasingly shape behavior, authority, and accountability in ways that reflect organizational structures.

This pattern calls for a new analytical model, one that treats AI-enabled systems not as tools but as organizational actors exercising authority. The more relevant question is not whether people trust AI-enabled systems, but why trust becomes difficult, or even irrational, within the systems we design. 

AI as an Organizational Actor

To understand why quiet failure occurs, we need to reconsider what modern AI-enabled systems actually do in real-world contexts.

Most discussions still frame AI as a tool, as an instrument that supports human decision-making, improves efficiency, or automates discrete tasks. That framing no longer captures how AI-enabled systems function in practice, particularly in environments where they shape decisions repeatedly and at scale.

Contemporary AI-enabled systems increasingly perform roles once occupied by organizational structures and human authorities. They evaluate performance, rank priorities, recommend actions, control access to resources, and coordinate workflows across teams and time. In many contexts, they do not merely assist decisions; they shape which decisions are available, visible, or actionable in the first place.

These functions are not neutral.

In organizational settings, systems that evaluate, allocate authority, and constrain action are understood as exercising power even when that power is indirect, procedural, or distributed. Policies, procedures, and managerial hierarchies do not require intentions or emotions to influence behavior. They do so through structure, consistency, and enforcement.

AI-enabled systems now occupy a similar position. Authority is mediated not through human judgment, but through technical design.

This is not a metaphor. AI-enabled systems do not merely resemble organizations symbolically; they increasingly function as organizational actors by shaping incentives, defining norms, and redistributing responsibility. When an algorithm determines whose work is flagged, which cases are escalated, or which recommendations are prioritized, it performs the same coordinating role long assigned to managers, committees, or institutional rules.

Despite this, AI-enabled systems are often deployed without reference to the extensive body of knowledge addressing how authority structures affect trust, motivation, and ethical behavior. The relational consequences of system design are treated as secondary concerns, as user attitudes to be managed after deployment rather than structural outcomes to be anticipated.

This mismatch produces a predictable failure mode.

When AI-enabled systems are designed solely around task performance, they inherit organizational power without organizational safeguards. They influence behavior without providing sensemaking, enforce decisions without accountability, and constrain agency without mechanisms for repair. From the user's perspective, disengagement becomes a rational response to a system that feels unclear, unresponsive, or unjust.

Once AI-enabled systems are recognized as organizational actors, the quiet failure problem becomes legible. In fact, what appears to be a problem of user trust is a problem of system governance.

Why Trust and Affect Are System Variables

Once AI-enabled systems are understood as organizational actors, the limitations of existing trust frameworks come into focus.

Much of the current discussion treats trust as an internal psychological state, something users possess, grant, or withhold based on attitudes toward a system. Affect is often framed as an emotional response users bring into the interaction. These perspectives capture important aspects of experience, but they operate at the wrong level of analysis for understanding quiet failure.

In organizational contexts, trust is not primarily a feeling. It is an infrastructural condition that emerges from how systems distribute power, enforce rules, and respond to breakdown. People do not decide whether to trust an organization in the abstract. Trust becomes rational or irrational through repeated interaction with processes that feel predictable or arbitrary, fair or biased, responsive or indifferent.

The same logic applies to AI-enabled systems that now mediate organizational authority.

In this sense, trust is a property of the system. It is produced, or undermined, by design features such as transparency, consistency, accountability, and repair capacity. When these features are present, trust becomes a reasonable stance. When they are absent, skepticism and disengagement are not failures of attitude; they are logical responses to structural conditions.

Affect operates in a similarly systemic way.

This framework understands affect as elicited by the system itself, rather than treating emotion as a subjective overlay on neutral interaction. AI-enabled systems generate affective conditions through how they constrain choice, allocate agency, and communicate (or fail to communicate) the rationale behind their actions. Confidence, anxiety, resentment, and relief are not incidental reactions. They are signals produced through ongoing interaction with authority embedded in technical form.

These affective conditions shape behavior long before explicit judgments of trust are articulated. Anxiety leads to overchecking. Resentment leads to workarounds. Loss of agency leads to withdrawal. None of these behaviors require a conscious decision to distrust the system; they emerge naturally when the system's design makes trust difficult to sustain.

Trust and affect also interact. Affective strain accelerates trust erosion, while degraded trust amplifies negative affect. This feedback loop unfolds gradually and often invisibly, particularly in systems that continue to meet formal performance criteria.

From a governance perspective, trust and affect function as leading indicators, signals that appear well before accuracy or efficiency metrics register decline.

Introducing the Trust & Affect Systems Model (TASM)

If AI-enabled systems function as organizational actors, and trust is infrastructural rather than psychological, then existing frameworks treating trust as user sentiment are operating at the wrong level of analysis. A systems model is needed that maps how design choices propagate through affect, behavior, and ethical risk over time.

To make these dynamics visible, I propose the Trust & Affect Systems Model (TASM), a systems-level framework for understanding how AI-enabled system design and governance shape trust, affect, behavior, and ethical risk over time.

TASM does not model individual attitudes toward AI, nor does it attempt to measure trust as a psychological state. Instead, it treats trust and affect as emergent properties of sociotechnical systems that increasingly function as organizational actors.

TASM describes a recursive process:

1. System Role & Design: AI-enabled systems are deployed into organizational roles such as evaluator, advisor, gatekeeper, or coordinator. These roles determine how authority is exercised and the amount of discretion users retain.

2. Affective Conditions Produced: Systems generate affective conditions through their role and design. These conditions include confidence or anxiety, clarity or resentment, agency or powerlessness.

3. Trust Infrastructure: Over time, affective conditions contribute to the emergence or erosion of trust infrastructure. Trust infrastructure is shaped by predictability, transparency, consistency, and the ability to make repairs.

4. Behavioral Response: Trust infrastructure shapes use in practice: reliance, overchecking, workarounds, conditional use, or avoidance.

5. Ethical & Organizational Risk: Behavioral adaptations generate ethical and organizational risk, including automation bias, moral disengagement, accountability diffusion, and a decline in legitimacy.

6. Metrics & Oversight (Lagging Indicators): These risks surface, if at all, through conventional performance metrics that detect problems only after trust and affect have already deteriorated.

Figure 1: The Trust & Affect Systems Model diagram

This process is recursive, not linear. Crucially, metrics and oversight feedback into system redesign, often without addressing the trust and affect conditions that produced failure in the first place. Organizations may repeatedly refine technical performance while leaving the underlying causes of disengagement unaddressed.

Consider a performance evaluation system that provides scores without explanation. Employees feel anxiety (affect), begin over-documenting to protect themselves (behavior), which degrades collaboration (organizational risk), while engagement scores remain acceptable (lagging metrics). Each 'improvement' iteration focuses on scoring accuracy while never addressing the opacity that triggered withdrawal in the first place.

This is how quiet failure becomes entrenched.

What This Changes

If trust and affect are treated as system variables rather than user dispositions, the implications for AI design, governance, and ethics are substantial.

For Designers

TASM reframes trust as a design outcome rather than a user goal. Designing for trust doesn’t mean encouraging reliance. It means creating systems with legible authority, explainable decisions, and repairable failures. Opacity and rigidity aren’t just usability issues; they are structural conditions that produce disengagement over time.

For Leaders

The model shifts responsibility away from users and toward governance. Adoption failure doesn't mean people 'don't trust AI,' but that trust has not been made rational within the system. This redirects attention upstream from training and change management to role definition, accountability, and oversight.

For Ethics and Compliance Teams

TASM challenges event-based approaches that focus on harm after the fact. Ethical risk does not originate solely in discrete failures; it accumulates through everyday interaction with systems that obscure agency or diffuse responsibility. From this perspective, ethical breakdown is not an anomaly. It is an emergent property of system design.

Conclusion: Reframing Failure

AI-enabled systems rarely fail all at once. They fail quietly.

They fail through gradual disengagement, conditional reliance, and loss of legitimacy that unfolds long before performance metrics register concern. These failures are often misattributed to user resistance or insufficient training, when they more accurately reflect structural conditions embedded in system design and governance.

The Trust & Affect Systems Model does not argue for greater trust in AI-enabled systems, but for systems that are deserving of trust.

TASM shifts responsibility away from users and toward the structures that shape interaction, authority, and accountability by foregrounding trust and affect as leading indicators of system health. It offers a way of naming a class of failures that have remained difficult to see, even as they recur across domains.

As AI-enabled systems continue to assume organizational roles, the question is no longer if trust matters.

It is whether we are willing to design, govern, and evaluate systems in ways that make trust reasonable.

The next article in this series examines how TASM can be operationalized to assess trust, affect, and ethical risk in AI-enabled systems before failures become visible in performance data.

Tags:

Human-Machine Interaction, AI and Work, Trust and AI, TASM
 

Read more