2026
2026
06
06
Context
Context
Behavior
Behavior
Context is the new content.
Context is the new content.
Context is the new content.
For most of the history of digital product design, content was a given. It existed before the user arrived. It would exist after they left. The designer's job was to organize it, present it, make it legible and accessible and appropriately weighted. The content itself was fixed. The design was the variable.
For most of the history of digital product design, content was a given. It existed before the user arrived. It would exist after they left. The designer's job was to organize it, present it, make it legible and accessible and appropriately weighted. The content itself was fixed. The design was the variable.
For most of the history of digital product design, content was a given. It existed before the user arrived. It would exist after they left. The designer's job was to organize it, present it, make it legible and accessible and appropriately weighted. The content itself was fixed. The design was the variable.
AI products have inverted this relationship. The content no longer exists before the user arrives. It is produced in response to them. What they see depends on what they asked, what they've done before, what the system has learned about them, and a dozen other variables that shift with every interaction.
AI products have inverted this relationship. The content no longer exists before the user arrives. It is produced in response to them. What they see depends on what they asked, what they've done before, what the system has learned about them, and a dozen other variables that shift with every interaction.
AI products have inverted this relationship. The content no longer exists before the user arrives. It is produced in response to them. What they see depends on what they asked, what they've done before, what the system has learned about them, and a dozen other variables that shift with every interaction.
The content is no longer the given. The context is.
The content is no longer the given. The context is.
The content is no longer the given. The context is.
What content meant before
What content meant before
What content meant before
In a traditional product, content is an artifact. It was created at a specific moment, by a specific person or process, and it persists. A product page has a description. A dashboard has data. A help article has instructions. The designer's work is to present that artifact in a way that serves the user's needs.
In a traditional product, content is an artifact. It was created at a specific moment, by a specific person or process, and it persists. A product page has a description. A dashboard has data. A help article has instructions. The designer's work is to present that artifact in a way that serves the user's needs.
In a traditional product, content is an artifact. It was created at a specific moment, by a specific person or process, and it persists. A product page has a description. A dashboard has data. A help article has instructions. The designer's work is to present that artifact in a way that serves the user's needs.
This assumption is so deeply embedded in how design works that most designers don't notice it. Design systems are built around it. Component libraries assume it. User research methods are structured around it. When you test a design, you test it with content that exists, that you can see and evaluate and compare across conditions.
This assumption is so deeply embedded in how design works that most designers don't notice it. Design systems are built around it. Component libraries assume it. User research methods are structured around it. When you test a design, you test it with content that exists, that you can see and evaluate and compare across conditions.
This assumption is so deeply embedded in how design works that most designers don't notice it. Design systems are built around it. Component libraries assume it. User research methods are structured around it. When you test a design, you test it with content that exists, that you can see and evaluate and compare across conditions.
AI products break this assumption completely. The content doesn't exist until the user asks for it. And when it does exist, it exists in a form shaped by everything the system knows about that user at that moment. Two users asking the same question get different answers. The same user asking the same question twice might get different answers. The content is not an artifact. It's an output. And every output is, in some meaningful sense, unique.
AI products break this assumption completely. The content doesn't exist until the user asks for it. And when it does exist, it exists in a form shaped by everything the system knows about that user at that moment. Two users asking the same question get different answers. The same user asking the same question twice might get different answers. The content is not an artifact. It's an output. And every output is, in some meaningful sense, unique.
AI products break this assumption completely. The content doesn't exist until the user asks for it. And when it does exist, it exists in a form shaped by everything the system knows about that user at that moment. Two users asking the same question get different answers. The same user asking the same question twice might get different answers. The content is not an artifact. It's an output. And every output is, in some meaningful sense, unique.
Designing for content that doesn't exist yet, that will be different for every user, in every context, at every moment, is a fundamentally different problem than organizing content that already exists. Most design practice hasn't caught up to this yet.
Designing for content that doesn't exist yet, that will be different for every user, in every context, at every moment, is a fundamentally different problem than organizing content that already exists. Most design practice hasn't caught up to this yet.
Designing for content that doesn't exist yet, that will be different for every user, in every context, at every moment, is a fundamentally different problem than organizing content that already exists. Most design practice hasn't caught up to this yet.
How context becomes the determining variable
How context becomes the determining variable
How context becomes the determining variable
In an AI product, context is everything the system knows when it produces an output. The user's current request. Their history with the product. The preferences they've expressed, explicitly or through behavior. The state of the conversation. The time, the platform, the device. The sum of every signal the system has accumulated about who this person is and what they're trying to do.
In an AI product, context is everything the system knows when it produces an output. The user's current request. Their history with the product. The preferences they've expressed, explicitly or through behavior. The state of the conversation. The time, the platform, the device. The sum of every signal the system has accumulated about who this person is and what they're trying to do.
In an AI product, context is everything the system knows when it produces an output. The user's current request. Their history with the product. The preferences they've expressed, explicitly or through behavior. The state of the conversation. The time, the platform, the device. The sum of every signal the system has accumulated about who this person is and what they're trying to do.
That context shapes the output more than any design decision the team has made. The same underlying model, presented through the same interface, produces radically different experiences for different users because their contexts are different.
That context shapes the output more than any design decision the team has made. The same underlying model, presented through the same interface, produces radically different experiences for different users because their contexts are different.
That context shapes the output more than any design decision the team has made. The same underlying model, presented through the same interface, produces radically different experiences for different users because their contexts are different.
This means the designer is no longer just deciding how to present content. They're deciding what context signals the system should use, how much weight to give them, when to surface them explicitly and when to let them operate invisibly, and how to handle the moments when the context is wrong or incomplete.
This means the designer is no longer just deciding how to present content. They're deciding what context signals the system should use, how much weight to give them, when to surface them explicitly and when to let them operate invisibly, and how to handle the moments when the context is wrong or incomplete.
This means the designer is no longer just deciding how to present content. They're deciding what context signals the system should use, how much weight to give them, when to surface them explicitly and when to let them operate invisibly, and how to handle the moments when the context is wrong or incomplete.
These are design decisions. They're just not decisions that most designers are currently making, because they sit at the boundary between design and engineering in a place where neither discipline has fully claimed ownership.
These are design decisions. They're just not decisions that most designers are currently making, because they sit at the boundary between design and engineering in a place where neither discipline has fully claimed ownership.
These are design decisions. They're just not decisions that most designers are currently making, because they sit at the boundary between design and engineering in a place where neither discipline has fully claimed ownership.
Context is not a technical detail to be handled by the backend. It's the primary material the user's experience is made of. Treating it as anything less means ceding the most important design decisions in the product to people who aren't thinking about the user.
Context is not a technical detail to be handled by the backend. It's the primary material the user's experience is made of. Treating it as anything less means ceding the most important design decisions in the product to people who aren't thinking about the user.
Context is not a technical detail to be handled by the backend. It's the primary material the user's experience is made of. Treating it as anything less means ceding the most important design decisions in the product to people who aren't thinking about the user.
What this changes for the designer
What this changes for the designer
What this changes for the designer
Designing with fixed content means designing states. You know what the user will see. You design the layout, the hierarchy, the interactions around a known artifact.
Designing with fixed content means designing states. You know what the user will see. You design the layout, the hierarchy, the interactions around a known artifact.
Designing with fixed content means designing states. You know what the user will see. You design the layout, the hierarchy, the interactions around a known artifact.
Designing with contextual content means designing systems of response. You don't know exactly what the user will see, because what they see depends on variables you can't fully control. Your job shifts from arranging known elements to defining the rules that govern how unknown outputs get presented.
Designing with contextual content means designing systems of response. You don't know exactly what the user will see, because what they see depends on variables you can't fully control. Your job shifts from arranging known elements to defining the rules that govern how unknown outputs get presented.
Designing with contextual content means designing systems of response. You don't know exactly what the user will see, because what they see depends on variables you can't fully control. Your job shifts from arranging known elements to defining the rules that govern how unknown outputs get presented.
This is a significant change in the nature of the work. It requires thinking about design at a level of abstraction that is genuinely unfamiliar to most practitioners.
This is a significant change in the nature of the work. It requires thinking about design at a level of abstraction that is genuinely unfamiliar to most practitioners.
This is a significant change in the nature of the work. It requires thinking about design at a level of abstraction that is genuinely unfamiliar to most practitioners.
Instead of designing a page, you're designing a container that has to work for outputs that vary in length, tone, structure, and content. Instead of designing a user flow, you're designing a framework flexible enough to accommodate paths that the user and the system will generate together in real time. Instead of designing for a specific user, you're designing for a spectrum of contexts that the same user might inhabit across different sessions.
Instead of designing a page, you're designing a container that has to work for outputs that vary in length, tone, structure, and content. Instead of designing a user flow, you're designing a framework flexible enough to accommodate paths that the user and the system will generate together in real time. Instead of designing for a specific user, you're designing for a spectrum of contexts that the same user might inhabit across different sessions.
Instead of designing a page, you're designing a container that has to work for outputs that vary in length, tone, structure, and content. Instead of designing a user flow, you're designing a framework flexible enough to accommodate paths that the user and the system will generate together in real time. Instead of designing for a specific user, you're designing for a spectrum of contexts that the same user might inhabit across different sessions.
The craft doesn't disappear. Typography still matters. Hierarchy still matters. Visual consistency still matters. But these are now in service of a system that produces variable outputs, not a product that presents fixed ones.
The craft doesn't disappear. Typography still matters. Hierarchy still matters. Visual consistency still matters. But these are now in service of a system that produces variable outputs, not a product that presents fixed ones.
The craft doesn't disappear. Typography still matters. Hierarchy still matters. Visual consistency still matters. But these are now in service of a system that produces variable outputs, not a product that presents fixed ones.
The designer who understands this stops asking "how do I present this content?" and starts asking "how do I design a system that presents any content well?" That shift in question leads to fundamentally different design decisions.
The designer who understands this stops asking "how do I present this content?" and starts asking "how do I design a system that presents any content well?" That shift in question leads to fundamentally different design decisions.
The designer who understands this stops asking "how do I present this content?" and starts asking "how do I design a system that presents any content well?" That shift in question leads to fundamentally different design decisions.
The problems contextual content creates
The problems contextual content creates
The problems contextual content creates
Designing for contextual content introduces problems that fixed content doesn't have.
Designing for contextual content introduces problems that fixed content doesn't have.
Designing for contextual content introduces problems that fixed content doesn't have.
Coherence across variation. When every user sees something different, how do you ensure the product feels like a consistent experience? The answer isn't uniformity of content. It's consistency of structure, tone, and interaction pattern. The container has to be stable enough that the variable content inside it doesn't feel chaotic.
Coherence across variation. When every user sees something different, how do you ensure the product feels like a consistent experience? The answer isn't uniformity of content. It's consistency of structure, tone, and interaction pattern. The container has to be stable enough that the variable content inside it doesn't feel chaotic.
Coherence across variation. When every user sees something different, how do you ensure the product feels like a consistent experience? The answer isn't uniformity of content. It's consistency of structure, tone, and interaction pattern. The container has to be stable enough that the variable content inside it doesn't feel chaotic.
Predictability within personalization. Users need to be able to form reliable expectations about how the product will behave, even if they can't predict exactly what it will produce. A product that surprises users in ways they can't anticipate or explain feels unreliable, even when every individual output is high quality.
Predictability within personalization. Users need to be able to form reliable expectations about how the product will behave, even if they can't predict exactly what it will produce. A product that surprises users in ways they can't anticipate or explain feels unreliable, even when every individual output is high quality.
Predictability within personalization. Users need to be able to form reliable expectations about how the product will behave, even if they can't predict exactly what it will produce. A product that surprises users in ways they can't anticipate or explain feels unreliable, even when every individual output is high quality.
The feeling of control over a system that's adapting to you. Personalization can feel like service or like surveillance, depending entirely on how it's surfaced. When the system clearly understands the user and responds to them as an individual, that feels valuable. When the user notices the system has been watching them and can't remember consenting to it, that feels uncomfortable. The line between the two is a design decision.
The feeling of control over a system that's adapting to you. Personalization can feel like service or like surveillance, depending entirely on how it's surfaced. When the system clearly understands the user and responds to them as an individual, that feels valuable. When the user notices the system has been watching them and can't remember consenting to it, that feels uncomfortable. The line between the two is a design decision.
The feeling of control over a system that's adapting to you. Personalization can feel like service or like surveillance, depending entirely on how it's surfaced. When the system clearly understands the user and responds to them as an individual, that feels valuable. When the user notices the system has been watching them and can't remember consenting to it, that feels uncomfortable. The line between the two is a design decision.
Handling context that's wrong. The system's model of the user is always incomplete and sometimes incorrect. When it produces an output that's clearly based on a misunderstanding of who the user is or what they want, the interface needs a path for the user to correct it without feeling like they're fighting the system.
Handling context that's wrong. The system's model of the user is always incomplete and sometimes incorrect. When it produces an output that's clearly based on a misunderstanding of who the user is or what they want, the interface needs a path for the user to correct it without feeling like they're fighting the system.
Handling context that's wrong. The system's model of the user is always incomplete and sometimes incorrect. When it produces an output that's clearly based on a misunderstanding of who the user is or what they want, the interface needs a path for the user to correct it without feeling like they're fighting the system.
These are not edge cases. They're the central design problems of any product where context shapes content. Solving them requires thinking about the user's relationship with the system over time, not just their experience of a single interaction.
These are not edge cases. They're the central design problems of any product where context shapes content. Solving them requires thinking about the user's relationship with the system over time, not just their experience of a single interaction.
These are not edge cases. They're the central design problems of any product where context shapes content. Solving them requires thinking about the user's relationship with the system over time, not just their experience of a single interaction.
Designing for content that changes without losing the user
Designing for content that changes without losing the user
Designing for content that changes without losing the user
The practical challenge is giving users enough stability to feel oriented in a product whose outputs are inherently variable.
The practical challenge is giving users enough stability to feel oriented in a product whose outputs are inherently variable.
The practical challenge is giving users enough stability to feel oriented in a product whose outputs are inherently variable.
Stable structure compensates for variable content. When the shape of the response is consistent, even if the substance varies, users develop reliable expectations about where to look and how to navigate. The variability becomes legible because it exists within a predictable container.
Stable structure compensates for variable content. When the shape of the response is consistent, even if the substance varies, users develop reliable expectations about where to look and how to navigate. The variability becomes legible because it exists within a predictable container.
Stable structure compensates for variable content. When the shape of the response is consistent, even if the substance varies, users develop reliable expectations about where to look and how to navigate. The variability becomes legible because it exists within a predictable container.
Explicit context signals help users understand why they're seeing what they're seeing. Not always. Not for every output. But at the moments when the personalization is significant enough to be noticeable, a brief signal that explains it turns potential confusion into a demonstration of value.
Explicit context signals help users understand why they're seeing what they're seeing. Not always. Not for every output. But at the moments when the personalization is significant enough to be noticeable, a brief signal that explains it turns potential confusion into a demonstration of value.
Explicit context signals help users understand why they're seeing what they're seeing. Not always. Not for every output. But at the moments when the personalization is significant enough to be noticeable, a brief signal that explains it turns potential confusion into a demonstration of value.
User-accessible context controls give users a sense of agency over their own experience. The ability to see what the system knows about them, correct it when it's wrong, or reset it when they want a fresh start, transforms context from something that happens to them into something they participate in.
User-accessible context controls give users a sense of agency over their own experience. The ability to see what the system knows about them, correct it when it's wrong, or reset it when they want a fresh start, transforms context from something that happens to them into something they participate in.
User-accessible context controls give users a sense of agency over their own experience. The ability to see what the system knows about them, correct it when it's wrong, or reset it when they want a fresh start, transforms context from something that happens to them into something they participate in.
Consistency of voice and tone across variable outputs creates a coherent identity even when the content changes. Users trust systems that feel like the same entity across interactions. A product that sounds different in different contexts feels unstable, regardless of the quality of individual outputs.
Consistency of voice and tone across variable outputs creates a coherent identity even when the content changes. Users trust systems that feel like the same entity across interactions. A product that sounds different in different contexts feels unstable, regardless of the quality of individual outputs.
Consistency of voice and tone across variable outputs creates a coherent identity even when the content changes. Users trust systems that feel like the same entity across interactions. A product that sounds different in different contexts feels unstable, regardless of the quality of individual outputs.
The goal is not to make contextual content feel fixed. It's to make it feel intentional. Users can adapt to variation. What they can't adapt to is variation that feels arbitrary.
The goal is not to make contextual content feel fixed. It's to make it feel intentional. Users can adapt to variation. What they can't adapt to is variation that feels arbitrary.
The goal is not to make contextual content feel fixed. It's to make it feel intentional. Users can adapt to variation. What they can't adapt to is variation that feels arbitrary.
Context as a design asset
Context as a design asset
Context as a design asset
There's a reframe that changes how you approach this entire problem.
There's a reframe that changes how you approach this entire problem.
There's a reframe that changes how you approach this entire problem.
Context is not a technical variable to be managed. It's the richest design asset an AI product has. It's the accumulated understanding of who this user is, what they care about, how they work, and what they need right now. Used well, it makes every interaction more valuable than the one before it. Used poorly, it makes users feel surveilled, confused, or manipulated.
Context is not a technical variable to be managed. It's the richest design asset an AI product has. It's the accumulated understanding of who this user is, what they care about, how they work, and what they need right now. Used well, it makes every interaction more valuable than the one before it. Used poorly, it makes users feel surveilled, confused, or manipulated.
Context is not a technical variable to be managed. It's the richest design asset an AI product has. It's the accumulated understanding of who this user is, what they care about, how they work, and what they need right now. Used well, it makes every interaction more valuable than the one before it. Used poorly, it makes users feel surveilled, confused, or manipulated.
The designer's job is to decide how that asset gets deployed. Which context signals get used in which moments. How explicitly the personalization is surfaced. What the user can see, control, and correct. How the system communicates that it knows the user without making that knowledge feel intrusive.
The designer's job is to decide how that asset gets deployed. Which context signals get used in which moments. How explicitly the personalization is surfaced. What the user can see, control, and correct. How the system communicates that it knows the user without making that knowledge feel intrusive.
The designer's job is to decide how that asset gets deployed. Which context signals get used in which moments. How explicitly the personalization is surfaced. What the user can see, control, and correct. How the system communicates that it knows the user without making that knowledge feel intrusive.
These decisions are not downstream of the product strategy. They are the product strategy, expressed at the level of every individual interaction.
These decisions are not downstream of the product strategy. They are the product strategy, expressed at the level of every individual interaction.
These decisions are not downstream of the product strategy. They are the product strategy, expressed at the level of every individual interaction.
Context is not what the system knows about the user. It's the raw material of the relationship between them. Designing that relationship, deliberately and at every point of contact, is what separates AI products that users trust from AI products that users merely use.
Context is not what the system knows about the user. It's the raw material of the relationship between them. Designing that relationship, deliberately and at every point of contact, is what separates AI products that users trust from AI products that users merely use.
Context is not what the system knows about the user. It's the raw material of the relationship between them. Designing that relationship, deliberately and at every point of contact, is what separates AI products that users trust from AI products that users merely use.
Raphaël D. - Head of Product Design, designing at the intersection of AI infrastructure and human experience.
Raphaël D. - Head of Product Design, designing at the intersection of AI infrastructure and human experience.
Raphaël D. - Head of Product Design, designing at the intersection of AI infrastructure and human experience.
Design for AI
Thinking through the design problems that AI products create.
Not how to use AI as a designer. How to design for it.
© 2026 Design for AI. All rights reserved.
Design for AI
Thinking through the design problems that AI products create. Not how to use AI as a designer. How to design for it.
© 2026 Design for AI. All rights reserved.
Design for AI
Thinking through the design problems that AI products create. Not how to use AI as a designer. How to design for it.
© 2026 Design for AI. All rights reserved.