Trust in Automation defines practices and technical as well as organizational measures to ensure appropriate reliability, transparency and human control of automated systems. It emphasizes observability, fault tolerance and clear escalation paths. The goal is to increase user acceptance and safe operation across product and run processes.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Trust in automation describes how strongly people expect an automated system to support tasks reliably and appropriately.
The approach grew from human-factors and automation research as systems increasingly took on tasks whose results people must supervise. In 1997, Lee and See framed trust in automation as a calibratable relationship between a person and a system.
Trust is a working hypothesis: people observe performance, compare it with their own judgment, and adjust how they use the system.
Application
Ein nachvollziehbarer Ablauf verbindet Anlass, Entscheidung und überprüfbares Ergebnis.
Die Methode braucht einen passenden Kontext und ersetzt keine fachliche Prüfung.
Trust can make supervision easier and support adoption. Overtrust encourages complacency, while distrust blocks useful assistance; performance and uncertainty must remain visible.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.