VOCABULARY / ENTRY
Value Sensitive Design
value-sensitive-design
Value Sensitive Design is a method for systematically accounting for human values throughout the design process: through an iterative, integrative tripartite methodology of conceptual, empirical, and technical investigations, it first clarifies what values are at stake in a decision and whose values they are, and identifies indirect stakeholders who never use the product but are affected by it, in addition to direct users.
Recognizing it
- State what values are at stake and whose values they are before settling on a solution
- Identify both direct users of the system and indirect stakeholders who never use the product but are affected by it
- Move back and forth between conceptual, empirical, and technical investigations rather than completing them once and closing the case
Concept boundary
Value Sensitive Design is not a synonym for inclusive design: inclusive design focuses on recognizing exclusion and differences in ability, while Value Sensitive Design addresses the broader question of how human values (such as privacy, autonomy, and fairness) are supported or undermined for both direct and indirect stakeholders; the two can complement each other but have different focal points. It is also not a one-off ethics review done at the end of a project: the conceptual, empirical, and technical investigations must be revisited throughout the design process, not tacked on as a compliance check once a solution is already final.
When to consider it
- A technical decision affects people who never use the product, such as applicants evaluated by an algorithm or bystanders in a monitored space
- Multiple stakeholder groups hold different or conflicting expectations about the same value, such as privacy versus efficiency
- The design is still at a conceptual stage, so its technical form can still be shaped by a values analysis
When to be cautious
- Treating a one-off ethics review at project close-out as the entire method of Value Sensitive Design
- Counting only paying or active users without asking what the technology costs indirect stakeholders
- Declaring a value tension resolved based on one stakeholder's preference or a single interview
Tradeoff
Identifying indirect stakeholders and running conceptual, empirical, and technical investigations significantly increases analysis and coordination cost, and different stakeholders' rankings of the same value often cannot be reconciled once and for all in a single study.
Conditional rules · Editorial advice
Related entries
Human-centered design focuses on direct observation of and iterative evaluation with users; Value Sensitive Design's scope is broader, also covering indirect stakeholders who never use the product and the values they hold.
Privacy realized through protective defaults is a common way Value Sensitive Design turns an identified value into a concrete technical investigation.
Knowing whose values are affected and who bears the consequences of a misjudgment provides the basis for deciding which stakeholders should see which confidence signals.
Sources and what they support
Defines Value Sensitive Design as a method for systematically accounting for human values throughout the design process, describes the integrative, iterative tripartite methodology of conceptual, empirical, and technical investigations, and divides stakeholders into direct and indirect classes, noting that indirect stakeholders are often ignored in the design process.
Retrieved: 2026-09-15 · Archived 2026-09-16Summarizes Value Sensitive Design as originating from Batya Friedman and colleagues' work in the 1990s, describes the integrative tripartite methodology of conceptual, empirical, and technical investigations, and mentions tools such as stakeholder cards for identifying direct, indirect, and excluded stakeholders.
Retrieved: 2026-09-15 · Archived 2026-09-16Lists Friedman & Hendry's 'Value Sensitive Design: Shaping Technology with Moral Imagination' (MIT Press, 2019) as the authoritative account of the methodology, along with Friedman's earlier foundational 1996 and 2004 publications.
Retrieved: 2026-09-15 · Archived 2026-09-16Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.
Type extensions and implementation notes
No operable specimen yet; the illustration is editorial. When applied to a product, still verify: whether indirect stakeholders were actually identified and reached, whether all three of the conceptual, empirical, and technical investigations were carried out rather than just one, and whether the record of how value tensions were adjudicated is traceable.
{
"values": [
"Systematically identifying human values",
"Accounting for both direct and indirect stakeholders",
"Iterating through conceptual, empirical, and technical investigations"
],
"tension": "The tension between direct stakeholders' immediate demands and the diffuse, harder-to-voice values of indirect stakeholders",
"questions": [
"Whose values does this decision involve, and to whom do they matter most?",
"Is there anyone who never uses this product but will still be affected by it?"
]
}Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.