Technography
- Introduced by
- Kees Jansen & Sietze Vellema (Wageningen); algorithmic strand by Taina Bucher
- Year
- 2011
- Type
- Ethnographic field method
- Family
- Ethnography of technology
What does it do?
Technography is the ethnographic description of technology-in-use: how tools, machines, and systems are actually handled, skilled, and enacted in the course of real tasks.
Articulated as a method by Kees Jansen and Sietze Vellema in the Wageningen tradition of agrarian and development studies, it places the technical at the centre of ethnographic attention, asking how people and artefacts together accomplish work. A digital strand, exemplified by Taina Bucher's study of algorithmic power, extends technography to software and platforms, examining how algorithms are encountered, felt, and acted upon. Across both, the method treats technology not as a finished object but as something performed in practice within particular social and material settings.
The intuition behind the method
Watch a skilled farmer running a tractor over a sloping field, a nurse threading an infusion pump, or a creator second-guessing what a recommendation algorithm 'wants' before posting. In each case the technology is not just sitting there; it is being worked, coaxed, repaired, and adapted by people whose hands and judgement carry knowledge that no manual records. Technography is the practice of looking closely at this doing—the grip, the workaround, the tacit feel for the tool—and at the web of other tools, tasks, and people it draws in. Rather than asking what a technology is in the abstract, it asks what happens when this technology meets these hands in this task, and what that encounter reveals about skill, power, and the ordering of work.
History
Technography was named and developed as a distinct method by Kees Jansen and Sietze Vellema at Wageningen University, where their 2011 NJAS article 'What is technography?' set out an ethnography of technology centred on skilled practice, tools, and tasks, drawing on agrarian, development, and STS traditions. The approach responded to a perceived neglect of the technical in social analysis, insisting that how technologies are made to work be placed at the heart of inquiry. A parallel and increasingly prominent strand applies technographic sensibilities to software and platforms: Taina Bucher's If...Then (2018) studies algorithmic power and politics through how algorithms are encountered and lived, extending the method into the digital domain. Together these strands have established technography as a recognised approach for studying technology-in-use.
When to use it
Use technography when you want to understand how a technology actually functions in the hands of its users—its skilled, embodied, and improvised use in real tasks—rather than its design intentions or its public representation. It suits studies of tools and machines in work settings, of technologies in development and agrarian contexts, and of digital and algorithmic systems as they are encountered and acted upon by users. The method assumes that technology is best understood as performed in practice, that close observation can surface tacit skill, and that the analyst can gain access to use settings (or, for digital systems, devise ways to study elusive software). It is less appropriate when only design documents or aggregate usage data are available, when the research question is about the artefact's internal mechanism alone, or when large-scale comparison rather than situated description is the goal.
Limitations and considerations
- Intensive, situated fieldwork limits the number of cases and the scope for generalisation.
- Tacit and embodied skill is hard to observe and articulate, depending on the researcher's own competence and access.
- Studying digital and algorithmic systems is complicated by their opacity, proprietary nature, and constant change.
- The close focus on practice can underplay the design decisions and political-economic forces upstream of use.
Source conditions do not replace independent scientific review or validation by an analysis engine.
Strengths
- Centres the technical, revealing skilled and tacit practice that design-focused or discourse-focused studies miss.
- Connects the embodied use of a single tool to the wider networks of tasks, tools, and people it depends on.
- Extends naturally from physical tools to digital and algorithmic systems, keeping pace with contemporary technology.
- Links close description of practice to questions of power, value, and inequality in how technologies order work.
Applications
- Studying the use, adaptation, and repair of agricultural machinery and techniques in farming and development settings.
- Analysing how clinicians use medical devices and the tacit skills their safe operation requires.
- Examining how users encounter and respond to recommendation, ranking, and other algorithmic systems on platforms.
- Investigating skilled craft and industrial work where tools and embodied know-how are central.
- Informing the design of technologies by revealing how prototypes and systems are actually used in the field.
How it works
How it works
Choose a specific technical practice or task in which a technology is used by skilled practitioners, since technography takes the technical performance, not the artefact in isolation, as its unit of study. Jansen and Vellema argue for centring the analysis on how technologies are made to work in concrete activity. The researcher delimits a practice—a cultivation routine, a clinical procedure, a platform workflow—rich enough to expose the interplay of tools, skills, and tasks.
Observe the technology in actual use through close, often participatory fieldwork, attending to how it is handled, adjusted, repaired, and made to perform in situ. The emphasis is on use rather than design or representation, capturing the embodied, improvised, and routine character of technical action. The researcher records the sequence of operations and the moments of friction, breakdown, and workaround where the technology's role becomes visible.
Document the tools deployed and the skills—often tacit and embodied—that competent use requires, including the know-how that is rarely written down. Following the Wageningen emphasis on skilled practice, the researcher describes how operators read, anticipate, and compensate for their tools. Attention to both the material affordances of the tool and the human competence it demands distinguishes technography from a purely textual or design-based account.
Analyse how the focal technology is bound into wider networks of other tools, tasks, people, and infrastructures that make its use possible and meaningful. Bucher's algorithmic technography shows how an algorithm is encountered not in isolation but through its entanglement with platforms, data, and users' anticipations and feelings. The researcher maps these task networks to show that a technology-in-use is always part of a larger sociotechnical arrangement.
Situate the practice within its social, political, and economic context, asking how power, value, and inequality are enacted through technology-in-use. Bucher's work demonstrates how algorithmic systems exercise politics through the ways they are encountered and lived, not only through their code. The researcher links the close description of practice to broader questions of who benefits, who is constrained, and how technical arrangements order social life.
Common pitfalls
- Describing the artefact's design or specifications instead of its actual, situated use by skilled practitioners.
- Overlooking tacit skill because it is unspoken, and so reporting only the explicit, manual-style account of use.
- Isolating the focal technology from the task networks and infrastructures that make its use possible.
- Studying digital systems only through their interfaces while ignoring users' anticipations, feelings, and workarounds.
Frequently asked questions
How does technography differ from laboratory ethnography?
Laboratory ethnography studies how scientific facts are produced inside research settings, focusing on knowledge-making, while technography focuses on technology-in-use—how tools and systems are skilfully handled in tasks across many settings, from farms to platforms. Both are ethnographic and attend to material practice, but technography foregrounds the technical performance and skill of users rather than the construction of facts. Technography can study any site where technology is put to work, not only laboratories.
Can technography study software and algorithms?
Yes. A growing digital strand, exemplified by Taina Bucher's If...Then, applies technographic methods to algorithmic systems, studying how they are encountered, anticipated, and felt by users rather than only how they are coded. Because algorithms are often opaque and proprietary, digital technography devises indirect ways to observe their effects in use—through users' experiences, workarounds, and the platforms in which they are embedded. This extends the Wageningen emphasis on skilled practice into the world of software.
What is the role of tacit knowledge in technography?
Tacit, embodied skill is central, because competent use of a technology typically relies on know-how that is never written in any manual—the feel for a tool, the anticipation of breakdown, the improvised workaround. Technography aims to surface and describe this skilled practice through close observation and, often, participation. Capturing tacit knowledge is also one of the method's hardest challenges, since the very competence at stake resists easy articulation.
Related methods
Sources
Jansen, K., & Vellema, S. (2011). What is technography? NJAS - Wageningen Journal of Life Sciences, 57(3-4), 169-177.
Open DOI referenceCopied.Bucher, T. (2018). If...Then: Algorithmic Power and Politics. Oxford University Press.
ISBN: 9780190493028Copied.