INF2170H Chap.8 Ethics, Consequences and Professional Practice
Ethics, Consequences and Professional Practice
Make structural consequences visible
The final course block names dark patterns, commerce, classification consequences and professional synthesis.
Because the assigned later readings are not captured, this chapter stays with a grounded method: record the visible options, identify the affected decision, explain which route or category becomes easier, and propose a repair that can be retested.
Preserve ambiguity and responsibility
Classification can turn ambiguous phenomena into stable values that downstream search, reporting and action inherit.
The chapter shows ways to record overlapping or unresolved cases, maps dependencies and closes a design argument with evidence, consequence, ownership and a review trigger.
Describe the structural effect before assigning motive
Record the options, wording, order and point where consequences become visible. Identify the user decision and compare the routes offered for competing choices.
A design can make one outcome easier without the interface alone proving deliberate deception. State the observed effect, the organisational incentive and the evidence that would be needed for a motive claim. This preserves critical analysis without turning suspicion into fact.
Ask whose knowledge the structure assumes. Experienced users may recognise an internal label that newcomers cannot interpret.
A route can be technically complete while placing the cost of orientation on people least familiar with the organisation. The repair can make consequences comparable, add an alternate route or expose the missing context before commitment.
Retest whether participants can explain each outcome rather than merely complete the favoured path.
Keep ambiguity from disappearing downstream
Discrete categories enable search and reporting, but they can erase overlap. Use repeatable values, broader classes, related terms, review status or notes when uncertainty affects later decisions.
Avoid leaving a growing set of difficult items in “other.” That residual is evidence that the universe, characteristic or value set needs review. Preserve the old value and migration rationale when historical reports depend on earlier boundaries.
Map every downstream consumer before changing the classification. Search filters, recommendations, reports and staffing decisions may inherit the same rule.
A professional proposal therefore includes affected systems, ownership, review triggers and verification. The closing claim should connect problem, evidence, structural response and consequence at the scale studied. It should also say what remains untested and how the architecture will be corrected when new content or user evidence challenges the current boundary.
What this chapter covers
- 01
Structural consequences
- 02
Affected choices
- 03
Classification ambiguity
- 04
Downstream inheritance
- 05
Professional evidence
- 06
Responsible maintenance
Worked example · free
Review an account renewal route
- 2Record both visible routes.
- 3Identify the affected decision and effect.
- 2Design a comparable disclosure and retest.
Key terms
- Boundary Consequence
- Boundary Consequence is the downstream effect created when a classification includes, excludes or obscures a case.
- Ambiguity Record
- Ambiguity Record preserves overlapping, contested or unresolved classification evidence for later review.
- Professional Rationale
- Professional Rationale links a structural decision to evidence, consequence, ownership and future verification.
Ethics, Consequences and Professional Practice FAQ
How can a consequential design be analysed without claiming intent?
Record the options, wording, sequence and point where consequences become visible. Explain how the structure makes one route easier or another harder, and note organisational incentives only as context. Motive requires separate evidence that the interface alone does not supply.
Why should ambiguity be preserved in a schema?
Discrete values can support retrieval while hiding overlap or contested cases. Use repeatable values, broader classes, related terms, review status or notes when ambiguity affects interpretation. Map downstream consumers so a boundary repair reaches search, reporting and action.
What makes a final design argument professional?
It defines the information problem, documents evidence, explains the schema or route, tests an uncertain assumption and addresses consequences. It also names ownership, review triggers and verification so the architecture can change without losing the rationale behind earlier decisions.
Assessment move
Practise moving from visible structure to affected decision, evidence, consequence and repair. Avoid unsourced taxonomies for later course topics. For the project, audit every recommendation for scope, alternate access, maintenance responsibility and the next test. Start with a reproducible observation: the options, labels, sequence and point where consequences become visible.
Identify whose decision is shaped and which route becomes easier, harder or less reversible. Separate demonstrated effects from claims about designer intent. If intent is not evidenced, describe the structural alignment and user consequence without assigning motive. Review classification boundaries for excluded or ambiguous cases, then choose a representation such as repeatable values, review status or a documented exception.
Map every downstream consumer that inherits the boundary so a repair reaches search, reporting and recommendations as well as the visible interface. Compare the proposed change with legal, operational and technical constraints, but do not treat a constraint as a reason to conceal unequal information. Record whose vocabulary and experience informed the evaluation.
Finish with a scoped claim, an alternate route for affected users, an accountable owner and a test of comprehension or recovery. Professional judgment remains strongest when its evidence and limits are explicit.
