Design as an algorithm, not as a feature

How can design cut a 90-minute process to just 6 minutes? By treating it as an algorithm, not a feature.

#1about 1 minute

Understanding the universal principles of design

All specialized design fields, from UI/UX to software design, originate from a single set of core principles that remain constant across domains.

#2about 4 minutes

Building an AI procurement bot for minor sourcing

Volkswagen addressed uncontrolled spending on small purchases by developing a three-bot system to automate sourcing, negotiation, and SAP integration.

#3about 4 minutes

Focusing on user objectives instead of objects

Effective design solves the user's underlying problem rather than just building what they ask for, requiring deep research into their context and goals.

#4about 4 minutes

Conducting comprehensive research across multiple domains

The design process begins with extensive research into user groups, data systems, business processes, and stakeholder needs to build deep domain knowledge.

#5about 5 minutes

Aligning stakeholders through co-creation and visualization

Involving all key stakeholders in the ideation process and using visualization helps to align everyone's understanding and define clear product hypotheses.

#6about 3 minutes

Developing the bot's technical and conversational framework

The bot's framework was designed by defining data parsing logic, system architecture, conversational dialogue flows, and selecting the right technology stack.

#7about 3 minutes

Using design to create workarounds for bad data

Instead of being blocked by imperfect legacy data, design workarounds can leverage human intelligence to overcome technical limitations and keep the process moving.

#8about 8 minutes

Validating the product through user testing and metrics

Rigorous user testing in multiple locations validated the bot's effectiveness, showing a dramatic reduction in order time from 90 minutes to just 6 minutes.

#9about 3 minutes

Viewing design as an algorithm, not a feature

Design is not an aesthetic feature added at the end, but an end-to-end process that functions like an algorithm to find the optimal solution between competing domains.

#10about 5 minutes

Q&A on frontend-first design and service design

The discussion covers the benefits of a frontend-first approach, the connection between service design and sequence-based design, and details of the bot's functionality.