Description
Systematically questions who and what is included in or excluded from a system's design, revealing the value judgements behind boundaries and whose interests are served.
Every system design draws boundaries: who counts as a user, what problems are in scope, what knowledge counts. Ulrich's Critical Systems Heuristics provides 12 boundary questions grouped into four sources of influence (motivation, control, knowledge, legitimacy), each asked in 'is' and 'ought' modes: who is the beneficiary, who should be? Who decides? What expertise is relied on? Who represents those affected but not involved? Midgley adds analysis of marginalised groups and conflicting boundaries. In UX, boundary critique exposes stakeholders and harms outside the design scope, such as people affected by AI decisions who never use the product. Rigour comes from structured use of all 12 questions and including affected stakeholders in answering them.
Attributes
- Discipline
- Systems & Complexity
- Loss type
- Unmigrated
- Stage
- Strategy, Definition
- Data
- Qualitative
- Effort
- Days
Steps
- Define the system under consideration and its current stated purpose.
- Answer Ulrich's 12 boundary questions in 'is' mode, based on documentation and interviews.
- Answer the same 12 questions in 'ought' mode with diverse stakeholders, including those affected but not involved.
- Compare 'is' and 'ought' answers to identify contested boundaries and marginalised groups.
- Decide which boundaries to change, documenting the rationale and trade-offs.
- Feed revised boundaries into research recruitment, requirements and evaluation criteria.
Sources
- Gopinath, V., Methods Atlas (DSRP protocol)
- PACT analysis (Dix; Benyon, Designing Interactive Systems)
- Methods Atlas — DSRP protocol (Gopinath)
- PACT analysis (Dix)
- The Inquiry Series, Ch 13 — DSRP Systems Thinking & Wicked Problems
Also known as
- Critical systems heuristics
- Boundary judgement analysis
Categories
- Strategy & Collaboration
- Systems & Complexity