Analyzing Deceptive Design (Dark Patterns) in Technology

Activity Overview

In this activity, participants will explore deceptive design practices (also known as dark patterns) in websites, apps, and digital services. These are design strategies that manipulate users into making choices they wouldn’t normally make—such as accidentally signing up for a subscription, sharing personal data, or making unintended purchases.

Each team will:

  1. Pick a real-world deceptive design case from Deceptive.Design.
  2. Conduct deeper research using web searches and AI tools to find similar cases and broader industry trends.
  3. Analyze the ethical, legal, and user experience implications of the case.
  4. Answer thought-provoking questions about the case.
  5. Prepare and deliver a 5-minute presentation to the class.

Step-by-Step Instructions

1. Divide the Class into 7 Teams (2 min)

  • Form 7 teams of 3-4 students each.
  • Assign each team a category of deceptive design from the list below.
  • Teams will choose a specific real-world case within their category from Deceptive.Design.

2. Case Study Selection (5 min)

Each team will pick one deceptive design case from the Deceptive.Design archive related to their assigned category:

Categories of Deceptive Design (Each Assigned to One Team)

  1. Sneaking – Practices that add charges, subscriptions, or personal data collection without clear user consent.
    (Example: Airlines adding hidden fees at checkout.)
  2. Forced Action – Making users do something unwanted to access a feature.
    (Example: Facebook requiring users to enable tracking to continue using the app.)
  3. Obstruction – Making canceling or opting out intentionally difficult.
    (Example: Gym memberships that require calling a support line to cancel.)
  4. Misdirection – Guiding users toward choices that benefit the company at their expense.
    (Example: Amazon’s confusing design that makes it easier to start a Prime trial than opt out.)
  5. Hidden Costs – Surprise fees or extra charges that appear late in the checkout process.
    (Example: Ticketmaster adding high service fees at the last step of booking.)
  6. Privacy Exploitation – Tricking users into sharing more data than they intended.
    (Example: Google auto-enrolling users into location tracking.)
  7. Confirmshaming – Guilt-tripping users into making a choice they might not want to.
    (Example: A pop-up that says “No thanks, I like being broke” when declining an offer.)

3. Research & Deep Dive (20 min)

Each team will use web searches and AI tools to gather more information on their selected case and similar examples.

Key Areas to Research:

  • Company Involved: Who is responsible for this deceptive design?
  • How It Works: Explain how the deceptive design tricks users into making unwanted decisions.
  • Impact on Users: What negative consequences do users experience? (Financial loss, frustration, privacy invasion, etc.)
  • Legal & Ethical Issues: Has this practice led to lawsuits, fines, or regulatory actions?
  • Similar Cases: Find other companies using similar tactics.
  • Solutions & Recommendations: What should companies, regulators, or users do to prevent this?

4. Discussion Questions (Teams Must Answer)

Each team will discuss and answer the following to prepare their presentation:

  1. How does the deceptive design pattern work in your case?
  2. What psychological tricks are being used to manipulate users?
  3. How does this benefit the company financially or strategically?
  4. What are the negative consequences for users?
  5. Has this company or a similar one faced legal action or public backlash?
  6. What regulations or policies exist (or should exist) to prevent this?
  7. What ethical considerations should software designers keep in mind to avoid deceptive design?
  8. What would be a better, more ethical way for the company to achieve its goals?

5. Presentations (10 min)

Each team will give a 5-minute presentation covering:

  • A summary of the case
  • The ethical & legal concerns
  • Similar cases & trends
  • Their recommendations to fix or prevent it

Post-Activity Class Discussion

After presentations, discuss:

  • Which deceptive design tactics seem most harmful?
  • Should deceptive design be illegal, or is it just “smart business”?
  • What role should software engineers play in resisting deceptive design?

Assessment & Learning Goals

By the end of this activity, students will:

✅ Identify real-world deceptive design tactics
✅ Analyze how deceptive design impacts users
✅ Discuss the ethical and legal implications
✅ Explore solutions for ethical UI/UX design
✅ Improve team collaboration and research skills

Scroll to Top