Episode #85: Durable UX Methods and Ethical Design with Julia DeBari

Julia DeBari's UX career reaches back to the era of Flash animations and early rich web experiences. At her first design studio, the team built what she describes as a no-code website builder in 2000 using Flash. She later worked at Macromedia during its acquisition by Adobe. That long view gives her a useful standard for evaluating design practice: technologies and deliverables evolve, but the underlying work of understanding people, systems, and movement through an experience remains essential.

Julia now serves as head of design operations at the Copenhagen Institute of Interaction Design. In this conversation, she examines durable UX methods, research interviewing, accessibility, behavioral science, AI, and the organizational barriers between design, engineering, product, and business teams. Her message is practical. Many useful methods already exist, but teams often blur their meaning, omit them from portfolios, or fail to use them across organizational boundaries.

What you'll learn

• Why user flows remain distinct from wireflows and screen flows

• How service blueprints expose gaps between channels and support systems

• What careful interviewing and behavioral science contribute to design decisions

• How designers can incorporate basic accessibility into routine delivery

• Why ethical product work must support existing customers as well as acquisition

Preserve the methods that reveal the whole experience

User flows are one of Julia's clearest examples of a durable practice. Boxes and arrows show how a person moves among screens before visual details take over. Wireflows and screen flows have expanded the available vocabulary, but combining all three terms can erase the specific role of information architecture. Julia says she had seen only one proper user flow during eight months of reviewing hundreds of portfolios. For designers, learning the distinction is not academic. It demonstrates the ability to reason about an experience before polishing interfaces.

Service blueprints offer a broader systems view. Companies commonly assign web, mobile, hardware, and other channels to separate teams that communicate poorly, even while customers experience them as one service. A blueprint maps those channels and the support systems that make them work. It can reveal barriers that an isolated screen design cannot. Julia believes the industry already has this answer in its toolbox but does not use it enough.

Research fundamentals are similarly stable. Listening, asking open-ended questions, and avoiding leading language still require practice. Julia notes how one familiar closing question has become more precise. Instead of broadly asking what someone would change with a magic wand, a researcher can ask what functionality or feeling the participant would change. More specific nouns and verbs can produce more articulate answers without steering the person toward a preferred solution.

Connect behavioral science and accessibility to delivery

Julia recommends the Cogload Cookbook as a resource that analyzes digital experiences through behavioral science and proposes improvements. She gives pricing pages as a simple example: for Western readers, behavioral science suggests placing the most expensive choice on the left and the least expensive on the right, with the expectation that people often select the middle option. The wider lesson is to understand why familiar patterns influence behavior rather than copying a template without scrutiny.

Accessibility presents a different gap between available knowledge and organizational action. Information is widely accessible, yet business priorities still determine whether teams allocate time and money to inclusive work. Designers therefore need to persuade product and engineering partners, but Julia also points to improvements that can become routine. Color contrast, for example, can be handled in design and implemented with engineering without turning it into a massive separate initiative. Small, consistent steps can improve the product while larger advocacy continues.

She applies the same pragmatic view to AI. UX research skills remain valuable because she does not expect AI to replace that human work soon, while AI may help streamline processes. Prompt engineering and careful handling of personal information are relevant skills, but designers do not need to treat responsible practice as a thousand-hour study before taking any action.

Align product growth with long-term customer care

Julia describes design, engineering, and product as teams that were supposed to form a three-legged stool but too often operate as separate stools under one table. Design consistency becomes difficult when UX standards, engineering frameworks, and product deadlines are negotiated from isolated positions. Progress requires each discipline to understand the others' constraints and stop treating collaboration as a fight for its own team.

Business alignment is necessary because, as a former boss told Julia, without the business there is no job. That does not require accepting growth at any cost. She questions an acquisition focus that prizes new users while neglecting people who already pay for and use the product. If growth design concentrates on bringing people through the door, someone must remain responsible for their experience afterward. The ethical issue is not only how users are acquired, but how long the company continues to support them.

Listen to Episode #85 audio for Julia DeBari's full discussion of enduring UX methods, organizational collaboration, accessibility, AI, and ethical growth.