Design'ers Matter

Digital product design and ethics. How to develop good products the right way?

Long Lecture
🇵🇱 Polish

About

The talk will consider the role of Design in the context of the latest digital product development practices focusing particularly on the relationship between design and ethics.

Watch the full talk

Watch this WaysConf session, then continue with related talks or explore the current programme.

From the recording

Talk in brief

A team-level framework for ethical digital product development. The talk moves ethics away from abstract declarations and into everyday visibility, customer contact, goals, metrics, decision-making, and learning culture. Teams become unsafe when they fear evidence that contradicts assumptions, do not understand why they are building something, or replace behavioral data with confident opinions. Business goals still matter, but product goals should describe the customer behavior the team intends to change. Ethical practice means creating enough transparency and psychological safety to question the solution before harm is normalized.

Key takeaways

  1. 01

    Turn ethical principles into team routines

    Values become useful when they shape research, goal setting, decisions, measurement, and how uncertainty is discussed.

    Watch from 7:14
  2. 02

    Seek evidence that can contradict assumptions

    Avoiding customer contact protects internal confidence but increases the risk of building harmful or irrelevant behavior.

    Watch from 12:39
  3. 03

    Make purpose visible to every contributor

    A team cannot make responsible tradeoffs when half its members do not understand the goals and intended outcome.

    Watch from 18:13
  4. 04

    Connect business goals to customer behavior

    Product goals translate strategy into a measurable change for customers instead of repeating a sales or marketing target.

    Watch from 23:43
  5. 05

    Prefer observed behavior over reassuring opinion

    Behavioral evidence helps teams decide whether value appears in practice and reduces dependence on status or confidence.

    Watch from 29:41
Read edited transcript highlights

These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.

Ethics must appear in the operating process

A statement of values does not determine what happens during discovery, prioritization, implementation, or measurement. Teams need routines that make customer consequences, assumptions, ownership, and dissent visible. Ethical practice is the repeated ability to pause, ask who may be harmed, gather relevant evidence, and change direction before the cost is hidden inside normal delivery.

Watch from 7:14

Fear of customers is a warning about culture

Teams sometimes avoid research because customers may contradict the chosen direction in front of a senior sponsor. Language and access can be genuine barriers, but fear of being wrong is different. Leaders should reward early contradiction as saved investment and protect researchers and contributors who surface uncomfortable evidence rather than treating it as disloyalty.

Watch from 12:39

People need the goal to exercise judgment

A contributor who sees only a ticket cannot judge whether an implementation supports the intended outcome or creates an avoidable risk. Shared goals and constraints allow design, engineering, research, and operations to challenge a local instruction constructively. Visibility is therefore an ethical safeguard as well as a coordination practice.

Watch from 18:13

Product goals should describe a behavior change

Revenue, sales, and market objectives sit beyond the direct control of one product team. The team can identify the customer behavior and value that plausibly contribute to them, then measure whether the product supports that change. This translation makes commercial intent testable and reduces pressure to manipulate a surface metric disconnected from customer benefit.

Watch from 23:43

Learning requires safety around failed assumptions

Opinions dominate when experiments are dangerous to careers and failure is interpreted as incompetence. A healthier culture distinguishes a contained, evidence-producing test from careless execution. Teams can then use behavioral data to revise decisions, document what was learned, and stop weak solutions without searching for a person to blame.

Watch from 29:41
Explore WaysConf 2026