Background

Ep 84 Design: The need for ethical design

  • cover play_arrow

    PLAY EPISODE


Best Of
Best Of
Show notes arrow_drop_down

Show notes

Design has reached a tipping point. It’s no longer just about usability or aesthetics—it’s about the lasting impact we have on society, psychology, and culture. In this critical episode, Stephen Gates explores why ethical design must become a fundamental part of our creative process. Through examples like Pokémon Go and Snapchat, he illustrates how unintended consequences can quickly turn into real-world harm. And most importantly, he outlines practical, powerful ways to embed ethics into how we think, work, and build.

 

What you’ll learn:

• Why ethics in design isn’t about right or wrong—it’s about unintended outcomes

• The hidden dangers in popular apps like Pokémon Go and Snapchat

• How your work might be shaping behavior in ways you never considered

• Why accessibility, inclusivity, and accountability are core design responsibilities

• The five actions every creative team must take to build ethically and intentionally

 

Key Themes & Takeaways:

  1. Design’s growing influence: As digital experiences scale, so does their power to shape culture, behavior, and even mental health.

  2. Unseen ethical risks: Ethical problems often arise not from bad intentions—but from blind spots, silos, or failing to ask the right questions early.

  3. Pre-mortems over PR damage control: Think ahead. Ethical planning starts before launch—not after a public crisis.

  4. Design is not neutral: Your choices send signals. They shape behavior. Every interface is a conversation.

  5. You can’t QA for ethics after launch: Build processes that test for behavior, not just bugs. Review impact, not just performance.

 

Ethical Design Action Framework:

• Pre-mortem meetings: Ask, “How could this fail ethically?” before a line of code is written.

• Break the silos: Teams must understand the whole user journey—not just their slice.

• User reality checks: Watch real people use your product without prompts or scripts.

• Design with fresh eyes: Invite people not involved in the build to try and break it—ethically.

• Post-mortems for people, not just process: After launch, revisit decisions to understand real-world effects—not just workflow efficiency.

 

Bold Close:

Being a good person doesn’t automatically mean you’re building good things. Design ethics must be built in—not bolted on. If your company says they care about it, push for proof. Budget. Headcount. Authority. Otherwise, it’s just lip service. Because if we don’t choose ethics now, we’ll be forced to answer for our inaction later.

 

Tagged as:

0%

Login to enjoy full advantages

Please login or subscribe to continue.

✖

Go Premium!

Enjoy the full advantage of the premium access.

✖

Stop following

Unfollow Cancel

✖

Cancel subscription

Are you sure you want to cancel your subscription? You will lose your Premium access and stored playlists.

Go back Confirm cancellation

✖