Design Ethics & Dark Patterns
As designers, we shape how millions of people interact with technology. This power comes with responsibility. Design ethics examines the moral implications of design decisions — from addictive scrolling patterns to deceptive 'dark patterns' that trick users into actions they didn't intend. Understanding ethics isn't just philosophically important — it's increasingly legally mandated to avoid deceptive practices. The EU's Digital Services Act, California's CCPA, and the FTC's crackdown on dark patterns all signal that ethical design is becoming a regulatory requirement. This module explores what ethical design looks like in practice, how to identify and avoid dark patterns, and how to advocate for user rights within your organization.
What are Dark Patterns?
Dark patterns are deceptive design techniques that trick users into doing things they didn't intend — signing up for newsletters, purchasing add-ons, or sharing personal data. The term was coined by UX researcher Harry Brignull in 2010. Dark patterns exploit cognitive biases — the mental shortcuts our brains use to make decisions quickly. By exploiting these shortcuts, designers can manipulate behavior in ways users don't consciously recognize. There are several common categories: Trick Questions use confusing language ('Uncheck this box to not unsubscribe from not receiving emails'). Hidden Costs reveal unexpected charges at checkout. Confirmshaming uses guilt-tripping copy ('No thanks, I don't want to save money'). Forced Continuity makes cancellation deliberately difficult. Roach Motels make it easy to sign up but nearly impossible to leave. Disguised Ads make advertisements look like content or navigation. These patterns may boost short-term metrics but destroy long-term trust. Amazon's Prime cancellation flow, which required users to navigate through multiple pages of retention offers, faced regulatory action in the EU.
Design patterns = reusable solutions to common design problems
Principles of Ethical Design
- Transparency: Users should always understand what they're agreeing to. If your Terms of Service require a law degree to parse, you've failed at transparency. Write in plain language, show costs upfront, and make privacy settings obvious
- Informed consent: Users should actively choose to opt in, not be tricked into it. Pre-checked checkboxes, auto-enrollment, and buried opt-outs all violate informed consent. GDPR mandates affirmative consent for data collection in the EU
- Reversibility: Users should be able to undo any action easily. If signing up takes one click, cancellation shouldn't take 15 steps. The 'roach motel' pattern (easy to enter, hard to leave) is both unethical and increasingly illegal
- Proportionality: Collect only the data you need. If a flashlight app asks for contact access, that's disproportionate data collection. Design data requests that match the functionality users are seeking
- Inclusivity: Design for the full spectrum of users — including those with disabilities, limited literacy, or different cultural contexts. Ethical design is inherently inclusive design
How to Advocate for Ethical Design
- Name the pattern: When a stakeholder asks you to make the unsubscribe link smaller or add a confirmshaming modal, name it: 'That's a dark pattern — it may boost short-term metrics but risks regulatory fines and user trust erosion'
- Show the data: Companies like Booking.com faced regulatory action for using fake urgency ('Only 2 rooms left!'). Present case studies of companies that suffered consequences for dark patterns
- Propose ethical alternatives: Instead of 'No thanks, I hate saving money' (confirmshaming), write 'No thanks' — it respects the user's choice and still provides the opt-out. You can advocate for users and still meet business goals
- Use an ethics checklist: Before shipping any feature, ask: Would I be comfortable if a journalist wrote about how this feature works? Would I be okay if my family were the users? Does this design respect the user's time, attention, and autonomy?
- Know the regulations: GDPR (EU), CCPA (California), Digital Services Act (EU), and FTC guidelines all restrict deceptive design. Ethical design isn't just moral — it's risk management
Tip
Tip
Practice Design Ethics Dark Patterns in small, isolated examples before integrating into larger projects. Breaking concepts into small experiments builds genuine understanding faster than reading alone.
Practice Task
Note
Practice Task — (1) Write a working example of Design Ethics Dark Patterns from scratch without looking at notes. (2) Modify it to handle an edge case (empty input, null value, or error state). (3) Share your solution in the Priygop community for feedback.
Quick Quiz
Common Mistake
Warning
A common mistake with Design Ethics Dark Patterns is skipping edge case testing — empty inputs, null values, and unexpected data types. Always validate boundary conditions to write robust, production-ready ui ux code.
Key Takeaways
- As designers, we shape how millions of people interact with technology.
- Transparency: Users should always understand what they're agreeing to. If your Terms of Service require a law degree to parse, you've failed at transparency. Write in plain language, show costs upfront, and make privacy settings obvious
- Informed consent: Users should actively choose to opt in, not be tricked into it. Pre-checked checkboxes, auto-enrollment, and buried opt-outs all violate informed consent. GDPR mandates affirmative consent for data collection in the EU
- Reversibility: Users should be able to undo any action easily. If signing up takes one click, cancellation shouldn't take 15 steps. The 'roach motel' pattern (easy to enter, hard to leave) is both unethical and increasingly illegal