---
title: Critical Technical Practice (CTP)
url: https://www.emergentmind.com/topics/critical-technical-practice-ctp
type: topic
---

# Critical Technical Practice (CTP)

Critical Technical Practice (CTP) offers a systematic approach for embedding normative, social, and ethical reflection within technical work. In contrast to conventional engineering methodologies that treat technical design as value-neutral, CTP integrates rigorous technical methods with ongoing critique focused on power structures, inclusion, exclusion, and social consequences. Drawing upon frameworks such as Critical Systems Heuristics (CSH), CTP provides heuristics and practical workflows that make explicit the assumptions, boundary judgments, and implicit values foundational to socio-technical systems, ranging from smart cities and artificial intelligence to requirements engineering in safety-critical domains [1906.02266, 2510.10588, 1910.01678].

## 1. Theoretical Foundations and Origins

CTP arose out of the limitations of traditional engineering and design thinking, which historically isolated technical work from questions of ethics and power. Foundationally, CTP is linked to Critical Systems Thinking and CSH, as developed by Werner Ulrich. CSH contends that any technical artifact or intervention is situated within a web of normative judgments—specifically, "boundary judgments" concerning what is included, excluded, prioritized, or ignored in a system [1906.02266].

Fundamental CTP commitments include:

- Systemicity: Attending to interrelations within technical and social domains.
- Criticality: Challenging presupposed power relations and immutable social structures.
- Reflexivity: Emphasizing that designers and analysts must interrogate their own roles and partial standpoints.
- Emancipation: Stipulating that those affected by technical designs should possess substantive influence over decision processes.

These premises establish CTP as a mode of engineering in which critique is built into every phase—not appended as an afterthought [1910.01678].

## 2. Central Methods and Heuristic Frameworks

CSH operationalizes CTP through a defined set of twelve boundary questions, grouped along motivation, control, expertise, and legitimacy. Each question is formulated in "is" and "ought" modes, supporting both description and critique. For instance:

- Who is (and ought to be) the intended beneficiary?
- What is (and ought to be) the purpose?
- Who is (and ought to be) the decision maker?
- Who is (and ought to be) a witness for those affected?
- What opportunities exist (and ought to exist) for contesting dominant worldviews?

These boundary questions serve as a discursive heuristic, structuring reflection and deliberation during requirements gathering, design, and evaluation [1906.02266, 1910.01678].

Integration with standard engineering flows is exemplified in requirements engineering, where CSH questions are mapped directly onto Volere specification sections, making critical reflection inseparable from functional specification [1910.01678]:

| CSH Category          | Volere Section                  |
|-----------------------|---------------------------------|
| Client/Beneficiary    | Stakeholders and Users          |
| Purpose/Goal          | Business Drivers                |
| Boundary Judgments    | Rationale/Traceability          |

*Table: Alignment of CSH boundary concepts with standard RE artifacts [1910.01678].*

## 3. CTP in Practice: Case Studies from AI and Urban Infrastructure

### 3.1 Explainable AI

Jin et al. [2510.10588] diagnose implementation failures in Explainable AI (XAI) as symptoms of imbalanced power structures where technical actors' interests systematically override affected communities. Four empirical cases are interrogated:

- XAI audience defaulting to machine learning engineers rather than actual end-users.
- Feature-attribution explainability methods evaluated only on datasets amenable to technical convenience.
- "Plausibility" as a metric incentivizing misleadingly agreeable explanations.
- The myth of the explainability-performance trade-off.

The root cause is formalized as an unchecked proliferation of unjust power \( P_{\mathrm{unjust}} \) relative to ethical power \( P_{\mathrm{eth}} \):

\[
\frac{dP_{\rm unjust}}{dt} = \alpha P_{\rm unjust} - \beta P_{\rm eth}, \quad 
\frac{dP_{\rm eth}}{dt} = \gamma P_{\rm eth} - \delta P_{\rm unjust}
\]

CTP interventions here comprise explicit power analysis, narrative reframing ("complementarity" over "trade-off"), and rigorous limitation analysis, operationalized in technical pseudocode and embedded at each lifecycle stage [2510.10588].

### 3.2 Smart Cities and Urban Governance

Application of CSH within the Sidewalk Toronto smart city project [1906.02266] revealed critical boundary tensions between stated values (triple-bottom-line sustainability) and practical dominance of platform and market imperatives. Official public engagement processes were shown to narrowly circumscribe authentic citizen influence. The CTP approach surfaced misalignments—e.g., ambiguous data trust governance, affordability algebra skewed toward middle-income groups, and infrastructural monopolization—by systematically mapping project documents and stakeholder critiques to each of the twelve CSH questions.

### 3.3 Requirements Engineering

In HomeSound, a safety-critical system, Duboc et al. [1910.01678] enacted CTP by embedding CSH questioning into the mainstream Volere template over six iterative ideal-mapping cycles. As a result, critical insights emerged: broadening the definition of beneficiaries, reconciling security vs. autonomy, replacing superficial performance metrics with deep psychosocial measures, and surfacing data privacy risks. Each requirements artifact was paired with its explicit CSH critique, demonstrating that critical reflection can be lightweight but influential if woven into standard tools.

## 4. Interventional Mechanisms and Workflow Integration

CTP is operationalized as a looping workflow where power analysis, critique of narratives, and limitation analysis are invoked at every stage—framing, data curation, modeling, evaluation, deployment [2510.10588]. Typical practical components include:

- **Power Analysis**: Identifying stakeholders, quantifying relative risks/benefits, and flagging imbalances.
- **Narrative Check**: Detecting and reframing discursive conventions (e.g., challenging the "performance-ethics" dichotomy).
- **Limitation Analysis**: Systematic identification and dissemination of model or system failure modes and their societal impacts.

Embedding these interventions produces artifacts—such as power/risk tables, narrative reframing annotations, and failure mode catalogs—that complement traditional technical documentation.

## 5. Implications for Governance, Participation, and Accountability

CTP’s explicit surfacing of boundary judgments, inclusion/exclusion logics, and traces of power is positioned as essential for democratic governance in complex socio-technical systems [1906.02266]. Methodological completeness is enhanced by drawing sources from policy documents, participant observations, stakeholder interviews, and press analysis. Effective CTP calls for iterative revisiting of critical questions; as boundaries and power shift, the mapping and critique must evolve accordingly.

CTP frameworks are adaptable: as reflective practice for technical teams, as external evaluative rubrics, or as polemical instruments by civil-society actors. They are also extensible across domains, from energy systems to e-government and organizational ERP platforms.

## 6. Limitations, Challenges, and Prospects

A plausible implication is that CTP’s impact depends on genuine commitment from technical and organizational leadership, since critiques can be marginalized if treated as process formalities. Full realization of CTP’s emancipatory aims requires that affected communities co-produce, not merely answer, critical boundary questions, a process that remains logistically and institutionally challenging in many settings [1906.02266].

Adoption of CTP in engineering education and technical standards signals an emerging consensus on the inseparability of ethics and technical rigor. Importantly, CTP does not offer a static methodology but a reflexive, iteratively updated practice sensitive to local contexts, evolving power relations, and newly emergent societal risks [1910.01678, 2510.10588].

Source: https://www.emergentmind.com/topics/critical-technical-practice-ctp