Product managers & designers working with AI face a unique challenge: designing a delightful product experience that cannot fully be predicted. Traditionally, product development followed a linear path. A PM defines the problem, a designer draws the solution, and the software teams code the product. The outcome was largely predictable, and the user experience was consistent. However, with AI, the rules have changed. Non-deterministic ML models introduce uncertainty & chaotic behavior. The same question asked four times produces different outputs. Asking the same question in different ways - even just an extra space in the question - elicits different results. How does one design a product experience in the fog of AI? The answer lies in embracing the unpredictable nature of AI and adapting your design approach. Here are a few strategies to consider: 1. Fast feedback loops : Great machine learning products elicit user feedback passively. Just click on the first result of a Google search and come back to the second one. That’s a great signal for Google to know that the first result is not optimal - without tying a word. 2. Evaluation : before products launch, it’s critical to run the machine learning systems through a battery of tests to understand in the most likely use cases, how the LLM will respond. 3. Over-measurement : It’s unclear what will matter in product experiences today, so measuring as much as possible in the user experience, whether it’s session times, conversation topic analysis, sentiment scores, or other numbers. 4. Couple with deterministic systems : Some startups are using large language models to suggest ideas that are evaluated with deterministic or classic machine learning systems. This design pattern can quash some of the chaotic and non-deterministic nature of LLMs. 5. Smaller models : smaller models that are tuned or optimized for use cases will produce narrower output, controlling the experience. The goal is not to eliminate unpredictability altogether but to design a product that can adapt and learn alongside its users. Just as much as the technology has changed products, our design processes must evolve as well.
User Experience Design Trends for Data-Driven Design Decisions
Explore top LinkedIn content from expert professionals.
Summary
Data-driven design decisions in user experience (UX) use data, analytics, and trends to create interfaces that align with user behavior and expectations. By integrating these insights, companies can design smarter, more intuitive experiences, particularly for AI-powered products and evolving customer needs.
- Embrace adaptable systems: Design for unpredictability, especially with AI-driven solutions, by incorporating feedback loops, robust testing, and flexible models tailored to real-world user behavior.
- Personalize experiences: Use data to create hyper-personalized interactions that cater to individual users, ensuring the interface continuously improves and feels intuitive.
- Simplify user journeys: Eliminate unnecessary complexity by focusing on instant, seamless, and clear experiences that meet users’ needs with minimal effort or confusion.
-
-
Work on designing AI-first assistant and agent experiences has been eye opening. AI UX is both fundamentally the same and widely different, especially for vertical use cases. There are clear and emerging patterns that will likely continue to scale: 1. Comfort will start with proactive intelligence and hyper personalization. The biggest expectation customers have of AI is that it’s smart and it knows them based on their data. Personalization will become a key entry point where a recommendation kicks off a “thread” of inquiry. Personalization should only get better with “memory”. Imagine a pattern where an assistant or an agent notifies you of an anamoly, advice that’s specific to your business, or an area to dig deeper into relative to peers. 2. There are two clear sets of UX patterns that will emerge: assistant-like experiences and transformative experiences. Assistant-like experiences will sound familiar by now. Agents will complete a task partially either based on input or automation and the user confirms their action. You see this today with experiences like deep search. Transformative experiences will often start by human request and will then become background experiences that are long running. Transformative experiences, in particular, will require associated patterns like audit trails, failure notifications, etc. 3. We will start designing for agents as much as we design for humans. Modularity and building in smaller chunks becomes even more important. With architecture like MCP, the way you think of the world in smaller tools becomes a default. Understanding the human JTBD will remain core but you’ll end up building experiences in pieces to enable agents to pick and choose what parts to execute in what permutation of user asks. 4. It’ll become even more important to design and document existing standard operating procedures. One way to think about this is a more enhanced more articulated version of a customer journey. You need to teach agents the way not just what you know. Service design will become an even more important field. 5. There will be even less tolerance for complexity. Anything that feels like paperwork, extra clicks, or filler copy will be unacceptable; the new baseline is instant, crystal‑clear, outcome‑focused guidance. No experience, no input, no setting should start from zero. Just to name a few. The underlying piece is that this will all depend on the culture design teams, in particular, embrace as part of this transition. What I often hear is that design teams are already leading the way in adoption of AI. The role of Design in a world where prototyping is far more rapid and tools evolve so quickly will become even more important. It’ll change in many ways (some of it is by going back to basics) but will remain super important nonetheless. Most of the above will sound familiar on the surface but there’s so much that changes in the details of how we work. Exciting times.
-
Ever looked at a UX survey and thought: “Okay… but what’s really going on here?” Same. I’ve been digging into how factor analysis can turn messy survey responses into meaningful insights. Not just to clean up the data - but to actually uncover the deeper psychological patterns underneath the numbers. Instead of just asking “Is this usable?”, we can ask: What makes it feel usable? Which moments in the experience build trust? Are we measuring the same idea in slightly different ways? These are the kinds of questions that factor analysis helps answer - by identifying latent constructs like satisfaction, ease, or emotional clarity that sit beneath the surface of our metrics. You don’t need hundreds of responses or a big-budget team to get started. With the right methods, even small UX teams can design sharper surveys and uncover deeper insights. EFA (exploratory factor analysis) helps uncover patterns you didn’t know to look for - great for new or evolving research. CFA (confirmatory factor analysis) lets you test whether your idea of a UX concept (say, trust or usability) holds up in the real data. And SEM (structural equation modeling) maps how those factors connect - like how ease of use builds trust, which in turn drives satisfaction and intent to return. What makes this even more accessible now are modern techniques like Bayesian CFA (ideal when you’re working with small datasets or want to include expert assumptions), non-linear modeling (to better capture how people actually behave), and robust estimation (to keep results stable even when the data’s messy or skewed). These methods aren’t just for academics - they’re practical, powerful tools that help UX teams design better experiences, grounded in real data.