Ethics in Architecture
The consequences of architectural decisions for people who did not choose them — and the architect's responsibility for the ones that are foreseeable.
Definition
Architectural decisions have consequences for people outside the organisation, and many of those consequences are determined at design time by people who will never meet them.
Where architecture carries ethical weight
Data collection. Every field collected is a field that can be breached, subpoenaed, sold or misused. Minimisation is both a security control and an ethical position, and it is decided in the data model.
Retention. How long personal data is kept is an architectural decision with real consequences for people, and the default — forever, because nobody set a policy — is a choice.
Algorithmic consequence. A ranking, pricing, matching or moderation system affects people's opportunities and outcomes. Whether it is auditable, whether its decisions can be explained, and whether there is a route to challenge one are architectural properties.
Accessibility. Decisions about client architecture, latency budgets and payload sizes determine whether people with slower connections, older devices or assistive technology can use the product.
Environmental cost. Compute has a footprint, and efficiency is an architectural property.
Failure asymmetry. Who bears the cost when the system is wrong? A false decline inconveniences a customer; a false approval may cost them money. Systems should be designed so errors fall where they are recoverable.
The questions worth asking in a design review
- What is the worst thing this could be used for, by us or by someone who acquires us?
- Who is harmed if this is wrong, and can they tell?
- Is there a route to challenge or correct an automated decision?
- What are we collecting that we do not need?
- Who cannot use this, and was that a decision or an oversight?
None of these require a philosophy background. They require asking.
The practical position
Architects are frequently the last people who see the whole system and the first who could raise a concern cheaply. Raising it early is a design conversation; raising it after launch is an incident.
Where a concern is not accepted, record it. That is not defensive paperwork — it is how an organisation's decisions remain visible to itself.
Interview question
"What ethical questions belong in an architecture review, and who should raise them?"