A Contextual Approach to Technological Understanding and Its Assessment

This paper refines the concept of technological understanding by categorizing it into three distinct types based on the contexts of design, operation, and innovation, and proposes an assessment framework grounded in counterfactual reasoning to evaluate these different forms of expertise.

The Gist

Imagine you are at a massive, high-tech music festival. To make the festival work, you need all sorts of people: the engineers who built the stage, the DJs playing the music, and the creative directors who decided that "Electronic Chill" was the perfect theme for the weekend.

If you asked each of these people, "Do you understand the technology here?" they would all say "Yes," but they would mean completely different things.

This paper by De Jong and De Haro argues that "understanding technology" isn't a single thing. It’s not like knowing a fact in a history book; it’s more like a skill that changes depending on your job and your goal. They break this down into three distinct "flavors" of understanding.

---

1. The "How it Works" Flavor (Design-Type)

The Analogy: The Master Chef
Think of a professional chef. If you ask them about a high-end oven, they don't just know how to turn it on. They understand how the heating elements interact, how the airflow affects the crust, and what happens if they swap a gas burner for an induction one.

In the paper, this is Technical Understanding. It’s about the "guts" of the machine. If you want to build or fix something, you need to understand the relationship between its physical parts and the science behind them. You need to be able to answer: "What happens to the machine if I change this specific screw or wire?"

2. The "How to Use It" Flavor (Operation-Type)

The Analogy: The Car Driver
Think of a person driving a car to work. They don't need to be a mechanical engineer. They don't need to know the chemical composition of the fuel or the exact physics of the piston stroke. They just need to know: "If I hit the brake, the car slows down," and "If it starts raining, I need to drive more carefully."

This is Operational Understanding. It’s about getting the job done. You understand the results of the machine, not necessarily its internal organs. You need to be able to answer: "What happens to my progress if the weather changes or if the battery gets low?"

3. The "What Else Could It Do?" Flavor (Innovation-Type)

The Analogy: The Visionary Entrepreneur
Think of someone like Steve Jobs or a creative director. They might not be the ones soldering the circuit boards, and they might not be the ones using the software all day. Instead, they look at a piece of technology and ask: "Could we use this laser to perform surgery instead of just cutting metal?" or "Could this AI help people learn languages faster?"

This is Functional Understanding. It’s about seeing the potential and the purpose. You aren't looking at the wires or the buttons; you are looking at the "superpowers" the technology gives you. You need to be able to answer: "What if we took this tool and applied it to a completely different problem?"

---

Why does this matter to you? (The "So What?")

The authors argue that we often get into heated arguments about new technologies (like AI or Quantum Computing) because we are using different "flavors" of understanding and not realizing it.

• The "Techies" are arguing about the Design (Is the code secure? Is the hardware efficient?).
• The "Users" are arguing about the Operation (Is it easy to use? Does it crash?).
• The "Public/Ethicists" are arguing about the Innovation (How will this change society? Will it take our jobs?).

The paper suggests that if we want to have a real conversation about the future, we shouldn't just demand that everyone becomes a technical expert. To have a meaningful debate about how technology affects society, you don't need to know how to build a quantum computer; you just need "Innovation-type" understanding—the ability to imagine what that computer could do and what that might mean for us.

In short: Understanding technology isn't about knowing everything; it's about knowing the right things for the role you are playing.

Technical Summary

Technical Summary: A Contextual Approach to Technological Understanding

Title: A Contextual Approach to Technological Understanding
Authors: Eline de Jong & Sebastian De Haro
Date: Preprint (Feb 2026)

---

1. Problem Statement

The authors address the conceptual ambiguity surrounding "technological understanding." Traditional views often treat understanding as a monolithic or uniform concept, failing to account for how different roles (e.g., a designer vs. a user) and different goals (e.g., repairing a machine vs. inventing a new application) require different cognitive competencies. This lack of precision leads to several issues:

• Educational/Policy Ambiguity: It is unclear what "public understanding of technology" actually entails—whether it requires expert-level technical knowledge or a qualitatively different kind of insight.
• Expertise Conflation: Different forms of expertise are often miscategorized, leading to a narrow view of what it means to "understand" a technology.
• Societal Impact Debates: Discussions regarding the ethical and societal implications of new technologies (like Quantum or AI) lack a formal epistemic framework to define what level of understanding is necessary for meaningful participation.

2. Methodology

The paper employs a conceptual and analytical framework to refine the definition of technological understanding. The methodology is built upon three pillars:

• Logical Specification: The authors use a logical taxonomy based on the "scope" of the concept—specifically, whether the Ultimate Aim ($A$) and the Technological Artefact ($t$) are fixed or open (underdetermined).
• Analogy with Scientific Understanding: Drawing on De Regt (2017) and Barman et al. (2024), the authors map the cognitive requirements of technological understanding onto the established structures of scientific understanding (the ability to use a tool/theory to achieve an end/explanation).
• Counterfactual Reasoning Framework: To move from a theoretical definition to a testable model, the authors propose an assessment methodology based on inferential reasoning. They argue that understanding is demonstrated by the ability to answer "what-if" questions (counterfactuals) regarding changes in circumstances or the artefact itself.

3. Key Contributions

The paper’s primary contribution is the tripartite classification of technological understanding, categorized by context:

Type of Understanding	Context	Logical Scope	Focus of Intelligibility
Technical	Design	Aim fixed; Artefact open	Inner Workings: Relationship between physical structure ($X$) and phenomenon ($P$).
Operational	Operation	Aim fixed; Artefact fixed	Practical Results: How the artefact achieves its direct aim ($a$) under varying conditions.
Functional	Innovation	Aim open; Artefact open	Capabilities: The "fitness for purpose" and potential applications of the artefact.

Additional Contributions:

• The Criterion for Technological Understanding (CTU): An aim $A$ is technologically understood if it can be realized by using a technological artefact $t$.
• The Criterion for Intelligible Technological Artefacts (CITA): An artefact is intelligible if a subject can recognize the qualitative consequences of its operation without performing it.
• Assessment Framework: A mapping of specific "what-if" question types to each context (e.g., design-type focuses on structural changes; operation-type focuses on environmental changes).

4. Results (Conceptual Findings)

The authors demonstrate that technological understanding is not a binary state but a gradual, pragmatic skill that exists on a spectrum.

• Context-Dependency: The "threshold" for sufficient understanding is relative to the agent's role. A professional operator requires a higher degree of operational understanding than a casual user.
• Non-Exclusivity: While the three types are conceptually distinct, they overlap in practice (e.g., an innovator may need to engage in design).
• Epistemic Requirements: The paper proves that different modes of engagement require different "levels" of the artefact's components ($X, P, a, A$) to be intelligible.

5. Significance

The implications of this framework are twofold:

• Societal & Ethical Significance: The paper provides a robust argument for "Functional Understanding" as the foundational competence for discussing societal impact. It suggests that citizens do not need to understand the "inner workings" (technical) of a technology to participate in ethical debates; rather, they need to understand its "capabilities" (functional). This democratizes technological discourse and provides a roadmap for public engagement.
• Epistemic & Educational Significance: By distinguishing between technical, operational, and functional expertise, the framework promotes a pluralistic view of expertise. It allows educators and policymakers to target specific types of understanding (e.g., teaching "functional" understanding to policymakers vs. "technical" understanding to engineers) rather than pursuing a vague, all-encompassing goal of "technological literacy."