Interview with Yao Morin
summary
Argues that a data-driven UX learns from live user behavior to deliver unique experiences per user rather than designer guesses, and requires three concrete components: real-time data pipeline, persistent storage and an online model-serving platform that returns decisions to the application. Distinguishes personalization (user-chosen playlists, font size) from global data-driven features like dynamic pricing. Warns of hard costs: engineering to build pipelines, more complex testing, and hiring data scientists, and demands a clear business use case before investing.
AI-written summary · about
chapters (5)
- 0:00Intro
- 1:16Components of a datadriven application
- 2:46Personalization vs datadriven
- 4:12Should organizations consider personalization
- 7:00Conclusion
related talks
04mHighlights - Data and Business
20mUsers acquired - Now what?: Maximising revenue from existing players
35mBuilding Data-Intensive Teams
23mCustom-made games with machine learning and big data
48mPersonalization in 10 Milliseconds
40mDesign for Data
49mPanel discussion - Building Data Products
31mA Feasibility of On-Device ML for Adaptive User Interfaces in Frontend Development