WorkshopsWorkshop Day · 15 September · Additional fee

Future of design

Wearing blinders

September 4, 2023 3:45 PM

Long Lecture

🇵🇱 Polish

Bratysława 1

About

Does strict specialization in our industry truly lead to better design? Is it beneficial for our creativity and innovation, or might it restrict us by introducing rigid thinking frameworks?Do these rigid frameworks of thought inadvertently trap us in our own bubble, thus limiting our perspective on the broader context?

Talk by

Photo of Sebastian Woźniak, Nucleus AI Platform Designer at UBS

Sebastian Woźniak

Nucleus AI Platform Designer at UBS

Watch the full talk

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

Explore the 2026 agenda More WaysConf recordings

From the recording

Talk in brief

Digital product teams develop blind spots when they treat a textbook process, professional silo, or design role as the whole reality. This Polish-language talk contrasts embodied offline experience with abstract digital work, challenges rigid adoption of methods, and examines how functional structures isolate design, development, analytics, and product ownership. It argues that failed experiments can still create organizational learning, that product operations often means translation across disciplines, and that designers should leave their own bubble by studying colleagues, history, ergonomics, and the wider system producing the interface.

Key takeaways

01
Digital work can flatten lived experience
Designers should remember that human experience is sensory, social, and contextual rather than only a sequence of screens.
Watch from 1:15
02
Adapt methods to the environment
A process should reflect the people, maturity, constraints, and quality of work present instead of reproducing a book diagram.
Watch from 7:35
03
Count learning even when delivery fails
An unsuccessful project can still improve how a product partner and team collaborate on the next attempt.
Watch from 11:16
04
Functional silos create duplicated certainty
Teams optimize their own targets and can unknowingly solve the same problem several times without sharing context.
Watch from 14:51
05
Designers must widen their reference frame
Understanding colleagues, production history, ergonomics, and adjacent disciplines reduces the belief that design alone drives outcomes.
Watch from 23:01

Video chapters

1:15Embodied experience versus digital abstraction
Sensory memory introduces the limits of treating human experience as interface behavior.
4:21Designed objects that disappear into life
Everyday products show how design can function without drawing attention to its authorship.
7:35Why process must fit its organization
Methods are challenged when they ignore actual people, constraints, and delivery conditions.
11:16Failure as collaboration training
A project can produce reusable team learning even when the intended outcome does not ship.
14:51Blind spots built by functional silos
Separate goals and leadership structures encourage duplication and narrow optimization.
18:55Product operations as translation
Cross-functional work requires people who can translate intent between design, product, and engineering.
23:01Leaving the designer’s own bubble
The close calls for broader references, conversation, and respect for knowledge outside design.

Read edited transcript highlights

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

Human experience is larger than an interface

People remember the smell of rain, physical effort, accidents, joy, and other embodied events differently from a digital flow. Interface work can make experience feel abstract and controllable, but the person using the product still lives in a sensory and social world. Designers need that wider frame when judging what an interaction means.

Watch from 1:15

A method is useful only inside its real context

No process should be imported unchanged simply because it appears in a course or book. Teams differ in capability, trust, constraints, and the quality they can produce. The method should be adjusted to that environment and revisited as it changes. Calling a process agile or user-centered does not make it so.

Watch from 7:35

A failed project can still improve the next one

An experiment may not deliver the expected result, yet the product owner can learn how to work with designers and the team can learn where its assumptions failed. That collaboration knowledge is a real outcome. Treating every miss as worthless encourages safer projects and prevents the organization from reusing what it learned.

Watch from 11:16

Silos optimize locally and duplicate globally

Design, development, analytics, and other functions often have leaders, targets, and reporting lines that reward attention to their own domain. Each group can be competent while the organization repeats work or produces several versions of the same control. The blind spot comes from the structure, not from individual bad intent.

Watch from 14:51

Professional humility expands design quality

Designers should ask what colleagues know, study the history behind established practices, and connect interface decisions with ergonomics, engineering, and production. Believing that the first designer or the design process is automatically the center of the product narrows the work. Better outcomes appear when disciplines translate and learn from one another.

Watch from 23:01

Explore WaysConf 2026

View the agenda

Get tickets